SPStackPilotOperating school

Mortgage Loan Officers · Chapter 05 of 10

Application to clear to close

Three CFPB clocks carry this whole file: the Loan Estimate, the appraisal copy, and the Closing Disclosure. Everything else, the lock, the conditions, the weekly update, is what an LO does in the space between them.

Nothing in this chapter is a rate quote, a promise about when a specific file will close, or advice about which program to choose. The dates, ranges, and rules below are the CFPB's own timing structure and the industry's dated 2026 practice around it, and every number carries its source. The three-day clocks are the skeleton; the milestone map, the lock, the conditions chase, and the weekly update are how an LO runs the muscle around them.

The application moment

An "application" under TRID is not a form, it is six pieces of information: the borrower's name, income, Social Security number, the property address, the estimated property value, and the mortgage loan amount sought. Receipt of the last of these six starts the clock verified [1]. The creditor must deliver or place the Loan Estimate in the mail no later than the third business day after that sixth piece arrives, where "business day" means a day the creditor's offices are open for substantially all business functions verified [1]. Know this moment precisely: an LO who does not track which of the six pieces is still missing can accidentally start a clock without meaning to, or fail to start one that already started.

The borrower must then affirmatively indicate intent to proceed with the loan described in the Loan Estimate before the lender may collect any fee beyond a bona fide credit report fee, and in most cases before the lender will lock the rate verified [2]. Intent to proceed is a distinct, later moment from application; do not conflate the two when explaining the process to a borrower or an agent partner.

The milestone map

Stage names and exact sequencing vary by LOS and lender, but the shape below is common across the industry report [5]. Use it as a conversation map, not a promised calendar.

StageWho actsWhat the borrower seesWhat the LO sendsClock or typical timing
Application (six pieces received)LO, LOAConfirmation of application receivedLoan EstimateLE within 3 business days verified [1]
Intent to proceedBorrower, then LOA request to affirm intent to proceedConfirmation, then rate lock if applicableNo fixed clock; precedes most fee collection and locking verified [2]
ProcessingProcessorA document request listStatus update, outstanding itemsVaries by file completeness report [5]
Submission to underwritingProcessor, underwriterLittle, unless askedWeekly status updateVaries by lender queue report [5]
Conditional approvalUnderwriterA conditions listConditions chase list, requests to borrowerVaries; some companies flag a file at 15 days without conditional approval as a check-in point report [9]
Appraisal ordered and returnedLO orders through the AMC; appraiser inspectsAppraisal copy on completionECOA-required copy deliveryPromptly on completion, or 3 business days before consummation, whichever is earlier verified [4]
Clear to closeUnderwriterNotice conditions are clearedClosing DisclosureCD at least 3 business days before consummation verified [7]
Closing and fundingTitle/escrow, LOSigning appointmentFinal coordination with title and the agentSame day in most purchase transactions; rescission-affected refinances add a delay inference

On turn time: two secondary sources give different 2026 figures for average application-to-close time, an average closing time of 38.2 days per one summary of ICE Mortgage Technology's May 2026 report (not independently opened; the report itself returned a blocked fetch), and roughly 43 days per a separate secondary source citing "the most recent ICE data" report [8]. These are not from the same measurement window and should not be treated as reconciled; present a range, roughly 38 to 43 days, and say plainly that the two figures are not confirmed against each other. Pull-through rate, the share of submitted applications that actually close and fund, has no single confirmed current industry-wide figure either; use your own trailing numbers, not a borrowed industry average report [8].

Rate lock and extensions

Locking generally follows intent to proceed. If a signed rate lock goes into place after the initial Loan Estimate was issued without one, Regulation Z requires a revised Loan Estimate within three business days of the lock report [3]. Floating versus locking is the borrower's decision, made from facts you supply: the current rate environment, how long the file is expected to take, and what your company charges for a lock extension if closing slips past the expiration, including for a lender-caused delay. Extension cost and procedure vary by company and investor and must be disclosed in writing; never quote an extension cost as a fixed industry number, and never present locking or floating as advice about which choice is right for a specific borrower report [3]. State the fact, let the borrower decide: "here is the lock length, here is what an extension costs on this file, here is the file's current pace."

Processing and conditions

A processor assembles and verifies documentation and submits the file first to automated underwriting, then to a human underwriter for conditional approval; underwriting returns a conditions list covering income, asset, title, and insurance items, and appraisal-related items where relevant, all of which must clear before the file reaches clear to close report [5]. The conditions chase is the highest-leverage weekly task on an active file: know who owns each open condition (borrower, title, insurance, the LO, the appraiser), what exactly is needed, and by when, and follow up before the underwriter has to ask twice.

Appraisal

