How often do condition deadlines slip after a borrower responds?

A borrower can respond on time and still watch a condition deadline pass. The documents arrive, but the review queue is full, the condition is unclear, or the reviewer asks for a second explanation. The borrower did what was asked and the file still lost days. That gap is the subject of this study. The protocol measures how often a condition deadline slips after a borrower response. It separates the borrower's response time from the internal review time. The separation matters because a team that only tracks borrower behavior will miss the queue it controls.

Question and scope

The study asks what share of borrower responses fail to clear the condition by its due date. Scope names the team, the condition types, the period, and the systems used. A team might study income and asset conditions on purchase files during a four-week window. The result describes that setting and should not be presented as an industry average.

Define the due date before collecting data. The due date may come from the condition record, the lender's deadline, or the team's service standard. Use one source and state it. A study that mixes deadlines from different sources cannot compare files.

Decide whether the unit is the condition or the file. A file can have several conditions with different responses and deadlines. Count each condition separately and report the file-level share beside the condition-level share. The two numbers answer different questions.

Defining a borrower response

A borrower response is a submission that includes the item the condition requested. A message that says "sending soon" is not a response. A partial upload that omits a required page is a response attempt, not a complete response. The protocol should state how attempts are recorded.

Record the time the response arrived in the team's system, not the time someone opened it. The arrival time is the fair start for the internal clock. If the document arrived after hours, start the clock at the next business morning. State the rule so the calculation is reproducible.

Separate a response from a re-response. A second upload after a review request starts a new segment. Report the first response and the re-response separately. Combining them hides the cost of an unclear request.

Defining a slipped deadline

A deadline slips when the condition is not cleared by its due date. Clearance means the reviewer has accepted the document and recorded the decision. A document that is received but not reviewed is not cleared. A condition marked pending review is not cleared.

Use the recorded due date, not a date reconstructed later. If the due date changed, record both the original and the revised date. A moved deadline can be legitimate, but it should be visible in the analysis. A study that silently accepts every extension will undercount the problem.

Report the size of the slip in business days. A one-day slip and a ten-day slip have different causes. A median alone can hide a long tail, so show the distribution. The share of conditions that slip is the headline, and the distribution explains the cost.

Sampling conditions

Use a sample that covers the condition types the team handles. Income, assets, credit, property, and disclosure conditions can behave differently. A sample drawn only from asset conditions may miss the review bottleneck in income. Stratify by type when the volume allows.

Use consecutive weeks rather than a convenience sample. A closing week can produce a different pattern from a quiet week. If the team cannot sample every week, rotate the weeks across a quarter. Record the volume so the reader can judge the sample. Include conditions that were cleared early and conditions that are still open at the end of the window. Excluding open conditions biases the result toward fast files. For open conditions, record the status at the cutoff and treat it as not cleared by the due date if the date has passed.

Capturing the internal queue

Record when the response entered the review queue and when a reviewer first looked at it. The difference is the queue delay. Record when the review was completed and when the condition was marked clear. The difference is the review time.

Ask reviewers to note the reason for a second request. The reason may be a missing page, an illegible image, an expired document, or a guideline mismatch. Use a short list and one free-text field. A reason list that is too long will not be used.

Capture the reviewer's workload at the time of the review. A simple band, such as light, normal, or heavy, is enough to show whether the queue was under pressure. Do not ask for an exact count unless the system provides it. The band is a context variable, not a performance score.

Coding and agreement

Have a second reviewer code a subsample of conditions. Compare the due date, the response time, the clearance time, and the slip reason. Report agreement for each field. A low agreement on the response time usually means the arrival source is ambiguous.

Write a rule for the ambiguous cases. For example, decide whether a document delivered by the borrower's agent counts as a borrower response. Write the answer in the protocol and apply it to the rest of the sample. Keep the examples that caused the disagreement.

Do not change the definition during the sample. If a rule must change, start a new segment and report both segments. A mid-study change can move the share for reasons unrelated to the work. The baseline segment should remain usable.

Reporting the result

Report the share of conditions that slipped, the median slip in business days, and the share of slips caused by internal review. Break the result down by condition type and by reviewer workload band. Show the borrower response time separately so the reader can see the two clocks. A high slip share with fast borrower responses points to an internal queue problem. A high slip share with slow borrower responses points to a communication or collection problem. A mix points to a process that needs both. The breakdown keeps the team from blaming the wrong step. Pair the result with the rework count. A condition that slips because the first request was unclear is different from one that slips because the queue was full. The mortgage operations support lead can use the pair to choose between a template fix and a staffing change.

What the result can change

A high internal slip share may justify a review schedule, a clearer intake rule, or additional review capacity. A high borrower-response slip share may justify a reminder sequence, a better explanation, or a different channel. The study should list the candidate changes before recommending one. Test one change on a small group and rerun the protocol. A review schedule is easy to test because the team can compare queue delay before and after. The test should run for a full closing cycle. Keep the definitions stable so the comparison is valid. If the slip share does not move, the team may have a genuine capacity gap or a condition mix that requires more review time. The loan processing support team can review the condition types and the reviewer assignments. The result should distinguish a workload problem from a communication problem.

Limits and sources of error

The study measures recorded timestamps, not the quality of the review. A quick clearance can be correct or careless. Pair the timing with a quality sample so speed is not rewarded on its own. Report the quality result beside the slip share.

A due date is a policy choice, not a natural fact. A team with tight deadlines will show more slips than a team with loose deadlines even when the work is similar. Report the deadline source and the range. Do not compare teams with different deadline rules.

The sample may miss conditions that were resolved outside the tracking system. A phone call that closes a condition without a record will look like a slip. Add a short prompt for offline resolutions. The prompt improves coverage without changing the definition.

Review cadence

Repeat the study after a change to the condition list, the review queue, or the borrower communication. Use the same definitions and the same sampling rule. A slip share that falls while rework rises may mean the team is clearing conditions without enough evidence. The quality sample should catch that tradeoff.

Share the result with the reviewers and the borrower-facing team. Ask which conditions were hardest to clear and which requests created a second response. The discussion can reveal a template that invites a follow-up. The next study should test one of those findings.

End with a sentence that states the slip share, the internal share, and the period. A precise finding with a named owner is more useful than a broad claim. The Congressional Research Service's mortgage market reports and the Consumer Financial Protection Bureau's mortgage resources provide context for the borrower timeline. The goal is a condition that clears on time because the process, not the borrower, was ready.