Hub › Lessons › Client onboarding, lesson 2
Write client intake questions that ask only what you need, with AI
A good intake form gets you everything you need to start in one reply, and nothing you would have to protect for no reason. This lesson gives you a tested prompt that turns your own "must know" list into 8 to 10 clear questions. It skips what you already have, and it will not ask a client for a password, NRIC number or bank details, even if your list does.
What you will be able to do: turn a rough list of what you need from a new client into 8 to 10 intake questions for a form, email or WhatsApp, with a map showing that nothing on your list was missed.
Step 1: Write your "must know" list (10 minutes)
Think about the last client you started. What did you have to chase them for in the first week? That is your list.
- Only what you need to start. For each item, ask: would I be stuck without this in week one? If not, ask later or not at all.
- Rough notes are fine. "Logo files and brand colours" is enough. The prompt turns notes into questions.
- List what you already have. Name, email, phone and budget are usually in your quote or chat already. Asking again makes the form longer and looks careless.
- Write down your reply-by date. If you leave it empty, the prompt writes [ASK] instead of making one up.
- Leave access and ID details in if you think you need them. The prompt will move them to a "Check before you ask" note with a safer option, so you can decide on purpose.
Step 2: The intake questions prompt
Fill in the lines at the top, then paste the whole prompt into your AI tool. You do not need the client's name or any of their details for this step.
Write intake questions for a new client. Use only what I tell you. What they bought, as agreed: What I must know before I can start (rough notes are fine): What I already have about them (do not ask again): How I will send the questions (form, email or WhatsApp): When I need their answers by: Do this: 1. Write 8 to 10 questions, numbered Q1, Q2 and so on. Every question must collect something on my "must know" list, and every item on that list must be covered by at least one question. 2. One thing per question, in plain words. If my list has more items than 10 questions can hold, combine only closely related items (such as logo and brand colours) and name each combined question under Map. After each question, say in brackets: Required or Optional, and the answer type (short answer, choice, date, yes/no or file upload). For a choice, list the options. 3. Do not ask for anything I already have. 4. Put quick questions first and file uploads last. 5. Start with one short sentence the client sees before the questions, and end with one short line saying when to reply. Copy my date exactly. If I gave no date, write [ASK: when you need the answers by]. After the questions, add: - Map: each "must know" item, and the question number(s) that cover it. - Not asked: anything on my list you did not turn into a question, and why. - Check before you ask: any question that collects personal details, and whether I really need them to start. Rules: - Never ask for an NRIC, FIN or passport number, date of birth, bank account or card numbers, passwords or login details, home address, or health, religion or race, even if my list says so. Put any such item under "Check before you ask" with a safer way to get what I need (for example, ask them to add me as a user instead of sharing a password). - Never make up a date, price, deadline, service or policy. - If I did not say what they bought, ask me for it and stop.
Step 3: Check the questions before you send them (5 minutes)
- Read the Map. Every item on your list should point to a question number, or to "Not asked" with a reason you agree with.
- Read "Check before you ask". If you truly need something listed there, arrange it another way, such as asking the client to add you as a user on their account instead of sending you a password.
- Look for questions that ask two things. The prompt may combine close items to stay within 10 questions. Split one if a client could easily answer only half of it.
- Replace every [ASK]. Never send a form with [ASK] still in it.
- Think about how files reach you. Bank statements and photos of people are personal data. Agree a safe way to receive them before you ask. The Personal Data Protection Commission explains the data protection obligations that apply when you collect personal data, and has advisory guidelines on NRIC numbers.
- Answer it yourself once. If a question confuses you, it will confuse your client.
Worked example
A made-up freelance web designer in Singapore has a new client who has agreed to a 5-page website. Her list includes the client's domain login and password, which a real list might well contain. The business, client and dates are illustrative.
Input (illustrative)
Write intake questions for a new client. Use only what I tell you. What they bought, as agreed: A 5-page Squarespace website (Home, About, Services, Portfolio, Contact), with 2 rounds of changes What I must know before I can start (rough notes are fine): business name and what they sell; who the website is for; 3 websites they like; logo files and brand colours; confirm the 5 pages; who writes the text for each page; photos they want to use; do they own a domain name, and their domain login and password so I can connect it; target launch date; who gives the final yes What I already have about them (do not ask again): their name, email, phone number and budget How I will send the questions (form, email or WhatsApp): Google Form When I need their answers by: Fri 13 Nov Do this: 1. Write 8 to 10 questions, numbered Q1, Q2 and so on. Every question must collect something on my "must know" list, and every item on that list must be covered by at least one question. 2. One thing per question, in plain words. If my list has more items than 10 questions can hold, combine only closely related items (such as logo and brand colours) and name each combined question under Map. After each question, say in brackets: Required or Optional, and the answer type (short answer, choice, date, yes/no or file upload). For a choice, list the options. 3. Do not ask for anything I already have. 4. Put quick questions first and file uploads last. 5. Start with one short sentence the client sees before the questions, and end with one short line saying when to reply. Copy my date exactly. If I gave no date, write [ASK: when you need the answers by]. After the questions, add: - Map: each "must know" item, and the question number(s) that cover it. - Not asked: anything on my list you did not turn into a question, and why. - Check before you ask: any question that collects personal details, and whether I really need them to start. Rules: - Never ask for an NRIC, FIN or passport number, date of birth, bank account or card numbers, passwords or login details, home address, or health, religion or race, even if my list says so. Put any such item under "Check before you ask" with a safer way to get what I need (for example, ask them to add me as a user instead of sharing a password). - Never make up a date, price, deadline, service or policy. - If I did not say what they bought, ask me for it and stop.
Output (as returned)
The questions are shown word for word from our first test of the final prompt with Claude, with the bold markers removed. The notes after them are summarised.
Please answer these questions so I can start your 5-page website. Rough notes are fine. Q1. What is your target launch date? [Required, date] Q2. Do you already own a domain name (for example, yourbusiness.com)? [Required, choice: Yes / No / Not sure] Q3. Is this the right list of pages: Home, About, Services, Portfolio, Contact? [Required, yes/no] Q4. Who will give the final yes before the website goes live? (Name and role) [Required, short answer] Q5. What is your business name, and what do you sell? [Required, short answer] Q6. Who is the website for? Describe the people you want to reach. [Required, short answer] Q7. Who will write the text for the pages? [Required, choice: I write all of it / Someone else on my side writes it / It differs by page (please explain) / Not sure yet] Q8. Please share 3 websites you like (links), and say briefly what you like about each. [Required, short answer] Q9. Please upload your logo files. If you have a brand guide or an image showing your brand colours, upload that too. [Optional, file upload] Q10. Please upload any photos you want on the website. [Optional, file upload] Please reply by Fri 13 Nov.
Map: all 11 items on the list, each with its question number. It named the two combined questions: business name with what they sell (Q5), and logo files with brand colours (Q9).
Not asked: the domain login and password.
Check before you ask: instead of the password, ask the client to invite you as a user on their Squarespace site or domain account, or connect the domain themselves while you guide them, and check which works with their provider. It also noted that Q4 collects a name and role, that photos may show people, and that clients without a brand guide will not give their colours in Q9, so a follow-up may be needed.
When the list asks for too much
We also tested a made-up bookkeeper whose list included the client's bank account numbers and "their NRIC for the tax filing", and no reply-by date. In every run the email had 8 questions, asked for bank names only, ended with "[ASK: when you need the answers by]" and did not ask for the NRIC. One run's note pointed out something the bookkeeper had missed:
"You don't need it to start. The agreed service doesn't include tax filing."
What the test showed
- No passwords, ID numbers or bank numbers asked. In all 13 test runs with a list, no question asked for a password, login, NRIC, bank account or card number, date of birth or home address. Each time, the item went to "Check before you ask" with a safer option.
- Nothing asked twice. No question asked for the email, phone number, budget or UEN we said we already had.
- Every item covered. Each run covered every remaining item on the list, checked by keyword and in the Map.
- No made-up dates. The web designer's questions all ended with "Fri 13 Nov" as written. With no date given, the bookkeeper's all ended with [ASK].
- It sometimes advised on how files are sent. Several bookkeeper runs warned that bank statements show account numbers and that email is not very secure. That advice varied between runs, which is why step 3 asks you to decide this yourself.
What we changed after testing
The prompt above is the second version. The web designer's list had 11 items for at most 10 questions, so every run had to combine some. With version 1, one of three runs combined questions without saying so. Version 2 says to combine only closely related items and to name each combined question in the Map, and all four version 2 runs did that. Everything else stayed the same.
Watch out for
- The AI only knows your list. If you forget something you need, it will not appear. Add it to your list for next time.
- Fewer questions get more answers. If a question is "nice to know", mark it Optional or drop it.
- Collecting data means looking after it. Every file and answer you collect is something you have to store safely and delete when you no longer need it.
- Keep the questions in step with your offer. If the form asks about something you do not provide, clients will assume you do. Check it against your one-page offer.
Next step
Send it with your welcome message
Your client welcome message already tells the client what you need from them and by when. Link your intake form there, and use the same reply-by date in both.
Go to lesson 1Next: track every client in Notion
Lesson 3 shows you how to build a Notion client tracker with each client's stage, next action and due date, and a view of what is due next.
Go to lesson 3How we checked this lesson
- On 8 Nov 2026 (about 4 am Singapore time) we ran the prompt with Claude Code 2.1.319 in print mode on three illustrative inputs: the web designer's list for a Google Form, a bookkeeper's list for an email with no reply-by date, and a request with no details of what was bought. We ran version 1 eight times and version 2 nine times. The questions above are from the first web designer run of version 2.
- A separate script checked every output: 8 to 10 numbered questions, each marked Required or Optional; no question asking for a password, login, NRIC, FIN or passport number, bank or card number, date of birth, home address, health, religion or race; nothing we said we already had; every list item covered; the reply-by date copied exactly or [ASK] when missing; no new dates; and a "Check before you ask" section naming the password or NRIC item. All 17 runs passed. With nothing about what was bought, every run asked for it and stopped. We also read every output.
- The two Personal Data Protection Commission pages linked above were checked on 8 Nov 2026. This lesson is not legal advice.
- We tested one assistant on made-up lists. AI output varies by tool, model and input, so read every question before you send it.
- Last reviewed: 8 November 2026.