# Project handover

## Purpose and scope

Describe the project and the task this handover supports.

## Authoritative locations

Record where the current files and documentation live. Distinguish individual
working copies, shared project files and approved outputs.

## File structure and identity

Describe the folders, naming/version conventions and relevant file formats.
Explain which material is original, derived or an output. Preserve identifiers
and units when describing data.

## Documentation

Locate the README, data dictionary, methods notes and source-linked decisions.
Explain any categories, missing-value codes or transformations a colleague needs
to understand.

## Access and responsibilities

Identify the owner, who should have access and who maintains the work. Record
unresolved permission questions rather than assuming access can be granted.

## Checks and limitations

Record what was checked, how it was checked and what remains unverified. Explain
how a colleague could repeat an important check.

## Retention and reuse

Record agreed retention, preservation and reuse conditions. If these are not
settled, identify the person or service that can advise.

## Next action

Name one action, its owner and when it will be reviewed.