Key finding
Files often record when a disclosure was sent but not when the consumer received it. The missing middle timestamp is where timing disputes begin.
Research question
The review asks how closing teams record the delivery of the closing disclosure and whether those records distinguish transmission from receipt. It examines the fields available in the file rather than the substance of the disclosure itself.
Files were grouped by delivery method: electronic portal, email attachment, in-person, and mail. Each method produces a different evidence trail, and comparing them without that distinction obscures the actual control.
Method
For each file, the reviewer looked for a sent timestamp, a delivery or access confirmation, a consumer receipt, and the date the team treated as the start of the waiting period. Where a field was absent, it was recorded as absent rather than inferred from the next document.
The review also noted whether a revised disclosure existed and whether the revision included a reason and a new receipt date. Version history was treated as part of the delivery record, not as a separate administrative artifact.
What the timestamps show
Electronic portals produced the richest transmission data and the weakest receipt data. A document could be uploaded on Monday and opened on Wednesday, while the file contained only the Monday timestamp. In-person deliveries often had a signed acknowledgement but no time of day.
Mail deliveries were the least consistent. Some files recorded the mailing date and applied an assumed receipt period; others recorded only the date the document was generated, which is not a delivery event at all.
Limits of the review
A timestamp does not establish that the borrower understood the document, and an access log does not prove the person who opened it was the borrower. The review therefore describes evidence quality, not compliance outcomes.
The files came from a small number of workflows and were not randomly selected. Differences between teams may reflect their software rather than their diligence.
Implications for the closing file
Add a received field that cannot be filled by the same action that sends the document. Require the consumer's acknowledgement or the system's access record, and keep the mailing date with the rule used to derive an assumed receipt date.
Before the signing appointment, compare the latest disclosure version with the receipt evidence. If the received date is missing, the appointment is at risk regardless of how complete the rest of the package looks.