TRID timer violations occur when lenders fail to enforce mandatory waiting periods between Closing Disclosure delivery and closing dates (3-business-day minimum) or miss tolerance cure deadlines when fees exceed disclosed amounts. Traditional timer tracking through spreadsheets, calendar reminders, and manual processor oversight breaks when infrastructure fails — a server restart, deployment, or application crash loses in-memory timer state, creating compliance risk. Confer solves this with Temporal durable workflows: when a CD is delivered, a workflow timer starts that survives server restarts, persists through infrastructure failures, and automatically prevents closing date scheduling until the 3-day waiting period expires. This same durable workflow architecture enforces tolerance cure deadlines, intent-to-proceed tracking, and other time-dependent compliance requirements, ensuring regulatory timers never fail due to infrastructure events.
The Problem with Manual Timer Tracking
Walk into any mortgage lender's operations floor and ask "How do you track TRID timers?" and you'll hear some variation of this:
"The processor logs the CD delivery date in a spreadsheet. They calculate the 3-day waiting period manually (counting business days, excluding weekends and holidays). They set a calendar reminder for the earliest closing date. The closer double-checks before scheduling closing."
This works until it doesn't. Here's what breaks manual tracking:
Server Restarts
Any in-memory timer state — background jobs, scheduled tasks, countdown timers — is lost when the application server restarts. If your TRID timer was tracked in-memory and the server reboots (maintenance, deployment, crash), the timer disappears. Unless someone manually reconstructs it from spreadsheet notes, the loan can schedule closing too early.
Human Error in Business Day Calculation
Calculating 3 business days sounds simple until you encounter federal holidays, regional holidays, or lender-specific closures. A processor manually counting days can easily miscalculate if they forget that Monday was a federal holiday or that the lender observes a state-specific holiday.
Staff Turnover and Knowledge Loss
When the processor who set the calendar reminder goes on leave, gets sick, or leaves the company, the knowledge of which loans have CD timers running goes with them — unless it's meticulously documented in a shared system. Relying on individual staff memory is fragile.
Audit Trail Gaps
Spreadsheet-based tracking doesn't create a compliance audit trail. If an examiner asks "How do you know this loan's CD was delivered 3 business days before closing?" and the answer is "The processor's spreadsheet says so," that's not defensible documentation. You need timestamped, system-generated proof.
What TRID Actually Requires
The TILA-RESPA Integrated Disclosure (TRID) rule, effective October 3, 2015, mandates specific timing requirements for mortgage closing disclosures. The two most critical are:
Critical TRID Timers
1. Three-Business-Day Waiting Period (12 CFR § 1026.19(f)(1)(ii))
The lender must deliver the Closing Disclosure to the borrower at least 3 business days before closing. Business days are defined as all calendar days except Sundays and federal holidays. The 3-day period starts the day after delivery — if the CD is delivered Monday, the earliest closing date is Thursday (assuming no holidays).
2. Tolerance Cure Deadlines (12 CFR § 1026.19(e)(3))
If actual fees exceed disclosed amounts beyond tolerance thresholds (0% for fees you cannot shop for, 10% cumulative for fees you can shop for), the lender must cure the tolerance violation by reducing charges or issuing a refund. The cure must occur before closing or within 60 days post-closing. Missing cure deadlines triggers compliance violations.
The compliance risk: If you schedule closing on day 2 instead of day 3, or if you fail to cure a tolerance violation before closing, you've violated TRID. Violations can result in audit findings, penalties, loan repurchase demands, and reputational damage.
Enter Durable Workflows
A durable workflow is a program execution managed by a workflow orchestration engine that survives infrastructure failures. Unlike scripts, cron jobs, or in-memory timers, durable workflows persist their state to a database and can resume exactly where they left off after a server restart.
Confer uses Temporal — an open-source workflow orchestration platform — to implement TRID timers as durable workflows.
How It Works: CD 3-Day Timer
- CD Delivery Event: When the lender delivers a Closing Disclosure to the borrower (via email, portal download, or mail), the system records the delivery timestamp.
- Workflow Initiation: A Temporal workflow named
TRIDWaitingPeriodWorkflowstarts. It receives the delivery timestamp and loan ID as parameters. - Business Day Calculation: The workflow calculates 3 business days from the delivery date, accounting for federal holidays and weekends. This calculation uses a holiday calendar service that knows which days are non-business days.
- Durable Timer: The workflow sets a Temporal timer for the calculated expiration timestamp. This timer persists to the database and survives server restarts.
- Blocking Enforcement: While the timer is active, the system prevents scheduling a closing date before the expiration. If a user tries to schedule closing on day 2, the system rejects it with a message: "Closing cannot be scheduled before [date] due to TRID 3-day waiting period."
- Timer Expiration: When the 3-business-day period elapses, the workflow completes and logs the event to the compliance audit trail. Closing can now be scheduled.
- Audit Logging: Every step — CD delivery timestamp, calculated expiration, timer start, timer completion — is logged with timestamps, user IDs, and event details. This creates a defensible compliance audit trail.
Why Temporal Survives Infrastructure Failures
Traditional timers — cron jobs, in-memory schedulers, background workers — run in application memory. When the application restarts, they're gone. Temporal workflows persist their state to a database (PostgreSQL in Confer's case).
Here's what happens during a server restart:
| Scenario | Traditional Timer (In-Memory) | Temporal Durable Workflow |
|---|---|---|
| Server Restart | Timer lost, must be manually recreated | Workflow resumes automatically from persisted state |
| Deployment | Active timers cleared during deployment | Workflow continues running through deployment |
| Application Crash | All in-memory state gone | Workflow recovers when application restarts |
| Database Backup/Restore | No timer state in database to restore | Workflow state restored from database |
Key insight: Temporal workflows treat timers as first-class data, not ephemeral background jobs. This makes compliance timers as reliable as the database itself.
Beyond CD Waiting Periods: Tolerance Cure Tracking
TRID's tolerance rules create another timer-dependent compliance requirement: when fees exceed disclosed amounts beyond tolerance, the lender must cure the violation before closing or within 60 days post-closing.
Tolerance Thresholds (Quick Recap)
- Zero tolerance (0%): Fees that cannot increase at all — lender charges, transfer taxes. Any increase is a violation.
- 10% cumulative tolerance: Fees the borrower can shop for (title, appraisal, etc.) can increase up to 10% in aggregate. Exceeding 10% triggers a violation.
- Unlimited tolerance: Prepaid interest, property insurance, and some other items have no tolerance limit but must be disclosed.
When a tolerance violation is detected, Confer initiates a ToleranceCureWorkflow:
- Violation Detection: The system calculates actual fees vs. disclosed fees at closing preparation and flags tolerance violations.
- Cure Workflow Starts: A Temporal workflow initiates with a deadline (closing date or 60 days post-closing, whichever is applicable).
- Alerts: Compliance staff receive automated alerts that a cure is required with the specific fee amount and deadline.
- Tracking: The workflow tracks cure actions — fee reductions, borrower refunds, revised CD delivery — and marks the violation as resolved when documented.
- Deadline Enforcement: If the deadline approaches without cure documentation, the workflow escalates alerts and can block loan closing.
Just like the CD waiting period, the tolerance cure workflow survives infrastructure failures. A deployment during the cure period doesn't reset the deadline or lose tracking state.
The Compliance Audit Trail: Defensible Documentation
When a federal or state examiner audits your TRID compliance, they ask for proof:
- When was the CD delivered to the borrower?
- How did you calculate the 3-business-day waiting period?
- What system prevented closing before the expiration?
- How do you track tolerance violations and cures?
Temporal workflows provide timestamped, immutable logs of every compliance event:
| Event | Timestamp | Actor | Details |
|---|---|---|---|
| CD Delivered | 2026-03-10 14:23:17 UTC | System (email) | Sent to borrower@example.com |
| Workflow Started | 2026-03-10 14:23:18 UTC | TRIDWaitingPeriodWorkflow | Loan ID: 12345, Expiration: 2026-03-13 |
| Timer Set | 2026-03-10 14:23:19 UTC | Temporal | Durable timer: 3 business days |
| Closing Attempt Blocked | 2026-03-11 09:15:42 UTC | Closer: Jane Doe | Rejected: TRID waiting period not expired |
| Timer Expired | 2026-03-13 00:00:01 UTC | Temporal | 3-day period complete, closing allowed |
| Workflow Completed | 2026-03-13 00:00:02 UTC | TRIDWaitingPeriodWorkflow | Compliance requirement satisfied |
This audit trail is system-generated, immutable, and timestamped. No manual notes. No spreadsheet reconciliation. No "the processor said they did it."
Real Compliance Risk Mitigation
TRID violations aren't theoretical. Lenders have faced enforcement actions, repurchase demands, and operational disruptions due to timer tracking failures. Here's what durable workflows prevent:
Without Durable Workflows
- Server restart loses timer state, loans close too early
- Manual calculation errors (holiday miscounts, weekend mistakes)
- Spreadsheet tracking with no audit trail
- Tolerance cure deadlines missed due to lack of automated alerts
- Compliance violations discovered during audits
With Durable Workflows
- Infrastructure-independent timers that survive restarts and deployments
- Automated business day calculation with holiday calendar integration
- Immutable, timestamped audit logs for examiner review
- Automated tolerance cure tracking with deadline enforcement
- Compliance violations prevented before they occur
Conclusion: The Future of Compliance Automation
TRID compliance shouldn't depend on spreadsheet discipline, calendar reminders, or hoping your server doesn't restart during a critical 3-day period. Durable workflows make compliance enforcement infrastructure-independent.
When timers persist to the database and survive infrastructure failures, compliance becomes a property of your system architecture — not a manual process subject to human error and technical fragility.
Confer's Temporal-based approach to TRID automation represents how modern mortgage platforms should handle compliance: automated, auditable, and resilient.