Action Tracker

The Action Tracker in PRISM is your cross-team follow-up list — corrective tasks from incidents and observations, permit conditions, meetings, and operational commitments — with owners, due dates, and status visibility.

Purpose

Safety and operations generate actions that outlive a single shift. Action Tracker prevents follow-up from living only in email or spreadsheets by giving each item an owner, due date, status, and evidence trail so supervisors and HSE can see what is open, overdue, or ready to close.

Who uses this

• Action owners — do the work and update status with proof of completion
• Assigners / HSE — create actions from incidents, observations, audits, or meetings
• Supervisors — monitor overdue items for their area or team
• Management — review open and overdue counts during pilot check-ins

Typical workflow

1. An action is created with title, description, owner, due date, and priority.
2. The owner acknowledges the assignment and moves work to In progress when started.
3. Comments and attachments document progress, blockers, or completion evidence.
4. When work is finished, the owner marks the action Completed.
5. The assigner or HSE verifies close-out where your process requires it.
6. Actions past due without progress appear as Overdue for escalation.

Roles and responsibilities

• Assigner — writes clear, achievable actions with realistic due dates and a single accountable owner.
• Owner — updates status honestly; escalates blockers before the due date passes.
• Verifier — confirms the fix addresses the underlying issue, not only the symptom.
• HSE / process owner — chases overdue pilot-scope actions in routine reviews.

Evidence / attachments

Each action should stand alone for someone reviewing close-out later:

• Clear title and description of what must change
• Owner, due date, priority, and linked source record when applicable (incident, observation, etc.)
• Progress comments and files showing completion (photos, sign-off documents, work orders)
• Status history from open through completed or cancelled

Status lifecycle

• Pending — assigned and awaiting start
• In progress — owner is actively working the item
• Completed — work finished and recorded
• Overdue — past due date without completion (display status for escalation)
• Cancelled — no longer required, with documented reason

What pilot users should do

• Create actions in REACTOR for every agreed follow-up from incidents, observations, and pilot meetings — not parallel trackers.
• Assign one owner per action; use due dates that match real resource availability.
• Review the Action Tracker in weekly HSE or operations meetings; escalate overdue items to supervision.
• Attach completion evidence before marking done — especially for actions tied to incident close-out.
• Tell your process owner if filters, notifications, or project scoping need adjustment during the pilot.

Where to open it in REACTOR

• PRISM → Action Tracker — list, filter by status/assignee, and update tasks
• Related: Incident Management, Observations