TRID Three Day Rule Lookup

Exact independently verified TRID waiting-period definitions and exceptions reference registry lookup in explicit US loan type, trigger, event and current rule context, retaining source and as-of date. Caller supplies the actual applicable record, including qualifications, exceptions and uncertainty; illustrative examples are not authoritative records. No built-in complete/current data, eligibility, authenticity, legal/coverage determination or advice.

Description

Mortgage disclosure timing depends on the applicable disclosure, transaction and day-counting rule.

Mortgage disclosure timing depends on the applicable disclosure, transaction and day-counting rule.1

A source-qualified notice does not compute a deadline or install a universal three-day rule. Use TRID Three Day Rule Lookup to retrieve an exact caller-supplied reference entry.

When to use TRID Three Day Rule Lookup

Use TRID Three Day Rule Lookup to retrieve an exact caller-supplied reference entry. Choose the relevant jurisdiction, transaction or institution context; review the source, record its as-of date and supply the reference entries.

How to use TRID Three Day Rule Lookup and understand its results

  1. Choose the relevant jurisdiction, transaction or institution context; review the source, record its as-of date and supply the reference entries.
  2. Enter Caller verified source, Caller verified context, Caller verified as of date, Caller reference keys, Caller reference texts, Query reference key using the field table and validation rules below, then run the tool.
  3. Read Matched Caller Reference, Source, Context, As Of Date in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
  4. Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
Input fieldMeaningValue typeRequirement
callerVerifiedSourceCaller verified sourcestringRequired; constraints below
callerVerifiedContextCaller verified contextstringRequired; constraints below
callerVerifiedAsOfDateCaller verified as of datestringRequired; constraints below
callerReferenceKeysCaller reference keysarray of stringRequired; constraints below
callerReferenceTextsCaller reference textsarray of stringRequired; constraints below
queryReferenceKeyQuery reference keystringRequired; constraints below

Provide aligned, nonempty arrays of reference keys and independently verified notices, then enter the exact query key. Keys must be unique, nonblank and at most 128 UTF-16 code units long; notices must be nonblank. Matching is case sensitive and does not trim the query or returned text. The matching notice is returned unchanged; an unknown key is an input error. The reference contents and their applicability are supplied by the caller; the tool does not retrieve external records or verify source authority. Also supply nonblank source and context identifiers of at most 256 UTF-16 code units each and a real Gregorian YYYY-MM-DD as-of date in years 0001 through 9999. Source, context and asOfDate are returned unchanged alongside the matched reference. The date is validated, but no freshness or current-law check occurs.

matched reference = suppliedTexts[indexOfExactQueryKey(suppliedKeys)]

Use the field order, units and branch conditions described above.

Output fieldMeaningValue type
resultObject containing the named result fields below.object
result.matchedCallerReferenceCaller reference text matched exactly by key, unchanged.string
result.sourceCaller source identifier, unchanged and unverified.string
result.contextCaller context identifier, unchanged and unverified.string
result.asOfDateCaller Gregorian as-of date, validated as a date but not checked for freshness.string
json
{
  "input": {
    "callerVerifiedSource": "independently-reviewed-source/edition",
    "callerVerifiedContext": "US loan type, trigger, event and current rule",
    "callerVerifiedAsOfDate": "2026-01-01",
    "callerReferenceKeys": [
      "record-a",
      "record-b"
    ],
    "callerReferenceTexts": [
      "Caller independently verified TRID waiting-period definitions and exceptions record a",
      "Caller independently verified TRID waiting-period definitions and exceptions record b"
    ],
    "queryReferenceKey": "record-a"
  },
  "output": {
    "result": {
      "matchedCallerReference": "Caller independently verified TRID waiting-period definitions and exceptions record a",
      "source": "independently-reviewed-source/edition",
      "context": "US loan type, trigger, event and current rule",
      "asOfDate": "2026-01-01"
    }
  }
}

Limitations and assumptions

Regulation Z distinguishes disclosure delivery, receipt and waiting periods, with different triggers and exceptions. This lookup does not implement those provisions, a business-day calendar or a loan eligibility determination.2

A source-qualified notice does not compute a deadline or install a universal three-day rule. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use Remittance Transfer Rule International30-Minute Cancel Lookup for a related task: Remittance cancellation rights depend on the covered transfer, timing and other applicable conditions.

Use Servicer Transfer60-Day Rescission Payment Suspension Rule for a related task: Mortgage servicing-transfer payment protection concerns qualifying payments sent to the former servicer.

References

  1. TRID Three Day Rule Lookup — tool.io

  2. Regulation Z § 1026.19: mortgage disclosures and timing — Consumer Financial Protection Bureau

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies