Client Onboarding Checklist for Freelancers

Copy This Client Onboarding Checklist

CLIENT ONBOARDING CHECKLIST

Client:
Project:
Main contact:
Decision-maker:
Kickoff date:
First milestone:

BEFORE KICKOFF
[ ] Confirm the project goal and first deliverable.
[ ] Record agreed scope and exclusions.
[ ] Complete the agreement process using your usual tools.
[ ] Confirm fees, billing basis and invoice schedule.
[ ] Identify who supplies materials and who approves the work.
[ ] Request required files and access through appropriate channels.
[ ] Check that the supplied access works.
[ ] Agree the communication channel and response expectations.
[ ] Schedule kickoff and send a short agenda.

KICKOFF CALL
[ ] Confirm the desired outcome and how it will be evaluated.
[ ] Review the first milestone and what "ready for review" means.
[ ] Confirm responsibilities and approval steps.
[ ] Identify missing inputs, dependencies and risks.
[ ] Agree dates, noting which are conditional.
[ ] Separate confirmed decisions from ideas and open questions.
[ ] End with named next actions and owners.

FIRST WEEK
[ ] Send a written recap for confirmation.
[ ] Turn confirmed actions into dated tasks.
[ ] Track onboarding work from day one.
[ ] Follow up on missing materials or access.
[ ] Complete the first agreed piece of work.
[ ] Request feedback through the agreed channel.
[ ] Record decisions and any changes to the original plan.
[ ] Send a short progress update and confirm the next milestone.

FIRST INVOICE
[ ] Check the agreed invoice trigger or date.
[ ] Confirm billing details and any required reference.
[ ] Review the work description and applicable time records.
[ ] Prepare and send the invoice through your invoicing system.
[ ] Record the next follow-up date.
[ ] Confirm receipt or follow up if needed.

The first-invoice section belongs wherever your agreement places it. If an upfront invoice is required before work starts, complete those steps before kickoff.

You can use this checklist in a plain document. The purpose is to begin with clear responsibilities, reliable inputs and a first milestone everyone understands.

Worked Example: Onboarding One Fictional Client

This example is entirely fictional. The freelancer, business, people, dates, work and time entries are invented to demonstrate the checklist.

Maya, a freelance web designer, is starting a homepage refresh for Cedar Lane Studio. The first deliverable is a wireframe for review, not a completed website.

Before kickoff

Maya records the initial scope: homepage structure and design. Additional pages and booking-system changes are outside this engagement.

The agreement is completed through her usual process. Billing is fixed-fee, with the first invoice due before design work begins.

The studio names Elena as the main contact and final approver. Elena supplies the logo and existing copy, but the new photographs are still missing.

During kickoff

They confirm that the homepage should make the studio's services easier to understand.

Maya will prepare the wireframe. Elena will consolidate feedback and provide the photographs. They agree that the first wireframe can use placeholders, so missing photographs do not prevent that milestone.

An idea for online booking is discussed but not approved. Maya records it as an open question, rather than quietly adding it to the task list.

The first-week plan

The wireframe date depends on timely feedback. Maya states that condition instead of presenting the schedule as guaranteed.

What the early record shows

Suppose Maya records 25 minutes checking access, 40 minutes in kickoff and 20 minutes preparing the recap. That is 1 hour 25 minutes of recorded onboarding work, not an estimate of the entire engagement.

Because this is a fixed-fee project, those minutes do not automatically become extra charges. They help Maya understand the effort involved.

By Friday, the useful questions are straightforward: what is confirmed, what is ready for review, what remains missing and who acts next?

What to Settle Before Starting Delivery

Define the first deliverable

“Start the website” is too vague to guide the first week.

“Prepare a homepage wireframe with the agreed sections for review” gives you a clear starting point and a completion condition.

Distinguish work ready for feedback from work approved for release.

Identify the approver

Your day-to-day contact may gather feedback without being able to approve it.

Ask who makes the final decision, who consolidates comments and what happens if reviewers disagree. This helps prevent conflicting instructions during the first revision.

Check inputs rather than merely requesting them

An access invitation is useful only if it works. A folder of images is useful only if it contains what the first deliverable needs.

Turn “request materials” and “verify materials” into separate actions when appropriate. Keep credentials in your appropriate access-management tools.

Make dependencies visible

If a milestone depends on feedback, copy or access, name the dependency and its required date.

“Wireframe review Friday, provided structure feedback arrives Wednesday” communicates more than a date alone.

Run the Onboarding Workflow in SelfManager

SelfManager's documented structure uses dates and tables to organize tasks and context. It also supports notes, comments, task statuses and time tracking.

Use that structure as your own working record. Complete agreements, approvals requiring signatures and invoicing through the appropriate tools you already use.

1. Create a clearly named client table

For the fictional example, use:

Cedar Lane Studio - Onboarding

Keep the agreed goal, first deliverable and open questions in the table's notes. Put actionable work in task rows.

Separate actions you own from inputs you are waiting for. “Ask Elena for photographs” is your action; “photographs received” is a condition you need to verify.

