Appearance
Actions
Actions are trackable work items for production-floor problems and manager decisions. Defect and deviation actions link a failure back to the check that found it and close the loop on corrective work. Review actions ask a manager to decide whether a temporary target trial should become permanent or be reverted.
How Actions Are Created
Automatic Actions
Continual raises automatic actions when a result or review decision needs follow-up:
- A failing CIL check creates a defect action.
- An out-of-target Centreline check creates a deviation action when the Operator records that they left it for follow-up. A reading corrected immediately or linked to a target dispute does not create new corrective work.
- Accepting a target proposal as a temporary trial creates a review action for the final verdict.
Only one active automatic action of each category exists per check at a time. If a check keeps failing, the existing defect or deviation action accumulates the failure count rather than creating duplicates. A review action remains open until its trial verdict is recorded.
When a reviewer rejects a fail-linked target proposal, they can raise a deviation action from the rejection. The review note becomes the action description; if an automatic action is already active for the check, the note is added to that action instead of creating a duplicate.
Auto-close for deviations: A deviation action closes automatically when the next result for that check passes. This reflects the nature of centreline deviations — often transient and self-correcting.
Manual resolution for defects: A CIL defect action requires explicit resolution by a Manager or Admin, followed by verification that the fix held.
Manual Actions
Team Leaders, Managers and Admins can raise actions manually within their assigned scope — for example, to capture an observation that did not come from a failing check, or to record a corrective task that needs tracking.
- In the portal, go to
Operations->Actions. - Click
Create action. - Select the factory, Line or Group, and machine.
- Enter a title and optional description.
Team Leaders, Managers, Admins, and Owners can also create manual actions from the Actions tab in the mobile app.
Action Lifecycle
Corrective actions can move through three statuses:
| Status | Meaning |
|---|---|
| Open | The problem exists and has not been addressed. |
| Pending verification | A resolution has been submitted; awaiting confirmation that it held. |
| Closed | The action is fully resolved and verified. |
Review actions use a shorter lifecycle: they remain Open while the temporary target trial awaits a verdict, then move directly to Closed when a manager records that verdict. They do not use pending verification.
Resolving a Defect or Deviation
When you have addressed the root cause:
- Open the action (portal or mobile).
- Select
Resolve. - Add a resolution note describing what was wrong and what was done to fix it.
- Optionally attach photos or videos as evidence of the fix.
- Submit.
The action moves to Pending verification. It closes automatically when a subsequent check result for that check passes, confirming the fix held.
Deviation actions may also close automatically when the next result for the check passes, without a manager submitting a resolution first.
Reviewing a Temporary Target Trial
Open a review action to see which format the trial covers and to compare the original and temporary targets, each labelled with its check version. A trial timeline plots every reading from 14 days before the trial started up to today (or up to the verdict), marking the start, the expiry, and the time left. Beneath it, compliance before and since the trial sit side by side, with the pass count and scheduled completion rate behind each figure, and the person who proposed the temporary target is shown with the reason they gave. You can also open the related check timeline. The timeline shows the newest activity first and links the trial's readings, proposal, definition versions, expiry and verdict back to the review action. You can still edit the action title and description or attach supporting media from the notes panel.
Managers, Admins, and Owners record one of two verdicts with a required resolution note:
- For an active trial, Keep permanently leaves the temporary target in place, while Revert now restores the original target immediately.
- For an expired trial, the original target has already been restored. Keep the trial value permanently reapplies the trial value, while Confirm revert leaves the restored original target in place.
If the action or affected target changed while the review was open, the verdict is not recorded. The panel refreshes the current trial and check state, shows the API's conflict detail, and leaves the action open so the reviewer can reassess it.
Once a verdict is recorded, the trial evidence and resolution note remain available as a read-only decision record. The action timeline shows who made the decision.
Viewing Actions
In The Portal
Go to Operations -> Actions to see all actions across your factories. Filter by:
- Factory, line, or machine
- Status (open, pending verification, closed)
- Category (defect, deviation, or review)
- Date range
Click an action to see its full history, including every state change and who made it.
In The Mobile App
The Actions tab in the mobile app shows open and pending actions for your assigned locations in the selected factory. It opens filtered to your own team's work, so you can see exactly what your team owns. The TEAM filter lets you switch to unrouted-only or all teams, and remembers your choice next time you open the tab. Tap an action to view details or submit a resolution.
Actions In Insights
The Analytics -> Insights -> Actions tab gives a cross-category view of every action (defects, deviations, and manual), including:
- Count of actions created per period, by category
- Median time to resolution (MTTR), by category
- Top affected machines
The Defects and Deviations tabs give the same kind of breakdown scoped to just that category — Defects additionally shows a resolution-time distribution (how long defects take to close, bucketed).
See Insights for details.
Who Can Do What
| Action | Operator | Manager | Admin | Owner |
|---|---|---|---|---|
| View actions | ✓ | ✓ | ✓ | ✓ |
| Create manual action | ✗ | ✓ | ✓ | ✓ |
| Resolve an action | ✗ | ✓ | ✓ | ✓ |
| Record a trial verdict | ✗ | ✓ | ✓ | ✓ |
Auto-close is system behaviour, not a user permission: a deviation action closes automatically when the next result for its check passes, regardless of who submitted it.