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
- Independent review
Independent review
Keep the accreditation decision with the reviewer and revision it belongs to.
OverviewPending independent decisions×
Accreditation Management · Independent review
New
Pending independent decisions
Approval conditions
| Source | Source revision | Reviewer | Decision | Evidence reference | Reason | |
|---|---|---|---|---|---|---|
| AC-63070 | 380 | Pending | ER-265 | Pending rd-574 | ||
| AC-20346 | 690 | Pending | ER-640 | Pending rd-390 | ||
| AC-55754 | 870 | Pending | ER-142 | Pending rd-837 | ||
| AC-70892 | 960 | Pending | ER-502 | Pending rd-875 | ||
| AC-54221 | 850 | Pending | ER-218 | Pending rd-123 |
6 of 6 records
ER-265Review decisions · RD-45159
PendingSourceAC-63070
Source revision380
ReasonPending rd-574
What you can do
Decide on the evidence that was submitted
Accreditation Management Reviewer receives a validated cycle revision with its criterion evidence and documents. The decision belongs to that exact revision. The reviewer examines the evidence reference, records the reason and chooses Approved, Returned or Rejected. This makes the handoff understandable to the operator who prepared the work and to colleagues reading the history later.
The person who prepared the cycle cannot supply its independent approval. Administrative configuration access also does not replace the reviewer’s decision. The institution should assign a reviewer who can explain the applicable standard and challenge evidence that needs correction before an outcome is delivered.
How the work is organized
A pending decision identifies the cycle, source revision and assigned reviewer. Reviewers can work from their own decision queue and inspect the related cycle context in Accreditation Cycles Workspace. The status history shows the earlier handoff, while the evidence strip keeps the underlying observations close to the decision.
- Check the revision. Compare the revision presented for review with the decision record before recording an outcome.
- Explain the decision. Include a reason and evidence reference that another authorized colleague can understand later.
- Return unresolved work. Use Returned or Rejected when the evidence does not support approval, and explain what the operator must address.
What to agree during setup
Agree the boundary between document verification and cycle approval. A document verifier checks supporting material; Accreditation Management Reviewer decides whether the assembled revision can proceed. Choose who reviews each organization’s cycles and how the team handles a reviewer who also helped prepare the work.
Decide what an adequate decision reason contains. A useful reason points to the reviewed material and explains the unresolved issue or basis for approval. Avoid a generic acknowledgment that leaves the preparation team unable to act. Review access with ordinary staff accounts so decision rights match the people responsible.
Check the handoff on an actual case
A cycle reaches independent review with a criterion observation marked Accepted, but the document reference points to an earlier evidence period. Accreditation Management Reviewer returns the decision with a clear explanation. Accreditation Management Operator investigates the document and prepares the correction for the appropriate revision handoff.
The corrected material requires the reviewer to examine the revision now being presented. The earlier returned decision remains part of the history. Ask the reviewer to show both the original reason and the new evidence reference, then ask the operator to explain which work is ready for delivery.
Also rehearse an attempted approval by the preparation account. That person should be able to see the next task without gaining the reviewer’s authority. A useful queue gives visibility of the pending handoff while preserving the distinction between preparing evidence and authorizing its outcome.
What your team sees
- Pending independent decisions — Review the waiting cycle revision and its supporting decision context.
- My review decisions — Find assigned decisions and revisit their recorded reasons.
- Cycles awaiting validation — See submissions before their independent review handoff.
Follow the work through
Review and deliver connects the decision to its outcome. Review permissions before inviting the pilot reviewers.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Accreditation cycles
- Accreditation cycles submitted for a standard, tracked through criterion evidence collection, independent review and submission.
- Criterion evidence
- Observation-level criterion evidence, document and metric detail captured against an accreditation cycle.
- Evidence documents
- Uploaded and verified supporting documents and source evidence.
- State history
- Immutable workflow-written status transition history for each accreditation cycle.
- People
- Staff, officers, reviewers and assigned team members.
Who uses it
Permissions- Accreditation Management Reviewer
- , Accreditation Management Operator, Read Only Analyst.
- The reviewer decides.
- The operator supplies corrections, and the analyst reads authorized outcomes without editing them.
Set up Accreditation Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.