How to Keep Clients Accountable Between Quarterly Strategy Reviews

The short answer: put one name and one date on every commitment, ask for a small update every week, look at the measures once a month, and agree in advance what happens when something is stuck. Quarterly meetings alone cannot do this — eleven weeks pass between them, and the meeting becomes archaeology.

Why quarterly meetings alone leave gaps

A quarter is long enough for an initiative to be re-scoped, its owner to change roles, and its measure to stop being collected — all without anyone deciding anything. By the time the review arrives, the team is reconstructing what happened rather than deciding what to do next. The first 30 minutes go on establishing facts, which is the most expensive way to spend a room full of senior people.

The fix is not more meetings. It is a small amount of visible movement between them.

1. Ownership that survives contact with the org chart

Every initiative, action, milestone and measure needs:

• One owner. A named person, not a department and not two co-owners. Shared ownership reliably produces no ownership.
• A date. Even an imperfect date. "Q3" is not a date.
• A definition of done. One sentence a third party could check.

If a commitment cannot get all three, it is not ready to be committed to — put it in a parking list and say so out loud in the review.

2. Weekly, where the work is weekly

Weekly is right for actions with near-term dates. It is wrong for annual outcome measures, and asking for weekly updates on them teaches people to ignore requests.

A workable weekly ask is one line per open action: still on track, at risk, or done. Two minutes per owner. In StrategyHub, owners see only their own items in a personal work queue, so the ask is small; a tokenized update link lets someone submit a value or a status without a full sign-in.

3. Monthly, for measures and progress

Once a month, look at:

• Measures due this month, against baseline and target.
• Initiatives whose percent-complete has not moved.
• Anything overdue.
• Anything with no update at all.

Send a short written note to the sponsor: what moved, what did not, what you need from them. No meeting required. This note is what makes a retainer visible in the months where nothing dramatic happens — see running strategy work as a retainer.

4. An escalation path agreed in advance

Most blockers are not mysteries. They are a decision nobody has authority to make, or a resource nobody has released. Agree the path before you need it:

1. Owner marks the item blocked and names what is blocking it.
2. If it is still blocked after two weeks, it goes to the sponsor with a specific ask.
3. If the sponsor cannot resolve it, it goes on the next review agenda as a decision item, with options.

Escalation with an ask attached gets resolved. Escalation as a status colour does not.

5. Distinguish a missing update from poor performance

This distinction is the difference between a consultant who is trusted and one who is resented. A blank field means one of:

• The owner is busy and has not updated.
• The data is not being collected.
• The work has genuinely stalled.

They call for different conversations. Ask before you conclude — and never present an empty field in a leadership meeting as evidence of failure. Where a measure has no recent value, say exactly that: "no update recorded since 12 June; owner to confirm whether the data is still being collected."

A sample accountability agreement

Agree this in writing at the start of the engagement, one page:

> Between reviews > - Each action owner updates their open items weekly (one line: on track / at risk / done). > - Each measure owner records a value on the agreed cadence. > - The advisor sends a monthly written progress note to the sponsor. > > When something is blocked > - The owner marks it blocked and names the blocker within the week. > - Unresolved after two weeks, the advisor raises it with the sponsor. > - Unresolved after that, it becomes a decision item on the quarterly agenda. > > What the advisor does not do > - Update the client's items on their behalf. > - Present missing updates as performance failures. > > What the sponsor commits to > - Responding to escalations within five working days. > - Chairing, or attending, each quarterly review.

A worked example, commitment to resolution

Fictional, to show the shape:

• Week 0 (review). Commitment: "Publish the revised permitting checklist." Owner: Deputy Director. Due: 30 September. Definition of done: checklist published on the internal site.
• Week 3. Owner marks it at risk — legal review not scheduled.
• Week 5. Still at risk. Advisor raises it with the sponsor with a specific ask: two hours of legal review time in the next fortnight.
• Week 6. Sponsor schedules it. Status returns to on track.
• Week 9. Marked done, with the published link recorded against the action.
• Week 12 (review). Two minutes on it, because the history is already written down.

Nothing here required software. It required someone noticing at week 5 instead of week 12.

How StrategyHub supports this

• Owners and due dates on goals, initiatives, actions and milestones, with a personal work queue per owner.
• Baseline, current and target values on measures, so drift is visible rather than argued about.
• Update request links and reminders, so chasing is not a manual email exercise.
• A risk and blocker register, so an escalation has a record rather than living in someone's inbox.
• Reporting and executive summaries drawn from the same records, so the monthly note and the quarterly pack do not need rebuilding.
• Prepare Client Review, inside the product, assembles what is overdue, what changed, which measures are missing updates, and which decisions need the sponsor — and keeps recorded facts, calculated indicators and AI suggestions clearly separated.

Software makes state visible and reduces the chasing. It does not create accountability. That still comes from a client leader who expects updates and an advisor who follows through.

A reusable checklist

Weekly

• [ ] Every open action has a status no older than seven days.
• [ ] Newly blocked items name their blocker.

Monthly

• [ ] Measures due this month have values recorded.
• [ ] Initiatives with no movement in 30 days are flagged.
• [ ] Written progress note sent to the sponsor.
• [ ] Blockers older than two weeks escalated with a specific ask.

Before each quarterly review

• [ ] Overdue list current.
• [ ] Missing updates identified and queried with owners, not assumed.
• [ ] Decision items drafted with options.
• [ ] Previous review's follow-ups closed or carried forward explicitly.