Client onboarding checklist for freelancers and small studios

Onboarding makes a new engagement ready to deliver

Client onboarding is the transition from an accepted engagement to a working relationship with the right information, people and access in place. A useful checklist confirms what is agreed, who makes decisions, what the client must supply and whether your team can actually begin. A welcome email alone does not complete it.

For a freelancer or studio, onboarding is broader than a kickoff meeting. The meeting aligns people; onboarding also includes collecting materials, confirming billing requirements, granting appropriate access and handing the agreement to the delivery owner. Ignition describes a similar professional-services sequence covering agreement, information collection, team assignment, kickoff and follow-up. This checklist is not a substitute for regulated financial-services identity checks.

Use this checklist with an owner and completion evidence

Give each item an owner, a due date and a status such as waiting on client, ready or blocked. Record what proves completion. “Portal invitation sent” is weaker evidence than “named reviewer can open the correct project.” Keep a short exception list for anything that remains unresolved.

1. Agreement: save the accepted version, included deliverables, exclusions, schedule assumptions and any required signatures.
2. Billing: confirm the legal customer name, billing contact, invoice destination, purchase-order requirement and any agreed initial-payment condition.
3. Decision roles: name the daily contact, commercial approver, delivery reviewer and payer; confirm any deputy arrangements.
4. Client inputs: list each required file, answer or permission, its owner, due date, accepted format and the task it enables.
5. Access: request named accounts with the permissions needed for the job, then confirm those accounts work before production depends on them.
6. Privacy: agree where sensitive files belong, who may see them and who handles access removal and retention decisions.
7. Communication: identify the channel for routine questions, how feedback is consolidated and how urgent blockers reach an accountable person.
8. Delivery handoff: transfer the agreed scope, decisions, dependencies and unresolved issues to the person doing the work.
9. Readiness: confirm the first deliverable, responsible owner and review date; explicitly record any remaining blocker or approved exception.

Separate access from decision-making authority

A person who can view a shared folder is not necessarily allowed to approve additional spend. Similarly, a finance contact paying an invoice may not be qualified to approve a design. Write down the roles even when one person holds several of them. Ask who can act if the usual approver is unavailable.

For systems access, prefer individual invitations and the least privilege needed for the assignment. A copywriter might need draft editing, not billing administration or permission to delete the site. Use appropriate secure credential-sharing methods when an invitation is not possible; do not ask for passwords in an intake form or a shared project comment. Record the access owner and when removal will be reviewed.

Collect usable inputs without collecting everything

Turn “send the assets” into a precise request: current logo files, approved homepage copy, licensed images and the person who can confirm their use. Note file format, version and deadline. A folder full of outdated drafts is not evidence that the copy dependency is ready.

Request only the information needed for the engagement. If a task can use anonymized sample data instead of a customer database, discuss that option first. Keep client-confidential files out of broad team channels and separate private working notes from shared deliverables. Confirm the agreed storage location and retention or deletion arrangements; legal obligations vary, so this practical checklist is not a privacy-compliance certification.

Example: onboarding a small website refresh

In a fictional two-person studio, Emi owns delivery and Luis builds the pages. Their client, Willow Ceramics, has agreed to a three-page website refresh. Sana is the day-to-day contact and delivery approver, founder Jo approves any added spend, and finance receives invoices. Those roles are recorded separately even though Sana attends every call.

The checklist requires approved page copy, current product photographs with confirmed usage rights and a named editor account for the staging site. Sana owns the files; the client administrator owns access. Emi confirms that Luis can edit staging without receiving production billing permissions. The shared client folder contains approved inputs, not internal estimates or unrelated customer records.

Two days before production, the photographs are ready but the contact-page copy is not. Emi marks that input blocked, names Sana as its owner and explains which task will move. The team may start the agreed homepage work if its inputs are complete, but does not label the whole project ready or silently promise the original completion date.

Send a welcome message that assigns the next actions

Keep the welcome note short enough to act on. Link to one current checklist rather than scattering requests across several emails. A copyable example for the website engagement is:

“Welcome, Sana. Emi is your delivery contact for the agreed three-page refresh. Please upload the approved copy and image files to the shared project folder by Tuesday. Your site administrator will receive a separate request for staging access; please do not email passwords. Sana will consolidate delivery feedback, and Jo will approve any priced additions. We will confirm the first review date after the required inputs and access are ready.”

Explain what happens if an input is late and where the client can ask for help. If an initial payment is a start condition, state it consistently with the agreement; do not present it as a requirement every client must follow.

Hand off the engagement, then use kickoff for unresolved decisions

The internal handoff should carry the accepted scope, commercial promises, relevant discovery notes, access locations, client roles and outstanding dependencies. Share only what the delivery team needs. A salesperson saying “it is all in my inbox” leaves the next person reconstructing the agreement and risks exposing unrelated correspondence.

Use the kickoff meeting to align the people doing the work and resolve remaining questions, not to reread the entire onboarding form. Keep the meeting agenda in the separate kickoff guide. Afterward, update the checklist with decisions, owners and dates; attendance alone does not prove that access works or that missing materials arrived.

Close onboarding with a visible readiness decision

Confirm that the first piece of work has its required inputs, an owner and a real review contact. Keep unresolved exceptions visible and revisit them at the first delivery check-in. Ask which request was confusing, then improve that checklist item for the next engagement instead of adding more introductory paperwork.

Moolamochi keeps commercial agreement, delivery acceptance and payment separate, and private work is not automatically shared with clients. New access is currently waitlist-only. Whatever tools you use now, make onboarding complete because the engagement is ready, not because every welcome email was sent.