A client onboarding sequence that prevents most future confusion

You signed the contract three weeks ago and the project already lives in four places. The brand fonts came as a zip attached to a reply nobody can find now. The homepage copy is in a Google Doc somebody shared with a personal Gmail address. Nobody on either side can get into the analytics account. The office manager texts you at nine at night asking when the site goes live, and you are not certain she is the person who approves anything.

None of that is a difficult client. It is an onboarding gap, and almost all of it is fixable in the first five business days.

Why the first week of a client project decides how the rest of it goes

A surprising amount of mid-project friction traces back to a question nobody answered in week one. The client does not sit down and decide to email you files at random. They do it because you never told them where files go, so they used the default they already had. Every question you leave open gets filled in by whatever the client is used to, and once a habit forms in week two you are fighting it in week nine.

Four defaults form fast. Where work lives defaults to email. Who to contact defaults to whoever answered last. Who approves defaults to whoever spoke most recently in the meeting. What counts as done defaults to nothing, because approval was never defined, so revisions never formally stop.

Front-loading works for a simple reason. The stretch right after signing is the one time a client is reliably paying attention to logistics. They have just made a decision, they are expecting instructions, and a long setup message reads as competence rather than as an interruption. Later in the project their attention belongs to the work itself, and anything procedural competes with everything else on their desk. Spend the attention while you have it.

The five questions your onboarding has to answer

A client onboarding sequence is complete when it answers five questions in writing, in one place the client can find again.

1. Where does everything live? One link. Files, messages, approvals, current status.
2. Who do I contact, and how fast will they answer? A name and a stated response window, not a promise of instant replies.
3. Who approves, and what counts as approved? One named person per decision and a definition of approval.
4. What do you need from me, and by when? A short list with dates and a named person on their side for each item.
5. What happens if I go quiet? Say plainly what stalls and what it costs in calendar time.

Here is a decision rule worth keeping. Any time a client asks you something after week one that belongs on that list, do not just answer it. Add the answer to your onboarding template that same day. Within a few projects the template stops leaking.

The onboarding sequence, message by message

This is a five message sequence over the first week. Adjust names and timing, keep the structure. Every message is short enough that a busy owner will actually read it.

Message 1, within an hour of signing

Subject: You are booked, here is what happens next

Thanks for signing. Your project is on the calendar starting Monday the 4th. Nothing is needed from you today. Tomorrow morning I will send one link with your project workspace, the schedule, and a short list of things I will need from your side. Our kickoff call is Wednesday at 10am, 45 minutes, calendar invite attached. If anything on the schedule already looks wrong, reply here and I will fix it before we start.

Message 2, next morning: the kickoff message

This is the message that does the most work in the whole sequence. It answers where things happen, who to contact, how fast you reply, what counts as urgent, and how the client can take part without ever logging in. Steal it and put your own names in it.

Subject: Your project workspace and how we will work

Here is your workspace: [link]. Everything for this project lives there. Files, messages, approvals, and the current status. If you ever wonder where something is, it is in that link.

A few ground rules so nothing gets lost. Send files and feedback in the workspace rather than by text or forwarded email. Anything sent somewhere else is invisible to the rest of my team, and it will not be in the record when we hand the project over at the end.

I answer within one business day, usually faster, and I do not work weekends. If something is genuinely urgent, call me at [number] and say that it is urgent.

You do not have to log in to answer me. Every notification from the workspace arrives in your inbox with the full message in it, and if you reply to that email your reply lands back in the right thread where my team can see it. Logging in is for when you want to look at files, check status, or approve something yourself.

Message 3, kickoff call agenda, sent the day before

Subject: Wednesday agenda, 45 minutes

1. What success looks like for you, in your words, 10 minutes.
2. Who does what on your side. I need to know who approves designs, who approves copy, and who signs. 10 minutes.
3. The schedule and the three dates I need from you. 15 minutes.
4. Questions. 10 minutes.

If the person who approves designs is not on this call, please forward the invite. It saves us a week later.

Then recap the call in writing the same day, in the workspace, with every decision and every owner named. The recap is the artifact, not the call. Nobody can search a Zoom conversation in month three.

Message 4, the day after kickoff: what I need from you

Subject: Three things from your side, dates included

1. Logo and brand fonts, vector and font files if you have them. Owner: Dana. Needed by Friday the 8th.
2. Staff photos and bios for the team page. Owner: Dana. Needed by Friday the 15th.
3. Access to your domain registrar and your analytics account. Owner: Dr. Patel. Needed by Friday the 15th.

Upload each one to the workspace. If item 1 slips past the 8th, design starts a week later and the launch date moves with it. That is not a penalty, it is just how the schedule works.

Name a person for each item. A request addressed to a company gets done by nobody. A request addressed to Dana gets done by Dana or gets escalated, and either outcome is progress.

Message 5, end of week one: the first status note

Subject: Week 1 status

Done this week: kickoff, sitemap drafted, hosting environment set up.
Next week: first two page designs, ready for your review Thursday.
Waiting on you: staff photos and bios, due the 15th, Dana.
Schedule: on track for launch the week of the 20th.

Send that same four line format every week for the life of the project. The client learns to open it, and the "waiting on you" line does more for your timeline than any reminder email you will ever write. If you want that weekly rhythm written down so it holds up when you get busy, that is the job of a client communication plan.

How to write an approval rule that survives the project

An approval rule works when it names one person, one place, one deadline, and what happens when the deadline passes. Anything less produces the review round that has been open for eleven days while everyone assumes somebody else is looking at it.

Put this in message 2 and repeat it before the first review:

Designs are approved by Dr. Patel only. Feedback from anyone else is welcome and I will fold it in, but the sign off is his. Approval means a written "approved" in the workspace on that specific item, not a verbal yes on a call. Each review round is open for three business days. If I hear nothing in three business days I will follow up once, and if the round closes without changes I will treat it as approved and move on. Two rounds are included. A third round is fine and it moves the launch date.

When something needs more than one approver, say the order and name the last one. "Sarah reviews the copy, then Dr. Patel approves it" gives you one person to chase instead of a thread to stare at.

One decision underpins all five messages: logging in is never a requirement for keeping the project moving. Some of the people you onboard will answer every email and never once open a workspace, and the email versus portal comparison works through what that means for your setup.

How to tell in week two whether onboarding worked

Onboarding worked if, in week two, nobody asks you where to send something. Three other signals matter. You can name the approver for every open decision without checking your notes. Every item you requested has a person and a date attached to it, even the late ones. And you could answer the question "what are we waiting on right now" in under ten seconds.

If any of those fail, the gap is in your week one messages, not in the client. Find the missing sentence and add it to the template.

If you do only one thing this week

Write message 2 once, for your own agency, and save it where you can paste it in ten seconds. That single message answers where things live, who to contact, how fast you reply, how to reach you in a real emergency, and how to answer you without logging in. It takes about twenty minutes to write and it is the highest return twenty minutes in your process.

Then send a version of it to two clients you are already mid project with. Retro onboarding is allowed. "Quick reset on how we will handle the rest of this project" is a completely normal message to send in week six, and clients tend to read it as competence rather than as an apology.