The short version
- Onboarding is a trust problem before it is a delivery problem.
- Get access with the minimum scope and write the mandate down.
- Kickoff is for decisions, not introductions.
- Send a 30/60/90 in the first week — it replaces a dozen status questions.
- Keep one handover file that survives staff changes.
Before day one
Send a single access request list with the exact scopes you need and why. Ask for a named decision-maker and a response window. Confirm what is explicitly out of scope — the cheapest way to prevent the scope creep that poisons a retainer.
Write the mandate
One page: what you may do, what you must never do, who approves what, and how quickly. For anything client-facing, the approval path is written, not implied. This protects both sides and is the first thing to point at when something goes wrong.
Kickoff is for decisions
Not a tour of your credentials. Bring three decisions: success metric for the quarter, the first deliverable and its date, and the one constraint that cannot move. Leave with those three written down and confirmed.
The 30/60/90
First month: audit, access, and one quick win. Second: the main build. Third: measure, report, and propose the next phase. Send it in week one — it converts ‘what are you doing?’ into a shared calendar.
Comms rhythm
One weekly written update, one monthly report, one quarterly review. The weekly update is three lines: done, next, blocked. It is the single highest-leverage habit in client retention because silence reads as drift.
The handover file
Accounts, accesses, decisions, brand rules, and the ‘why’ behind the plan. When a teammate leaves — or the client asks for the keys — this file is the difference between professional and chaotic.
Checklist
- Access request list with exact scopes
- One-page mandate signed (may/must-not/approvals)
- Kickoff produced three written decisions
- 30/60/90 sent in week one
- Weekly three-line update scheduled
- Handover file created and shared
If you would rather hand this over
AMAN's scribe (Katib) drafts the onboarding pack from your standard template, sets up per-client mandates with scoped, expiring access, and keeps the weekly update drafted from the actual work log. You review and send.
Questions people actually ask
How long should onboarding take?
Two weeks to full delivery is a reasonable target for a small account; complex ones need a month. What matters is that the client knows the dates.
What access should I ask for first?
Read-only first, then scoped write access once the mandate is signed. Ask for the minimum that lets you deliver the first milestone.
How do I stop scope creep?
Name what is out of scope in the mandate, and answer new requests with a written change note: what it replaces, what it costs, when it can start.