Verify a completed action

In a Corrective and Preventive Action (CAPA) workflow, marking an action complete isn’t enough. Someone other than the do-er has to verify the fix actually works. SteadyOn captures both steps: Completed and Verified.

Lifecycle

Open  →  In progress  →  Completed  →  Verified
                              │
                              └──→  (rejected, return to In progress)

Steps to mark complete (any member)

1. Open the action.
2. Click Edit in the kebab menu (⋯).
3. Set Status to Completed.
4. Add a description note: what was done, when, and any evidence.
5. Optionally attach photos or documents on the Attachments tab.
6. Save.

Steps to verify (admin or owner)

1. Open the completed action.
2. Inspect the evidence — read the description, look at the attachments, confirm the fix is real.
3. Click Edit in the kebab menu (⋯).
4. Set Status to Verified.
5. Save.

The action’s BRAG turns blue. It drops out of the dashboard’s red / amber counts.

Role check. A server-side guard ensures only admins and owners can move an action into the Verified state. If a member tries, the action remains in Completed status. The full role check is being tightened — see your org’s owner if you’re unsure.

What “verified” means in practice

Verified is not “the worker says it’s done”. It’s “someone with authority confirmed the fix works as intended”. For most actions this means:

• The control is physically in place (e.g. you walked over and looked).
• It’s behaving as expected (e.g. the new mat is grippy underfoot).
• Anyone affected has been told (e.g. the team knows the new procedure).

If any of those aren’t true, don’t verify — bounce it back to In progress with a note.

See also

• The CAPA workflow — why verification matters.
• User roles and permissions — exactly who can verify.