Project Handover Form

What this document is

Projects rarely end with a ceremony — they trail off in a last email with attachments, and that vagueness is where final payments go to die. A project handover form closes the project formally: it lists every deliverable handed over, every password and account transferred, notes anything still outstanding, and carries the client's signature confirming acceptance. From that moment, 'you never delivered X' stops being an available argument.

For freelancers and small agencies, the form has a very practical second function: most contracts make the final payment due on completion, and the handover form is the dated evidence that completion happened. It also protects the client — they get a checklist of everything they now own and control, which matters months later when they need a source file or a login and the freelancer has moved on.

When to use it

• A design, development, or construction project is finished and the final invoice depends on proving completion.
• You are transferring accounts, domains, hosting, or admin passwords and want a signed record of what was handed to whom.
• The client accepted the work in a meeting and you want that acceptance captured on paper the same day.
• A project ends early by agreement and both sides need a record of what was delivered up to that point.
• You are the client and want a complete inventory of files, credentials, and licenses before the freelancer's involvement ends.

When not to use it

• Deliveries of physical goods against a purchase order — the delivery confirmation is built for that.
• Mid-project milestone sign-offs; use a short written approval per milestone and keep the handover form for the true end.
• Handovers of rented property — the move-out checklist covers condition and keys properly.
• Disputed projects where the client refuses to accept the work; a handover form signed under protest helps no one — document what was delivered and take advice.

Information you will need

• Project name and the contract or scope of work it completes
• Names of the provider and the client representative signing off
• Every deliverable handed over: files, formats, quantities, physical items
• Accounts, credentials, domains, or licenses transferred, and where they were sent
• Anything outstanding, with an owner and a date for each item
• Any support or fix-it period that applies after handover
• The handover date
• Confirmation of the final amount now due, referencing the final invoice

Clauses included

How to sign it

Walk through the list together — in person or on a call with the document on screen — ticking each item before signing. Five minutes of joint checking prevents the awkward week-later message about a missing file.

If handover happens remotely, send the form with the deliverables, ask the client to sign and return it, and keep the sending email. A client who uses the deliverables but never returns the form is weaker ground — chase the signature while goodwill is high.

Attach or merge the signed form with the final invoice and keep them together. That pair — accepted handover plus invoice — is the strongest possible footing if the last payment needs chasing.

Common mistakes

• Sending final files scattered across emails and chats with no consolidated list anyone signed.
• Handing over all source files and passwords before the final payment is settled, removing your last leverage.
• Letting one small unfinished item delay acceptance of the entire project instead of noting it on the snag list.
• Forgetting credentials in the list — the client discovers at renewal time that the domain sits in your account.
• No support window defined, so every future bug report arrives as an unpaid obligation.
• Getting a verbal 'all good!' in the meeting and never collecting the signature.

Frequently asked questions