Case Study 19.2 — The Condition That Sat: A File Lost to a Verification Nobody Owned

⚠️ This is a labeled composite. No borrower, lender, employer, or transaction described below is real. The file is assembled from documented industry patterns — third-party verification delays, employer acquisitions that break HR contact paths, loan-origination-system statuses that read as completion, and financing contingencies allowed to lapse — and all figures are constructed for teaching. Nothing here should be read as an account of an actual transaction.

Background: a clean file with one loose end

A two-borrower purchase, both W-2 wage earners, no credit events, no self-employment, no gift funds, no unusual deposits.

THE COMPOSITE FILE                                        [constructed teaching example]

  Contract price ................. $298,000
  Down payment, 5% ............... $14,900
  Loan amount .................... $283,100        LTV 95.00%
  Program ........................ conventional 30-year fixed
  Qualifying income .............. $7,200.00/month
  Contract closing date .......... day 45
  Appraisal contingency .......... day 25
  FINANCING CONTINGENCY .......... day 32
  Earnest money .................. $4,000
  Conditional approval ........... day 22, nine conditions

One fact in the file required extra work. Borrower 2 had changed employers seven months before application — a lateral move within the same field, at slightly better pay, of the kind that strengthens a file rather than weakening it. But the two-year history behind that job sat with a prior employer, and the underwriter conditioned for a written verification of employment covering it.

Condition 6 of nine. Source: third party. Type: prior-to-doc. Nobody doubted the employment. There was a W-2 in the file, and a final paystub, and the borrower had worked there for six years.

That condition is the entire case study.

The issue: "ordered" is not an owner

By day 30, eight of the nine conditions had cleared. Condition 6 had not, and here is the full anatomy of why — because none of the four failures below is unusual, and all four together are completely ordinary.

One: the request went to an address that no longer received mail. The processor's verification vendor sent the written VOE request to the prior employer's HR address of record. That employer had been acquired eighteen months earlier, the office had closed, and mail was not being forwarded. Nothing bounced. Nothing failed visibly. The request simply went nowhere.

Two: the loan origination system said "ordered." Every day the loan officer looked at the pipeline, condition 6 showed a status of ordered — awaiting response. That status is informationally identical to nothing is happening, and it reads as handled. This is worth naming as a general hazard: a system status is a record of an action, not a record of progress.

Three: each of the two people who could have chased it believed the other had. The loan officer assumed the processor was following a vendor order, because vendor orders are processing work. The processor assumed the loan officer was tracking it, because prior-employer history is an underwriting-strategy question and those come from the front end. Neither assumption was unreasonable. Neither person was assigned.

Four: the condition read as harmless. It was a documenting condition, not an interrogating one. Everybody who looked at it correctly concluded that it carried no credit risk — the employment was real, the W-2 was in the file, and the verification would confirm what everyone already knew.

That last one is the trap this case study exists to teach, and it is a limit on the triage rule in §19.2 of the chapter. A condition can carry zero credit risk and enormous schedule risk at the same time, and a third-party source is what converts the second into the first. You cannot make a stranger's HR department hurry, and a document you cannot obtain is not less fatal for being uncontroversial.

What it shows: the day the file actually died was not the day anyone noticed

Follow the calendar.

WHERE THE FILE WENT                                       [constructed teaching example]

  day 22   Conditional approval, 9 conditions. Condition 6 ordered same day.
  day 30   8 of 9 cleared. Condition 6 status: "ordered — awaiting response."
  day 32   ► FINANCING CONTINGENCY EXPIRES. No extension requested.
  day 39   Closer requests the file. Condition 6 discovered open — 17 days old.
  day 40   Acquiring company's HR shared-services line located. Standard
           turnaround for a written verification: ten business days.
  day 41   Lock extension purchased. 0.125 point on $283,100 = $353.88.
  day 43   Exception requested: accept W-2, final paystub, and tax transcript
           in lieu of the written VOE. Approved in principle; transcript pending.
  day 45   Contract closing date. Missed.
  day 47   Seller delivers notice of termination.
  day 52   Earnest money of $4,000 returned after negotiation. House gone.

