Building an Action Log That People Actually Use
Every project generates decisions and follow-ups faster than anyone can remember them. The team agrees to chase a supplier, confirm a permit, or revise a number, and three weeks later nobody can say whether it happened. In 2022 that gap costs more than usual: with materials lead times stretched and labour hard to hold, a forgotten action is not a tidy-up item, it is a slipped milestone. The fix is not a better tool. It is a small, boring discipline that the team trusts enough to keep using.
An action log is the simplest accountability mechanism in project management, and the most commonly abandoned. People start one, fill it with vague entries, stop updating it, and quietly go back to email. The difference between a log that sticks and one that dies is almost entirely in how each action is written and how the list is run.
Write actions that can actually be closed
A good action is unambiguous about who, what, and when. "Look into the steel order" is not an action; it is a worry. "Sam to confirm the revised steel delivery date with the fabricator and email the team by Feb 4" can be done, checked, and closed. Capture each one in the same shape every time.
One owner, named. A team is not an owner. If two people share an action, it will fall between them. Assign a single person, even if they delegate the work.
A verb and a result. State the outcome you expect to see, not the activity. "Decide on the cladding sample" beats "discuss cladding."
A real due date. Pick a date the owner agrees to, not a hopeful one. A date nobody believes is worse than no date.
Where it came from. Note the meeting or decision that spawned it, so context survives when memory fades.
Run the list, do not just keep it
A log only works if it is reviewed on a rhythm the team can rely on. Open every status meeting with the open actions, in due-date order, and spend two minutes per item: done, on track, or stuck. Resist the urge to re-explain finished work. The point is to surface the items that are about to slip while there is still time to act.
Keep one master list, not a copy in every inbox. Scattered versions are the same as no version.
Track only actions, not status updates or risks. Mixing them turns the log into noise.
Close items visibly. People stay honest when they can see progress, and a list that only grows feels hopeless.
Age the overdue items. Anything past due for two reviews needs a different conversation, not another nudge.
When something is stuck, the log should make that visible quickly so the project manager can clear the blocker, renegotiate the date, or escalate. In a year of supply volatility, that early warning is the whole value. The discipline is modest, but a well-run action log is often the difference between a project that drifts and one that lands.
If you want help putting a lightweight tracking discipline in place across a portfolio, XNM's program & project delivery advisory can set it up with you.