Route 70 of 176
Corrective-Action Status
QRCompliance.us · Validation Layer · Source of truth: QRCodex.us
Summary
When a compliance condition requires a corrective action — a repair, a retraining, a documentation fix, a process change — that action does not resolve itself the moment it is assigned. It moves through a defined lifecycle from open to verified complete, and at every point in between, its status needs to be known with precision: is it not yet started, in progress, submitted for review, verified, or overdue. Corrective-action status is the record of exactly where a required action stands.
QRCompliance.us tracks and validates corrective-action status against defined evidence. It does not perform the corrective action itself, and it does not decide whether the underlying condition that required correction should be enforced against in the meantime — that determination and any resulting action belong to the layers built to hold them.
A corrective action is a promise to fix something, and a promise on its own changes nothing. Between the moment a corrective action is assigned and the moment it is verified complete, the underlying condition that triggered it typically remains open, and anyone relying on that identity's compliance state needs to know precisely how far along the correction actually is — not just that one was assigned at some point in the past.
Corrective-action status exists to answer that question with the same rigor applied to any other compliance determination. A status of 'in progress' claimed informally in an email is not the same as a status recorded against defined evidence and a checkable timeline. This route defines the recognized states a corrective action can occupy, what evidence moves it from one state to the next, and who is responsible for reporting that evidence.
This route is distinct from the routes governing corrective response and reinstatement after correction. Those routes address what happens once a corrective action is triggered and what happens once it is fully verified and the identity's broader condition is restored. This route addresses the tracking in between — the status itself, at any given moment, of an action that has been assigned but not yet closed.
01Plain-English Definition
Corrective-action status is the recorded, evidence-based state of a required corrective action at any point between its assignment and its verified completion, tracked through a defined set of stages rather than reported informally.
A corrective action can be as narrow as correcting a single mislabeled field or as broad as a facility-wide process change. Regardless of scope, its status is tracked the same way: as a defined state, supported by evidence, with a timestamp marking when that state was reached.
The status itself is not a judgment about whether the corrective action was a good one or whether it fully addresses the underlying problem — those are substantive determinations made when the action is assigned and again when its completion is verified. Status is the tracking layer that sits between those two determinations.
02Recognized Status States
A corrective action occupies exactly one recognized state at any given time, and movement between states requires a specific triggering event.
| State | Entered When | Left When |
|---|---|---|
| Open | The corrective action is assigned, with a defined deadline and responsible party recorded. | Work begins and progress is reported, or the deadline passes without any report. |
| In Progress | The responsible party reports that work has begun, typically with an interim update. | Evidence of completed work is submitted, or the deadline passes without submission. |
| Submitted For Review | Evidence of completed corrective work is submitted for verification. | The evidence is verified as sufficient, or it is rejected and returned to In Progress. |
| Verified Complete | Submitted evidence is confirmed to satisfy the corrective action's requirements. | Status is closed and feeds into the underlying condition's reassessment. |
| Overdue | The assigned deadline passes without a status update or evidence submission. | A late report or submission is received, returning the action to an active state, or the condition escalates. |
A rejected submission does not erase the effort already reported — it returns the action to In Progress with the rejection reason recorded, preserving the full history rather than resetting it.
03What Moves A Status Forward
Status does not advance on the responsible party's assertion alone. Each transition requires a specific, checkable trigger appropriate to the state being left.
- Moving from Open to In Progress requires a reported update from the responsible party, timestamped and attributed.
- Moving from In Progress to Submitted For Review requires actual evidence — documentation, inspection results, photographs, retraining records, or an equivalent — not a bare statement that work is done.
- Moving from Submitted For Review to Verified Complete requires an independent check of that evidence against the corrective action's original requirements.
- Moving to Overdue requires only the passage of the assigned deadline without any of the above — it is a status the record reaches automatically, not one anyone has to declare.
- Reopening a Verified Complete action, where new evidence later shows the correction did not hold, requires the same evidentiary standard as the original submission.
04Operational Flow
Tracking a corrective action from assignment to closure follows a consistent operational sequence.
- 1Corrective action is assignedA required action is defined with a scope, a deadline, and a responsible party, and status opens.
- 2Progress is reportedThe responsible party submits interim updates as work proceeds.
- 3Evidence is submittedDocumentation supporting completion is submitted for review once the work is finished.
- 4Completion is verifiedQRCompliance.us checks the submitted evidence against the original requirement and confirms or rejects it.
- 5Status is closed and fed backA verified completion closes the status and is fed into reassessment of the underlying condition that required correction.
Closing a status is a tracking event. Whether the underlying compliance condition is actually resolved as a result is a separate determination made by reassessing that condition against the now-verified correction.
05Status Versus The Underlying Condition
It is tempting to assume that once a corrective action reaches Verified Complete, the underlying compliance problem is automatically resolved. That assumption does not always hold, and this route keeps the two questions separate.
| Aspect | Corrective-Action Status | Underlying Compliance Condition |
|---|---|---|
| Tracks | Where a specific assigned action stands in its lifecycle | Whether the identity or party meets the requirements the action was meant to restore |
| Reaches Verified Complete when | Submitted evidence satisfies the action's own defined requirements | A separate reassessment confirms the broader condition no longer applies |
| Can be Verified Complete while | The underlying condition remains partially open due to a separate, unrelated factor | Multiple corrective actions may need to close before the condition is fully resolved |
| Held by | QRCompliance.us, tracking against defined evidence | QRCompliance.us, reassessing the broader condition using the closed status as one input |
This separation matters most when a single underlying condition required several distinct corrective actions. Each action's status can close independently, but the condition itself is not reassessed as resolved until every required action tied to it has closed and the reassessment confirms the requirement is now met.
06System Relationship
System Chain — Six Locked Entities
- 1QuickResponseCode.usRoot / System EntryPublic entry point to the QR infrastructure.
- 2QRProtocol.usGovernance (Rules)Writes and governs the applicable rules.
- 3QRCompliance.usValidationValidates compliance readiness against applicable rules and conditions.
- 4QRCertified.usCertification AuthorityAuthorizes the QR for certification.
- 5QRRegistered.usRegistration ResultMandatorily registers the authorized QR.
- 6QRCodex.usOperations / RecordsRecords, operates, logs and preserves canonical operational truth.
No registration → no certified QR output.
Corrective-action status is a tracking function inside monitoring, but its outcome feeds directly into decisions made across every other layer.
| Layer | Relationship To Corrective-Action Status |
|---|---|
| ROOT — QuickResponseCode.us | Anchors every corrective action and its status history to the fixed identity it was assigned against. |
| GOVERNANCE — QRProtocol.us | Defines the recognized status states, the evidentiary standard for each transition, and who may act as a responsible party. |
| VALIDATION — QRCompliance.us | Tracks status through its lifecycle, verifies submitted evidence, and confirms or rejects transitions. |
| AUTHORIZATION — QRCertified.us | Uses a closed corrective-action status as one input when reassessing whether certification can be restored or must remain withheld. |
| REGISTRATION — QRRegistered.us | Reflects current corrective-action status on the identity's registration record so it is visible wherever that record is consulted. |
| OPERATIONS — QRCodex.us | Retains the complete status history — every state, every transition, every piece of submitted evidence — as the permanent record. |
Where a status displayed elsewhere in the system differs from the sequence recorded in QRCodex.us, Codex governs.
What This Does — And Does Not — Do
Does
- ✓Track a corrective action through a defined set of recognized states from assignment to closure
- ✓Require specific, checkable evidence — not bare assertion — before advancing status past In Progress
- ✓Move an unreported action to Overdue automatically once its deadline passes
- ✓Preserve full transition history, including rejected submissions, without erasing prior reported effort
- ✓Feed a closed status into reassessment of the broader condition, without assuming that reassessment automatically resolves that condition
- ✓Track each assigned corrective action independently when a single condition required more than one
Does Not
- ✕Perform the corrective action itself or substitute for the work it requires
- ✕Advance status to Verified Complete on an unverified assertion of completion
- ✕Assume a Verified Complete status automatically resolves the underlying compliance condition
- ✕Erase or overwrite prior status history when a submission is rejected and the action reopens
- ✕Decide independently whether to enforce against the underlying condition while corrective action remains open
- ✕Treat corrective actions tied to the same condition as a single undifferentiated status
Related Routes
Common Questions
Does a corrective action move to Verified Complete just because the deadline passed?
No. Passing the deadline without reported progress or evidence moves the status to Overdue, not to Verified Complete. Completion requires submitted evidence that is independently verified.
If a submission is rejected, does the corrective action start over?
No. It returns to In Progress with the rejection reason recorded, preserving the history of the prior submission rather than discarding it.
Does closing a corrective action's status automatically resolve the underlying compliance condition?
Not automatically. The closed status is fed into a separate reassessment of the broader condition, which may depend on other corrective actions as well.
Who reports progress on a corrective action?
The responsible party assigned to the action reports interim updates and submits completion evidence; QRCompliance.us verifies that evidence rather than generating it.
Can one underlying condition require tracking multiple corrective actions at once?
Yes. Each assigned action is tracked independently through its own status, and the underlying condition is not reassessed as resolved until all required actions tied to it have closed.