How to onboard a new client so the project starts well

Most project problems are first-week problems. The scope was vague. Communication expectations were never discussed. The client assumed the adjacent work was included.

Client onboarding isn’t paperwork. It’s the setup that makes the rest of the project manageable.

The four things clients leave vague

Before any work starts:

Scope boundaries. What’s in, what’s out — in writing. If you don’t list the exclusions, clients assume everything adjacent is included. A scope of work written before the project starts makes this explicit.

Communication cadence. How often you’ll check in, what channel, expected response time. Clients without a defined cadence fill the silence. One status update on Friday replaces fifteen mid-week messages.

Decision authority. Who approves deliverables, who has input. On complex projects, delivering to the wrong person means rework after you thought you were done.

Payment terms. Whatever’s in the contract, confirm it verbally on the kick-off call. Clients who’ve signed and heard the terms explained once pay faster than clients who’ve only signed.

Run through all four before you discuss the actual work. These five minutes prevent most of the problems.

Set up the billing structure on day one

Add the client name to your calendar convention the day you start. Every event gets [ClientName] in the title — billable or not. If you track invoiced versus offered time, add [F] and [O]. The bracket naming method takes thirty seconds to set up. At month end, every hour is visible without reconstruction.

If you bill hourly, create the billing period in Timescanner that day: client name, rate, start date. The first invoice generates itself from the calendar — no estimation, no reconstruction from memory.

Walk the scope, don’t send it as a PDF

Write the scope, then go through it on the kick-off call. “I want to make sure we have the same picture of what’s in and what’s out — can we walk through the main points?” takes five minutes and catches every misalignment before it becomes a dispute.

The client who skimmed the PDF and assumed adjacent work was included disputes the invoice. The client who discussed the scope on a call knows exactly where the boundary is.

Handle the first delivery carefully

The first delivery calibrates expectations for everything that follows. Present it with a brief rationale for the decisions made, mark what’s open for revision and how many rounds are included, give a specific date for feedback — not “whenever you get a chance.”

“I’d like feedback by Thursday so we can stay on schedule” gets a response by Thursday. “Take your time” doesn’t.

When the start is rough

Some projects have a rough first week despite good preparation. Missing inputs from the client. Decisions escalating to someone you haven’t met. Scope shifting before you’ve delivered anything.

Name it early. “I’ve noticed that X is creating a delay — can we agree on Y before it compounds?” sent in week one is project management. Sent in week six, it’s a conflict.

Timescanner reads your calendar to calculate billable hours per client. Name your events consistently from day one, and your first invoice is ready the moment the month ends. Works with any iCal calendar — Google Calendar, Apple Calendar, Outlook.