- The problem
- In a hurried build the rate lock date and the pre-approval expiry end up inside a call summary, which means the two dates deciding whether a file survives are invisible to every filter, every list view and every automation that was supposed to warn somebody.
- Once it is loaded
- Loan purpose, property address and type, target closing date, lock date and expiry, pre-approval expiry, credit band, employment type, referring agent and assigned processor are structured fields, filled by the receptionist and the application form and readable directly as triggers.
- How it pays back
- Every pre-approval expiring in the next three weeks becomes a call list a broker can work on a Monday, and that list funds the month. For you, the schema and the automations reading it ship together, removing the usual second build after the client asks why nothing fires.