Actions & Approvals

Every step.
Every signature.

Actions raised in NCRs, audits, meetings, MOCs, and exemptions all live in one queue — assigned, due-dated, and tied back to the record they came from. Approvals route by policy, with passkey step-up on the calls that matter.

app.qformance.io / actions

Actions

All modules · 47 open · 12 awaiting your sign-off
My actionsTeamAllApprovals
ACT-2026-0182Corrective
Replace worn LOTO tags on Press 4
NCR-2026-0418
S. Romero
Due 22 Apr
ACT-2026-0179Approval
SOP-MX-04 v3.2 — Engineering sign-off
DOC-MX-04
M. Patel
Awaiting · 2 of 3
ACT-2026-0173Verify
Confirm M-0102 returned to nominal
MOC-0102
L. Chen
Verify · in meeting
ACT-2026-0162Preventive
Add PPE check to weld-bay daily walk
AUD-2026-014
J. Tan
Closed · 14 Apr
One inbox across NCRs, audits, meetings, MOCs, and exemptions — your whole queue, no module hopping.

One queue. Every module.

Quality work used to live in six different inboxes. Now it's one — with a record-of-truth link back to wherever each item came from.

NCRs

Corrective · Containment · Preventive

Audits

Findings → corrective + verification

Meetings

Agreed actions raised in the room

MOCs

Implementation tasks + verify-return-to-nominal

Exemptions

Renewal, scope-change, expiry follow-up

Documents

Approval routing · acknowledgement chasing

Routing by policy

Up to three serial steps. Delegation built in.

An approval chain is a property of the record's risk and policy — not a private convention. Configure up to three serial signers per record type; each step can have a primary and a delegate. The chain is part of the audit trail, not a side-channel email.

DOC-MX-04 v3.2 · Approval chain
Author
A. Khan
Step 1 · 18 Apr 09:14
Quality Manager
M. Patel · or J. Park
Step 2 · 18 Apr 11:02
3
Engineering Authority
L. Chen · or D. Hayes
Step 3 · awaiting passkey
Chain template: 3-step Document — set at Admin → Documents → Approval matrix
Passkey step-up

Identity proven at the moment of decision.

On the calls that matter — approving a high-risk MOC, signing a customer-facing concession, releasing a controlled document — the system asks for a passkey at the click. Five-minute confirmation window, full audit log entry, no per-feature passwords to manage.

Step-up confirmation
About to approve
MOC-0102 · Press 4 LOTO procedure update
Risk tier: High · Author: A. Khan · 6 linked records
Confirm with passkey
Touch ID, Face ID, or hardware key. Confirms identity at the point of approval; valid for 5 minutes.
Window
5 min
Logged
user · time · IP
Required for
High-risk approvals
Closing an action

Closure notes are required. Evidence is welcome.

An action closes when the assignee writes specific notes about what they did — no scrolling past a placeholder textarea. Evidence is optional but encouraged: link a document version, drop a photo, attach a meeting where it was signed off. Verification is its own step when policy demands it.

ACT-2026-0182 · Close
Closure notes
Replaced 4× LOTO tag-out points on Press 4. Confirmed legibility from 5 m and tested with a fresh padlock. New tags ordered to match the revised SOP-MX-04 v3.2 colour code.
Evidence (optional)
LOTO-2026-tags.jpgPre-shift-walk-22Apr.pdfSOP-MX-04 v3.2 §4.1
States & transitions

Open · In progress · Verify · Closed.

States are deliberately small. Open is what you've been given. In progress means you've started. Verify means you're done but a second person needs to sign off (set per record type). Closed is final and read-only. Re-opening exists, leaves an entry in Activity, and never silently undoes the previous closure.

Action lifecycle
Open
Assigned. Nothing started yet.
In progress
Owner has started; partial evidence allowed.
Verify
Closure submitted; second person reviewing.
Closed
Final. Read-only. Reopen logs to Activity.
Verify is opt-in per record type — turn it on in Admin → Actions → Verification policy.

Linked back. Always.

Every action shows where it came from. Every source record shows the actions it raised. Audit trails reconstruct themselves.

Every action carries its source

ACT-2026-0182 didn't appear out of nowhere. It came from NCR-2026-0418, raised on the Press 4 jam audit. One click on the link, you're back at the parent record.

Filter by source, owner, or due date

Open the Actions list, choose 'Source: NCR', 'Due this week', 'Mine'. The filters compose. Save the combinations you use as views you can return to.

Closed in a meeting? Link the meeting.

Many actions are closed out in management review. Tag the meeting at closure and the audit trail captures who-decided-what alongside the closure note.

Permission-aware

Actions inherit the access of the source. If you can't see the underlying NCR, you don't see actions raised from it. Cross-facility queues filter automatically.

Get every step, every signature, in one place.

Pull every team's open work out of email and into a single, audit-ready queue with the approval chain built in.