Appraisal Order Tracking: What the Desk Sees Between Placement and Delivery

Appraisal order tracking is the continuous record of where a valuation assignment stands between placement and delivery: who holds it, which status it's in, when that status changed, and what has to happen next. It isn't a dashboard. It's a discipline. Named statuses, a timestamp on every change, and a rule for what happens when an order sits in one place too long.

The test of it is whether anyone can answer "where is this order" without interrupting the person doing the work. Most desks can't, and the reason is rarely a missing screen. It's that the record was never built to answer two different questions at once.

Lenders and AMCs both track orders, and they are not tracking the same thing. A lender is tracking a loan file with regulatory dates attached to it. An AMC is tracking capacity, coverage, and a promise made to several clients at once. Building one record that serves both is what separates an operation that runs on exceptions from one that runs on phone calls.

The Two Jobs One Order Record Has to Do

Done properly, tracking produces an operational view for the desk and an audit record for the examiner, from the same data.

Those two outputs pull in different directions, and an operation can end up with neither. The desk wants the current state of everything. The examiner wants the history of one thing. Only a record that keeps every status change, with its timestamp and the user who made it, answers both.

A second distinction matters as much. The order and the work are not the same object. The order is a request with a client, a fee, a property, and a due date. The work is an assignment held by an appraiser with their own schedule, their own access problems, and their own queue. Two clocks run at once, they don't start together, and a desk watching only one of them finds out late.

The Statuses an Appraisal Order Carries

Appraisal Host ships a status catalog that reads like the work itself:

• New Order

• Appraiser Assigned

• Appraiser Accepted

• Appraiser Declined

• Borrower Contacted

• Left message for borrower / broker

• Appointment Scheduled

• Property Inspected

• Submitted for QA

• Report Complete

• Report Rejected, Please Revise

• Revised Report Completed

• Correction Requested By the Lender

• Request a reconsideration of value

• On Hold

• Off Hold

• Order Cancelled

• Order Reactivated

• UCDP Hard Stop

• EAD Portal

• File Upload

Two things about that list matter more than the words in it. Every install can rename these statuses and change the order they display in, so what your team reads on screen ends up being your own vocabulary. And the platform does not enforce a sequence. It records status changes; it doesn't march an order down a track. Any ordering in this article, including the one above, is narrative rather than a rule the software imposes.

Read the list as an operations person and it says two useful things.

Assignment and acceptance are separate events. Appraiser Assigned, Appraiser Accepted, and Appraiser Declined are three different statuses, and each writes its own timestamped row attributed to the user who caused it. Assignment is something your operation does. Acceptance is something an appraiser does. The gap between the two is real elapsed time on the file, and it's measurable only because the two events are recorded separately.

Report Complete is not the end of the pipeline. It's the end of the appraisal work and the beginning of several downstream obligations. The report still has to reach the loan file, the borrower, and, where a conventional mortgage delivered to the GSEs requires an appraisal, a GSE portal.

Those statuses don't all arrive the same way. Assignment, acceptance, and scheduling are each triggered by somebody on the other end of the order, and report production has no equivalent outside trigger. That's the stretch where a desk usually loses time. While the report is being written, Appraisal Host keeps the desk in the loop through the order's status events, which email the manager and the lender according to rules the firm sets per status, and every order carries a File Access History, on the manager's order view, showing which documents were downloaded, by whom, and when.

On the Lender Side, Tracking Is a Set of Dates

Not curiosity about progress. Dates that carry consequences, and a small number of decisions that have to be made before the file can close.

The borrower's copy. The ECOA valuations rule (12 CFR 1002.14) puts a dated delivery obligation on the creditor for every appraisal developed on a first-lien dwelling application, which makes "the copy went out, on this date" a fact the order record has to carry rather than one the file infers from "the appraisal is done."

Whether the loan is higher-priced, and what that changes. For a higher-priced mortgage loan, the creditor must provide the consumer a copy of each written appraisal "No later than three business days prior to consummation of the loan" (12 CFR 1026.35(c)(6)(ii)(A)). The same section can require a second appraisal entirely. Subject to the exceptions it carries, a creditor may not extend a higher-priced mortgage loan to a consumer to finance the acquisition of the consumer's principal dwelling without obtaining two written appraisals where the seller acquired the property 90 or fewer days before the consumer's agreement and the price exceeds the seller's acquisition price by more than 10 percent, or acquired it 91 to 180 days before and the price exceeds that acquisition price by more than 20 percent (1026.35(c)(4)(i)). Note the scope: that rule reaches the acquisition of a principal dwelling, not every higher-priced loan you write.

