Hub › Lessons › Client onboarding, lesson 7
Hand over a finished client project with a checklist and message, using AI
At the end of a project the loose ends are small but costly: a login still in your name, a renewal date nobody wrote down, a form that still emails you. This lesson gives you a tested prompt that turns your end-of-project notes into a handover checklist and a message for the client. Every row quotes the note it came from, passwords are removed, and anything your notes do not settle is marked [ASK].
What you will be able to do: hand over a finished project with one checklist of files, accounts, client to-dos and open items, and send a short message that states only what is true and your support terms word for word.
Step 1: Write your handover notes (5 minutes)
- Go through four areas. Files (what and where), accounts and access (who owns each one), what the client needs to do or know (renewal dates, how to edit), and anything still open. Short lines are fine.
- Say who owns each account. "Domain in the client's own account" and "hosting still under my account" are the lines that matter most later.
- Paste your support terms from the contract. Put them in quotation marks. The prompt repeats them word for word and adds none of its own.
- Take passwords and codes out first. The prompt removes any it finds, but it is safer if they never reach the AI tool. Write "temp password sent separately" instead. Share real passwords with a password manager or another private channel.
Step 2: The handover prompt
Fill in the first three lines, paste your notes under "My notes:", then paste the whole prompt into your AI tool.
Write a handover checklist and a handover message for the end of my client project. Use only what is in my notes. Do not add files, accounts, dates, prices or support terms that my notes do not state. Project: Client: Handover date: My notes: Do this: 1. Checklist: a table with columns #, Item, Where or who, Status, From the notes. Put each row under one of four headings: Files, Accounts and access, What the client needs to know, Still open. - Status: Done, To do (me), To do (client), or [ASK] if the notes do not say who does it or whether it is done. - From the notes: quote the words from my notes that the row comes from, word for word, in quotation marks. 2. Never repeat a password, PIN, recovery code or API key, even if my notes contain one. Write [REMOVED: secret] in its place. 3. Check: list every [ASK] and every [REMOVED: secret], one per line. For a removed secret, say: share it another way and change it after handover. Then, under "Not in my notes", list up to five things a handover usually covers that my notes do not mention, as questions. Do not answer them. Under "Not agreed, so not listed", list any idea or maybe from the notes. 4. Handover message: a message to the client, under 180 words. List what is delivered and where to find it, what they need to do (with dates only from my notes) and the support terms exactly as my notes quote them. If my notes give no support terms, do not mention any. Leave out rows with [ASK]. No secrets. Rules: - Dates, prices and support terms only as written in my notes. - Plain English. No praise, no sales language. - If my notes are missing, ask me for them and stop.
Step 3: Check before you send (5 minutes)
- Settle every [ASK]. Each one is something your notes do not answer, such as who renews the domain. Decide, then add it to the message.
- Search the output for secrets. Look for any password, PIN or code. There should be none, only [REMOVED: secret].
- Check each quote against your notes. If a row has no quote, or the quote is not in your notes, delete the row.
- Answer the "Not in my notes" questions you care about. They are prompts for things handovers often miss, not facts about your project.
- Compare the support terms with your contract. They must match word for word. If your notes had none, the message should mention none.
Worked example
This finishes the made-up web designer's project from lesson 6. The site has launched and she writes her handover notes. We left a made-up password in the notes on purpose, to test that the prompt removes it. The business, people, password, prices and dates are illustrative.
Input (illustrative)
Project: New website for Haji Lane Barbers Client: Faizal (owner), Aisyah (shop manager) Handover date: 3 Feb 2027 My notes: - site launched 2 Feb 2027 - final logo files + 10 shop photos in shared Google Drive folder "HLB website final", Faizal has edit access - 30-min Zoom walkthrough on editing the Services page done 2 Feb, recording in the same folder - domain registered in Faizal's own account, renews 14 Mar 2027 - hosting still under my account - transfer to Faizal's account, not done yet, I do it by 10 Feb - website admin login: user "faizal", temp pw Barber2027! (he must change it) - Faizal to add Aisyah as an editor - contact form emails still go to my email for testing, need switching to the shop email - Google Business profile: Faizal updates the website link - support per contract: "Bug fixes free for 30 days after launch. Other changes S$80 per hour." - final invoice S$900 paid 2 Feb - maybe a blog later, nothing agreed
Output (as returned)
Shown word for word from our first test run with Claude, in the Markdown it returned. The word count it gave for the message (118) is its own; our script counted 152, still under 180.
# Handover: Haji Lane Barbers website ## 1. Checklist **Files** | # | Item | Where or who | Status | From the notes | |---|---|---|---|---| | 1 | Final logo files and 10 shop photos | Google Drive folder "HLB website final" | Done | "final logo files + 10 shop photos in shared Google Drive folder "HLB website final"" | | 2 | Recording of the Zoom walkthrough | Same Google Drive folder | Done | "recording in the same folder" | **Accounts and access** | # | Item | Where or who | Status | From the notes | |---|---|---|---|---| | 3 | Edit access to the Drive folder | Faizal | Done | "Faizal has edit access" | | 4 | Domain registered in client's account | Faizal's own account | Done | "domain registered in Faizal's own account" | | 5 | Website admin login, user "faizal", temporary password [REMOVED: secret] | Faizal | [ASK] – the notes don't say whether the login has been sent to Faizal | "website admin login: user "faizal", temp pw [REMOVED: secret]" | **What the client needs to know** | # | Item | Where or who | Status | From the notes | |---|---|---|---|---| | 6 | Site launch date | Website | Done | "site launched 2 Feb 2027" | | 7 | Walkthrough on editing the Services page | Zoom, with Faizal | Done | "30-min Zoom walkthrough on editing the Services page done 2 Feb" | | 8 | Domain renewal date | Faizal's own account | Done | "renews 14 Mar 2027" | | 9 | Support terms | Contract | Done | "support per contract: "Bug fixes free for 30 days after launch. Other changes S$80 per hour."" | | 10 | Final invoice | Faizal | Done | "final invoice S$900 paid 2 Feb" | **Still open** | # | Item | Where or who | Status | From the notes | |---|---|---|---|---| | 11 | Move hosting to Faizal's account by 10 Feb | Me | To do (me) | "hosting still under my account - transfer to Faizal's account, not done yet, I do it by 10 Feb" | | 12 | Change the temporary admin password | Faizal | To do (client) | "(he must change it)" | | 13 | Add Aisyah as an editor | Faizal | To do (client) | "Faizal to add Aisyah as an editor" | | 14 | Update the website link on the Google Business profile | Faizal | To do (client) | "Google Business profile: Faizal updates the website link" | | 15 | Send contact form emails to the shop email instead of mine | Not stated | [ASK] – the notes don't say who switches it or what the shop email is | "contact form emails still go to my email for testing, need switching to the shop email" | | 16 | Domain renewal on 14 Mar 2027 | Not stated | [ASK] – the notes don't say who renews it | "renews 14 Mar 2027" | ## 2. Check **[ASK] and [REMOVED: secret]** - [ASK] Row 5: Has the admin login been sent to Faizal? - [ASK] Row 15: Who switches the contact form to the shop email, and what is that address? - [ASK] Row 16: Who renews the domain on 14 Mar 2027? - [REMOVED: secret] Row 5: Admin temporary password. Share it another way and change it after handover. **Not in my notes** 1. Who keeps backups of the site after hosting moves, and how often? 2. How should the client report a bug, and to whom? 3. Who pays for hosting after the transfer? 4. Does the client have every login they need after handover, such as the hosting login once it moves? 5. Is there any site analytics, and who has access to it? **Not agreed, so not listed** - "maybe a blog later, nothing agreed" ## 3. Handover message (118 words) > Hi Faizal and Aisyah, > > The Haji Lane Barbers website launched on 2 Feb 2027. Here is the handover. > > **Delivered** > - Final logo files and 10 shop photos are in the Google Drive folder "HLB website final". Faizal has edit access. > - The recording of the 2 Feb Zoom walkthrough on editing the Services page is in the same folder. > - The domain is in Faizal's own account and renews 14 Mar 2027. > - The final invoice of S$900 was paid on 2 Feb. > > **What I will do** > - Move the hosting from my account to Faizal's account by 10 Feb. > > **What Faizal needs to do** > - Change the temporary password for the website admin login (user "faizal"). > - Add Aisyah as an editor. > - Update the website link on the Google Business profile. > > **Support, per our contract:** "Bug fixes free for 30 days after launch. Other changes S$80 per hour." > > [Your name] The message leaves out the three [ASK] items: sending the login, switching the contact form email, and renewing the domain. Once you know the answers, add them to the message.
What the test showed
- No secret was repeated. The made-up website password and a made-up Xero backup code never appeared in any of the eight outputs that had them. Each was replaced with [REMOVED: secret]. Checked by script.
- Nothing was invented. In all ten runs with notes, every date and S$ amount in the output was in the notes, and every row quoted the notes word for word (apart from the removed secret).
- Support terms were copied, not written. The web designer's message quoted the contract terms word for word in five of five runs. For a made-up bookkeeper and a made-up logo designer, whose notes gave no terms, no message mentioned free fixes, hourly rates or a warranty (five of five).
- Loose ends were flagged. "Contact form emails still go to my email" was marked [ASK] in five of five runs, and the domain renewal got an [ASK] for who renews it in five of five. The hosting move stayed "To do (me)" by 10 Feb every time.
- Maybes stayed out. "Maybe a blog later" and the bookkeeper's "new bookkeeper may want a call with me" were never checklist rows or in the message (eight of eight).
- One row varied. The notes do not say whether the admin login was given to the client. Three of five runs marked it [ASK] and two marked it Done. Write "login sent on (date)" in your notes to avoid the guess.
- With no notes, it stopped and asked (two of two). One of the two replies said you could leave passwords in your notes. We disagree: take them out first, as in step 1.
Watch out for
- It only knows what you wrote. If you forgot a login or a file, it will not appear. Use the "Not in my notes" questions as a reminder.
- Removing a password from the message is not enough. If a password has been in a chat or email, ask the client to change it after handover.
- Your contract decides. The prompt copies your support terms; it does not check whether they are fair or complete.
Next step
Track the open items
Copy each "To do (me)" row, with its date, into your Notion client tracker, so it shows in the "Due in the next 7 days" view.
Go to lesson 3Series complete: start the next client well
This is the last lesson in the client onboarding series. For your next client, go back to lesson 1 and write a welcome message from your own facts.
Go to lesson 1How we checked this lesson
- On 17 Nov 2026 (Singapore time) we ran the prompt with Claude Code 2.1.325 in print mode on four illustrative inputs: the web designer's handover notes (five runs), a bookkeeper's notes at the end of an engagement (three runs), short notes for a logo project (two runs), and no notes at all (two runs). The output above is from the first web designer run.
- A separate script checked every output: no made-up password or code appears and [REMOVED: secret] does; every date and S$ amount is in the notes; every row's quote is in the notes word for word; the message is under 180 words and has no [ASK]; for the web designer, the support terms are quoted word for word, the contact form row is [ASK], the hosting move is "To do (me)" by 10 Feb and the blog is not a row; for the bookkeeper, GST is not a task; for the bookkeeper and logo designer, no support terms appear; with no notes, it asks and makes no table. 12 of 12 runs passed. We checked the script with altered outputs (a leaked password, an invented date, price and quote, an invented support term, and a contact form row with an owner added); it caught all of them. We also read every output.
- We did not change the prompt after testing: the first version passed, so this is it.
- We tested one assistant on made-up notes. AI output varies by tool, model and input, so run the step 3 check each time.
- Last reviewed: 17 November 2026.