QC review & revision loop
How a submitted report is reviewed, the revision loop, and the reconsideration-of-value paths.
Quality control is where a submitted report is checked against USPAP, client requirements, and data integrity. The report either passes (Report Accepted13) or goes back for a fix (Revision Requested12). This loop repeats until the report passes.
The two outcomes
ReportSubmitted ──► (QC review) ──► ReportAccepted ✅ proceeds to delivery
└─► RevisionRequest 🔁 back to the vendor
| Outcome | Status | What it means |
|---|---|---|
| Pass | Report Accepted13 | Meets requirements; proceeds to delivery |
| Revision | Revision Requested12 | Issues found; vendor fixes and resubmits |
Reviewing the report
Review can be manual (a QC Reviewer works a checklist) and/or automated (CrossCheck runs rules against the report).
| Action | Endpoint |
|---|---|
| Open the order's checklist | |
| Answer a checklist item | |
| View review findings | |
| Run an automated CrossCheck report | |
| View a CrossCheck report |
Requesting a revision
When issues are found, a revision is created with a type and a detailed reason the vendor can act on. The order moves to Revision Requested12.
| Action | Endpoint |
|---|---|
| Request a revision | |
| Request a revision tied to a checklist | |
| Get the latest revision |
A revision without a clear reason just bounces the report back and forth. Record the revision type and a specific explanation so the vendor can fix it on the first resubmission. Every revision is part of the order's audit trail.
The loop
When the vendor resubmits, the order returns to Report Submitted11 and re-enters QC. The loop continues until the report passes. Revisions are counted, so repeated loops are visible — operations typically escalate at three or more.
Client-initiated revisions
A client can also request a revision after the fact:
This moves the order to Revision Requested by Client20.
Reconsideration of Value (ROV)
A borrower or client can dispute the appraised value with supporting evidence. This opens a reconsideration cycle distinct from a standard QC revision.
| Action | Endpoint |
|---|---|
| Submit an ROV (client) | |
| Submit an ROV (borrower) | |
| Approve/deny an ROV |
A borrower ROV moves the order to ROV — Borrower17; a client ROV moves it to ROV — Client18.
A standard revision corrects a defect in the report. An ROV disputes the value with new evidence (e.g., additional comparables). They follow different paths and are tracked separately.
What's next
Once the report is accepted, it can be delivered to the borrower.