2. Put onboarding actions on the relevant dates

SelfManager allows tables within dates.

Keep a client reference table for context, then create clearly named client tables on the dates when onboarding work belongs. The schedule in the example is a planning pattern you can set up manually.

Do not assume one table automatically spreads its tasks across future dates. Deliberately place the actions where you will review them.

Keep genuine due dates distinct from the day you intend to work on a task.

3. Record decisions in comments

SelfManager documents table comments and notes for preserving context.

For example:

October 13: Elena confirmed placeholders are acceptable for the first wireframe. Final photographs remain outstanding. Online booking was discussed but has not been approved.

That comment preserves three distinctions: a decision, a missing input and an unapproved idea.

Confirm important decisions through the agreed communication channel too. Your personal record and the client's confirmed understanding should agree.

4. Use the time tracker from day one

Enable time tracking for the onboarding tasks you want to measure. SelfManager supports tracking time at task level.

Include preparation, access checks and follow-up when they matter to your review. These small activities can otherwise disappear from your understanding of the project.

Keep recorded time separate from billable time. Your agreement determines what you charge.

Test the workflow with one new engagement: create its onboarding table, plan the first week's actions and record decisions as they happen. Try SelfManager free for 7 days, with no credit card required.

Capture a Voice Recap After Kickoff

While the conversation is fresh, dictate your own short recap: decisions, missing inputs, responsibilities, dates and unresolved questions.

SelfManager supports voice-to-text in table comments and notes, with recordings or dictation up to 30 minutes. For comments and notes, you can choose whether to keep the audio; the transcript remains either way. Its table Audio section also supports recording and uploading audio.

A spoken recap might be:

Elena approved placeholders for the first wireframe. She will confirm the structure Wednesday. New photographs are still outstanding. Booking was only an idea, not agreed work. I need to send the recap today and check Wednesday's feedback before continuing.

This is your post-call note. It does not require recording the meeting.

A concise recap is usually easier to check than a long narration. Read the transcript and correct names, dates and any missing qualifiers.

Turn Kickoff Notes Into Tasks with AI

SelfManager documents a text-to-task feature that can use meeting notes or a planning-call brain dump to create task rows.

Use the corrected transcript as input. This suggested instruction helps keep the resulting plan close to what was actually agreed:

Turn these kickoff notes into onboarding tasks.

Create actions only from confirmed commitments.
Keep unapproved ideas and unresolved questions separate.
Preserve names, owners and dates only when stated.
Flag missing information instead of inventing it.
Separate my actions from inputs I am waiting for.
Do not treat a requested approval as an approval received.

Notes:
[Paste the corrected kickoff recap]

The generated tasks are a starting point. Review them before using them as your working plan.

Remove unsupported tasks, clarify ambiguous wording and place the accepted actions on suitable dates.

An AI-generated priority is a suggestion. Decide what deserves attention based on the actual commitment.

Keep the First Invoice Tied to the Agreement

Check the invoice trigger during onboarding, even when billing will happen later.

Confirm who receives it, what reference is required and how the work should be described. Prepare the invoice through your normal invoicing system.

For the fictional engagement, the agreed upfront invoice comes before design work. Task time remains useful for understanding effort, while the invoice follows the fixed-fee agreement.

Where This Checklist Stops

This article covers the beginning of one engagement: getting inputs, confirming decisions and reaching the first milestone.

Use the related guides when the work moves into a different stage:

• Manage tasks for multiple clients for balancing ongoing commitments.
• Scope creep tracker for freelancers for recording later changes to agreed work.
• Client invoice summary from tracked tasks and time for preparing a work summary to support your billing process.
• Project handover template for passing work and context to someone else.

Keeping those stages separate makes onboarding shorter and easier to repeat.

Start with the Next New Project

Copy the checklist, adapt the invoice timing and define the first deliverable. Then record decisions and turn confirmed commitments into dated actions.

Start your 7-day SelfManager trial to organize one new engagement with a client table, daily tasks, comments and time tracking. After kickoff, capture a voice recap and review the AI-generated tasks before adding them to your plan.

FAQ

What should a freelancer's client onboarding checklist include?

Include the agreed goal, scope, billing arrangement, contacts, access, materials, kickoff decisions, first-week actions and first-invoice steps.

When is onboarding complete?

For this checklist, onboarding is complete when the working arrangements are confirmed, required inputs are available or explicitly accounted for, and the first delivery milestone is underway. Adapt that finish line to your service.

Should the first invoice come before kickoff?

Follow the agreed billing arrangement. If an upfront invoice is a condition of starting work, complete it before delivery begins. The checklist's sections do not override that sequence.

Can I use the checklist without SelfManager?

Yes. Copy it into a document and use your existing planning, communication and invoicing tools.

Can SelfManager turn kickoff notes into tasks?

Yes. Its documented text-to-task workflow can use notes as input. Check the generated actions against the confirmed scope, responsibilities and dates before relying on them.