What a client onboarding checklist is for
A client onboarding checklist is the list of things you confirm, collect and set up between "yes, let's do it" and the moment you start the work. For a first service business it does three jobs: it prevents scope arguments later, it protects you and the client when files and data change hands, and it makes the first job feel professional even if it's your first ever.
This checklist is built for a small, productized online service — a fixed deliverable for a fixed price — and for someone delivering their first few client jobs. It has five phases and 28 steps. Not every step applies to every service; skip what doesn't fit, but skip it on purpose.
Phase 1: Before you say "confirmed"
These steps happen right after the client agrees, before the job is officially booked.
- Restate the scope in writing. Copy the deliverable, inputs, limits and exclusions from your offer into the confirmation. Ask the client to reply "confirmed".
- Confirm the price and currency. Include whether tax is added, and the payment terms.
- Agree the deadline as a date. "Three working days after inputs arrive" becomes a real date once inputs arrive.
- Agree the acceptance criteria. How both sides will know the job is done.
- Name one contact on each side. One person who answers questions and approves the result.
- Check for conflicts. Make sure the work doesn't conflict with other commitments, such as an employer agreement.
Phase 2: Inputs and access
Most delays come from missing or wrong inputs. Ask for everything in one message.
- List every input you need. For a catalogue audit: the export file, the field list and any rules the client already uses.
- Confirm the client is authorised to share them. They should own the data or have the right to share it with you.
- Agree the format and size limits. For example CSV, up to 2 MB, up to 200 rows and 10 fields.
- Ask whether personal data is included. If customer names, emails or addresses are in the file, agree how you'll handle, store and delete them — or ask for a version without them.
- Agree how files are transferred. A shared folder the client controls is often better than email attachments.
- Request only the access you need. Avoid asking for passwords or admin access to systems if a file export will do.
Phase 3: Kick-off
A short kick-off message or call sets expectations.
- Send a welcome message. Thank them, restate the date and what happens next.
- Confirm what you'll deliver and in what format.
- Explain how you'll handle questions. For example, one batch of questions after the first review, by email.
- Set the check-in point. One update halfway through is enough for a short job.
- Explain what you won't do. Repeat the exclusions in plain words. This prevents "while you're at it…" requests.
Phase 4: Delivery
Use the same delivery format every time. It becomes part of your product.
- Check the deliverable against the scope. Everything promised is there; nothing extra that wasn't agreed.
- Check it against your quality rubric. For a data audit: every flag has row, field and rule; protected fields such as IDs and prices are unchanged.
- Include a change log. What you changed, where and why.
- List open questions. Anything you couldn't resolve without the client.
- Label anything uncertain. Mark "unknown" rather than guessing.
- Deliver on the agreed channel and date.
- Ask for acceptance. "Please confirm the delivery meets the agreed criteria, or tell me what's missing."
Phase 5: After delivery
- Send the invoice according to the agreed terms. Payment happens outside Proofoak.
- Delete or return client files as agreed, and confirm in writing that you've done so.
- Ask for feedback in their own words. Save it as it was written.
- Ask — don't assume — whether you can mention the work. A case study or testimonial needs explicit permission.
The checklist at a glance
| Phase | Steps | Key output |
|---|---|---|
| 1. Before confirming | 1–6 | Written scope, price, date and acceptance |
| 2. Inputs and access | 7–12 | Authorised inputs, data-handling agreed |
| 3. Kick-off | 13–17 | Expectations and exclusions confirmed |
| 4. Delivery | 18–24 | Checked deliverable, change log, acceptance request |
| 5. After delivery | 25–28 | Invoice, files deleted, feedback, permission |
Adapting it to your service
| Service type | Add | Remove |
|---|---|---|
| Data cleanup | Field-mapping confirmation; protected fields list | — |
| Writing | Style guide and tone examples; approval rounds | File-transfer steps if text is pasted |
| Bookkeeping support | Access to accounting software; period covered | Sample-file steps |
| Research | The exact question; criteria; sources to exclude | Data-handling steps if no client data is used |
| Setup and automation | Test account; rollback plan | — |
A confirmation email you can copy
Adapt the details to your service. The point is that every important item — scope, inputs, date, price, data handling and exclusions — is written down before the work starts.
How long onboarding should take
For a small productized job, onboarding should take minutes, not days: one confirmation email, one file transfer and one short kick-off message. If it takes longer, the scope is probably not fixed enough yet. Each time a client asks the same question during onboarding, add the answer to your confirmation email so the next client doesn't need to ask.
What to do when inputs are wrong or incomplete
It happens on almost every early job: the file is bigger than agreed, a column is missing, or the export contains data you didn't expect. Handle it the same way every time:
- Stop before you start the work. Don't silently fix or expand the scope.
- Tell the client exactly what's different — "The file has 340 rows; the agreed limit is 200."
- Offer clear options — trim the file, split it into two jobs, or upgrade to a larger size at a stated price.
- Wait for written confirmation before continuing.
- Add the case to your edge-case list so your next confirmation email prevents it.
The same applies to personal data you didn't expect: pause, tell the client, and agree how it's handled — or ask for a clean export.
Data handling in plain words
| Question | A good default for small jobs |
|---|---|
| Where are files stored? | In a folder the client shares, or a private folder only you can access |
| Who can see them? | Only you, unless the client agrees otherwise |
| How long are they kept? | A fixed period after delivery, for example 14 days |
| How are they deleted? | Removed from your folder and downloads, with a confirmation to the client |
| Are they used for anything else? | No — not for marketing, not for training AI models |
Write your defaults once and include them in every confirmation email. Clients notice, and it builds trust faster than any testimonial.
Onboarding a recurring client
When a one-off client becomes a monthly client, add four steps:
- agree the monthly limit and what happens if it's exceeded;
- agree the delivery day each month;
- agree how changes to scope are requested and confirmed;
- agree how either side can pause or end the arrangement.
Common onboarding mistakes
- Starting before inputs are complete. Half-complete inputs create half-complete work and a second round nobody planned.
- Accepting more data than you need. It increases risk for both sides.
- No written scope. A verbal "yes" is easy to remember differently.
- Skipping acceptance. Without it, "done" stays open.
- Assuming permission to publish. Always ask.
How Proofoak helps
When a test produces a real request or a first client, Proofoak gives you this checklist inside the project, linked to the offer version the client accepted. You can record the client's request and their feedback as evidence, separate from your SaaS billing. Contracts, escrow and delivery into the client's systems stay outside Proofoak in v1.