Blog

A client onboarding checklist for freelancers: what to collect before kickoff

By DevlectaDesigns · October 12, 2026

The gap between a client saying yes and the first real day of work is where many projects go wrong. A missing logo file, an unclear goal or an unpaid deposit rarely looks serious on day one, but each one delays the work later. A short, repeatable onboarding checklist closes that gap.

This guide lists what to collect before kickoff and how to decide when a client is genuinely ready to start. Adapt it to your own services; it is a working template, not legal or financial advice.

Think in stages, not a pile of tasks

Onboarding is easier to manage when every client moves through the same few stages. A simple sequence:

1. Contract. The scope and terms are agreed in writing.
2. Deposit. Any upfront payment you require has been recorded.
3. Brief. The client has answered your intake questions.
4. Assets. You have the files and access you need.
5. Ready. Everything required for kickoff is in place.
6. Kickoff. The project officially starts.

The rule that makes stages useful: a client only moves to Ready when the items you marked as required are actually done. That turns “I think we’re ready” into a yes or no answer.

1. Agreement and money

• A signed contract or written acceptance of your proposal, with scope, timeline and price.
• What is out of scope, written down. This is the item most often skipped and most often regretted.
• Deposit amount, currency and due date, and whether it has arrived.
• How and when the remaining invoices will be sent.

Keep a record of each invoice, its total, the deposit target and the due date, even if the invoices themselves live in your accounting tool.

2. The intake brief

Send the same core questions to every client so answers are comparable. Four that cover most creative and service projects:

• What outcome are you aiming for? For example, “launch the refreshed brand by March”.
• Who is the audience? For example, “independent shop owners”.
• What deliverables are expected? For example, “identity files and website direction”.
• What is in or out of scope? Ask the client to say it in their own words, then compare it with your contract.

Mark the questions you cannot start without as required. If a required answer is blank, the client is not ready.

3. Materials and access

List every file or login you need, then track each one as requested or received:

• Brand files: logo, fonts, colors, existing guidelines.
• Content: copy, product information, photos.
• Access to the accounts or platforms you will work in.
• Examples the client likes, and examples they do not.

Never ask clients to email passwords in plain text. Ask them to share access through the platform’s own team or delegate features where possible.

4. People and communication

• Who approves the work, and who just gets copied.
• Preferred channel and expected response times on both sides.
• Dates of the kickoff meeting and the first check-in.
• A short log of important decisions, so “we agreed on that call” has a date attached.

5. Kickoff summary

Before the kickoff meeting, write one page that restates the goal, audience, deliverables, scope, key dates and open items. Send it to the client and ask them to confirm. It becomes the reference point when questions come up later.

How to tell when a client is ready

Count only the required items. If three of four required items are done, the client is 75 percent ready, and the missing item tells you exactly what to chase. Move the client to Ready only at 100 percent. This one habit prevents most “we started too early” problems.

Keeping it repeatable

The checklist only works if you use it the same way for every client. A shared document works, and so does a dedicated tool. Onboard Desk, a downloadable HTML app from DevlectaDesigns, follows this structure: a pipeline from Contract to Completed, intake briefs and checklists with a readiness percentage, requested materials, meetings, a communication log, manual invoice records, and a kickoff summary you can copy, print or export as text. It keeps the data in your browser on your computer, so export JSON backups regularly.

Whatever you use, the point is the same: decide what “ready” means before the client arrives, then hold every project to it.