The appraisal is ordered through the company's appraisal management company (AMC), not hand-picked by the LO, and the borrower must be notified within three business days of application of their right to a free copy of any appraisal or written valuation verified [4][11]. The completed appraisal copy itself must be delivered promptly upon completion, or no later than three business days before consummation, whichever is earlier; the borrower may waive that specific timing, but not the delivery itself, and the waiver must be given at least three business days before closing verified [4][11]. Do not let a completed appraisal sit in the file; trigger delivery the moment it is done, not when the closing package is assembled.

When an appraisal comes in low, present facts and let the borrower and the borrower's agent decide, without advising which option to take:

  • Renegotiate the purchase price with the seller, through the borrower's agent.
  • Bring the difference between the appraised value and the contract price to closing in cash.
  • Dispute the appraisal through the company's formal reconsideration-of-value process, if one exists.
  • Walk under the contract's appraisal contingency, if the contract has one.

Each of those four is a fact about what is available, not a recommendation. The borrower's agent and the borrower make the call.

Underwriting findings

Most files run through an automated underwriting system (AUS): Fannie Mae's Desktop Underwriter (DU) or Freddie Mac's Loan Product Advisor (LPA), and many lenders run both to find the best execution verified [6]. DU returns a recommendation such as Approve/Eligible or Refer with Caution; LPA returns a separate risk class and purchase-eligibility result. A "Refer" outcome routes the file to full manual underwriting against written guidelines rather than the automated system's own findings verified [6]. An AUS finding is not a final approval; it is an input the human underwriter still has to work from, and it is never something an LO explains to a borrower as a decision in itself.

The CD and the three resets

The Closing Disclosure must reach the borrower at least three business days before consummation verified [7]. Only three specific triggering events restart that three-day clock; every other correction requires a corrected CD but does not restart the wait.

TriggerResets the 3-day clock?
APR becomes inaccurate beyond tolerance (generally 1/8 of a percentage point for regular transactions, 1/4 point for irregular ones)Yes
The loan product changes (for example, fixed to adjustable, or an interest-only feature is added)Yes
A prepayment penalty is addedYes
Any other correction: a fee change within tolerance, a typo, a name spellingNo, but a corrected CD is still required at or before closing

This three-trigger rule is a common point of confusion; know it precisely, because a mistaken reset (or a missed one) directly moves a closing date verified [7].

Closing and funding

Closing (signing) and funding (disbursement of loan proceeds) can happen the same day in most purchase transactions. Certain transactions, notably a refinance of a primary residence, carry a three-business-day right of rescission that pushes funding out; a primary CFPB step-by-step diagram of closing and funding timing specifically was not confirmed in this pass, so treat the same-day-versus-delayed distinction as a general fact to verify against your own company's closing calendar, not a promised timeline inference. Coordinate the actual signing date and time directly with title and the borrower's agent; that coordination is the LO's job, not something a document draft can stand in for.

The weekly status update

Regular, commonly weekly, proactive updates to both the borrower and the referral partner are a widely cited service-differentiation norm in the industry, not a regulatory requirement report [9]. Speed and communication consistently rank as what agents and builder reps want most from a lender relationship, which is exactly what a fixed weekly update format delivers without depending on the LO remembering to send one report [9]. Keep the format fixed and factual every time.

WEEKLY STATUS UPDATE
Borrower: [name]
Property: [address]
Loan officer: [name], NMLS #[number]

Current stage: [application / processing / underwriting / conditional approval /
clear to close / closed]

This week:
- [what happened, factually: "submitted to underwriting," "appraisal ordered,"
  "two conditions cleared"]

Still needed from you:
- [specific outstanding item, if any, and who it is needed from]

Next expected step: [the next stage in the process, not a date]

Questions: [LO name], [phone], [email]

What never goes in a weekly status update: a promised closing date before title and underwriting have both confirmed one, any rate talk, and any program advice or comparison. The update reports facts about where the file stands; it does not forecast, and it does not sell.

What causes delays

Secondary sources converge on a short, consistent list: incomplete or illegible documentation as the most cited cause, appraisal turnaround and valuation issues, last-minute borrower financial changes such as new credit, a job change, or a large undocumented deposit, and communication breakdowns among borrower, lender, agent, and title or escrow report [10]. One source characterizes delays as usually the accumulation of several small neglected tasks rather than one large catastrophic issue, and estimates roughly one in three transactions experiences a delay that pushes the closing date report [10]. The documents checklist from the previous chapter and the weekly status update in this one are the two highest-leverage tools an LO has against both causes.

Claude workflow: weekly borrower status update

Trigger: the LO's regular pipeline review, or a specific file crossing a stage change.

What Claude prepares: a draft weekly status update in the compliance-approved template, built strictly from the LO's own stage notes for that file: what happened, what is still needed, and the next expected step.

