Action Tracking and Workflow System
One register, whatever raised the action
The number worth watching is not how many are open. It is how old the oldest one is.
We put every action on one register with an owner and a date, whatever raised it. Studies, audits, inspections and incidents each generate actions and each keeps them in the system that produced them, so nobody holds the whole queue and a hazard study recommendation reaches its fourth year unnoticed.
- Hazard study recommendations
- Audit and inspection findings
- Incident and near miss actions
- Management of change conditions
- Regulatory undertakings
- Management review decisions
One register
One owner, one date, one escalation path, whatever raised it
Four rules that make it work
- An owner and a date at creation
- An action without either is a note, and notes do not get done.
- Escalation runs on the calendar, not on a person
- Reminders climb the line as the date approaches and passes, so chasing is not what keeps the queue moving.
- Evidence at closure
- Closure carries the document, photograph or test record that shows the action was done.
- Revision is visible
- Closing by quietly rewriting the action shows as a revision, not a completion.
Approval happens in Teams or Outlook, so nobody has to open a second system to unblock somebody else.
What a single register exposes
A single register makes the backlog undeniable. Sites that were carrying four year old study actions will see them on the front page, and somebody will have to decide whether to resource them or formally accept the risk.
Put every action on one register
We will come back with the register design, the escalation rules and a delivery timeline. Tell us which systems raise actions today and who is accountable for closing them.