That's a tracking requirement, not a compliance footnote. The trigger is knowable at order entry, and a second order placed late is a second cycle stacked on the one already running.

Whether the report reached the GSE portal. The Uniform Collateral Data Portal is, in Freddie Mac's own description, "a single portal for the electronic submission of appraisal data files to Freddie Mac and Fannie Mae (the GSEs)", and "The appraisal report must be submitted to UCDP before the delivery date of the mortgage to Freddie Mac and must include all exhibits, addenda, and photographs" (Freddie Mac, UCDP). GSE submission status shows on the order once the firm has set it up: the UCDP and EAD designations appear only after the appraisal type and the lender company are configured for the portals, the UCDP Hard Stop and EAD Portal events land in the manager's status history, and the Submission Summary Report appears in the order's documents automatically once the report has actually been submitted. None of it is on by default. The designations record what the order is set up to submit to, not proof that anything arrived, and the hard stop is what turns a portal rejection into a dated fact rather than an email somebody remembers receiving.

Status where the work already happens. A lender's operations team lives in the loan origination system, not in a valuation portal. A status that's accurate but only visible in a separate portal generates exactly the phone calls it was supposed to prevent, so where the status lives is a design decision worth making deliberately. Appraisal Host integrates directly with the Byte Software loan origination system (BytePro): BytePro sends the loan and property details and the appraisal order is created from them automatically, and BytePro can request the current order status and pull back the finished report, invoice and certificates through the same connection.

On the AMC Side, Tracking Is Capacity and Coverage

An AMC is running the supply side, and the supply side has failure modes a lender never sees.

Acceptance behavior, by appraiser and by market. Declines are data. An appraiser who accepts everything and delivers late is a different management problem from one who declines half of what you send. Neither is visible unless every acceptance and every decline carries its own timestamp on the order, which is what separate Appraiser Accepted and Appraiser Declined statuses give you. Under automated appraiser assignment, a decline also routes the order to the next eligible appraiser without staff involvement, so the decline becomes a data point rather than an interruption.

Capacity and coverage at the moment of assignment. The question is never just "who is licensed here." It's who is licensed here, currently credentialed, inside their workload limit, and approved by this particular client. Getting that right at order entry is what prevents the reassignment cycle that follows a bad match. Coverage gaps are a panel problem that shows up first as a tracking problem, and the discipline behind it is ordinary appraiser panel management: an operation needs credential tracking, expiration alerts, and coverage mapping maintained continuously rather than at assignment time.

Credential state as of the assignment date, not today. When an examiner or a client asks about an order from months ago, the answer they need is what was true when it was placed. A panel list showing only current state can't produce it, so the order record has to hold the credential fact it relied on.

Per-client rules and per-client billing. Each lender client brings its own fee schedule and approved appraiser list. Serving several from one platform means client-specific configuration and genuine data separation, not a shared queue with a client column.

The money side of a completed order. Completion creates an invoice to the client and a payable to the appraiser. If those live in a different system from the order status, reconciliation becomes a monthly exercise in re-deriving facts your tracking record already had.

Time in Status Is the Signal, and You Set the Threshold

The most useful number on an appraisal order isn't its due date. It's how long it has been sitting in the status it's in right now.

Appraisal Host runs that calculation on a schedule and flags the orders that cross the line, so nobody has to sweep the queue by hand. Managers get an Overdue tab. Appraisers see Overdue orders and Orders Due in Next 3 Days on their own dashboard, which puts the same fact in front of the person who can act on it.

The thresholds are yours. A Past Due Notifications screen sets them per status, in days or in hours, with a "Would you like to count weekends?" toggle for the operations that don't run on Saturday. The clock starts when the order entered its current status, not when the order was placed, which is what makes this a stall detector rather than another due-date report. An order can be three weeks from its due date and already be the most urgent thing on your desk.

Nothing ships pre-configured here, and that's the setup decision worth spending an hour on. Pick the statuses where silence costs you something, and set a threshold on each. Waiting on acceptance is usually the first one. Report production is usually the one that pays for the exercise.

