TRID Compliance with AI Agents: The Six-Element Trigger, the 3/7-Day Clocks, and Re-Disclosure

The Origination Workflow Where the Clock Starts Before Anyone Notices

The TILA-RESPA Integrated Disclosure rule's timing problem is not in the calendar math. It is in the moment the rule decides an "application" was received, which is when the clock for the Loan Estimate starts. By the time the loan officer realizes the customer crossed that line two days ago, the three-business-day window to deliver the Loan Estimate is already a one-business-day window, and a delivery on day four is a finding regardless of intent. The institutions that put AI agents on the mortgage intake without redesigning when the application is recognized are the ones whose TRID exception reports get longer.

We work with mortgage banks and depository lenders that handle origination volume across digital and voice channels. The TRID rules are unforgiving but mechanical, which makes them a good fit for an agent that is built to recognize the trigger and run the timing. The design below is what passes a mortgage-operations audit and a state-DOB exam.

The Six Elements That Define an Application

Regulation Z at 12 CFR 1026.2(a)(3) defines a residential mortgage application for TRID purposes as the consumer's submission of six pieces of information: the consumer's name, the consumer's income, the consumer's Social Security number to obtain a credit report, the property address, an estimate of the value of the property, and the mortgage loan amount sought. Once those six are in the institution's possession, an application exists under TILA, and the Loan Estimate clock under 1026.19(e)(1)(iii) starts.

The six elements do not have to arrive on a form. They can arrive across a chat, a voice call, a partially completed online application, and an emailed pay stub, and the moment the sixth piece lands the application exists whether the loan officer's queue has caught up or not. This is the rule the agent has to enforce because the institution cannot afford to let the trigger be a human's noticing.

What the Intake Agent Does at the Six-Element Moment

The intake agent tracks the six elements as a state machine across every channel the customer touches in a given session and across sessions tied to the same prospect. As each element arrives the agent writes the timestamp and the source. When the sixth element completes, the agent does three things at once: it records the moment as the application-received timestamp under 1026.2(a)(3), it opens a TRID case in the loan-origination system, and it starts the Loan Estimate clock with the delivery deadline computed against the institution's business-day definition.

The agent does not let a customer's premature signal alone trigger an application. A customer who says "I want a mortgage for two hundred thousand" without providing an SSN, an address, an income figure, or a value estimate has not made an application under the rule, and starting a clock on incomplete information is its own pattern of mishandling. The state machine waits for the six.

The other thing the agent does at the moment of application is freeze the discussion of specific terms. Under 1026.19(e)(2), the lender cannot impose any fee on a consumer in connection with the consumer's application before the consumer has received the Loan Estimate and intended to proceed, with a narrow exception for a credit-report fee. The agent's policy at the six-element moment is to confirm the application, set the LE delivery clock, and route the conversation to a path that does not request a fee.

The Loan Estimate Itself, Drafted From System Data

The Loan Estimate content is specified in 1026.37 at field-level granularity, including the loan terms, the projected payments, the costs at closing, the cash to close, and the comparison and other-considerations sections. The agent assembles the draft from the loan-origination system rather than generating any of the fields from model output, because every figure on the LE is one a consumer will rely on and a lender will be measured against under the tolerance rules.

The fields the agent does generate are the form's narrative pieces and the customer-facing communication around the LE delivery: the cover note, the delivery method confirmation, the instructions about the intent-to-proceed acknowledgment. The agent does not write a fee, a term, or an APR. The fields that come from the system come from the system, and the agent's role is to assemble, format, and deliver, not to produce a financial figure.

The Tolerance Buckets and the Cost of a Cure

The LE locks in fees within tolerance buckets that the rule defines: zero tolerance for the lender's own charges and for affiliated services and transfer taxes, ten percent cumulative tolerance for third-party services the lender selected, and no tolerance for services the consumer was permitted to shop for and chose an independent provider. A final cost that exceeds the LE estimate beyond the applicable tolerance is a violation the lender cures by refunding the excess and re-disclosing.

The agent's role here is not to do the tolerance math after the fact. It is to track the LE values per bucket from the moment they are disclosed and to flag any in-flight change that would breach a tolerance before the change is committed, so the lender's decision to absorb the cost, re-disclose under a valid change-of-circumstance, or alter the service is a deliberate one. A tolerance breach that the institution discovers at closing is a cure cost on the lender's books; a tolerance breach the system flagged two weeks earlier is a decision the loan officer made on purpose.

