# Website project handoff checklist

By cluein.me — https://cluein.me/resources
Version: 2026-10-29. Copy and adapt for your own projects.
This is a workflow checklist, not a contract or legal advice.
Never put passwords, tokens or API keys inside a handoff archive.

## 1. Identify the handoff

- Project:
- Client / organization:
- Prepared by:
- Intended recipient:
- Handoff date:
- Brief version:
- Agreed implementation scope:
- Next milestone:

## 2. Readable brief

- [ ] Project goal and target audience are described.
- [ ] Primary visitor action is identified.
- [ ] Pages and deliverables are listed.
- [ ] Each page has a content owner.
- [ ] Constraints, dependencies and exclusions are recorded.
- [ ] Open decisions are visible rather than silently treated as approved.
- [ ] The receiving designer or developer can read the brief without your tools.

## 3. Asset inventory

| Asset | Archive path / source | Intended use | Current version | Rights evidence location | Ready? |
| --- | --- | --- | --- | --- | --- |
| Logo | | | | | |
| Photographs | | | | | |
| Fonts | | | | | |
| Copy | | | | | |
| Other | | | | | |

- [ ] Filenames describe the content and avoid ambiguous duplicates.
- [ ] Source files are included where agreed and available.
- [ ] Superseded versions are identified or excluded.
- [ ] Permission questions are resolved or listed as open.
- [ ] No credentials or unrelated client files are included.

## 4. Decisions and review

| Deliverable / version | Review status | Reviewer | Date | Comments / next action |
| --- | --- | --- | --- | --- |
| | Pending / changes requested / approved for the next step | | | |
| | | | | |

Record exactly which version was reviewed and what the status means for this
project. Do not imply approval of an entire project from one approved item.

## 5. Open questions

| Question | Effect if unresolved | Owner | Due date | Blocks the next step? |
| --- | --- | --- | --- | --- |
| | | | | |
| | | | | |

## 6. Export acceptance test

- [ ] Download the complete handoff as the intended recipient.
- [ ] Open the archive and confirm it is not corrupt.
- [ ] Read the brief and check non-English characters where relevant.
- [ ] Open a sample of every included file format.
- [ ] Match files against the asset inventory.
- [ ] Check that missing items are clearly marked.
- [ ] Confirm that no files from another project are present.
- [ ] If JSON is supplied, parse it and compare representative values with the readable brief.
- [ ] Record where the final handoff will be retained and who may access it.

## 7. Receipt

- Received by:
- Received on:
- Missing or unreadable material:
- Next owner and next action:

## Inspect a working example

The cluein interactive demo uses a fictional website relaunch. Complete its
three requirements and download a ZIP containing:

- brief.md — readable example answers;
- brief.json — structured example answers;
- assets/sample-logo.svg — fictional logo.

https://cluein.me/demo/client-portal

The demo is a small example, not an export of a real client project.
Current product plans and limits: https://cluein.me/pricing