How much notice do borrowers get before a document deadline?

A document deadline can feel sudden to a borrower even when the team has known about it for weeks. The difference is often the date the borrower first heard about the request. This protocol measures the notice interval between the first clear request and the deadline, then checks whether reminders and channel changes affect the borrower's ability to respond. The measure starts with the date the borrower could first understand what was needed.

Question and scope

The question is how much calendar time a borrower receives between the first clear document request and the deadline attached to that request. The scope should name the loan types, the document categories, the communication channels, and the deadline types. A team might study purchase files with income and asset conditions received within thirty days of closing. The result describes that setting and should not be generalized to every borrower or every loan program.

Define a clear request before measuring. A clear request names the document, the period or signer, the channel, and the date by which the team needs it. A general message such as send your documents does not start the clock because the borrower cannot tell what is missing. The protocol should record only requests that meet the definition.

Separate the team's internal due date from the borrower's deadline. An internal target may be earlier than the date the borrower is told, and that gap is part of the notice the borrower actually receives. Measure both so the analysis can show whether the team is protecting its own schedule with a shorter borrower window. Record both dates so the analysis can show which one the borrower actually experienced.

Unit of analysis

The unit is one document request for one condition on one file. A condition that asks for two years of tax returns may produce one request, while a condition that asks for a tax return and a transcript may produce two. Use the request as the unit because the borrower experiences the request, not the abstract condition. Use the request as the unit because the borrower responds to a specific ask, not to a category.

Record the time of the first request, the time of each reminder, the stated deadline, and the channel. Add the document type, the loan stage, and the person who sent the request. The channel matters because a portal notification and a phone call may produce different response times even with the same notice interval. A channel change can reset the borrower's attention even when the deadline stays the same.

Keep borrower identity out of the working file. Use a request key that links to the system of record through an authorized reviewer. The borrower communication support lead should approve the fields and the retention rule. Notice data can show how the team treats borrowers, so the protocol should say how the results will be shared.

Defining the notice interval

Measure notice in calendar days from the first clear request to the stated deadline. Use calendar days rather than business days for the borrower-facing interval, because borrowers plan around weekends and holidays. Report business days as a secondary measure when the deadline is tied to a business process. Report the business-day equivalent only when the deadline is tied to a business process.

If the request is revised, keep the original request date and add a revision date. A revision can extend the notice or shorten it, and the analysis should show which. Do not reset the clock to the revision, because that would hide the time the borrower already spent on the original request. Treat the revision as a separate event in the timeline.

If the deadline changes, record both the old and the new date. A deadline that moves earlier reduces notice without any new request, and that is a distinct kind of pressure. The protocol should count those cases and report them separately from a short first request. The two situations need different fixes.

Sampling and observation

Use consecutive requests from a defined window, or a random sample with a recorded start. Include requests sent through every channel the team uses and every document type that appears often enough to compare. If the sample includes only portal requests, the result will miss the borrowers who receive email or phone calls. That omission can make the notice interval look better than it is.

Record the number of requests excluded and the reason. A request with no stated deadline cannot be scored, and a request that duplicated another within the same day is not a new event. Report the exclusions beside the interval. A high exclusion count suggests the request template is inconsistent, which is itself a finding.

Capture the borrower's first response as well as the team's request. A borrower who responds in an hour had enough notice for that document, while a borrower who responds after the deadline may have had too little. The response time does not prove the notice was adequate, but it helps interpret the interval. A response that arrives after the deadline is still useful evidence about the notice.

Data quality checks

Check that every request names a document, a deadline, and a channel. A request that lacks one of those fields cannot be scored. Mark the missing field rather than inferring it from a later message. An inferred deadline may reflect the team's hope rather than what the borrower was told.

Compare the recorded send time with the channel's delivery record. A message drafted on Friday and sent on Monday gives the borrower less notice than the draft date suggests. Use the send time, not the creation time, and note any delay between them. The mortgage operations support routine should define which timestamp counts as the request.

Check whether the borrower could access the channel. A portal message sent to an account the borrower never activated is not effective notice. Record the delivery status and any bounce or failed login. A request that was sent but not received belongs in a separate category from one that was received and ignored.

Analysis and reporting

Report the median and spread of notice days by document type, channel, and loan stage. A median alone can hide a group of borrowers who received very little notice. Show the share of requests with fewer than three calendar days and fewer than one business day. Those thresholds make the tail visible.

Compare notice with the borrower response time and the deadline outcome. A short notice interval that still produces on-time responses may be acceptable for a simple document, while a long interval with late responses may point to a confusing request. The combination is more useful than either measure alone. Avoid treating a long interval as proof of good communication.

Report the reminder pattern separately. A request with one reminder may produce a different response than one with four. The number of reminders is not the same as notice, and a team can send many reminders after a late start. The analysis should show the first request date and the reminder dates on the same timeline.

Limits and sources of error

The study measures the request as recorded, not the borrower's understanding. A borrower may receive a clear message and still not know what to send. The response and the follow-up messages are the best available evidence, but they are not a direct measure of comprehension. Report the limitation and avoid blaming the borrower for a request the team cannot explain.

The sample may exclude borrowers who never engaged. A borrower who did not respond at all may have received the request through a channel they do not use. Add the count of requests with no response and the channel mix for that group. That count gives the reader a sense of the borrowers the interval measure cannot describe.

Channel and template changes can shift the interval during the observation period. Record the dates of any change and avoid comparing periods across them without a note. A new portal or a revised reminder schedule may improve the interval for reasons unrelated to the team's effort. The next study should be designed to test that change.

Review cadence

Repeat the protocol after a template change, a channel change, or a new reminder schedule. Use the same definitions and sampling rule so the comparison is meaningful. If notice rises but response time does not improve, the request may still be unclear. Report both movements and the document types where they diverge.

Share the result with the people who write the requests. Ask which document types produce the most questions, and review the wording for those types first. The loan processing support team can test a revised request on a small group before a full rollout. The change should appear in the next sample.

End the report with the group that received the least notice and the reason the team can verify. Name the evidence needed and the owner who will bring it. A notice study that ends with a median but no action leaves the same borrowers with the same short window. The point is to find the requests that give borrowers too little time and fix the process that produced them.