These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Accreditation Management
- Features
- Corrections and follow-up
Corrections and follow-up
Resolve accreditation corrections without losing the earlier decision or delivery.
OverviewMy follow-up actions×
Accreditation Management · Corrections and follow-up
New
My follow-up actions
Follow up actions
| Title | Source | Due date | Status | Completed at | Resolution | |
|---|---|---|---|---|---|---|
| Open fua-145 | AC-80930 | 19 Oct | Open | RSL-998 | ||
| In progress fua-949 | AC-41793 | 15 Oct | In progress | RSL-746 | ||
| Completed fua-551 | AC-17043 | 24 Oct | Completed | 15 Oct | RSL-548 | |
| Cancelled fua-140 | AC-68027 | 07 Oct | Open | RSL-474 | ||
| Open fua-269 | AC-90271 | 09 Oct | In progress | RSL-483 |
6 of 6 records
Open fua-145Follow up actions · FUA-65568
OpenSourceAC-80930
Due date19 Oct
ResolutionRSL-998
What you can do
Preserve the earlier outcome when work changes
A correction can arrive after an accreditation cycle has already been executed. The preparation team needs to fix the issue while retaining the evidence that supported the earlier outcome. Accreditation Management Operator starts the documented correction process, explaining what changed and why. The process preserves the earlier revision, completed steps and decisions while creating a successor for independent review.
Follow-up actions make the outstanding work assignable. Each action belongs to a cycle and a named person, with a due date and working status. The resolution and completion date explain how the action was finished. This lets the quality team distinguish open corrections from resolved tasks while keeping the successor’s independent review separate.
How the work is organized
Use the correction path when changing an executed revision. A superseded delivery needs an explicit compensating follow-up action so the team can track what must happen because the earlier outcome has already left the institution. The successor revision still requires an independent decision before another delivery.
- Describe the correction. Retain the reason and the source evidence that changed so the reviewer can compare the earlier and revised work.
- Assign the follow-up. Name the person responsible and agree the due date before treating the action as a meaningful handoff.
- Record resolution. Complete the action with an explanation, while keeping the cycle’s separate review decision visible.
What to agree during setup
Agree who can initiate a correction and who will review the successor revision. Decide what a compensating action means for the institution’s delivery destination, including the person responsible for confirming the earlier submission’s treatment. Keep that responsibility explicit when an external portal or recipient requires a separate correction procedure.
Choose a consistent practice for due dates and cancellations. If an action is cancelled, explain why the work is no longer required. A completed task means its assigned work has been resolved; the reviewer still decides whether the revised cycle can proceed. Review both meanings with the pilot team.
Check the handoff on an actual case
After delivery, a department reports that a supporting observation used the wrong period. Accreditation Management Operator opens a correction with the explanation and revised evidence. The earlier revision retains its document and decision, allowing Accreditation Management Reviewer to compare the original submission with the new material.
Because the delivered outcome is being superseded, the team records a compensating follow-up action for the person handling the receiving organization. That person documents the result and completion date. The reviewer then decides on the successor revision using the corrected evidence and the recorded treatment of the previous delivery.
Rehearse a cancellation as well as completion. Ask the action owner to explain why a task was cancelled and ask the reviewer whether that reason resolves the accreditation issue. The history should show both answers without rewriting the earlier delivered cycle.
What your team sees
- Open follow-up actions — Review outstanding corrections with their owners and due dates.
- My follow-up actions — Work assigned actions and record their resolution.
- My review decisions — Revisit the independent decision associated with a corrected cycle.
Follow the work through
Correct a delivered revision describes the handoff. Use execution reconciliation when the original delivery result is uncertain.
What it keeps track of
Data model- Follow up actions
- Assigned outstanding actions and corrections for an accreditation cycle.
- Accreditation cycles
- Accreditation cycles submitted for a standard, tracked through criterion evidence collection, independent review and submission.
- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- State history
- Immutable workflow-written status transition history for each accreditation cycle.
- Operation runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
- Operation steps
- Ordered steps inside an operation run with input, output and external receipt state.
Who uses it
Permissions- Accreditation Management Operator
- , Accreditation Management Reviewer, Read Only Analyst.
- The operator coordinates corrections, the reviewer decides on the successor, and the analyst examines preserved history.
Set up Accreditation Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.