What documents should a consultant hand over at the end of a project?
You should receive seven things: a written scope record, a plain-words description of what was built, the admin and ownership list, the test results, a how-to guide for your team, a list of open issues, and a signed sign-off page. Put them in the contract before work starts.
What should be on the handover list?
- Scope record: what you asked for, what was built, and what was left out on purpose.
- Build description: each app, form, flow or site in plain words, with its name and where it lives.
- Ownership list: who owns each item, and which admin role each person holds.
- Test results: what was checked, by whom, and the date.
- Team guide: the steps your staff follow each day, with screenshots from your own system.
- Open issues: known problems, with a name and a date next to each.
- Sign-off page: a one-page record that you accepted the work.
Why do key documents go missing at the end?
Most often, the contract said nothing about them. A project that lists only the build, such as a tracker or a form, leaves documents as an extra. When the budget runs short, the extra is the first item cut.
The fix is to name each document as a deliverable, with the same weight as the build itself. Then a missing document is a missing deliverable, and the final payment waits for it.
What does a good scope record look like?
Requested: a request form for the front desk.
Built: the request form, a status view, and an email to the manager.
Not built, on purpose: a monthly report. Moved to phase 2 on 12 March.
Changed during the project: the approver is now the office lead, not the owner. Agreed by email on 4 March.
Keep it to one page. The goal is that a person who joins in a year can read it and know why the system looks the way it does.
Who should own which document?
| Document | Consultant writes it | You review it |
|---|---|---|
| Scope record | Yes, kept up to date during the project | At each change |
| Build description | Yes | Before sign-off |
| Ownership list | Drafts it | You fill in the names |
| Test results | Yes | You confirm the key cases |
| Team guide | Yes | A staff member follows it once |
| Open issues | Yes | You rank them |
| Sign-off page | Drafts it | You sign it |
How do you avoid reviewing documents over and over?
- Agree the document list and its outline on day one.
- Set one review date for each document, not a review whenever you ask.
- Give feedback in one round, in one place, from one named person.
- Let the consultant fix the points and mark the document as final.
- Treat later changes as a change request, with a date and a decision.
A single named reviewer matters most. When three people each ask for a different edit, the same document returns three times. Our guide on a RACI chart in Microsoft 365 shows how to name who decides.
What is the ownership list, and why does it matter?
It records who can manage each part of your system. Microsoft 365 uses admin roles to grant that access, so the list should name each person and their role. See the Microsoft Learn page on admin roles for the role names.
Check that at least two people on your side hold an admin role before the consultant leaves. A system with one admin, who is the consultant, is hard to take over.
Tip: Ask for the ownership list a week before the end, while the consultant can still answer questions.
What if the work changes in the middle?
Write the change down when it happens. A short log with the date, the request, the effect on cost and time, and the decision keeps a fixed price project from turning into an argument. See change request log for a way to keep it.
At the end, the scope record and the change log together explain every difference between the first quote and the final build.
How do you ask for this in the contract?
Deliverables include the following documents, in editable form: scope record, build description, ownership list, test results, team guide, open issues list. Final payment is due after the client signs the acceptance page.
Use your own words if you prefer. Keep the list of named documents and the link to final payment. Ask a lawyer to check any contract wording before you sign.
Want help with this?
250 High Street is an independent consultancy run by Al Davies. If you want a handover pack written into your next project, read about us first. We scope the documents with the build. See also our guide on onboarding checklists for the start of a project.
FAQ
Is documentation part of a normal consulting project?
Only if the contract says so. Name each document as a deliverable so it is not treated as an extra.
How long should handover documents be?
As short as the content allows. A scope record fits one page. A team guide needs only the steps your staff follow.
Who should hold admin access when the project ends?
At least two people on your side. Do not leave the consultant as the only admin.
Can I hold back final payment until I have the documents?
If the contract links final payment to the documents and the sign-off page, yes. Agree this before work starts.