Client onboarding documents: the 5 every agency should send in week one
Week one is loud, then quiet, then the client gets nervous. The arc is so predictable that you can almost set a calendar to it. Five short documents in the first week kill that arc and replace it with momentum. None of them takes more than an hour to build, and once you have them as templates, the time per engagement is minutes.
1. The welcome note
Not a contract. A two-paragraph note from the partner or account lead, on the day of signing, that says three things: we are glad to be working together, here is what happens this week, here is your point of contact.
Send it from a real inbox, not a workflow tool. The first message after signing is the loudest one in the relationship. Make it feel human.
2. The kickoff agenda, sent before the kickoff
A one-page agenda for the kickoff meeting, shared 48 hours in advance. Topics, time per topic, who is leading, what each side should bring.
The single most underrated move in agency onboarding is sending the agenda before the meeting. It signals that the meeting will be useful, gives the client time to gather inputs, and turns a sales handoff into a working session. Agencies that skip this step lose the room.
3. The contact map
A short document showing who on your team owns what, and the same for the client side. Names, roles, response time expectations.
The contact map answers the question every client has on day three: who do I email about this. Without it, every question routes to the account lead and the team feels slower than it is.
Two columns is enough. No org chart.
4. The access checklist
Everything the team needs from the client to get started, in one list, with a deadline. Analytics access, file shares, brand assets, stakeholder availability, login credentials.
The mistake here is collecting access as you go. You do it in batches, and the client never knows what is coming. Sending the full list on day one means the client can knock it out in one sitting and the team is not waiting on credentials in week three.
5. The working agreement
Half a page. How the team communicates, what tools the work lives in, what counts as a quick question versus a meeting, what the response times look like on both sides.
This sounds soft. It is not. Most engagements drift on communication norms long before they drift on scope. A short working agreement up front saves the awkward "can we talk about how we are working together" call six weeks later.
How to ship all five at once
If you put these into a single document hub at the start of the engagement, the client sees them as a set, not a stream. One page links to all five. The welcome note is the first thing they read. The other four are there when they reach for them.
Sending them as five emails over five days is fine if that is what you have. Sending them as five attachments on the same email is worse, because half of them never get opened.
Why week one matters more than week six
The client decides whether you are organized in the first ten days. They will not tell you that decision out loud. They will renew or not renew on it.
Six weeks of excellent work cannot fully fix a sloppy first week. The reverse is also true: a clean first week buys you patience when something later goes sideways, and something later almost always does.
What to skip
Onboarding decks longer than five slides. A 20-slide welcome deck reads as bureaucracy.
Generic "Welcome to the team" videos with stock B-roll. Either record a real one from the account lead or do not record one at all.
Surveys before the kickoff. The kickoff is your survey.
Where Docsiv fits
We built Docsiv so all five of these documents can live in a single branded client portal alongside the contract, the proposal, and everything that comes after. One link, one home, one experience. The client sees the engagement as one firm instead of a stack of tools.
Templates for each of these documents are minutes to set up and reusable across every engagement. The first week stops being the most operational week of the year.
Frequently asked questions
Tap a question to expand the answer. The same content is in structured data on this page for search.
What documents should an agency send during client onboarding?
Five that earn their keep: a short welcome note, a kickoff agenda sent ahead of the meeting, a two-column contact map, an access checklist with a deadline, and a half-page working agreement. Each takes under an hour as a template.
Why does week one of an engagement matter so much?
Clients form their durable impression of how organized you are inside the first ten days. They will not articulate that judgment, but they will renew or not renew on it. A clean first week buys patience later.
What goes in a kickoff agenda?
Topics, time per topic, who is leading, and what each side should bring. Send it 48 hours before the meeting so the client can gather inputs. Sending the agenda after the meeting defeats most of the point.
Should the agency build a contact map for the client?
Yes. Two columns, your team and theirs, names and roles and response time expectations. It answers the question every client has on day three, which is who do I email about this.
How early should an agency send the access checklist?
Day one of the engagement, with a clear deadline. Sending a single list once is faster for the client than asking for credentials in batches over three weeks, and it stops the team from waiting on logins in week three.
Related posts
Multi-stakeholder deals: how silent committee buyers stall good work
"Send it to the team" is rarely a yes. It is more often the moment a deal goes dark. How multi-reader buying behaves, and how to keep momentum without nagging.
Docsiv Team
Approvals in email are a graveyard: a saner way to get sign-off on creative
Threads splinter, files multiply, somebody forgets to reply-all. The email approval loop is the top cause of stalled creative. A simple alternative your team will actually use.
Docsiv Team
Custom domain for your client portal: why portal.youragency.com beats a shared subdomain
A portal on portal.youragency.com reads as infrastructure. A portal on tool.io/youragency reads as a SaaS subscription. The URL is doing more PR than you think.
Docsiv Team