Brief, Check, Hand Over: A Three-Meeting Rhythm for UK Consultancy Projects

Most UK consultancy projects have a full diary and a thin decision trail. The kick-off is pleasant, the mid-point review is crowded, and the close-out is rushed before the next piece of work begins. The result is a project that feels busy but leaves the client unsure what was agreed, what changed and what is now owned by whom.

A simpler rhythm works better. Three meetings, each with a single job, give the client and the consultancy a clear control system without adding layers of governance. The meetings are not a ritual. They are decision points.

1. The scoping kick-off: agree the job, the boundary and the evidence

The first meeting is not an inspiration session. Its purpose is to agree what the engagement will change, what it will not touch and how success will be judged. Without that clarity, the project will drift towards whatever is most visible in the final weeks.

Who should attend: the client sponsor, who is accountable for the outcome; the day-to-day client lead; the consultancy delivery lead; and subject experts only where they are needed to define scope. Finance or procurement may attend for budget and contractual points, but they do not need to stay for the whole session.

Decisions this meeting must produce:

• A one-sentence problem statement that both sides accept.
• A clear in-scope and out-of-scope boundary.
• Success measures that can be evidenced, not just described.
• A named client-side counterpart with time and authority to work with the consultancy.
• Decision rights: who can say yes, who can say no and who must be consulted.
• A meeting and reporting cadence that fits the project, not the consultancy's template.
• An agreed definition of handover, including what the client team must be able to do at the end.

Useful questions for the chair: What will be different in three months? What are we deliberately not doing? How will we know it is working? What does good handover look like? Who can make the final call?

The note should be one page: decisions, actions, owners and dates. It should not be a transcript. If the kick-off produces a long document that nobody reads again, the meeting has failed its main test.

2. The mid-point sense-check: test the evidence, not the deck

The second meeting exists to course correct before the close-out. It is not a progress update. It is a check on whether the original hypothesis still holds, whether the evidence is strong enough and whether the client team is building the capability it will need later.

Who should attend: the client sponsor, the client lead, the consultancy delivery lead and the people who will use the output. For some projects, finance or operational colleagues should attend because they own the risk or the budget. Keep the group small enough to make decisions.

Decisions this meeting must produce:

• Continue, change or stop. All three are valid outcomes.
• Confirm or revise the success measures agreed at kick-off.
• Resolve the main blockers, or assign an owner and a date for resolving them.
• Confirm the final scope and rule out late additions that would weaken delivery.
• Check handover readiness: is the client team being trained, involved and given access to the work?

The chair should ask four questions: What has changed since kick-off? What are we recommending? What decision is needed today? What is the risk if we do nothing? These questions keep the meeting focused on judgement rather than activity.

The note should follow the same format as the kick-off note: decisions, actions, owners and dates. Add a short section on changes to scope or success measures. If the meeting cannot produce a decision, record that fact and set a date for the decision. Ambiguity is not a neutral outcome; it is a cost carried by the project.

3. The close-out handover: prove the capability has moved

The final meeting is not a presentation. It is a handover. The test is whether the client team can run the core process, defend the recommendations and manage the residual risks without the adviser in the room.

Who should attend: the client sponsor, the client team who will own the work after the engagement, the consultancy delivery lead and, where relevant, finance or legal for contract close. End users should attend if they will operate the new process. The meeting should be practical, not ceremonial.

Decisions this meeting must produce:

• Acceptance or rejection of the deliverables against the agreed success measures.
• Confirmation of ownership for each output, process and risk.
• Sign-off of residual risks and the plan for managing them.
• Agreement on any post-engagement support, with a clear limit and exit point.
• Closure of open actions, or transfer of those actions to a named owner with a date.

The chair should ask: Can the client team run this next month without us? Where does the knowledge live? Who has been trained? What remains uncertain? What should the client stop doing now? The answers should be recorded, not simply discussed.

The handover pack should be short and usable: a decision log, a risk register, an ownership map, a process summary and evidence of training. If the pack is long but the client team cannot explain it, the handover has not happened.

Keeping notes short enough to be useful

Meeting notes are useful only if someone can read them in five minutes and see what changed. A simple format works for all three meetings:

• Decisions made.
• Actions agreed, with owner and date.
• Open questions, with owner and date.
• Changes to scope, budget, risk or success measures.

Circulate the note within one working day. Store it in a client-owned system. Keep a single decision log across the project so that later meetings do not reopen settled points without reason. Avoid verbatim minutes unless there is a legal or contractual need. A good note is not a record of everything said. It is a record of what has been agreed.

A rhythm, not a ritual

Three meetings will not solve every problem in a UK consultancy project. They will, however, give the client a simple control system: agree the job at the start, test the evidence in the middle and prove the handover at the end. Each meeting has a decision. Each note is short enough to use. That is a better use of time than another crowded review with no clear outcome.