Strategic Encompass Initiatives · Non-QM Business-Purpose Channel
Loan Enters Consumer/Agency Application
Business-purpose transaction starts in the consumer/Agency pipeline — channel identified mid-stream
Full Consumer/TRID Application Taken
Full consumer application completed; unnecessary consumer questions answered or skipped ad hoc
Entity & Guarantor Data Added at Closing
Entity added late — borrowing entity, signers, and guarantors patched in near closing instead of structured at origination
Standard Agency Milestones Apply
Agency milestone structure mirrors consumer flow — validation, entity review, and BP disclosure steps don't exist
LE/CD/TRID Disclosures Issued
TRID path applied to eligible business-purpose transactions; disclosure choices interpreted manually each time
Prepayment Penalty Applied by LO Interpretation
PPP allowed/not allowed, term, and structure decided case-by-case from guidance docs
File Routed to Agency Underwriting & Closing
No dedicated personas or queues — file handled by Agency staff with manual workarounds to force it through
Closing Docs Retro-Fitted to Entity/Guarantor Structure
Entity structure, guaranty, and PPP addenda retro-fitted into standard docs — rework and re-review cycles
PPP Assumptions Reconciled Manually
Pricing, Encompass, and closing documents can disagree on PPP — closer re-interprets and escalates
Compliance & Investor Checks Manual
Compliance testing forced through consumer rules; investor/product combinations validated by hand
Loan Closes After Rework Cycles
Loan closes in entity name — late, after rework, with no clean path for Novus ONE to consume
Initial Scenario — Business Purpose Identified
Loan identified as business purpose at intake; system indicator drives the entire downstream workflow
Business-Purpose Validation Trigger
System-supported determination with supporting documentation, validation owner, and re-review when occupancy, purpose, or entity type changes
Business-Purpose Application Flow
Pared-down application collects entity, guarantor, and transaction data only — unnecessary consumer questions hidden, conditional, or bypassed
Entity / Guarantor Structure Captured at Origination
Borrowing entity, type, ownership, authorized signers, guarantors, ownership %, vesting, and title captured at origination — entity borrower → individual guarantor → entity closes and takes title
Purpose-Built Non-QM Milestones
Initial Scenario/Application → BP Validation → Entity Review → Disclosure → Processing → Non-QM UW → Conditions → CTC → BP Closing → Funding → Investor Delivery, with triggers, persona access, and required fields per stage
Dedicated UW & Closing Workflow
Dedicated non-QM personas, queues, assignment logic, and pipeline views — business-purpose files cannot unintentionally enter the Agency workflow
Business-Purpose Disclosure Path
Business-purpose, state-specific, investor-specific, entity, and personal guaranty disclosures — Compliance/Legal validated before programming; no TRID on eligible BP transactions
PPP Determined by System Controls
PPP matrix as single source of truth — state, investor, product, entity type, term, and restrictions drive hard stops, warnings, and auto-population; Optimal Blue, Encompass, and closing docs aligned on one PPP answer
ComplianceEase — Non-QM Compliance Review
Fully separate from the Agency/consumer process (Mavent unchanged) — data, test point, state and BP rules, warning vs. hard-stop logic, full audit trail
Closing Docs Auto-Generated for Entity/Guarantor
Note, Mortgage/Deed of Trust, entity certifications, borrowing resolutions, personal guaranty, riders, BP affidavits, and PPP addenda auto-reflect the entity/guarantor structure — simple closing validation point
Investor / Product Controls Enforced
Hard stops prevent selection of unsupported investor/product/entity/state/PPP/DSCR combinations; exceptions documented through LO → AskNovus → Compliance/Capital Markets
Novus ONE Data Handoff & Loan Closes in Entity Name
Clean, controlled loan record with classification, entity vs. guarantor fields, doc categories, attestation fields, and milestone/status mapping — Novus ONE designed around a controlled Encompass process