The contractor has finished and moved on, and now you need to change one small thing. You click "forgot password," and the reset link goes to an inbox that isn't yours.
That's usually the moment people go looking for a project handover checklist.
This one is for the business owner on the receiving end. You brought in a freelancer, a contractor, or an agency, and you want to know what should be in your hands when they finish.
Most of what goes wrong at a handover was settled at the start, or never settled at all.
The time to ask for your logins, your documents, and the know-how is before anyone starts.
Still deciding who should run the work at all? Start with how to delegate a project, not just the tasks.
Decide how the work will end, now or along the way
What you need back depends on how the work ends. Outside work can end in three ways, and each one changes the list.
If your outside help finishes the work and hands it over, you get everything on the list on an agreed date. If they keep running it until you say your people are ready, they hand it over later. You'll need a written description of what "ready" means, so both sides know when that day has arrived. And if they run it for good because you never want it back, they hand nothing over at all. The list still matters then. It describes what you keep hold of instead of what they hand back, and there's a section on that below.
Any of the three can be the right one. Then agree when the handover happens, and tell everyone involved. Plan it from the beginning, while the people doing the work still remember why they did it that way. By the last week, everyone's attention has moved on to the next thing, the contractor's and yours. If your focus tends to leave the moment the interesting part is done, whatever the reason, you already know how that goes.
Not sure which end you want yet? That's fine. You can decide along the way. Agree when you'll come back to it, so you both make the choice while it's still an easy conversation.
Name one person on your side to receive the handover
If the handover goes to "the team," nobody in particular checks it. So pick one person and write their name down.
That person has three jobs:
- checking that everything on the list arrived,
- making the call when something is unclear, so questions don't wait for a meeting, and
- knowing who to contact on each side once the work is done.
From then on, they own the documents and the accounts. If the work keeps running, they own the relationship instead, and they're the one at the check-ins. It can be you. The point is that it's a name on paper, and nobody has to guess.
Every account and login should be in your name, with admin access
This is the item behind the forgot-password moment. Every account and tool used for the work should be yours, set up in your name with your own login. That goes double for your domains. Where the work runs on someone else's platform, you should still have your own account on it, one you can take with you without asking anyone's permission.
Ask for admin access too. A user login lets you use the thing. Admin access lets you add and remove people, change the settings, and decide what happens to it next.
Then ask for a list of every account the work touches, what each one is for, and where it lives. Without the list, you find the missing ones on the day you need them. If test or shared accounts were used along the way, ask for any personal data in them to be cleared out before the handover.
Better still, have the accounts set up in your name from day one. Then there's nothing to transfer at the end and nothing to forget to transfer. You can also see the work while it's being built, instead of meeting it for the first time at the finish.
Get documents you could run the work from, plus a walk-through
"It's all documented" means something you can test. Could someone on your side with a basic grasp of the work pick up the document and follow it, with nobody looking over their shoulder? That's the bar the US EPA sets in its guidance on writing standard operating procedures. It works for an office as well as it does for a lab.
The documents should cover the written processes, what was built, and how it's set up. They should also cover the decisions behind it, so the next person doesn't undo something for a reason they never heard. Anything unfinished belongs in writing too: open issues, known risks, and the assumptions the work depends on. A risk mentioned once on a call is gone by the following week.
Relevant beats thick. A stack of manuals padded out to look thorough is harder to use than five pages that cover your work and nothing else.
Documents carry the steps, and the reasons behind them travel better in a conversation. So ask for walk-throughs or training with your own people in the room, before the handover is done. That way they can ask their questions while someone is still there to answer them. If the processes are being written as the work goes, how to document business processes while the work is getting done shows how.
The project handover checklist: what should end up in your hands
Everything above, in one list you can copy and work through.
Before work starts
Agree these now, while the end is still an easy conversation.
- How the work will end (finished and handed over, run until you're ready to take it in-house, or run for good), or when you'll decide
- What they'll hand back to you, or what they'll keep running
- When the handover happens, agreed and shared with everyone involved
- One named person on your side to receive it
Access
This is what lets you log in, change anything, and leave on your own terms.
- Every account and tool used for the work is in your name
- Admin access to every account
- A list of every account, what it's for, and where it lives
- Personal data cleared out of test and shared accounts
Documents
With these, someone on your side can run the work without calling whoever built it.
- Written processes someone on your side could follow without supervision
- What was built, how it's set up, and why
- Open issues, known risks, and assumptions, in writing
Know-how
Your people get their questions answered while someone is still there to answer them.
- Walk-throughs or training, with your own people taking part, before the handover is done
Closing it
It's on record that everything arrived, so nothing rests on anyone's memory.
- A written handover summary with the key links, kept as the formal record
- Your named receiver confirms in writing that everything on this list arrived
If outside help keeps running the work, you still own the accounts and documents
The list above reads like a hand-back. If the work runs until you're ready for it, or runs for good, nearly all of it still applies. It just never stops applying.
The accounts are in your name from now on, with no handover to wait for. The processes are written down, and they change when the work changes. The EPA's guidance makes the case for this. Written procedures are what keep work consistent through "temporary or permanent personnel changes," and a change in who runs your work is one of those.
Agree the check-ins up front, so you can see how it's running without chasing anybody. If the goal is to bring the work in-house one day, write down what "ready" will look like.
When you hold all of this, running something for good is a choice you can change later. If you ever want the work back, or want someone else to run it, most of that handover is already done.
Agree the list early, while it's still easy to ask for
Every item on this list is easy to agree at the start. Once the last invoice is paid, each one becomes a favor you have to ask for.
I want my own businesses to follow my own advice, and in them I follow this same list. On a Sparkitive project, if you take the work back, we pass it to your people with the processes ready to run. If you'd rather we finish it or keep running it, you can decide that up front or along the way. You own what we build, and every account is set up under your own login.
Want us to run a project for you, with this whole list agreed before we start? We can go through it on a free 30-minute discovery call. You'll get straight answers and no sales pitch, and the checklist is yours to use either way.
