On this page
An appraisal delay creates a gap that borrowers fill with worry. The loan officer may be in closings, the processor may be waiting on the appraiser, and the borrower hears nothing for several days. A written update script gives the team a calm, approved way to fill that gap without inventing a completion date. It also keeps the same message from being rewritten under pressure by five different people.
Define the milestone that slipped
Start by naming the milestone in language the borrower already saw. "Appraisal ordered" and "appraisal received" are different events, and a slip in one does not mean the other is late. The script should state which event moved, when it was expected, and what the team now knows. Avoid replacing a missed date with a vague phrase such as soon or shortly.
The internal record also needs the same definition. Write the milestone name, the original target, and the current status field into the file note before drafting the borrower message. If the system of record and the update script use different words, the borrower will hear one version and the file will show another. Agreement on the label is the first step toward an honest update.
Give the borrower the next dated checkpoint
A borrower can tolerate uncertainty when the next contact has a date. The script should promise a specific day for the next update, not a completion date for the appraisal. For example, the message can say the team will check with the appraisal desk on Tuesday and send an update that afternoon. The date must be one the specialist can actually meet.
Put the checkpoint on the follow-up queue at the same time the message goes out. If the check depends on a vendor response, record who is being contacted and when the response is due. The borrower should never be the person who notices that the promised update did not arrive. A missed checkpoint damages trust faster than the original delay.
Say what the team is doing without promising a date
The script can describe concrete actions without claiming control the team does not have. It can say the order is active, the appraiser has the property details, and the team is waiting for a scheduled inspection. It can explain that the processor will review the report the same day it arrives. It cannot promise that the report will clear underwriting on a particular date.
Use plain language about the dependency. A sentence such as the appraiser has not yet confirmed the inspection is more useful than the file is in process. If the delay involves a property access issue, say what the borrower can do to help and who will contact them. Keep the focus on the next action rather than on assigning blame.
Route questions the script cannot answer
A script is not a license to answer everything. Questions about value, eligibility, rate, or approval belong with the licensed or accountable owner. The update should include a clear return path, such as a named contact and a response window. The specialist can record the question and route it instead of improvising an answer. That record also shows the loan officer what the borrower was told before the call.
Give the specialist a short list of triggers that require an immediate handoff. A borrower who mentions a closing date, a purchase contract deadline, or a hardship needs a person with authority to respond. The script should not delay that handoff while the specialist finishes a routine message. The borrower communication support workflow exists to keep those boundaries visible.
Log the message and the response
Record the message template used, the date sent, the channel, and the checkpoint promised. When the borrower replies, log the response and the next action rather than leaving it in a personal inbox. That record lets a backup specialist continue the conversation without asking the borrower to repeat the story. It also shows whether the update cadence is working.
The log should distinguish an acknowledgment from a resolution. A borrower saying thank you does not close the question, and a specialist saying we will check does not close the milestone. Use a status field that shows whether the item is waiting on the vendor, the borrower, or the team. The loan processing support queue can then sort the work by what it is actually waiting on.
Review the script after a busy week
Once a week, read the messages sent during the busiest days and compare them with the original templates. Look for promises the team could not keep, missing checkpoints, and questions that should have been routed sooner. Ask a specialist which sentence borrowers misunderstood most often. The answers usually point to one clause that needs rewriting.
Update the script and the checklist together, then note the change and the date. Tell the specialists which version is current and where to find it. A script that changes quietly in individual inboxes will fragment within a month. The CFPB's mortgage servicing rules are not a template for origination updates, but they reinforce the value of accurate, timely borrower communication. A short review keeps the approved version in use.