Loan Pipeline Tracking Workflow Design
Design the complete loan origination pipeline tracking system, from application intake through funding, with automated status updates, borrower and agent notifications, pipeline reporting, and exception queue management.
Scope Confirmation
Confirm which pipeline components are in scope:
Component 1: Application Intake and Channel Capture
Origination channels to track:
| Channel |
Source System |
Data Capture Method |
Initial Status |
| Point-of-Sale (POS) system |
[Blend, SimpleNexus, BeSmartee, etc.] |
API integration |
Application submitted |
| LOS — manual entry |
[Encompass, BytePro, Calyx, etc.] |
LOS webhook or polling |
Application in progress |
| Referred (paper/email) |
Manual upload |
Staff entry in LOS |
Application pending |
| Wholesale broker submission |
Broker portal |
API or file import |
Broker submitted |
Required data at intake (minimum for 6-piece TRID application definition):
| Field |
TRID Required? |
Source |
| Borrower legal name |
Yes |
Borrower entry |
| Borrower SSN |
Yes |
Borrower entry |
| Property address |
Yes |
Borrower entry |
| Estimated property value |
Yes |
Borrower entry |
| Loan amount |
Yes |
Borrower entry |
| Income (used for qualification) |
Yes |
Borrower entry |
| Borrower DOB |
No |
Borrower entry |
| Email and phone |
No |
Borrower entry |
| Co-borrower information |
No |
If applicable |
| Loan purpose (purchase/refi) |
No |
Borrower selection |
| Property type |
No |
Borrower selection |
| Loan program |
No |
LO selection |
Application date rule (TRID):
Application is "received" for TRID purposes when all 6 required pieces are collected. The LE 3-business-day clock starts at application receipt. System must:
- Flag the exact date/time all 6 fields are populated
- Store this as the official
application_received_date
- Calculate
le_due_date = application_received_date + 3 business days (business day = Monday–Friday excluding federal holidays)
- Alert if LE has not been issued by day 2
Component 2: Milestone Status Tracking
Standard pipeline milestones:
| # |
Milestone |
Description |
Preceding Milestone |
Common SLA |
| 1 |
Application received |
All 6 TRID pieces collected; application date set |
— |
Day 0 |
| 2 |
Pre-approval issued |
Tri-merge credit pulled; DU/LP run; pre-approval letter generated |
Application received |
1–2 business days |
| 3 |
Under contract |
Purchase agreement received (purchase only) |
Pre-approval |
Borrower-dependent |
| 4 |
Disclosures sent |
LE and intent to proceed received |
Application received |
Day 3 (LE due) |
| 5 |
Intent to proceed received |
Borrower signed intent to proceed |
Disclosures sent |
Varies |
| 6 |
Processing — active |
Loan package submitted to processor; conditions collection underway |
Intent to proceed |
Day 5–7 |
| 7 |
Appraisal ordered |
Appraisal ordered through AMC |
Processing active |
Day 5–7 |
| 8 |
Appraisal received |
Appraisal report received and reviewed |
Appraisal ordered |
5–14 days from order |
| 9 |
Title ordered |
Title search ordered |
Processing active |
Day 5–7 |
| 10 |
Title received |
Title commitment received and reviewed |
Title ordered |
5–10 days from order |
| 11 |
Submitted to underwriting |
Complete loan package submitted to UW |
Processing active |
Day 10–15 |
| 12 |
Conditional approval |
UW issues conditional approval with conditions list |
Submitted to UW |
1–5 business days |
| 13 |
Conditions received |
All UW conditions collected and submitted |
Conditional approval |
Varies |
| 14 |
Clear to close (CTC) |
UW clears all conditions; loan approved |
Conditions received |
1–2 business days |
| 15 |
CD issued |
Closing Disclosure issued to borrower |
CTC |
3 business days before closing |
| 16 |
Closing scheduled |
Closing date/time/location confirmed |
CD issued |
— |
| 17 |
Closing |
Loan documents signed |
Closing scheduled |
— |
| 18 |
Funding |
Loan funded by lender; disbursement complete |
Closing |
1–3 business days |
| 19 |
Post-closing complete |
Post-close package reviewed; shipped to investor |
Funding |
1–5 business days |
Status change triggers:
Each milestone status change is triggered by one of:
- LOS event (automated): LOS webhook fires when LOS status changes
- Processor/UW action (semi-automated): Staff changes status in pipeline system after completing an action
- System detection (automated): Document received, time elapsed, condition cleared
- Manual (staff entry): Phone call confirmed, verbal acknowledgment received
Audit all status changes: record actor (staff member or system), timestamp, previous status, new status.
Component 3: Automated Milestone Notifications
Notification recipients:
| Recipient |
Relationship |
Channel |
Content Level |
| Borrower |
Primary |
Email + SMS |
Consumer-friendly, no jargon |
| Co-borrower |
Primary |
Email + SMS |
Same as borrower |
| Loan officer |
Internal |
Email + in-app |
Detailed milestone + next action |
| Processor |
Internal |
In-app task |
Action items |
| Real estate agent (purchase) |
External |
Email |
Brief status; no financial details |
| Listing agent (purchase) |
External |
Email |
Brief status; no financial details |
| Settlement agent / title company |
External |
Email |
Closing-relevant milestones only |
Borrower notification triggers and content:
| Milestone |
Notification Sent |
Subject Line |
Key Content |
| Application received |
Immediate |
"Your application is received — here's what happens next" |
Checklist of what they'll need to provide; timeline overview |
| Disclosures sent |
Immediate |
"Your Loan Estimate is ready — please review" |
LE summary; link to e-sign intent to proceed; LE explanation |
| Appraisal ordered |
Same day |
"Your appraisal has been ordered" |
Expected timeline; what appraiser access they need to provide |
| Appraisal received |
Same day |
"Your appraisal is complete" |
Result (value confirms/exceeds/below purchase price); next steps |
| Conditional approval |
Same day |
"You're approved — we need a few more items" |
Plain-English list of outstanding conditions; how to submit; priority |
| CTC |
Immediate |
"You're clear to close!" |
Congratulations; what to expect at closing; wire fraud warning |
| CD issued |
Immediate |
"Your Closing Disclosure is ready — please review" |
CD summary; 3-business-day window explained; final cash to close |
| Closing confirmed |
Confirmation |
"Closing confirmed for [date/time/location]" |
Location, what to bring (ID, cashier's check if applicable), wire instructions warning |
| Funded |
Same day |
"Your loan is funded — congratulations!" |
Next steps: first payment date, servicer information |
Component 4: Pipeline Dashboard and Reporting
Pipeline dashboard views:
Loan officer view:
- My pipeline: all active loans assigned to me
- Columns: borrower name, loan amount, program, loan purpose, current milestone, days in current milestone, CD due date, closing date, red flags
- Filters: milestone, loan type, closing date range
Manager/branch view:
- Full pipeline: all active loans by LO
- Pull-through metrics: application → CTC → funded rates
- Days-to-close by LO, loan type, lead source
- Loans at risk (closing within 7 days + not CTC)
- Fallout analysis: what stage are withdrawn/denied loans falling out?
Pipeline reports:
| Report |
Frequency |
Recipients |
Purpose |
| Daily pipeline snapshot |
Daily |
LO, processor, manager |
Current status of all active loans |
| Loans closing this week |
Monday AM |
LO, settlement, operations |
Closing preparation |
| Aged loans report |
Weekly |
Manager |
Loans stuck in a milestone > threshold days |
| Monthly production summary |
Monthly |
Branch / company |
Volume, pull-through, days-to-close by period |
| HMDA LAR data extract |
Monthly |
Compliance |
Required for HMDA reporting |
Pull-through rate formula:
Pull-through rate = Funded loans / Applications received (same cohort period)
Target: typically 65–80% for purchase; 50–70% for refi
Days-in-stage monitoring:
| Milestone |
Days-in-Stage Alert Threshold |
| Application → LE issued |
3 business days (TRID requirement) |
| Intent to proceed → Submitted to UW |
10 business days |
| Submitted to UW → Conditional approval |
5 business days |
| Conditional approval → CTC |
10 business days |
| CTC → CD issued |
1 business day |
| CD issued → Closing |
3 business days minimum (TRID) |
| Closing → Funded |
3 business days |
Component 5: Exception Queue
Exception queue triggers:
| Exception Type |
Trigger Condition |
Priority |
Action |
| LE not issued |
Day 3 from application without LE issuance |
Critical |
Immediate alert to LO and compliance |
| CD not issued |
CTC granted + closing within 4 business days + no CD issued |
Critical |
Immediate alert |
| Loan stuck — processing |
No milestone change in [N] business days during processing |
High |
Processor alert + manager notification |
| Loan stuck — conditions |
Conditional approval issued; no conditions cleared in [N] business days |
High |
LO alert |
| Missing appraisal |
Closing within 7 days; no appraisal received |
High |
Alert to LO and processor |
| Missing title |
Closing within 7 days; no title commitment received |
High |
Alert to processor and settlement |
| Rate lock expiring |
Rate lock expires within 3 business days |
High |
Alert to LO; extension decision required |
| Changed circumstance not documented |
Any fee on LE changed without changed circumstance documentation |
Critical |
Compliance alert |
| HMDA data incomplete |
Loan reaching disposition without complete HMDA data |
Medium |
Compliance alert |
Exception workflow:
- Exception detected → logged to exception queue
- Notification sent to responsible party (LO, processor, or compliance based on exception type)
- Responsible party must acknowledge exception and enter disposition within SLA
- If unacknowledged: escalate to manager after [N] hours
- Exception resolved → removed from queue; resolution documented
Output Format
Deliver two artifacts:
Pipeline Workflow Specification — Step-by-step description of each milestone, trigger conditions, automated notifications, and SLA targets; include TRID compliance checkpoints at LE and CD milestones
LOS Integration Requirements — For each LOS event that triggers a pipeline status change: event name, data fields passed, status mapping (LOS status → pipeline milestone), error handling if event fails, retry logic
1---2name: loan-pipeline3description: Design loan origination pipeline tracking and status workflow specifications for mortgage brokers and lenders. Use when automating loan status tracking, milestone notifications, or pipeline reporting for a mortgage operation.4---56# Loan Pipeline Tracking Workflow Design78Design the complete loan origination pipeline tracking system, from application intake through funding, with automated status updates, borrower and agent notifications, pipeline reporting, and exception queue management.910## Scope Confirmation1112Confirm which pipeline components are in scope:13- [ ] Application intake and channel capture14- [ ] Milestone status tracking15- [ ] Automated notifications (borrower, agent, real estate agent, settlement agent)16- [ ] Pipeline dashboard and reporting17- [ ] Exception queue (stuck loans, missing conditions)18- [ ] LOS integration for status sync1920---2122## Component 1: Application Intake and Channel Capture2324**Origination channels to track:**2526| Channel | Source System | Data Capture Method | Initial Status |27|---------|--------------|---------------------|---------------|28| Point-of-Sale (POS) system | [Blend, SimpleNexus, BeSmartee, etc.] | API integration | Application submitted |29| LOS — manual entry | [Encompass, BytePro, Calyx, etc.] | LOS webhook or polling | Application in progress |30| Referred (paper/email) | Manual upload | Staff entry in LOS | Application pending |31| Wholesale broker submission | Broker portal | API or file import | Broker submitted |3233**Required data at intake (minimum for 6-piece TRID application definition):**3435| Field | TRID Required? | Source |36|-------|---------------|--------|37| Borrower legal name | Yes | Borrower entry |38| Borrower SSN | Yes | Borrower entry |39| Property address | Yes | Borrower entry |40| Estimated property value | Yes | Borrower entry |41| Loan amount | Yes | Borrower entry |42| Income (used for qualification) | Yes | Borrower entry |43| Borrower DOB | No | Borrower entry |44| Email and phone | No | Borrower entry |45| Co-borrower information | No | If applicable |46| Loan purpose (purchase/refi) | No | Borrower selection |47| Property type | No | Borrower selection |48| Loan program | No | LO selection |4950**Application date rule (TRID):**5152Application is "received" for TRID purposes when all 6 required pieces are collected. The LE 3-business-day clock starts at application receipt. System must:53- Flag the exact date/time all 6 fields are populated54- Store this as the official `application_received_date`55- Calculate `le_due_date` = application_received_date + 3 business days (business day = Monday–Friday excluding federal holidays)56- Alert if LE has not been issued by day 25758---5960## Component 2: Milestone Status Tracking6162**Standard pipeline milestones:**6364| # | Milestone | Description | Preceding Milestone | Common SLA |65|---|-----------|-------------|--------------------|-|66| 1 | Application received | All 6 TRID pieces collected; application date set | — | Day 0 |67| 2 | Pre-approval issued | Tri-merge credit pulled; DU/LP run; pre-approval letter generated | Application received | 1–2 business days |68| 3 | Under contract | Purchase agreement received (purchase only) | Pre-approval | Borrower-dependent |69| 4 | Disclosures sent | LE and intent to proceed received | Application received | Day 3 (LE due) |70| 5 | Intent to proceed received | Borrower signed intent to proceed | Disclosures sent | Varies |71| 6 | Processing — active | Loan package submitted to processor; conditions collection underway | Intent to proceed | Day 5–7 |72| 7 | Appraisal ordered | Appraisal ordered through AMC | Processing active | Day 5–7 |73| 8 | Appraisal received | Appraisal report received and reviewed | Appraisal ordered | 5–14 days from order |74| 9 | Title ordered | Title search ordered | Processing active | Day 5–7 |75| 10 | Title received | Title commitment received and reviewed | Title ordered | 5–10 days from order |76| 11 | Submitted to underwriting | Complete loan package submitted to UW | Processing active | Day 10–15 |77| 12 | Conditional approval | UW issues conditional approval with conditions list | Submitted to UW | 1–5 business days |78| 13 | Conditions received | All UW conditions collected and submitted | Conditional approval | Varies |79| 14 | Clear to close (CTC) | UW clears all conditions; loan approved | Conditions received | 1–2 business days |80| 15 | CD issued | Closing Disclosure issued to borrower | CTC | 3 business days before closing |81| 16 | Closing scheduled | Closing date/time/location confirmed | CD issued | — |82| 17 | Closing | Loan documents signed | Closing scheduled | — |83| 18 | Funding | Loan funded by lender; disbursement complete | Closing | 1–3 business days |84| 19 | Post-closing complete | Post-close package reviewed; shipped to investor | Funding | 1–5 business days |8586**Status change triggers:**8788Each milestone status change is triggered by one of:89- **LOS event** (automated): LOS webhook fires when LOS status changes90- **Processor/UW action** (semi-automated): Staff changes status in pipeline system after completing an action91- **System detection** (automated): Document received, time elapsed, condition cleared92- **Manual** (staff entry): Phone call confirmed, verbal acknowledgment received9394Audit all status changes: record actor (staff member or system), timestamp, previous status, new status.9596---9798## Component 3: Automated Milestone Notifications99100**Notification recipients:**101102| Recipient | Relationship | Channel | Content Level |103|-----------|-------------|---------|--------------|104| Borrower | Primary | Email + SMS | Consumer-friendly, no jargon |105| Co-borrower | Primary | Email + SMS | Same as borrower |106| Loan officer | Internal | Email + in-app | Detailed milestone + next action |107| Processor | Internal | In-app task | Action items |108| Real estate agent (purchase) | External | Email | Brief status; no financial details |109| Listing agent (purchase) | External | Email | Brief status; no financial details |110| Settlement agent / title company | External | Email | Closing-relevant milestones only |111112**Borrower notification triggers and content:**113114| Milestone | Notification Sent | Subject Line | Key Content |115|-----------|------------------|-------------|-------------|116| Application received | Immediate | "Your application is received — here's what happens next" | Checklist of what they'll need to provide; timeline overview |117| Disclosures sent | Immediate | "Your Loan Estimate is ready — please review" | LE summary; link to e-sign intent to proceed; LE explanation |118| Appraisal ordered | Same day | "Your appraisal has been ordered" | Expected timeline; what appraiser access they need to provide |119| Appraisal received | Same day | "Your appraisal is complete" | Result (value confirms/exceeds/below purchase price); next steps |120| Conditional approval | Same day | "You're approved — we need a few more items" | Plain-English list of outstanding conditions; how to submit; priority |121| CTC | Immediate | "You're clear to close!" | Congratulations; what to expect at closing; wire fraud warning |122| CD issued | Immediate | "Your Closing Disclosure is ready — please review" | CD summary; 3-business-day window explained; final cash to close |123| Closing confirmed | Confirmation | "Closing confirmed for [date/time/location]" | Location, what to bring (ID, cashier's check if applicable), wire instructions warning |124| Funded | Same day | "Your loan is funded — congratulations!" | Next steps: first payment date, servicer information |125126---127128## Component 4: Pipeline Dashboard and Reporting129130**Pipeline dashboard views:**131132**Loan officer view:**133- My pipeline: all active loans assigned to me134- Columns: borrower name, loan amount, program, loan purpose, current milestone, days in current milestone, CD due date, closing date, red flags135- Filters: milestone, loan type, closing date range136137**Manager/branch view:**138- Full pipeline: all active loans by LO139- Pull-through metrics: application → CTC → funded rates140- Days-to-close by LO, loan type, lead source141- Loans at risk (closing within 7 days + not CTC)142- Fallout analysis: what stage are withdrawn/denied loans falling out?143144**Pipeline reports:**145146| Report | Frequency | Recipients | Purpose |147|--------|-----------|-----------|---------|148| Daily pipeline snapshot | Daily | LO, processor, manager | Current status of all active loans |149| Loans closing this week | Monday AM | LO, settlement, operations | Closing preparation |150| Aged loans report | Weekly | Manager | Loans stuck in a milestone > threshold days |151| Monthly production summary | Monthly | Branch / company | Volume, pull-through, days-to-close by period |152| HMDA LAR data extract | Monthly | Compliance | Required for HMDA reporting |153154**Pull-through rate formula:**155```156Pull-through rate = Funded loans / Applications received (same cohort period)157Target: typically 65–80% for purchase; 50–70% for refi158```159160**Days-in-stage monitoring:**161162| Milestone | Days-in-Stage Alert Threshold |163|-----------|------------------------------|164| Application → LE issued | 3 business days (TRID requirement) |165| Intent to proceed → Submitted to UW | 10 business days |166| Submitted to UW → Conditional approval | 5 business days |167| Conditional approval → CTC | 10 business days |168| CTC → CD issued | 1 business day |169| CD issued → Closing | 3 business days minimum (TRID) |170| Closing → Funded | 3 business days |171172---173174## Component 5: Exception Queue175176**Exception queue triggers:**177178| Exception Type | Trigger Condition | Priority | Action |179|---------------|------------------|---------|--------|180| LE not issued | Day 3 from application without LE issuance | Critical | Immediate alert to LO and compliance |181| CD not issued | CTC granted + closing within 4 business days + no CD issued | Critical | Immediate alert |182| Loan stuck — processing | No milestone change in [N] business days during processing | High | Processor alert + manager notification |183| Loan stuck — conditions | Conditional approval issued; no conditions cleared in [N] business days | High | LO alert |184| Missing appraisal | Closing within 7 days; no appraisal received | High | Alert to LO and processor |185| Missing title | Closing within 7 days; no title commitment received | High | Alert to processor and settlement |186| Rate lock expiring | Rate lock expires within 3 business days | High | Alert to LO; extension decision required |187| Changed circumstance not documented | Any fee on LE changed without changed circumstance documentation | Critical | Compliance alert |188| HMDA data incomplete | Loan reaching disposition without complete HMDA data | Medium | Compliance alert |189190**Exception workflow:**1911921. Exception detected → logged to exception queue1932. Notification sent to responsible party (LO, processor, or compliance based on exception type)1943. Responsible party must acknowledge exception and enter disposition within SLA1954. If unacknowledged: escalate to manager after [N] hours1965. Exception resolved → removed from queue; resolution documented197198---199200## Output Format201202Deliver two artifacts:2032041. **Pipeline Workflow Specification** — Step-by-step description of each milestone, trigger conditions, automated notifications, and SLA targets; include TRID compliance checkpoints at LE and CD milestones2052062. **LOS Integration Requirements** — For each LOS event that triggers a pipeline status change: event name, data fields passed, status mapping (LOS status → pipeline milestone), error handling if event fails, retry logic
Lobbi-Docs