TRID timing: business days, Loan Estimates, and Closing Disclosures

The general definition

For the three-business-day Loan Estimate delivery deadline, a business day is generally a day on which the creditor's offices are open to the public for substantially all business functions. The creditor calendar therefore belongs in organization settings.

The specific definition

For the seven-business-day LE wait, deemed receipt, and CD waiting period, every calendar day counts except Sundays and the legal public holidays in 5 U.S.C. 6103(a). Saturday usually counts.

The actual fixed-date holiday controls. When July 4 falls on Saturday, the observed Friday closure does not automatically become excluded under this specific definition.

Receipt versus sent date

A sent date is not always the operative received date. The review should preserve actual receipt evidence where available and separately model deemed receipt. Corrected disclosures require their own trigger analysis.

Why the software does not declare legal liability

A computed variance is a compliance finding for review. Coverage, valid changed circumstances, emergency waivers, delivery evidence, and restitution require lender policy and legal/compliance judgment.

How to evaluate this workflow

A TRID compliance tool should make its date assumptions visible. Buyers should verify which business-day definition is used for each deadline, how actual and deemed receipt are represented, where the source dates came from, and how a reviewer records a changed circumstance, cure, waiver, or other fact the calculation cannot decide.

Buying criteria

• Use the correct general or specific business-day definition
• Preserve sent, received, consummation, and corrected-disclosure dates
• Show the calculation rather than only a pass/fail label
• Route legal and policy conclusions to a qualified reviewer

Put this guidance into a controlled operating record.

Translate each requirement or method into a named control with an owner, effective date, scope, required inputs, acceptable evidence, review authority, exception path, and retained output. Link the configured control to the current primary source or approved policy instead of copying a sentence into a checklist with no change history.

Test the workflow with one complete cycle. Another qualified reviewer should be able to identify the eligible population, reproduce the sample or calculation, open the cited evidence, understand the response and rationale, see who approved the disposition, and verify how the result reached corrective action and management reporting.

Guidance, software, and automation do not decide legal applicability or replace agency, investor, institutional, or counsel judgment. Record the source review date, monitor changes, version the control, and preserve which rule and evidence state produced every report.

Confirm requirements against current source material.

Requirements and vendor capabilities change. These sources were reviewed July 31, 2026. Confirm current source material, product scope, commercial terms, and your approved QC plan before changing a production process.

• 12 CFR 1026.2(a)(6)
• 12 CFR 1026.19