Key finding
Resolution time should be reported with the exception type and the expiration date, because a fast average can hide locks that died waiting on one document.
Question and scope
This brief defines one mortgage measurement question: how rate lock exception resolution behaves inside a single lending team. The answer is a local reading of evidence, not a benchmark, a compliance opinion, or a prediction for another lender. Everything below covers one named population and one fixed window, and the report repeats both beside every number. An operations lead with the same export can rerun the procedure without asking the author for help.
This review examines rate lock exception resolution as a records question rather than a sales or credit question. It asks whether a second person could follow the file from the source document to the recorded decision. The unit, population, and window are fixed below so the result cannot drift while the sample is collected. The closing section states the limits before anyone repeats the number in a meeting.
The scope here is deliberately small: one mortgage workflow, one population, and one window of observation. The Mortgage Assistant wants to know whether the rate lock exception resolution file shows its evidence, its reviewer, and its decision date. The brief will not score loan quality, predict fallout, or compare one lender against another. It offers a repeatable way to inspect the record and a clear statement of what the record cannot show.
Population and unit
The population is rate locks with an open exception during the observation window. The Mortgage Assistant locks the export date, the systems included, and the duplicate rule before looking at outcomes. A file with a missing document, a conflict, or no available reviewer remains in the denominator unless the plan says otherwise. That choice keeps the rate from looking better simply because the difficult files disappeared.
The unit is one rate lock with an open exception before expiration, counted once under a written identity rule. Name the opening event, the closing proof, and the condition that pauses a file before the first record is pulled. If the pipeline changes size mid-window, a bare total stops being a measurement. List every removal with its reason so another analyst can rebuild the same list.
Definitions and measures
For this review, a file counts as complete when it supports the median and upper-quartile hours from exception to documented resolution with a dated source and a named reviewer. The guide also settles how a reopened file and a duplicate file are counted. The Mortgage Assistant prints the sample count, the unresolved total, and the oldest open item under each result. Those three figures keep volume, evidence, and delay from hiding one another.
The Mortgage Assistant keeps a short field guide that lists each field, its permitted values, and the document that proves it. Blank, unavailable, and confirmed-negative answers go into separate columns. The headline number is the median and upper-quartile hours from exception to documented resolution, and it never appears without the denominator and the window. A percentage alone cannot tell a team what to fix.
Define a finished rate lock exception resolution file before the export is opened. The definition names the required documents, the accepted source, and the treatment of a blank field. Report the median and upper-quartile hours from exception to documented resolution with the eligible count and the exact dates of the window. Beside it, show the missing-document count and the age of the oldest open file.
Evidence standard
Every sampled file must show the source, the observation time, the field it proves, the reviewer, and the accountable owner. Borrower data stays inside the approved system, and the review note carries only a reference. The Mortgage Assistant accepts only evidence the plan can defend, even when a tidier summary is easy to produce. A complete file does not prove the lending decision was right, and the report says that in plain words.
A file passes only when and sit in the approved system under the same loan reference. If two records conflict, keep both and write down which one drove the decision. The Mortgage Assistant tags every estimated figure as an estimate so a later reader cannot mistake it for a verified value. The goal is a trail another person can follow, not a flawless folder.
Sampling and collection
Pull files from the whole window, including the week when coverage was short and volume was high. A list drawn only from calm days will make a weak control look steady. Write down the observation time and the initials of the person who opened the record. If the eligible list is short, show the raw count and say the estimate is unstable.
Pick a random or systematic start, then take consecutive files inside each stratum. Stratify by stage, owner, and exception type so the easy files do not dominate the result. Include one hard case: a missing document, a conflict, an absent owner, or a deadline that forced a quick call. The Mortgage Assistant logs every access failure instead of quietly swapping in a different file.
The extract begins with the pipeline export for rate lock exception resolution, not a set chosen after the result is known. The Mortgage Assistant keeps the selection rule, the seed, and the exclusion log with the sample. No file may be added once the result is visible, and no hard file may be dropped to improve the rate. A repeatable draw lets the team rerun the review after the workflow changes.
Analysis and reporting
The analysis asks whether the file supports the decision, not whether the team looked busy. Break the result out by stage, owner, and exception type so the weak spot becomes visible. The Mortgage Assistant gives a range or a raw count when the sample is thin instead of implying precision. Each report closes with one proposed change and the measure that will reveal whether it worked.
Publish the spread, not only the average, because a median can conceal a long tail of untouched files. Show the open count and the oldest file by owner, then point to where delay collects. A finding without an owner or a next step is not ready for the pipeline meeting. The Mortgage Assistant writes the result in ordinary language and puts the technical detail in an appendix.
Limits and sources of error
The central limit is that a rate lock exception resolution record can be late, partial, or kept outside the team's systems. This method cannot recover work that left no trace or prove that a policy was followed in a silent file. The Mortgage Assistant prints those caveats next to the finding instead of hiding them in a footnote. Changes to systems, investor rules, product mix, or volume can date the result, so list those triggers.
Three limits bound the answer: sampling error, coder judgment, and records that never reached the system. The Mortgage Assistant publishes the overlap agreement and any disputed code rather than declaring the coding clean. One team and one window produced this number, so it cannot stand in for an industry benchmark. The closing paragraph states what the review still cannot see.
A finished file does not prove the lending call was right, because this review scores documentation rather than credit quality. The design cannot read intent and cannot describe a file that left no trace in any system. The Mortgage Assistant prints the caveats directly under the finding so a reader cannot lift the number without them. If the rule changes midstream, retain the earlier and later versions and tag each file with the version applied.
Review cadence
The follow-up sample should reuse the guide and the population rule so the comparison means something. If the rule changed, mark which version applies to each file and keep both extracts. The Mortgage Assistant reruns the measure after the repair and reports whether the gap actually narrowed. A decision someone can reproduce matters more than a precise-looking number.
Put the next review on the calendar and name the person who owns both the measure and the follow-up. Close with a single process change, its owner, and a date to recheck, not a wish list. If the same defect returns, repair the form, the source, or the routing rule before retraining anyone. The Mortgage Assistant reuses the same sampling rule and stores the note beside the change record.
Put the brief to work
Use the finding as a review prompt, not as a substitute for policy or accountable judgment. Compare the cited source material with your current record, decision owner, and escalation path.
For implementation context, review the scope and handoffs in CRM and pipeline support.
Compare this evidence with How often do investor delivery files have a complete audit trail? to test a related workflow boundary.
Sources and further reading
These are the public sources associated with this brief. Open each source to review its scope and current guidance directly.
Evidence into operations
Review the workflow behind the evidence
Bring one recurring mortgage workflow and its current handoff. We will help identify the preparation, review, and escalation boundaries.
Discuss the workflow in a free call