CLIENT HANDOVER / WORKSHEET

Client handover checklist

A plain-English worksheet for understanding a completed admin automation: what starts it, what it does, what it needs, and what to do when something changes.

01 / CLIENT NOTES

What does it do?

Describe the agreed process in everyday words.

Name of this automation or process

Date these notes were reviewed

What starts it?

What steps does it carry out, in order?

What result should you expect, and where should it appear?

Which steps need a person’s judgment, approval, or review?

I checked this section against the handover agreed for my project.

02 / CLIENT NOTES

What does it need?

List each input and the access it relies on.

Add one row for each required input. Record the account and permission needed, never a password or secret.

Required input 1

What input is needed?

Where does it come from?

What format is expected?

What account access or permission is needed?

I checked this section against the handover agreed for my project.

03 / CLIENT NOTES

What if something goes wrong?

Write down safe next steps before you need them.

These are general examples, not claims about a particular project. Follow the agreed safe manual fallback. If no safe next step is documented, pause and seek help rather than guess or retry blindly.

If an input is missing or incomplete, what is the safe next step?

If an unexpected case appears, what should you do?

If processing is duplicated or delayed, what should you check before retrying?

If a connected tool is unavailable, what is the safe fallback or pause point?

Where can you find the agreed manual fallback or pause instructions?

I checked this section against the handover agreed for my project.

04 / CLIENT NOTES

How will you keep it dependable?

Record the checks and review rhythm agreed for this automation.

Which required access should you confirm is still available?

How will you check that outputs still match expectations?

What notes should be updated if the process, inputs, or connected tools change?

What review frequency was agreed for this automation?

I checked this section against the handover agreed for my project.

05 / CLIENT NOTES

When should you seek help?

Keep the agreed escalation route easy to find.

Keep these help triggers with your notes:

Seek help if failures happen repeatedly.
Seek help if the result is unexpected.
Seek help if account access or process rules change.
Pause and seek help if there is no documented safe next step.

What support contact or route was agreed for your project?

Support arrangements and response times depend on the agreed scope. This worksheet does not set or promise them.

I checked this section against the handover agreed for my project.

Your entries are stored in this browser on this device. They are not sent to Clubwolf-Freelance. Avoid passwords and private client details; use the secure method agreed for your project when sharing notes.

Need to check what a handover includes?

Read the FAQ about handover scope