What share of closing delays start with a missing wire confirmation?

Closing delays are often described after the fact as a title problem or a funding problem. The real cause may be a wire confirmation that never arrived, a call-back that was not returned, or an account detail that changed at the last minute. The delay is visible, but the sequence that produced it is not. A short timeline is the only way to tell a verification gap from a bank-side wait.

This protocol traces closing delays back to the wire confirmation step. It asks what share of delayed closings had a missing or failed confirmation as a contributing cause. It does not assume that every wire issue is avoidable. It separates a verification gap from a same-day borrower change and from a bank-side delay. The result is a description of one team's closing week.

Question and scope

The study asks what share of delayed closings include a wire confirmation gap as a contributing cause. Scope names the team, the closing types, the settlement partners, and the period. A team might study purchase closings with two title partners during a quarter. The result applies to that setting and should be reported with the scope.

Define a delayed closing before collecting data. A closing is delayed when the scheduled signing or funding time moves after the original date was confirmed with the borrower and the settlement agent. A closing that moves before confirmation is a schedule change, not a delay. The distinction prevents the study from counting routine rescheduling.

Decide which closings to include. A cash closing has different wire needs from a financed closing, and a refinance may have a different funding path. Include the closing types the team actually manages and report the mix. A blended share without the mix is hard to interpret.

Defining a wire confirmation gap

A wire confirmation gap exists when the team cannot produce evidence that the wire instructions were verified before funds moved. The evidence may be a call log, a confirmation email from a verified number, or a signed verification form. The gap may be a missing step, a late step, or a step that used an unverified contact. The reviewer should name which of those conditions applies rather than recording a generic gap.

The definition should distinguish a gap from a fraud event. A fraudulent instruction is a security incident, not only a process delay. The study can include the incident as a separate category, but it should not treat it as a routine confirmation gap. A fraud event needs its own review and response.

Do not count a wire that was verified correctly but arrived late at the bank. A bank-side delay is outside the team's confirmation step, even though it affects the closing. The protocol should record the cause as bank delay and keep it separate from a team gap. A clear category prevents the team from taking responsibility for something it cannot control.

Capturing the closing timeline

Record the scheduled signing time, the scheduled funding time, the actual signing time, and the actual funding time. Add the time the wire instructions were received and the time they were verified. The four timestamps let the reviewer see where the schedule moved. A single closing date is not enough to identify a delay.

Record the person who confirmed the wire and the source of the phone number. The source should be a verified directory, a prior signed document, or a direct call to a known contact. A number from an email is not a verified source. The note should say which source was used and when.

Capture the reason for any change to the wire instructions. A borrower may change a bank account, or a title partner may issue corrected instructions. The reason and the time of the change matter because a late change can trigger a new verification. The note should name who requested the change and who approved it.

Sampling closings and delays

Use a sample of closings that were scheduled during the period, not only the ones that were delayed. A sample of delays alone cannot estimate the share of all closings affected by a wire gap. The denominator should be the closings that were scheduled, including the ones that closed on time. Record the scheduled count and the delayed count in the report so the share is reproducible.

Include closings across settlement partners and loan types. A partner with a different wire process may produce a different delay pattern. The sample should reflect the team's actual mix. If one partner is excluded, the report may miss its most common issue.

Record the sample method and the number of closings. A convenience sample of the files the team remembers is not a trend. A rotating sample over a quarter gives a fairer picture without reviewing every closing. The report should state the sample size beside every share.

Separating causes

A closing delay can have more than one cause. A missing wire confirmation may combine with a late closing disclosure or a borrower who arrives late. The protocol should allow more than one cause and ask the reviewer to name the primary cause. The primary cause is the one that would have moved the schedule on its own.

Use a short cause list that the team can apply consistently. The list might include wire confirmation, closing document, borrower availability, title issue, lender funding, and bank delay. Add a category for unknown cause only when the evidence is insufficient. Too many categories produce inconsistent coding.

Review the cause list with the settlement partners. A partner may use a different word for the same step, and the difference can cause a misclassification. A short glossary helps the team and the partner describe the same event. The glossary should be part of the study record.

Measuring the hours added

Measure the delay in hours rather than days when the closing is same-day. A two-hour delay can matter for a funding cut-off even when the closing happens on the same date. Record the original time and the actual time, and calculate the difference. For multi-day delays, report both the days and the hours.

Separate the time spent waiting for the confirmation from the time spent fixing the cause. A confirmation that arrives late may add a short wait, while a changed account may add a longer re-verification. The two intervals point to different fixes. A single total hides the difference.

Pair the delay with the consequence. A delay that moves a signing but not the funding may be less costly than a delay that misses the lender's cut-off. The consequence helps the team prioritize the causes that matter. A short note is enough to show the effect.

Report the share of delayed closings with a wire confirmation gap as the primary or contributing cause. Show the number of closings sampled, the number delayed, and the number with a wire gap. A share without the denominator is not a finding. Show the hours added as a median and a range.

Break the share down by settlement partner and by closing type. A high share with one partner may point to a communication issue, while a high share across partners may point to the team's verification step. The breakdown is more actionable than the total. It also helps the team decide where to start.

State the limits clearly. The study measures recorded causes, not every conversation. A wire call that was made but not logged may look like a gap. The report should say whether the evidence rule required a log or accepted a recollection. A stricter rule produces a lower share but a stronger finding.

What the number can change

A high wire gap share does not automatically justify a new hire. It may justify a confirmation checklist, a verified contact directory, or a rule that no funds move without a recorded call-back. The study should list the changes that could reduce gaps before it recommends additional capacity. The team should separate a verification problem from a workload problem.

The mortgage operations support lead can test one change on a small group and rerun the protocol. A call-back log with a required source field is easy to test because the team can compare the gap share before and after. The test should run long enough to cover a normal closing cycle. Keep the test group small enough that the rest of the team can continue the normal work.

If the share stays high after the change, the team may have a genuine capacity gap or a partner process that requires more time. The loan processing support team can review the closing sequence and the partner contacts. The result should distinguish a verification problem from a workload problem. A measure that leads to the wrong fix is worse than no measure at all.

Limits and sources of error

The study measures recorded confirmation, not the actual security of the wire. A logged call may still have used an unverified number. The protocol should check the source of the number, not only the presence of a log. A confirmation that cannot be tied to a verified source is a weak confirmation.

The sample may miss closings that were delayed before the wire step. A closing that moved because of a title issue may never reach the wire confirmation. The study should record the stage where the delay occurred and avoid attributing earlier delays to the wire. A clear timeline is the best defense against misattribution.

The settlement partner may have its own record that differs from the team's. Compare the two records for a subsample and note the differences. A partner record can fill a gap in the team's log, but it can also introduce a different definition. The report should state which record was used.

Review cadence

Repeat the study after a change to the wire procedure, the settlement partner, or the closing calendar. Use the same cause list and the same sampling rule so the comparison is meaningful. A share that falls while the number of unlogged calls rises may mean the team is recording less, not confirming more. A comparison across different cause lists is not valid, so freeze the list before the second round.

Share the result with the closing coordinators and the settlement partners. Ask which confirmation step was hardest to complete and which change caused the most rework. The discussion can reveal a contact list that is out of date or a cut-off that nobody understands. The next study should test one of those findings.

End with a single sentence that states the gap share, the period, and the confirmation step the team can fix. A precise finding with a named owner is more useful than a long report. The goal is a closing day that moves on a verified instruction, not a hopeful email. The sentence should name the change the team can make, not a cause outside its control.