Skip to content
DeliverBoth sidesChecklist

Final Delivery and Handover Checklist

Use this near final review and again at close-out. Adapt it to the deliverables, acceptance criteria, rights, payment triggers, access plan, and support terms in the actual agreement.

Source: assistedfreelance.com/templates/final-delivery-checklist

Context and limits

Before you use it

  • A checked item should point to evidence, a delivery location, an approval, or a recorded outstanding issue.
  • Never put live passwords, recovery codes, private keys, or unnecessary personal data in the checklist.
  • Confirm ownership and license rights from the actual agreement; possession of a file does not answer every rights question.

Blank reusable version

Copy, edit, and verify.

Final Delivery and Handover Checklist

Deliverables

  • ☐ Every agreed deliverable is listed and available at the recorded location.
  • ☐ File names, formats, versions, and delivery dates are clear.

Acceptance tests

  • ☐ Agreed tests and acceptance criteria have been completed.
  • ☐ Results, approvals, and any exceptions are recorded.

Outstanding items

  • ☐ Every open item has an owner, action, and date—or the record says none remain.

Source and editable files

  • ☐ Agreed source/editable files and production exports are delivered.

Licenses and dependencies

  • ☐ Third-party assets, software, fonts, plugins, services, costs, renewal owners, and use limits are documented.

Documentation

  • ☐ Setup, operation, update, maintenance, and recovery instructions required by the agreement are delivered.

Accounts and access

  • ☐ Organization-owned administrative access and recovery methods are verified through a secure process.
  • ☐ No live credentials are written in this checklist.

Backups

  • ☐ Required backups or exports exist, are stored appropriately, and can be restored as agreed.

Access removal

  • ☐ Temporary access is removed or reduced after handover verification.

Final approval

  • ☐ Acceptance is confirmed in the required written form.

Invoice and payment

  • ☐ Final invoice, payment status, credits, and any recorded outstanding balance match the agreement.

Support or correction period

  • ☐ Agreed duration, included issues, contact method, response expectations, and boundary for new work are recorded.

Portfolio, testimonial, and referral permission

  • ☐ Each permission is requested separately and recorded; no consent is assumed.

Completed fictional example

Harbor Street Bakery website handover

Use this to understand the level of specificity, not as facts, pricing, tax treatment, or agreement wording for your project.

Final Delivery and Handover — Harbor Street Bakery

Fictional educational example · project HSB-WEB-01 · completed December 13, 2026

Deliverables and acceptance

  • ✓ Home, Products, Catering, About, Contact, Wedding Catering, and Corporate Catering pages are live at the recorded address.
  • ✓ The catering inquiry form validates, routes to the designated inbox, and shows its confirmation.
  • ✓ Agreed mobile, desktop, browser, keyboard, and documented accessibility checks passed.
  • ✓ The mobile confirmation defect reported December 4 was corrected and rechecked.
  • ✓ The online-deposit idea remains future scope, not an unfinished deliverable.

Files, licenses, documentation, and backup

  • ✓ Agreed source assets, production exports, analytics handoff, editor update guide, third-party license list, renewal responsibilities, and launch backup are recorded in the bakery’s project folder.

Accounts and access

  • ✓ Sam verified bakery-owned editor and administrative access through the bakery’s secure process. No credentials appear here.
  • ✓ Jordan’s temporary access was reduced after handover verification.

Approval and payment

  • ✓ Sam confirmed final acceptance in writing on December 5.
  • ✓ Final invoice HSB-WEB-01-INV-04 requested $2,000: the $1,400 base handover milestone plus the $600 CR02 acceptance installment.
  • ✓ Sam paid the final invoice on December 12. Total project payments are $6,800 USD: $5,600 base fee plus $1,200 approved change.

Support and permissions

  • ✓ The bounded post-launch correction window and the process for separately quoted new work are recorded.
  • ✓ Portfolio permission was requested and recorded separately. No testimonial or referral permission was assumed.

Field by field

Adapt it deliberately

Deliverables and acceptance
Replace generic checks with the exact outputs and tests from the agreement.
Files and licenses
Name formats, locations, third-party terms, renewal costs, and responsible account owners.
Documentation and backups
Record what the receiving party needs to operate, update, and recover the work.
Access
Verify organization ownership securely, then remove or reduce temporary permissions.
Approval and payment
Use the actual acceptance form, invoice reference, payment term, and outstanding-item record.
Support and permissions
Separate corrections from new work and request portfolio, testimonial, and referral permissions individually.

Important considerations

Common mistakes

  • Do not mark an item complete because it was discussed; link it to evidence or a recorded decision.
  • Do not keep unnecessary access open after the receiving party has verified handover.
  • Do not combine acceptance, payment, portfolio use, testimonial, and future support into one implied approval.