Free Tool
Client Onboarding Checklist
A client who is onboarded properly pays on time and asks fewer questions. This builder turns the project type into a checklist — scope, payment, access and the kickoff call.
Runs entirely in your browser. Nothing you type leaves your device, and nothing is stored or sent anywhere. The output is a planning aid built from the figures you enter — check the results before relying on them.
What this tool does
Pick the project type, enter the client and the project name, the start date and the payment terms, and the builder returns a checklist: the scope questions to confirm in writing, the payment terms to agree before work starts, the access to request, and the kickoff call agenda. Copy it into your notes and check each item off as the client answers.
The checklist exists because the most expensive freelancer mistakes happen before the work starts: scope that was never written down, payment terms that were never agreed, access that arrives a week late. A checklist does not slow the project down — the missing answer does.
Try it
Waiting. Fill in the client and the project, then press Calculate.
How it works
The checklist has four sections, in the order they must be settled: scope first, because everything else depends on it; payment second, because it must be agreed before work starts; access third, because late access is the most common delay; and the kickoff call last, where the three are confirmed together.
The item count is the scope items plus the two payment items, the one access item and the four kickoff items, plus any extras you add. A count is not a score — it is a way to see at a glance how much of the onboarding is done.
Assumptions and limitations
A checklist is a record of agreement. It is not the agreement itself.
- Nothing here is legal advice. The scope and payment items should be confirmed in writing — an email counts — and for large projects a proper contract is worth the cost.
- The access item changes with the project type: a developer needs repository access where a writer needs the style guide. The list names the most common access for each type; add what is missing.
- Payment terms are agreed before work starts, not after. A deposit that is requested after the work has begun is a negotiation; a deposit agreed in the checklist is a term.
- The kickoff call is the last item, not the first. A call without confirmed scope is a conversation; a call with the checklist in hand is a confirmation.
Worked example
Example (illustrative inputs, not a real client). Acme Studio, website redesign, starting 23 November 2026:
| Item | Figure |
|---|---|
| Checklist items | 13 items (12 standard + 1 extra) |
| Scope items | 5 — deliverables, success measure, revisions, deadline, contact |
| Payment | 50% upfront, 50% on delivery |
| Access | Brand files, fonts and design system |
Frequently asked questions
Why confirm scope in writing?
Because memory differs. The client remembers what they asked for; you remember what you heard. A written scope is the version both of you can point at, and it is the only version that settles a dispute about what was included.
What if the client will not pay a deposit?
Then the risk is yours, and you should price it. Either decline, or agree shorter payment terms with a written pause-on-nonpayment clause. A client who will not pay a deposit is telling you something about how the project will end.
Should I ask for access before the start date?
Yes — access that arrives a week late is a week of the deadline gone. Request it in the onboarding, confirm it before the start date, and start the clock when the access arrives, not before.
Do I need a kickoff call for a small project?
A call, an email or a message — the form does not matter. What matters is that scope, payment, access and the first check-in are confirmed in one place before the work starts.