Table of contents
A rate lock can expire while the file looks healthy. The borrower has returned documents, the appraisal is complete, and the processor is waiting on one condition. Nobody notices that the lock date is three days away until the lender sends a new pricing sheet. The cost lands on the borrower or the lender, and the team spends the next week explaining the change.
A lock expiration watchlist prevents that surprise by making the date visible early. The watchlist is a short list of files with an approaching lock, a named owner, and a decision point. It is not a second pipeline report or a daily export that nobody reads. This guide explains how to build a watchlist that the processing pod can actually maintain.
Use one lock date source
Choose one system as the authoritative source for the lock date. That may be the lender portal, the lock desk confirmation, or the loan origination system. Whichever source the team chooses, record it in the file and use it for the watchlist. A watchlist built from two sources creates arguments about which date is correct.
Confirm the date when the lock is registered. A lock confirmation can arrive by email or portal, and the processor should compare the date with the request. Record any difference and resolve it with the lock desk before the file moves forward. A date that was wrong at registration will be wrong on every later report.
Set review checkpoints that match the work
Set checkpoints at ten business days, five business days, and two business days before expiration. The ten-day checkpoint confirms that the file has a path to closing. The five-day checkpoint confirms that all conditions are cleared or on track. The two-day checkpoint confirms that the closing has been scheduled and the lender has issued the clear to close.
The checkpoints should trigger different actions, not the same reminder three times. At ten days, the owner reviews the pipeline and escalates any file without a closing date. At five days, the owner confirms the closing disclosure and the funding schedule. At two days, the owner confirms the wire and the final signing appointment.
Assign the re-lock decision to the right role
The processor can monitor the date and prepare the file, but the re-lock decision may belong to the loan officer, the lock desk, or a manager. Write down who decides and who communicates the cost to the borrower. A processor who is asked to make a pricing decision without authority will either delay or guess. A named decision owner also gives the processor a clean escalation path when the deadline is close.
Define the decision options before a file reaches the checkpoint. The options may include closing on time, extending the lock, re-locking at current pricing, or changing the closing date. Each option has a cost and a borrower conversation. The decision owner should know which options the lender allows and what the borrower has already agreed to.
Flag files with no confirmed closing date
A lock date is only useful when it is compared with a closing date. A file with no confirmed closing date is the highest-risk item on the watchlist because the team cannot tell whether the lock will last. The watchlist should show a blank closing date in a separate column and sort those files to the top. Sorting by that blank field keeps the risk visible at the top of the weekly review.
Set a rule that any file without a closing date at the ten-day checkpoint gets a call to the title company and the loan officer. The call should confirm the target date, the outstanding items, and the scheduling window. The result should be recorded in the file and reflected in the next watchlist refresh. The owner should also confirm who will update the borrower if the date moves.
Do not let a tentative closing date look confirmed. Mark the source of the date, such as "scheduled with title" or "borrower requested." A tentative date is useful for planning but not for a lock decision. The distinction prevents the team from assuming a closing is real when it is still a hope. A short note in the watchlist is enough to preserve that distinction for the next reviewer.
Write the borrower conversation before the deadline
Prepare a short explanation for the borrower before a lock extension or re-lock becomes necessary. The explanation should say what the lock is, when it expires, and what the team is doing to protect the current terms. It should avoid jargon and avoid blaming the lender or the borrower. A clear explanation reduces the chance of a complaint.
If an extension costs money, explain the cost and the alternatives before the borrower decides. Do not present the extension as the only option if a closing date change or a re-lock is available. Give the borrower time to ask questions and confirm the choice in writing. The decision should be documented with the borrower's response.
If the lock expires, explain the new pricing and the next step without speculation. The loan officer should own the conversation, with the processor providing the facts. The borrower should know who to call and when. A calm, factual conversation is more valuable than a promise that the old price will be honored.
Test the watchlist during a busy week
Run the watchlist for one busy week before making it a permanent control. Check whether the refresh captures new locks, whether the checkpoints fire on time, and whether the owners act. Ask the pod what created extra work and remove that step. A control that adds ten minutes of duplicate entry will not survive.
Compare the watchlist with the files that actually closed or extended during the test week. Look for a file that should have appeared and did not. The gap may be a missing lock date, a wrong source, or a stale export. Fix the data path before adding more checkpoints.
Review near misses without blame
A near miss is a file that reached the two-day checkpoint without a confirmed closing plan but still closed on time. These files are valuable because they show where the process almost failed. Review a near miss with the owner and ask what made the recovery possible. The answer may be a helpful title officer, a flexible lender, or a processor who checked the portal twice.
Do not use near misses to punish the team. A blame response hides the next near miss and removes the chance to learn. Instead, record the cause and the recovery step in a short note. Share the lesson without naming the individual if the note will be read widely.
Track near misses by month and look for a pattern. A cluster around a particular lender may call for an earlier checkpoint. A cluster around a particular loan officer may call for a conversation about borrower expectations. The pattern should lead to one process change, not a new pile of reports.
The Consumer Financial Protection Bureau's mortgage resources explain how rate locks and closing costs affect borrowers. A watchlist supports those expectations by making the expiration date visible and the decision accountable. The mortgage operations support team can maintain the watchlist while the lock desk keeps pricing authority. Pair it with the weekly condition aging review so lock risk and condition risk are reviewed together.