IT Handover Document Template
Lay out everything that has to move, colour each item by status, and keep the evidence and sign-off behind every item.
Free forever on the Personal plan
IT handovers: an example
Everything that moves
Access, contracts, documents and knowledge, grouped on one page.
Status at a glance
Done, in progress and not started, so both sides know what is left.
Evidence and sign-off
Each item records what moved, the proof, and who signed for it.
The basics
What is an IT handover document?
An IT handover document lists everything that must move when responsibility for IT changes hands, for example from an MSP to a new provider or an in-house team: admin access and credentials, contracts and licences, documentation and runbooks, open work, and the knowledge only the outgoing team has.
Handovers fail on the items nobody listed: a domain registered in the wrong name, a vendor login one engineer knew, a backup nobody was told to keep running. A handover pack the receiving team can open and check, with a status on every item, closes those gaps.
In Blueprintr the handover pack is a diagram with each item coloured by status, and each item's stratum records what moves, the evidence and who signed for it.
Why Blueprintr
Handovers that leave nothing behind
The pack on one page, the evidence behind every item.
The handover on one page
Group every item that moves, colour it by status and add a key, so both sides read the state of the handover in seconds.
VellumEvidence behind each item
Give every item a stratum with what moves, how it was checked, the date and who signed for it.
StratumChecked by the receiver
Share the pack and the client's documentation privately with the receiving team, so they confirm each item themselves.
BlueprintsMove the documentation
If you administer both workspaces, moving a blueprint into the client's workspace transfers it, and its old links redirect.
A copy they can keep
Export blueprints as zips of diagrams, markdown and strata, and on the Team plan print a documentation site to PDF from the browser.
FoliumThe same pack every time
Save the handover pack as a template, so no client's handover forgets the domain or the backup again.
How to
How to plan an IT handover in Blueprintr
Create a blueprint
Sign up free and create a private blueprint for the handover.
List everything that moves
Add an item for each account, contract, document and walkthrough, grouped by kind.
Colour by status
Mark each item done, in progress or not started, and add a key beside the pack.
Record the evidence
Right-click each item and add a stratum with what moved, how it was checked and who signed.
Sign off together
Share the pack with the receiver and walk through it on handover day.
FAQ
Questions about it handovers
Is this IT handover template free?
Yes. The Vellum editor, strata and blueprint export are on the free Personal plan. Teams per client and documentation sites are part of the Team plan.
What should an IT handover checklist include?
Admin accounts and credentials, domains and certificates, contracts and licences, documentation and runbooks, open tickets, walkthroughs of unusual systems, and what the outgoing provider keeps.
How do I hand over passwords safely?
Never put them in the handover document. Share them through a password manager, have the receiver sign in and change each one, and record in the stratum the vault entry and the date it was rotated.
Can I transfer documentation to the client in Blueprintr?
Yes, if you are an owner or admin of both workspaces: moving a blueprint into a portfolio the client's workspace owns transfers it. Otherwise, share it privately or export it.
Can the client keep the documentation if they leave Blueprintr?
Yes. A blueprint exports as a zip with a README, its diagrams in their native formats, rich text as markdown and every stratum, so nothing is locked in.
Who signs off an IT handover?
Usually the person taking over IT and someone at the client with authority, such as a director. Record both names and the date in the sign-off item's stratum.