What the human checks and does: confirms every fact in the draft against the actual file status, removes anything that reads as a promised date, rate talk, or program advice, and sends it through the company's approved borrower-communication channel.

What is never automated: sending a status update directly to a borrower or partner without a human review, and stating or implying a closing date that title and underwriting have not both confirmed.

Claude workflow: conditions chase list

Trigger: a file receives a conditions list from underwriting.

What Claude prepares: a chase list from the conditions list, organized by who owns each item (borrower, title, insurance, appraiser, LO), what exactly is needed, and a follow-up date the LO sets.

What the human checks and does: verifies the chase list matches the actual underwriting conditions letter word for word, follows up directly with each party, and confirms each condition is actually cleared before marking it done.

What is never automated: deciding a condition is satisfied; that determination belongs to underwriting, working from the documents actually submitted.

Claude workflow: low appraisal options memo

Trigger: an appraisal returns below the contract price.

What Claude prepares: a factual options memo listing the paths available on this file: renegotiate the price, bring the difference in cash, dispute through the company's formal process, or walk under the contract's appraisal contingency, each stated as a fact about what exists, not a recommendation.

What the human checks and does: confirms which options actually apply to this specific contract and lender, and the human and the borrower's agent, not the LO alone and never Claude, decide which path the borrower takes.

What is never automated: recommending one option over another to the borrower, or drafting any communication that reads as advice rather than a list of what exists.

What stays human

  • Tracking which of the six application pieces are in hand, and knowing precisely when the LE clock starts.
  • Every decision to lock or float, made by the borrower from facts the LO supplies, never as advice.
  • Verifying every condition is actually cleared before a file moves toward clear to close.
  • Triggering appraisal copy delivery to the borrower the moment the appraisal is complete, never waiting for the closing package.
  • Deciding, with the borrower and the borrower's agent, what happens after a low appraisal; the LO presents facts, not a recommendation.
  • Reviewing every Claude-drafted status update or chase list against the actual file before it reaches a borrower or partner.

Do this today

  1. Pull one active file and confirm you know exactly which of the six application pieces started its Loan Estimate clock, and the date it did.
  2. Check your company's current rate lock extension policy and cost so you can state it as a fact, not an estimate, the next time a file is at risk of slipping past its lock.
  3. Set up your own fixed weekly status update template from the format in this chapter, and confirm it with compliance before using it on a live file.

Sources

  1. CFPB: TILA-RESPA Integrated Disclosure FAQs, retrieved 2026-09-04.
  2. CFPB: Intent to Proceed, retrieved 2026-09-04.
  3. RateBeat: Application date vs. intent to proceed and the rate lock, retrieved 2026-09-04.
  4. Federal Register: Disclosure and delivery requirements for copies of appraisals under ECOA, retrieved 2026-09-04.
  5. AnnieMac: What actually delays a closing, retrieved 2026-09-04.
  6. Fannie Mae: Desktop Underwriter/Desktop Originator, retrieved 2026-09-04.
  7. CFPB: The Closing Disclosure three-day rule, retrieved 2026-09-04.
  8. AnnieMac: turn time and pull-through context, retrieved 2026-09-04; ICE Mortgage Technology May 2026 Mortgage Monitor cited via secondary summary, direct fetch blocked.
  9. AnnieMac: the 15-day conditional-approval check-in norm and the weekly update norm, retrieved 2026-09-04.
  10. Gustan Cho Associates: delays in mortgage loan closings, retrieved 2026-09-04.
  11. CFPB: Regulation B, 12 CFR 1002.14, appraisal and valuation copy delivery, retrieved 2026-09-04.
  12. Operator evidence, from a Phoenix buyer's agent who works new construction with builder lenders: rate lock and appraisal-contingency steps of the 12-step new-construction buying process, retrieved 2026-09-04.

← Previous  ·  All chapters  ·  Next →

Starting from zero? Use the field manuals first.

02 · BEFORE YOU BUY SOFTWARE
If you're still choosing the buyer, offer, stack, agents, content, customers, and delivery, don't start with a tool: start with the manuals. These create local worksheets only: no checkout, outreach, or account setup.

Find the first manual

Not sure which guide to open first? Start from your stuck point and let the finder recommend the next manual and the first worksheet question. No personal data is collected: it just points you at the right starting move.

Work the starter pack

Move through buyer, offer, stack, agents, content, customers, and delivery as a sequence of short local worksheet sessions. One artifact at a time, in order, so you build the business instead of browsing for it.

See what "done" looks like

Read a fully worked field manual before writing your own version, so the output feels concrete: a real, numbered workflow with the risky steps gated, not a fake proof claim.

STARTER PACK · 7 WORKSHEETS

Get the starter pack as one download.

Keep the whole from-zero sequence together when you are ready to work it.

Instant pack link. Occasional field notes. Unsubscribe anytime.