Where Appraisal Orders Go Quiet, and What a Desk Does About It

Five places, each with a signal you can watch and an action that belongs to someone specific.

1. Waiting on acceptance. The signal is time in Appraiser Assigned, not a missed due date. Automated assignment handles the decline path on its own. What a threshold on that status catches is the quieter case: no response either way. Caught early it's a quiet reassignment. Caught on the due date it's a phone call to the client.

2. The inspection that can't be scheduled. Tenant-occupied properties, vacant properties with no lockbox, and unresponsive contacts produce an order that's accepted and going nowhere. The signal is Appraiser Accepted with no Appointment Scheduled, and the record of the effort is already there in Left message for borrower / broker. The action rarely involves the appraiser. It involves whoever controls access, so the escalation routes to the client, not to the panel.

3. The stretch while the report is written. No outside party generates an event while a report is being written. The events on the order in that window are your own team's and the appraiser's, which is why the age of the status is what surfaces a stall. An order between Property Inspected and Submitted for QA looks completely normal right up until it's late, and a threshold on that status is what makes it look different sooner.

4. The revision loop. Revisions rarely register as lateness. They register as an order that was almost done twice. Because Report Rejected, Please Revise, Revised Report Completed, and Correction Requested By the Lender are distinct statuses, passes are countable per order and per appraiser, and a repeated pattern reads as a panel signal rather than a paperwork event. Record what each pass actually asked for. Regulation Z's valuation independence rule, 12 CFR 1026.42, which reaches consumer credit transactions secured by the consumer's principal dwelling, treats asking an appraiser to correct an error as a permitted action rather than coercion. A request your record cannot characterize is a request nobody can explain a year later.

5. Delivered, but not confirmed. Report Complete says the appraisal work is finished. It doesn't say the report reached the loan file, the borrower, or the portal. The signal is a completed order carrying no confirmation from any of the three, and the discipline is to treat delivery as a set of receipts rather than one status. Whoever owns the file owns the receipts.

Why Two Systems Show Two Different Statuses

Run orders across several client portals and an LOS and you'll see the same order described three ways at once. There are three ordinary reasons, and none of them is a bug.

Vocabulary. "In progress" in a client portal can cover three statuses in your own queue. Reconciling those vocabularies is real integration work, and it's where a connection is either built properly or fudged.

Direction. Every field needs a system of record. When status can be edited in two places, the last write wins and nobody can explain the result a week later.

What gets synced at all. A connection can carry the status alone. The useful kind carries the status, the timestamp, and the actor, which is the only version that answers a client asking what happened on one order.

The fix is unglamorous. Agree the vocabulary, name the system of record for each field, and confirm both directions before you rely on it. Turning on an integration is done inside Appraisal Host by a manager once the integration is enabled for your account: a per lender screen activates the connection, and a separate order type screen maps your appraisal order types to that partner's product codes. The vendor credentials are requested from the vendor and entered once at the site level. Most Appraisal Host integrations are live and syncing within 3 to 5 business days.

Seven Things the Queue Should Answer Without a Phone Call

A working tracking layer answers these without anyone being contacted:

• Every order from every client and channel in one queue

• An exception view rather than a list of everything, because nobody manages by scrolling

• The age of the current status on each order, not just its name

• The full timestamped history, including who changed what and when

• Past due thresholds your operation configured, firing before the client notices

• Panel context beside the order: capacity, credential state, and coverage

• Downstream confirmations, so a completed order shows where the report actually went

That is what "real time" should mean in practice. Not a faster refresh, but a shorter distance between something happening and the right person knowing.

Appraisal Order Tracking Is an Operating Discipline

The operations that struggle with appraisal order tracking usually don't have a visibility problem. They have a definition problem. The statuses aren't agreed, the owner at each one isn't named, the history isn't kept, and the exception rules live in the head of whoever has been there longest.

Fix those four things and the software question becomes simple: you know exactly what you're asking it to record. A lender needs the dates that carry consequences and status inside the loan file. An AMC needs acceptance behavior, capacity, credential state as of the assignment, and per-client separation. Both need a timestamped history that answers an examiner's question without a reconstruction project.

Start with the status no outside event will ever tell you about. That's where your time is going.

See how appraisal order tracking works when the desk, the panel, and the loan file share one record. Book a demo and we'll walk through your queue, your clients, and the statuses your team manages.