# Delivery and handover checklist

Use for any business system, whether adopted, adapted or built from scratch. Mark each item complete, not applicable or open with an owner and next step. A checked box should point to an actual demonstration, document or agreed decision.

Project:

System / delivered version:

Partner implementer:

Client sponsor:

Client administrator:

Review date:

## Scope and acceptance

- [ ] Record the starting system or new-build scope and the changes delivered.
- [ ] Demonstrate the agreed first process with representative employees.
- [ ] Demonstrate the agreed exception and restricted-action cases.
- [ ] Record acceptance results, open issues and deferred requirements.
- [ ] Obtain the sponsor's decision on delivery and the go-live step.

## Data, permissions and integrations

- [ ] Reconcile imported record counts and relevant totals against the source.
- [ ] Check required relationships, matching rules and duplicate handling.
- [ ] Confirm each role can perform its agreed actions and cannot access restricted records or fields.
- [ ] Confirm the client administrator controls access decisions and can manage the agreed workspace settings.
- [ ] Record integration owners, failure handling and recovery steps.
- [ ] Remove or reduce temporary partner and agent access as agreed with the client.

## Reviewed changes

- [ ] Record the system and builder skills used with Proto, where applicable.
- [ ] Review changes to records, permissions, workflows and integrations before applying them to the client's working environment.
- [ ] Keep a record of approved changes and the delivered configuration.
- [ ] Agree how to recover if the go-live step fails, using capabilities confirmed for this system.

## Employee guidance and administration

- [ ] Provide short instructions for the tasks employees actually perform.
- [ ] Show the client administrator the agreed access and configuration responsibilities.
- [ ] Provide process notes, data mappings and known limitations without passwords or API keys.
- [ ] Confirm who manages business data and how the client can use available export or recovery functions.

## Ongoing service

- [ ] Record what the partner will maintain and what the client will own operationally.
- [ ] Name the support route, escalation owner and follow-up review date.
- [ ] Agree how improvements, releases and scope changes are requested and approved.
- [ ] Confirm the client has received the documents and access needed to operate the accepted scope.

## Closeout record

- Accepted scope and evidence:
- Open items, owners and next steps:
- Sponsor decision and date:
- Client administrator acknowledgement:
- Next review: