The First Thirty Days: A Client Onboarding Playbook for UK Consultancies

Most client relationships are decided long before the first invoice. The first thirty days establish the pattern: who decides, how quickly people respond, what counts as an urgent request, and whether changes are recorded or absorbed. Firms that treat onboarding as an administrative formality tend to spend the rest of the engagement repairing assumptions.

The playbook below is designed for UK consultancies and professional services firms. It is deliberately practical. It assumes a signed engagement letter, a named client sponsor and a delivery team that has other work to do. It does not require new software. It does require discipline in the first month.

Days 1 to 3: The kick-off that produces decisions

A kick-off meeting should not be a tour of the proposal. It should produce decisions. Send an agenda in advance with four items: outcomes, roles, constraints and the change process. Ask the client to confirm who can approve work, who can request changes, and who will sign off deliverables.

Record the answers in a short note and circulate them within one working day. This note is not a formality. It is the reference point when a request arrives in week six that was never discussed in week one. In UK collaboration, where indirect phrasing is common, written confirmation is a courtesy as much as a control. It prevents the slow drift that occurs when everyone is trying to be agreeable.

Days 4 to 10: The written agreement behind the engagement letter

The engagement letter governs the contract. The onboarding note governs the working relationship. Keep it to two pages and cover:

• The agreed outcomes and the measures of success.
• Named decision-makers on both sides, with deputies.
• The communication rhythm: weekly call, fortnightly report, or monthly review.
• Response expectations, stated realistically. A promise of same-day replies is usually a promise that will be broken.
• The change process: how a new request is raised, estimated, approved or declined.
• The boundary between advice and implementation.
• How documents and data will be shared, stored and returned.

Circulate the note for confirmation rather than comment. A request to confirm produces a clearer response than an invitation to review.

Days 11 to 20: Establish the communication rhythm

Scope creep often grows in the gaps between formal meetings. A client who cannot see progress will ask for updates; a client who receives a predictable update has less reason to interrupt. Set a rhythm and keep it, even when there is little to report. A short written update is more useful than a long meeting.

Agree the channel. Email for decisions and approvals; collaboration tools for working documents; calls for sensitive or ambiguous matters. Do not let urgent requests arrive through three channels with no record. If a client asks for something on a call, confirm it by email with a one-line summary and the impact on time or cost.

There is a UK-specific point here. Clients often soften requests with phrases such as when you get a moment or just a quick thought. The polite form does not reduce the work. Treat the substance, not the tone. A short reply that states the request, the estimated effort and the effect on the agreed plan is not confrontational; it is clear.

Days 21 to 30: The first review and the first change control

Hold a thirty-day review before the first invoice if possible. Cover three questions: what has worked, what has been slower than expected, and what needs to change in the working arrangement. Use the review to test the change process with a real example. If a small request has already arrived, show how it was recorded and priced. This establishes the norm while the relationship is still new.

If no change has arrived, do not invent one. Instead, confirm the process in writing: requests will be assessed against the agreed outcomes, estimated before work begins, and approved by the named sponsor. This gives the client a route to say yes as well as a route to say no.

The scope-creep controls

Scope creep is rarely malicious. It is usually the accumulation of small, reasonable requests made by people who do not see the cumulative cost. Five controls reduce it:

• A named approver for changes, not a general client contact.
• A simple change note: request, reason, estimate, impact, decision.
• A weekly written update that shows progress against the agreed plan.
• A rule that verbal requests are confirmed in writing before work starts.
• A thirty-day review that examines the working relationship, not only the deliverables.

Template checklist

Use the following as the basis for a one-page onboarding template.

• Engagement letter signed and filed.
• Client sponsor and deputy confirmed in writing.
• Delivery team roles and decision rights confirmed.
• Kick-off agenda issued in advance.
• Outcomes and success measures agreed.
• Communication rhythm and channels agreed.
• Response expectations stated realistically.
• Change process described and accepted.
• Data-sharing and confidentiality arrangements confirmed.
• First written update issued on schedule.
• Thirty-day review booked.
• First change, if any, recorded and approved before work begins.

Onboarding is not a courtesy sequence. It is the point at which the commercial relationship is made operational. Firms that invest a few structured hours in the first thirty days usually spend fewer unstructured hours repairing the relationship later.