Key finding
The impact share should name the affected lock status and the borrower communication, because a reviewed sheet does not prove the file was repriced.
Question and scope
We frame rate sheet impact as a documentation question rather than a credit or sales question. The test is whether a stranger can follow the file from the source document to the recorded action. Unit, population, and window are locked below before the first file is drawn. The final section says what the review cannot see.
We want to know whether a closed rate sheet impact file lets a second reviewer find the source, the reviewer, and the decision date. The team applies the finding to one workflow, not to a person or a borrower. Only the population described below is in scope, and the rest of the pipeline stays outside the review. This is a desk method for a mortgage operation, not a vendor benchmark.
Our protocol takes one mortgage team and asks what the rate sheet impact file actually documents. We call the result a local reading of retained records, not an industry rate, a legal opinion, or a forecast. A fixed population and a fixed calendar window frame the answer, and both are printed with every table. An operations lead with the same pipeline export can repeat the work from the steps below.
Population and unit
Our unit is one rate sheet change affecting active loan files, counted once under an identity rule we write down. Before pulling a file, we name the opening event, the closing proof, and the pause condition. If the pipeline changes size during the window, a bare total is no longer a measurement. We list every removal with a reason so a colleague can rebuild the sample.
We count one one rate sheet change affecting active loan files once, and the identity rule sits beside the extract. Our window spans a normal month and at least one week of heavy volume. Outages, staffing gaps, and investor changes are noted as context rather than deleted. If the rule changes, both versions survive and each file is tagged with the version used.
Definitions and measures
A compact field guide records each field, the values it may take, and the document that proves it. Blank, unavailable, and confirmed-negative answers each get their own column. The headline figure is the share of affected files reviewed before the next lock; it never travels without the denominator and the window. A bare percentage cannot tell a desk what to repair.
We define a finished rate sheet impact file before the export is opened. The definition lists the documents required, the source we accept, and the treatment of a blank field. We report the share of affected files reviewed before the next lock, with the eligible count and the exact dates of the window. Next to it sit the missing-document count and the age of the oldest open file.
A file is complete for this review when it supports the share of affected files reviewed before the next lock with a dated source and a named reviewer. The guide also settles how reopened files and duplicate files are counted. We print the sample count, the unresolved total, and the oldest open item beneath each result. Those three numbers stop volume, evidence, and delay from masking each other.
Evidence standard
A file passes only when and appear in the approved system under the same loan number. Where two records conflict, both are kept and we note which one drove the decision. Every estimated figure is marked as an estimate so a later reader cannot mistake it for a verified value. We want a trail another person can follow, not a flawless folder.
We settle the evidence test for rate sheet impact before choosing the first file. It identifies the document that counts, the date that travels with it, and the rule for a blank value. A one-page guide is attached to the extract so the standard does not live only in one reviewer's memory. That guide is part of the method and ships with the finding.
Sampling and collection
We choose a random or systematic start and then take consecutive files within each stratum. Strata cover stage, owner, and exception so the easiest files cannot dominate. One hard case is always included: a missing document, a conflict, an absent owner, or a forced deadline call. Each access failure is logged rather than quietly replaced with a different file.
The extract starts with the pipeline export for rate sheet impact, not a set chosen after the result is known. The selection rule, the seed, and the exclusion log travel with the sample. Nothing is added once the result is visible, and no hard file is dropped to improve the rate. A repeatable draw lets the team rerun the review after the workflow changes.
Files come from the whole window, including the week when staffing was short and volume was high. A list built only from quiet weeks will make a weak control look stable. We record the observation time and the initials of whoever opened the file. When the eligible list is short, we show the raw count and say the estimate is unstable.
Analysis and reporting
We publish the spread, not only the average, because a median can hide a long tail of untouched files. Open counts and the oldest file by owner show where delay collects. A finding without an owner or a next step is not ready for the pipeline meeting. The result is written in ordinary language, with technical detail kept in an appendix.
We keep observation separate from interpretation and label every table with its denominator and dates. The oldest open file and the missing documents are shown, not just the completion percentage. The report names the next decision and the operations owner who must make it. The sample count sits beside each rate so a reader can weigh the evidence.
Limits and sources of error
Sampling error, coder disagreement, and documents that never entered the system each cap what the number can claim. The overlap agreement and any disputed code are published 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.
Completing the paperwork does not establish that the lending decision was sound, 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. Caveats sit directly under the finding so a reader cannot lift the number without them. If the rule changes midstream, earlier and later versions are retained and each file is tagged.
One hard boundary is that a rate sheet impact record can be late, partial, or held outside the loan system. The method cannot recover work that left no trace or prove that a policy was followed in a silent file. Those caveats are printed beside the finding rather than buried in a footnote. Changes to systems, investor rules, product mix, or volume can date the result, so we list those triggers.
Review cadence
Schedule the next check and assign one person to own both the measure and the follow-up. It closes with a single process change, its owner, and a recheck date, not a wish list. If the same defect returns, we repair the form, the source, or the routing rule before retraining anyone. The same sampling rule is reused, and the note is stored beside the change record.
The review for rate sheet impact is finished when the sample closes and the field guide is attached. Extract, guide, and finding are filed together so a later reviewer can rerun the work. The closing note names what moved, what did not, and what the review still cannot see. That note is worth more than a neat rate built on a denominator nobody can explain.
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