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.

Copying and downloading happen in this browser. AssistedFreelance does not receive or save the template.

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

## Deliverables
- [x] Home, Products, Catering, About, and Contact pages plus the catering inquiry form are live at the recorded site address.
- [x] Final source assets, exports, and the update guide are stored in the bakery’s project folder.

## Acceptance tests
- [x] Approved content, navigation, links, form routing and confirmation, agreed mobile/desktop/browser checks, keyboard checks, and documented accessibility checks passed.

## Outstanding items
- [x] No outstanding items. The optional online-deposit idea is recorded as future scope, not an unfinished deliverable.

## Source and editable files
- [x] Agreed source assets and production exports were delivered in the recorded formats.

## Licenses and dependencies
- [x] Hosting, analytics, fonts, plugins, renewal responsibility, and third-party terms are listed. Sam verified which accounts belong to the bakery.

## Documentation
- [x] Editor update guide and analytics handoff notes were delivered.

## Accounts and access
- [x] Sam verified bakery-owned editor and administrative access using the bakery’s secure process. No credentials appear here.

## Backups
- [x] A launch backup was created and its storage and restoration responsibility were recorded.

## Access removal
- [x] Jordan’s temporary access was reduced after Sam verified handover.

## Final approval
- [x] Sam confirmed acceptance in writing on the recorded date.

## Invoice and payment
- [x] The fictional $1,400 final milestone invoice was received and processed under the agreed term.

## Support or correction period
- [x] The bounded post-launch correction window and the process for separately quoted new work are recorded.

## Portfolio, testimonial, and referral permission
- [x] Portfolio permission was requested 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.