Action Lifecycle
The action lifecycle in uAuditor describes the stages an action passes through from creation to completion. Understanding this lifecycle helps teams track issue resolution clearly and ensures corrective work is completed within expected timelines.
Each action moves through structured status updates that reflect its progress and resolution level.
Overview of the Action Lifecycle
An action typically progresses through the following stages:
- Action created
- Action assigned
- Work in progress
- Action completed
- Action verified or closed (if applicable)
These stages provide visibility into how operational issues are handled across locations.
Action Creation
The lifecycle begins when an action is created.
Actions can be created:
- automatically from failed inspection responses
- manually by supervisors or administrators
- from observations during operational reviews
- as follow-up tasks outside inspections
At this stage, the issue is officially recorded and ready for assignment.
Action Assignment
After creation, the action is assigned to a responsible user.
Assignment includes:
- selecting the responsible person
- defining a due date
- setting priority (if enabled)
- linking to inspection, location, or asset
Clear assignment ensures accountability from the start.
Action In Progress
Once the assigned user begins working on the issue, the action status may change to In Progress.
During this stage, users may:
- update action status
- upload evidence 📷
- add comments
- coordinate with supervisors
- document corrective steps
This stage reflects active resolution work.
Action Completion
An action becomes Completed when the assigned user confirms the issue has been resolved.
Completion may include:
- uploading supporting evidence
- documenting corrective steps taken
- confirming compliance restoration
- attaching repair or verification photos
Completed actions remain visible for reporting and auditing purposes.
Action Verification (If Required)
In some workflows, supervisors review completed actions before final closure.
Verification ensures:
- the issue was resolved correctly
- evidence supports the resolution
- corrective work meets operational standards
After verification, the action may be marked as closed depending on configuration.
Overdue Actions
If an action is not completed before its due date, it becomes Overdue ⏱️
Overdue actions help supervisors:
- detect delays quickly
- follow up with responsible users
- prioritize unresolved risks
- maintain operational discipline
Monitoring overdue actions improves response performance across teams.
Tracking Action Progress
Throughout the lifecycle, action progress can be monitored from the Actions module.
Users can track:
- current status
- assignee
- due date
- related inspection
- attached evidence
- activity history
This ensures transparency across corrective workflows.
Why the Action Lifecycle Matters
Managing actions through a structured lifecycle helps organizations:
- resolve inspection failures faster
- improve accountability across branches
- reduce repeated operational issues
- maintain compliance readiness
- strengthen execution quality across teams
Following the action lifecycle ensures that identified issues move from observation to verified resolution in a consistent and traceable way.
