Glossary
Definitions for common OmniValVMS appraisal, workflow, integration, and compliance terms.
This glossary defines the terms used across the docs and the order lifecycle.
| Term | Meaning |
|---|---|
| AMC | Appraisal Management Company — coordinates appraisal orders between clients, vendors, borrowers, and operations teams. |
| Client | The lender or organization requesting appraisal services. |
| Client Admin | A client-side administrator who can create the client account, invite team members, and manage organization setup. |
| Vendor | The appraiser or appraisal vendor performing the assignment. |
| Panel | A curated group of vendors approved for specific clients, regions, and product types. |
| Order | The appraisal request moving through intake, assignment, inspection, report upload, QC, delivery, payment, and close/cancel. |
| Draft order | An order created but not yet activated. It should not start SLA tracking until required data is complete. |
| Activation | The point where a draft order enters the operational lifecycle and SLA tracking begins. |
| Assignment | Selecting a qualified vendor for an order and moving the order into the vendor acceptance flow. |
| Accept with conditions | A vendor or client accepts the order but requests changes such as fee or due date. |
| Inspection | The property visit scheduled and completed by the vendor. |
| Report | The appraisal deliverable uploaded by the vendor and reviewed by QC/client workflows. |
| QC | Quality control review of the submitted report before final acceptance and delivery. |
| Revision request | A request for the vendor to correct or update the report after review. |
| Delivery | Sending the accepted report to the borrower or downstream recipient. |
| UCDP | Uniform Collateral Data Portal, used for agency appraisal submission workflows. |
| EAD | Electronic Appraisal Delivery, used for FHA appraisal submission workflows. |
| Invoice | The billing artifact generated for an order after report acceptance/delivery gates. |
| Payment | Collection or recording of money for the order; includes charges, received payments, and refunds. |
| Payment link | A borrower-facing link used to pay an order when configured for that payment scenario. |
| Workflow event | An internal or partner-triggered event that can drive automation rules. |
| Webhook | An HTTP callback. OmniValVMS currently exposes provisioned inbound partner webhook handlers; self-service outbound webhooks are planned but not available yet. |
| Audit trail | The authoritative operational record of who did what, when, why, and what changed. |
| Order history | The order-level timeline used to reconstruct status changes, comments, assignments, and operational actions. |
| P0 flow | Mission-critical workflow requiring extra validation, auditability, and failure recovery. Examples: activation, assignment, QC/revision, payment, UCDP/EAD submission, audit trail. |
| SLA | Service-level agreement or target timeline for operational steps such as assignment, inspection, review, and delivery. |
| Bearer token | The access token sent in the Authorization: Bearer <token> header after sign-in. |
| Programmatic API access | Future self-service API-key and developer-portal model. Today, API calls use sign-in and bearer tokens. |