The 7-Day Wait and the 3-Day Wait

After the LE is delivered, the consumer must receive it at least seven business days before consummation under 1026.19(e)(1)(iii)(B). The agent computes the earliest consummation date the moment the LE goes out and writes it into the loan record. The Closing Disclosure under 1026.19(f)(1)(ii) must be received by the consumer at least three business days before consummation, with the rule specifying mail-rule presumption of receipt three days after delivery for non-acknowledged delivery methods.

The "three business days" piece of this is more than a calendar count. Certain CD revisions reset the clock and certain do not. An APR change above the prescribed threshold of one-eighth of a percentage point, a change of the loan product, or the addition of a prepayment penalty re-triggers the three-business-day waiting period. A change in a fee that does not move the APR or the product does not re-trigger. The agent encodes the reset triggers explicitly and refuses to let a consummation date stand if a triggering CD change occurred inside the window. This is the rule a transaction coordinator under pressure to close on the contract date misapplies most often, and a closing held over because the agent refused to ignore a triggering change is preferable to a closing that breaches the rule.

The Failure Mode We Engineer Against

The pattern we saw at the first mortgage customer we put an intake agent on, before we got the design right, was the application clock starting at a different moment than the rule said it should. The loan-origination system marked the application as received when the loan officer pressed the button, which often lagged the actual receipt of the six elements by a business day or two. The customer had submitted income and an SSN through the digital flow, the agent had collected the property and the loan amount on a call, and a coordinator opened the case the next morning. The institution had been compliant on its own internal clock and out of compliance on the rule's clock without noticing.

What we changed in the design we run now is that the application-received timestamp is set by the state machine at the moment of the sixth element, not by the human action that opens the file. The internal workflow is allowed to lag by the amount of time the operations team needs, because the rule's clock does not care whether the human caught up. The LE timing engine works from the actual receipt timestamp, and any LE delivered later than the rule's deadline registers as an exception with the reason recorded, rather than as a routine event the exception report misses.

Re-Disclosure Triggers Without Drift

1026.19(e)(3)(iv) sets the conditions under which an LE may be revised after delivery to reset tolerance baselines. The trigger categories include changed circumstances affecting eligibility, changed circumstances affecting settlement charges, the consumer's interest-rate-dependent changes, the consumer's request for revisions, the consumer's interest rate having expired before the consumer indicated intent to proceed, and a new Construction Loan delay.

The agent maps each in-flight change against this list before issuing a revised LE, because issuing a revised LE that does not correspond to one of the rule's triggers does not reset the tolerance baseline. A loan officer who revises an LE in good faith without a qualifying trigger has produced a document that does not legally lower the original obligation, and the institution that closes against the second LE absorbs the difference. The agent's check is the structural one that keeps the loan officer from misapplying the trigger under volume.

The Audit File the Mortgage Examiner Asks For

State mortgage examinations and CFPB-style mortgage reviews work from the loan file, and TRID is one of the first sections they pull. Per loan in scope, the file we keep includes the six-element receipt log with the source of each element and the timestamp, the application-received timestamp the agent set, the LE draft with the system-of-record provenance of each fee and term, the LE delivery date and method and the customer's intent-to-proceed acknowledgment, every revised LE with the triggering changed-circumstance citation, the tolerance tracking by bucket through the life of the loan, the CD delivery date and method with the consumer's receipt date, every CD revision with the reset-trigger determination, and the consummation date with the rule-compliance check that ran against it.

A loan file that produces this without a person digging is a file that ages well. A file that requires reconstruction six months after the closing is the file an exception turns into a finding around.

The Trade-Off

A TRID-aware intake agent slows the moment of application acceptance because the state machine waits for the actual six and refuses to fudge. It also holds closings when a triggering CD change should reset the three-day window, which the contract date does not always tolerate. The cost is real and we say so. The return is fewer cures absorbed at closing, fewer findings on the application timing, and a loan file the mortgage-ops team trusts the institution can defend. The intake agent does not replace the loan officer; it makes the rule's clock the institution's clock, which is the change that holds the program together at volume.