How to Run a Client Action Register

The workshop ends with energy. Everyone agrees on the next steps. Three days later, nobody is sure who owns the data request, when the sponsor will review the recommendation, or whether the follow-up meeting was booked.

The problem is not a lack of commitment. The commitments were never turned into a shared operating record.

A client action register is a short list of open actions, owners, due points, and status. It gives the project one place to answer: what must happen next?

Record actions as outcomes

Write each action so that a new reader can tell when it is complete. “Follow up on data” is not enough. “Client operations lead sends the last six months of service data” is testable.

Use a simple structure:

The owner should be one person. Other people can help, but shared ownership often means nobody knows who must close the loop.

Separate actions from decisions

An action produces an output. A decision chooses a path. Keep them distinct.

“Review the recommendation” is an action. “Approve option B” is a decision. If you mix the two, a task can look complete even though the project is still waiting for a choice.

Link decisions to a decision log or label them clearly in the register. That makes the real constraint visible.

Use due points that match the work

Not every action needs an arbitrary calendar date. Some are tied to a milestone: before interviews begin, before the steering meeting, or before the draft can be finalized.

Name the consequence as well. If an input arrives late, what moves? This is not a threat. It helps the client understand why the timing matters.

Review only what is open

Do not read the entire register aloud in every meeting. Start with overdue actions, then cover anything due before the next check-in. Close completed items and preserve them for the project record.

When an action stalls, ask a useful question: Is the owner wrong? Is the requested output unclear? Is another decision blocking it? Fix the condition instead of sending the same reminder again.

End every meeting with confirmation

Reserve the final two minutes to read back new actions, owners, and due points. Send the updated register with the meeting recap while the context is fresh.

The register should make follow-up lighter, not create another reporting chore. Keep it short, current, and tied to the next milestone. When every promise has an owner and a clear finish line, the project can move without constant chasing.

[Keep client work clear from conversation to completion](https://getconsultkit.com)