A useful project handoff separates delivered work from decisions that are still open. Use this free worksheet to record what you are sharing, where it lives and what needs a follow-up.
Copy it into your usual notes or spreadsheet. It works on its own. It does not transfer file access, send messages, collect a signature or confirm that a client accepted the work.
Copy this handoff record
Project: [project name]
Prepared on: [date]
Agreed delivery: [short description of the agreed work]
Repeat these six fields for each deliverable:
Deliverable: [what is being handed over]
Where to find it: [folder or file location]
Responsible person: [role or agreed contact]
Handoff status: [ready to share / shared / access checked / needs follow-up]
Follow-up action: [next action, or none recorded]
Due date: [date agreed for that action, or not agreed]
A status is a record you maintain. Check the actual sharing permission independently. Keep passwords and access tokens out of the worksheet; share credentials through your established secure method.
Fictional example: a five-page website
The project covers five website pages and a logo export set. The client has also asked about a separate journal page. All names, locations and dates below are fictional.
Deliverable: Five website pages
Where to find it: Project folder / Final pages
Responsible person: Project lead
Handoff status: Shared
Follow-up action: Ask the recipient to confirm access through the normal project channel
Due date: 15 October 2026
Deliverable: Logo export set
Where to find it: Project folder / Brand assets
Responsible person: Designer
Handoff status: Access checked
Follow-up action: None recorded
Due date: 15 October 2026
Deliverable: Journal page request
Where to find it: Separate change-request record
Responsible person: Project lead
Handoff status: Needs follow-up
Follow-up action: Confirm scope and decision before treating it as an agreed deliverable
Due date: 16 October 2026
Before you call the handoff complete
Review every open follow-up. Check that the intended recipient can access the files you meant to share, and keep their actual confirmation with your project records. Keep the journal-page request separate from the agreed five-page delivery until its scope and decision are settled.
Save an editable copy of your record and check that it opens. A printed summary is useful for review, but it may be harder to update later.
When extra requests need their own record
The free scope-change example and worksheet shows how to estimate extra work before starting it.
If you want a local browser tool for that task, Scope Change Desk keeps the agreed baseline and change requests together, with separate proposed and recorded-approved totals and editable JSON backups. The delivered version costs $19 once. It does not collect client sign-off, transfer files or manage access. The handoff worksheet above is separate; the paid app does not include a handoff module.
Explore the other free examples and worksheets.