The file was discovered to be in trouble on day 39 and everybody involved treated that as the day things went wrong. It was not. Day 39 was the day the symptom surfaced.

The file died on day 32, when a financing contingency expired on a loan that had one open condition and no confirmed path to closing it. Until day 32, the buyers had a contractual right to walk away and recover their deposit if financing did not come together — and, just as importantly, a reason for the seller to grant an extension rather than terminate. After day 32 they had neither. The seller, on day 47, was not being punitive. The seller was exercising a right the buyers had handed over fifteen days earlier.

Why didn't the loan officer ask for an extension on day 30? The honest answer, and the one worth sitting with: because asking felt like an admission of failure. Eight of nine conditions were cleared. The ninth was paperwork. Calling the buyer's agent to say "I have a condition I am not sure I can get" reads, in the moment, as broadcasting incompetence to the person who sends you referrals.

It is the opposite. A contingency extension requested on day 30, from a position of eight-of-nine strength, is a routine amendment that sellers grant without a second thought. The same request on day 45 is a plea. Chapter 20 covers what a financing contingency actually protects and how an extension is documented; the point here is narrower and it is about character rather than paperwork. The instinct to delay bad news is the single most expensive instinct in this business, and it feels, every time, like professionalism.

Outcome: what it cost, and to whom

The earnest money was returned, which is the one merciful line in the table and was not guaranteed. It came back because the seller's counsel accepted a negotiated release rather than pursuing the deposit; with an expired financing contingency, that outcome was a matter of the seller's disposition, not the buyers' right.

Note what does not appear in that table. There is no credit problem. No income shortfall. No appraisal gap. No fraud, no misrepresentation, no adverse underwriting decision of any kind. The written verification, when it finally arrived, confirmed exactly what everyone had believed all along. The loan was always approvable. It was never closeable, from day 30 onward, and nobody knew it.

The lesson, and the contested part

Three lessons are uncontroversial:

1. Order third-party conditions first and confirm receipt by a human. Not "sent." Received, by a named person, with a stated turnaround. A verification request that goes to a dead address fails silently, and silence is the failure mode you cannot see.
2. A status is not an owner. If the answer to "who owns condition 6?" is a screen, the condition is unowned.
3. Age the list, not the difficulty. Condition 6 was seventeen days old on day 39 and it was the easiest item on the sheet. The daily question is not what is hard but what is oldest.

The contested part is harder, and it is worth arguing out loud with colleagues rather than reading past.

Was the real error the condition, or the contingency? One reading says the file died of an ownerless verification and the contingency was a secondary casualty. Another says the verification was recoverable — sellers extend for financing all the time — and the file died the moment the buyers' protection lapsed without anyone converting a paperwork problem into a contract conversation. The two readings imply different fixes: better condition tracking, or better willingness to make an uncomfortable call fifteen days early. Most experienced originators will tell you the second is rarer and worth more.

And what about the triage rule? Chapter 19 teaches you to read interrogating conditions first, because those are the ones that can change the loan. That rule is correct and it did not help here, because condition 6 was purely documentary. The refinement this file forces: triage twice — once by credit risk, and once by whether you control the counterparty. An item you cannot chase belongs at the top of the list no matter how harmless it is.

Discussion questions

1. Rank the four failures in the "issue" section by how easy each is to prevent, and design the single cheapest control that would have caught at least two of them.

2. The loan officer did not ask for a contingency extension on day 30 because it felt like admitting trouble. Write the eighty-word call you would have made instead. Then write the call the agent would prefer to receive on day 45 if you did not make it.

3. This file had zero credit risk and lost the house anyway. What does that do to the way you would explain "approved with conditions" to a borrower and to an agent?

4. The chapter says interrogating conditions are the dangerous ones. This case study says a purely documenting condition killed a file. Are these in conflict? State the combined rule in one sentence you could actually use on a Wednesday afternoon.

5. Compare this file with the Linden Street file. Both lost time to something nobody was watching. One closed and one did not. Identify every structural difference that explains the different outcomes — and say honestly how much of the difference is skill and how much is luck.

6. Suppose you inherit this file on day 39. You have six days, a ten-business-day HR turnaround, and an expired financing contingency. Write your plan in five steps, in order, and name the one step most loan officers would skip.