The work is finished. Your client still needs a clear answer to four questions: What changed? Where is the finished work? What was checked? What do I need to do next? A project handoff should answer those questions without making the client reconstruct the job from a chat thread.
This freelance project handoff checklist gives you a short completion report, an evidence checklist and a copyable delivery email. It works for a small website update, Shopify job, design delivery or research assignment. Use it for one completed job at a time.
The five-minute handoff checklist
- Name the job and its agreed scope. Give the client one recognizable project name. Separate delivery of this job from the health of their entire business or website.
- State the outcome in client language. Say what the client can now do, rather than list every technical task you performed.
- Summarize two to five changes. Keep the full task history in your project records. The handoff needs the changes that matter to the client.
- Link the finished work. Check that the intended recipient can open the destination with their normal access. A working link in your own signed-in session is not enough.
- Attach or link the strongest existing evidence. Explain what each screenshot, result or check establishes, when it was captured, and what it does not establish.
- Name any client action. Give one action, owner and date. If none is needed, say so explicitly.
- Separate remaining work from optional work. An unfinished agreed task, a dependency on the client and a possible future improvement are different things.
- Explain the next contact point. Use the review and support terms already agreed for the job. A handoff is not a new promise of unlimited support.
Write the outcome before the task list
“Updated theme settings, edited Liquid and tested the form” tells the client how you worked. “Your contact form now sends enquiries to the agreed inbox, and the confirmation message explains what happens next” tells them what changed.
Keep the claim as narrow as your checks. If you checked one form, do not describe the whole website as fully tested. If you reviewed a saved export, say that the finding comes from the export rather than a fresh live check.
A completion report you can copy
Job: [Client / project / delivery date]
Status: [Complete / waiting for named client action / agreed task still open]
Outcome: [One sentence describing the useful result]
Delivered:
1. [Change and client benefit]
2. [Change and client benefit]
3. [Change and client benefit]Open the finished work: [Destination and access instructions]
Checked: [Check, date, source and observed result]
Your next action: [Action, owner and agreed date — or “None required”]
Remaining: [Unfinished agreed work, if any]
Optional / outside this job: [Future improvements and exclusions]
Review / support: [Existing agreed terms and contact point]
Keep the client-facing summary short enough to read in one sitting. Put detailed evidence in a second page or appendix so it supports the message without obscuring it.
Choose evidence that matches the claim
A screenshot proves what was visible in that capture. A test result supports the behavior covered by that test. A record from your project notes is a reported result. None of those automatically proves successful checkout, email delivery, search indexing or every device layout.
- Before / after: use comparable views of the same item where possible. Label the date and context.
- Check result: state the input, scope and observed outcome. “Three links opened” is clearer than “Everything works.”
- Source: distinguish a check you performed from an existing result supplied by someone else.
- Limitation: name important behavior you did not check. An honest limit makes the evidence easier to use.
Do not turn different counts into a success story. For example, an earlier scan with 20 statuses and a later scan with 14 may have different scopes. That does not establish that six problems were fixed.
Protect access and client information
Use invitations or the client’s existing access process for credentials. Do not place passwords, recovery codes or API keys in the report. Before sharing screenshots, remove customer details, private messages, billing information and other material the recipient does not need.
Redact the actual file content, rather than cover it with a removable shape. Check the exported file and its selectable text. For a public portfolio example, get the client’s permission or use your own project, label it honestly, and remove identifying details.
What if something is still open?
Use a small action list with an owner and a next step. “Client to provide approved copy; final upload is waiting on that input” is useful. “Nearly done” is not.
Separate an open finding from unfinished delivery. A completed audit can identify a broken link; fixing that link may be outside the audit’s scope. A completed release can still have a documented limitation. State both without implying that you performed extra work.
If the original job requires formal acceptance, follow that agreement. Sending a completion report by itself does not establish acceptance, payment entitlement or resolution of a dispute.
A client handoff email you can copy
Subject: [Project] — delivery and next steps
Hi [Name],
[Job] is [status]. You can now [specific outcome].
Finished work: [link]. The attached completion report lists the main changes, the checks recorded and the scope limits.
Your next action: [one action / none required]. [Any remaining dependency and owner.]
Please use [agreed review process] for factual corrections or questions. Additional work can be scoped separately.
Thanks,
[Name]
See a real two-page example
The redacted ProofPack sample shows this structure on HCR Digital Works’ own completed project: a readable handoff first, then evidence and limits. It is a work sample, not a customer testimonial or a promise of results for your project.
If you prefer help preparing a report from your existing notes and proof, choose a C$39 ProofPack for one completed job. Keep access details and private client material out of your initial fit enquiry.
Keep the next project organized
For the broader workflow, read what to track in a freelancer client-management spreadsheet. The Freelancer Client Ops Dashboard supports leads, onboarding, projects, invoices and follow-ups. It complements the final handoff rather than replacing your project records.
For website delivery, use the website launch QA checklist to organize the checks before you declare the job complete. If you need a different tool or service, Start Here maps common problems to useful first steps.