Template text
# [Client name]: [system name] handover document
| Field | Value |
|---|---|
| Project | [project name] |
| Handover date | [YYYY-MM-DD] |
| Version | [1.0] |
| Client contact | [name, role] |
| Implementation lead | [name, role] |
## 1. Project summary
- Scope: [modules and processes delivered]
- Out of scope: [what was deliberately not done]
- Environments: [production, test, training and access URLs]
## 2. Roles and permissions
| Role | Who | Can access | Admin? |
|---|---|---|---|
| [Sales rep] | [people] | [quotes, customer records] | [No] |
| [Finance] | [people] | [invoices, collections] | [No] |
| [System admin] | [people] | [all settings] | [Yes] |
## 3. Daily tasks (user guides)
| Task | Done by | Guide |
|---|---|---|
| [Create a customer record] | [role] | [link] |
| [Build a quote] | [role] | [link] |
| [Enter an order] | [role] | [link] |
| [Issue an invoice] | [role] | [link] |
## 4. Admin tasks
| Task | When | Guide |
|---|---|---|
| [Add a user and assign permissions] | [when someone joins] | [link] |
| [Add a field or list value] | [as needed] | [link] |
| [Back up and restore] | [regularly, checked by the admin] | [link] |
## 5. Integrations
| Connected system | Data flow | If it fails |
|---|---|---|
| [system name] | [direction and frequency] | [whom to tell, what to do] |
## 6. Known limits and next steps
- [What was deliberately not configured]
- [Requests for a later release]
## 7. Support
- Channel: [email, form or phone]
- Include in a request: [user, screenshot (without personal data), what they were trying to do]
- Support scope and duration: [clause from the agreement]
## 8. Acceptance checklist
- [ ] Daily task guides tried with the client team
- [ ] Admin tasks tried with the system administrator
- [ ] Roles and permissions verified
- [ ] Integrations working in production
- [ ] Guide owner named on the client side: [name]
- [ ] Handover date and acceptance: [client name, date]
## 9. Revision history
| Version | Date | Changed by | Change |
|---|---|---|---|
| [1.0] | [YYYY-MM-DD] | [name] | [First handover] |
customer-handover-document.md · A plain Markdown file that opens in any editor.How do you fill in the handover template?
- List the client’s daily tasks first. Which role does which task? Section 3 comes from that list.
- Prepare a guide for each task and add its link. Record in the client’s training or test environment.
- Keep admin tasks apart. Steps ordinary users should not see stay in section 4.
- State the known limits plainly. Things deliberately left out can be mistaken for bugs later.
- Carry the agreement into the support section. Do not leave scope and duration unclear.
- Tick and date the acceptance list with the client. Name the guide owner on the client side.
For the scenario, see ERP and CRM implementation handover. For the roles table, look at the RACI matrix.
How do you fill the daily and admin task sections with Izly?
The setup team records each daily and admin task once in the client’s environment with the Chrome extension; each click becomes a step with a screenshot. Redact real client and employee data after the recording. Add the guides to the tables as links, or download PDFs for the handover folder. The client team reads the guides without needing seats. Only interfaces that run in the browser are recorded. Pricing.
Frequently asked questions
Does the handover document need to be signed by the client?
Whether it is required depends on your agreement. A signed acceptance list can help in a project because it shows when the project was handed over.
Is the template only for ERP and CRM?
No. It adapts to any implementation project, for example accounting, HR or project management software. Replace the example rows with your own system.
Who should update the handover document?
A named owner on the client side. If you offer an update service, write it into the agreement and the support section.
Related pages
Record it once and let the guide write itself
With Izly you do the task once in the browser. Clicks and screenshots become a step-by-step guide that you edit and share by link.