A timestamp is useful, but not a certification
HomeLantern stores creation timestamps on conversation messages and uploaded chat media. Jobs also carry recorded fields for creation, work start, and completion. These help organize what is currently available in the app. They do not establish a certified, immutable history of every action.
The existing activity view can summarize current job state and may use a later update timestamp when a specific event timestamp is absent. That is a status summary, not proof of exactly when an earlier assignment happened. The records export therefore uses explicit recorded milestones only and does not invent missing dates.
A simple records packet
Open a property or job chat in the authenticated app, choose Export records, review the scope, and choose Download ZIP. The packet contains a readable report, structured JSON, the accessible transcript in chronological order, and optional accessible files shared in that chat.
Open report.html after extracting the ZIP. You can print it to PDF with your browser. records.json preserves record IDs and original timestamp strings for a professional who needs structured data. See the step-by-step guide.
An illustrative faucet repair
Suppose a tenant reports a leak at 09:00, the property team replies at 09:20, and a completion milestone is recorded later. The packet can show those recorded entries and include a shared photo or invoice attachment. These times are illustrative, not a customer case study.
If the invoice exists only in a separate financial screen, it is not automatically part of this conversation packet. If a file is inaccessible or exceeds the size limits, the report lists that limitation instead of claiming a complete bundle.
What is deliberately excluded
Other conversations, private job notes, AI tool payloads, and unshared job photos are not pulled into the packet. Record reads are capped at 10,000 per section; included files are limited to 25 MiB each and 100 MiB in total. A record-read failure does not produce a silently partial transcript.
Edits or deletions during collection can affect the snapshot. A local report cannot recreate deleted history, verify bank settlement, or guarantee acceptance in legal or insurance proceedings. Data protection explains why permission scope remains important even when compiling evidence.
This is a documentation system, not a promise of permanent preservation. For review practices, see compliance-first design.
Return to the source
Documentation integrity: what a HomeLantern record actually proves is part of the HomeLantern Trust Center and product boundaries. Browse all help topics or all articles for practical next steps.