Blog · Published 2026-10-30

Freelance client onboarding checklist

The first week of a freelance project decides a lot about the next ten. If you start without a signed agreement, a clear contact person or the files you need, you spend the project catching up. A short, repeatable onboarding routine fixes most of that. Here is the checklist we use, plus a kickoff email you can adapt.

What "onboarding" actually means for a freelancer

Onboarding is everything between the client saying yes and you starting the real work. It's not a welcome gift or a branded PDF. It's making sure four things are true before you spend billable hours:

• The deal is written down. Scope, price, payment terms and revision rounds are in a document both of you have agreed to.
• The money side has started. Any deposit you require has been invoiced, and ideally paid.
• You have what you need. Logins, brand files, content, data, and a named person who can answer questions and approve work.
• Both sides know how the project runs. Where you talk, how fast you reply, how feedback works, and what the next dates are.

If any of those is missing, the gap usually shows up later as a delay, a dispute about scope, or a late invoice.

The client onboarding checklist

Copy this list into your notes app or project tool and tick it off for every new client. Not every item applies to every project; delete what you never use.

1. Paperwork

• Proposal or quote accepted in writing (an email reply counts as a record, a signed agreement is better).
• Agreement or contract signed by both sides, covering scope, deliverables, price, payment terms, revision rounds and what happens if the project is paused or cancelled.
• Exclusions written down: what a client might reasonably expect that is not included.
• Who owns the work and when (for example, on final payment). Have a professional review contract wording if you're unsure.

2. Money

• Deposit invoice sent, if you take one, with the amount, due date and how to pay.
• Billing contact confirmed: the person who actually pays invoices is often not the person you work with.
• Any purchase-order number or invoicing details the client's finance team needs.
• Payment schedule for the rest of the project (milestones or dates) noted in your calendar.

3. People and decisions

• Main contact named, with their preferred channel.
• Decision maker named. If someone else approves the work, find out now, not at the final review.
• Who else gives feedback, and whether their feedback should come to you combined or separately.

4. Materials and access

• A written list of everything you need from the client, each item with a date.
• Access to accounts and tools set up and tested (use a password manager or the client's own sharing feature; avoid passwords in plain email).
• Brand guidelines, existing content, examples they like and dislike.
• A shared folder or file location both sides use.

5. How the project runs

• Communication channel agreed (email, Slack, a project tool) and your normal response time.
• Your working hours and time zone stated.
• Status update rhythm (for example, a short update every Friday).
• How feedback works: one consolidated round per draft, how many rounds are included, and how fast you need it.
• What counts as a change request, and how you'll handle one (estimate first, written approval before work starts).

6. Kickoff

• Kickoff email sent (template below).
• Kickoff call booked, if the project needs one, with an agenda.
• First deliverable and its date confirmed.
• Onboarding questionnaire sent, if you use one.

A kickoff email you can adapt

Send this once the agreement is signed. Keep it short; the checklist does the heavy lifting.

Subject: [Project name]: next steps and what I need from you

Hi [Name],

Thanks again for choosing to work together on [project]. Here's how the next couple of weeks look.

What happens next
- [Date]: kickoff call (link: [calendar link])
- [Date]: first draft of [deliverable]

What I need from you by [date]
- [ ] Access to [tool/account]
- [ ] [Brand files / content / data]
- [ ] Name of the person who will approve the final work

How we'll work
I'll send a short update every [day]. I usually reply within [time] on weekdays. For feedback, one combined set of notes per draft works best; the agreement includes [number] rounds.

Any questions, just reply here.

[Your name]

Notice what it doesn't do: it doesn't add new promises, and every date comes from the agreement. If a date isn't confirmed yet, leave a placeholder and fill it in before sending.

Questions for an onboarding questionnaire

A questionnaire saves you from chasing details one email at a time. Keep it short: ten to twelve questions, most of them quick to answer. Pick from these and adjust for your service:

1. What is the main goal of this project, in one or two sentences?
2. How will you decide whether the project was a success?
3. Who is the audience or end user?
4. Do you have brand guidelines, a style guide or examples we should follow?
5. Share two or three examples you like, and one you don't, with a line on why.
6. What existing material should I use (content, data, previous versions)?
7. Which tools or accounts will I need access to?
8. Who will give feedback, and who gives final approval?
9. Are there any fixed dates (launches, events, board meetings) I should know about?
10. Anything that has gone wrong on similar projects before that you'd like to avoid?

Add a one-line note on why you're asking for each item that might seem intrusive, such as account access. People answer faster when they understand the reason.

Using AI to speed this up (without losing accuracy)

AI assistants are good at turning your notes into a tidy email or questionnaire. They are bad at knowing your actual dates, prices and agreements, and they will happily fill gaps with something plausible. Two habits prevent most problems:

• Give it only real facts, and tell it so: "Use only the details below."
• Ask it to flag gaps instead of guessing: "If a date or name is missing, write [NEED: …]."

For example, a kickoff prompt might look like this:

Write a kickoff email to [CLIENT NAME] for [PROJECT].

Confirmed details: scope [SCOPE], start date [DATE], first deliverable [DELIVERABLE], communication channel [CHANNEL].
What I need from them: [LIST OF MATERIALS, ACCESS, DECISIONS] by [DATE].

Structure: welcome (one sentence), what happens next with dates, what I need from them as a checklist, how and when we'll communicate, one line on how feedback works. Under 200 words. Do not add dates or commitments I haven't provided. If something is missing, write [NEED: what's missing].

Then read the draft against your agreement before you send it. The AI writes; you check and decide.

Common onboarding mistakes

• Starting before the paperwork. Eager clients ask you to "just get going". A friendly, firm line helps: you begin once the agreement is signed and the deposit is in, and in the meantime you can do the planning that doesn't carry risk.
• No named approver. If a senior person appears at the end with new opinions, the project restarts. Ask who approves on day one.
• Vague material requests. "Send me your content" invites delays. List each item and give each a date.
• Feedback by committee. Ask for one combined set of notes per round, or you'll be reconciling contradictory comments.
• Not writing it down. After the kickoff call, send a short summary of what was agreed and what's still open. It's your record if questions come up later.

Make it a template, not a one-off

The point of a checklist is that you don't have to think about it. Save the list, the kickoff email and your questionnaire somewhere you can copy from in a minute. After each project, add one item you wish you'd asked about and delete one you never use. After a few clients, your onboarding will fit your business rather than a generic list.

This article is general information for freelancers, not legal advice. For contracts and payment terms, use a qualified professional where you work.