Practical templates
Client Handoff Document Template for Freelancers and Agencies
Give clients a clear route from “the project is delivered” to “we can run this ourselves.” Includes a free, editable Markdown template.
A client handoff document explains what was delivered, who owns it and how to operate it. For a freelancer or agency, the most useful version is a short project overview linked to specific procedures. The client should be able to find tomorrow's task without searching a long email thread.
This guide covers handing a completed project to a client. If you are transferring your job to a colleague, use our separate guide to role handoff documentation.
What belongs in a client handoff?
Start with the decisions a client will face during the first week. What is ready to use? Which account do they need? What should they check after making a change? Who handles a failure? Organize the document around those questions.
| Part | What to include | Completion check |
|---|---|---|
| Delivery summary | Deliverables, locations, scope exclusions and known limitations. | The client can distinguish finished work from open work. |
| Access map | Systems, required roles and who grants access. | The client's named user can sign in successfully. |
| Recurring work | Tasks, triggers, owners and links to procedures. | The client knows what to do next week. |
| Task instructions | Steps, screenshots where useful, expected results and stop conditions. | A reader can complete a representative task. |
| Open issues | Impact, next action, owner and due date. | No unfinished item relies on an unspoken assumption. |
| Support agreement | The agreed contact, scope, period and documentation owner. | Both parties know where a new request belongs. |
Use the support terms you actually agreed with the client. A handoff document records that arrangement; it should not quietly introduce a new warranty, service level or deadline.
Copy or download the client handoff template
Use the Markdown version in a text editor, or copy its headings into your existing document tool. Keep one current version and link to it from the project record.
Download the client handoff template (.md)
# Client handoff
Project / client:
Prepared by:
Client owner and backup:
Version / last verified:
Current documentation location:
## Scope and acceptance
Delivered:
Not included:
Known limitations:
Client acceptance criteria:
Acceptance date and reviewer:
## Access map (no passwords or access tokens)
System | Required role | Access owner | Invitation verified
## Recurring work
Task | Trigger / frequency | SOP link | Expected result | Owner
## Procedure
Purpose:
Prerequisites and approved test data:
Steps:
Expected result and where to verify it:
Stop conditions:
Recovery / escalation contact:
## Open work
Issue | Impact | Next action | Owner | Due date
## Support and maintenance
Support contact and agreed scope:
Support period, if agreed:
Documentation owner:
Next review date:
Access removal / transfer checklist:
## Reader test
Tester and date:
Task completed using client's normal role:
Questions or failures:
Corrections made:
Retest result:
Worked example: handing over a website enquiry workflow
Suppose you built a website and connected its enquiry form to a client's CRM. Sending the website URL is not enough. The client needs to understand the route from a submitted form to a lead someone owns.
Project summary: the new enquiry form creates a lead in the CRM's Website Enquiries view. Automatic email campaigns are outside the delivered scope. The operations manager owns the workflow and a named backup covers absences.
Routine: each working day, the assigned employee opens the view, checks unassigned records and assigns an owner. The SOP links directly to that task and identifies the role the employee needs.
Verification: using an approved test record, submit the form once and confirm a single CRM lead appears with the expected source and assigned owner. Describe where to inspect the result. Remove or label the test record according to the client's process.
Exception: if the form reports success but the CRM record is missing, stop repeated submissions. Record the time and a non-sensitive reference, then escalate to the named integration owner. Repeated submissions can make troubleshooting harder by creating duplicate records once a delay clears.
Acceptance: the client performs that check with their own account while following the document. Note any permission error or unclear step, fix it, and repeat the failed part before marking the handoff complete. This is an illustrative workflow, not a report of a customer result.
Turn the recurring tasks into short SOPs
Make a separate procedure for each task the client will repeat. “Review a new enquiry” and “Change a website form field” have different triggers, permissions and risks. Keeping them separate lets readers find the right guide and makes later updates smaller.
- Prepare a safe demonstration. Use test data and the role the client will actually have. Close unrelated tabs and notifications.
- Capture the task. Show the normal path from the starting screen to a verified result. In Claudia, you can record the browser steps and review them before exporting.
- Add the decisions. Explain how to choose an owner, when to stop and which changes need approval. A recorded click cannot explain a business rule by itself.
- Deliver the right format. Claudia can export a printable guide for PDF or a ZIP with SKILL.md and screenshots. Put the reviewed output in the client's agreed documentation location.
- Check the received copy. Confirm the client can open every file, see the images and reach the linked systems with their own permissions.
Review exported text and screenshots before sharing. Document the access process and responsible person; transfer credentials through the client's approved secure method. Do not put passwords, recovery codes or API keys into the handoff.
Use a reader test to finish the handoff
Ask the future operator to complete one ordinary task and find the instruction for one exception. Let the document do the teaching. Every point where you need to explain something verbally is a candidate for a clearer step.
- The client can locate the current guide without asking the author.
- All required accounts belong to the right organization and have a named owner.
- A normal task produces the documented result.
- The reader can find the stop condition and escalation contact.
- Open issues have an owner and a next action.
- The client knows who updates the guide after a process change.
Record the review date and any remaining exceptions. Confirm account ownership and recovery access before removing a contractor's access. Do not leave a client dependent on a personal email address for a critical service.
Keep the document useful after delivery
Add a short change record: date, affected procedure, reason and reviewer. When a screen changes, update the relevant steps, replace exported copies and repeat the affected reader test. Our SOP version-control guide gives a fuller review process.
For a small project, one overview and a few tested procedures are a sensible starting point. Add documentation when it answers a recurring question or prevents a known error. The target is a client who can operate what you built, with a clear route for the things they cannot yet handle.