Real estate and property condition
Handover and return of a rental property
Goal: compare the visible condition at move-in and at move-out. If your material is older, keep in mind that a timestamp obtained today covers the hash submitted today. Documents from the time have their own dates and their own sources of proof; the Record does not certify the date of the event or the capture.
The problem
You need to document the property's condition at the start of, during or at the end of a tenancy, when damage, repairs, furniture, the deposit or upkeep may be disputed.
Repeat the same angles and rooms, link each photo to the inspection report and report any discrepancies through the agreed channel. Keep the key handover record.
Years can pass between getting the keys and handing them back. Nobody remembers exactly how the floor or the shower screen looked, the inspection report is vague, and the photos are scattered across a phone with no reliable date. When it's time to return the deposit or charge for a repair, each side remembers it differently.
This works both ways. The tenant wants to show the defect was already there. The landlord wants to show how the property was handed over.
What to preserve
Continuous video, photos, the inspection report, meter readings, the list of keys, included items and defects.
Goal: compare the visible condition at move-in and at move-out.
Main file: comparable photos and the inspection report.
When to capture: at move-in, when something relevant happens and at move-out.
Supporting sources: the inspection report, the key handover record and your messages reporting discrepancies.
Limit of this scenario: on its own, the Record does not establish the cause of the damage, who is responsible or the actual date of the inspection.
Collect only what you need, through access you are lawfully entitled to. Use neutral file names and descriptions, store files securely and share them only with people who need them. Where it is lawful to make a redacted copy, keep it as a separate file from the preserved original and note which version's hash you registered. See the Privacy Policy.
A continuous video, walking from room to room without cuts, shows the whole. Photos show the details: cracks, stains, sockets, fittings, doors. Water, electricity and gas meter readings and the list of keys complete the picture of the day. The inspection report, if there is one, goes in as a document.
How Provenia documents this scenario
Your browser calculates the SHA-256 hash of the file you select. The file itself stays on your device: Provenia receives only the hash and metadata, meaning the file name, its size and the context fields you fill in. Provenia stores the hash and the Record data. Keep the exact file you used and the exported Dossier, because they are what make a byte-for-byte check possible later.
Three different times are involved. The time the Record was created on Provenia comes from Provenia's server and is not certified. The date of the event or capture is something you declare in the context, in the description or in the file itself, and it depends on other sources. The externally certified UTC date and time ties the hash you submitted to the timestamp authority's response; it does not certify when the event happened.
Provenia sends the hash, never the file, to FreeTSA, an external timestamp authority, which issues an RFC 3161 timestamp. Provenia validates that timestamp before the Record is completed. If FreeTSA is unavailable, or the timestamp cannot be obtained or does not validate, the Record is not created and no credit is used. Older Records created before this feature was active may have no external timestamp. A timestamp obtained today covers the hash submitted today; it is never issued later or backdated.
Each Record's timestamp is separate from the signatures on the exported Dossier: Provenia's digital signature on the PDF and the Ed25519 signature on Dossier.json. Those signatures cover the exported documents and do not certify the date of the event. See Trust and Verifiability.
In this scenario, use comparable photos and the inspection report as your reference material and check it against the inspection report, the key handover record and your messages reporting discrepancies. The timestamp on a hash does not confirm the cause of the damage, who is responsible or the actual date of the inspection.
Step by step
- Define your goal and check that your access is legitimate, which permissions apply and whether any deadlines are running before you collect anything.
- Repeat the same angles and rooms, link each photo to the inspection report and report any discrepancies through the agreed channel. Keep the key handover record.
- Preserve comparable photos and the inspection report exactly as it is; don't edit the file you register.
- Link the material to the inspection report, the key handover record and your messages reporting discrepancies; describe its origin and when it was captured as declared information.
- Group the milestones in a Project and register each relevant file separately. Keep the files untouched and the exported Dossier, with a secure backup.
What the Record shows and what it does not
A Record is a private electronic document that can form part of a wider body of evidence, assessed according to its context and origin. On its own, it does not establish the cause of the damage, who is responsible or the actual date of the inspection. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
What can this Record be used to check?
Whether the file you kept matches the registered hash and, where there is a valid timestamp, that the hash is tied to the UTC date and time shown. On its own, it does not establish the cause of the damage, who is responsible or the actual date of the inspection.
How should I organize the files for this case?
Use one Project per tenancy and keep move-in, any incidents and move-out as distinct milestones. Shoot the same rooms from the same angles each time and name the files by room, so photos from the two moments can be compared side by side.
Which date is certified?
Only the UTC date and time in a valid external RFC 3161 response tied to that Record's hash. The time on Provenia's server and the event or capture date you declare are separate pieces of information. The timestamp does not certify when the event happened.
Official references
Technical reference for context only. It is not legal advice or a conclusion about any case. Provenia is not affiliated with, integrated with or endorsed by the organization listed.
- RFC 3161 — Time-Stamp Protocol (IETF)https://datatracker.ietf.org/doc/html/rfc3161
Start with three free credits
Each Record covers one file. Each completed Record uses one credit, including the first one, which creates the Project. A new account includes three free Document Credits and one Project, with no payment and no card, so the starter credits cover three single-file Records. For prices and conditions, see Pricing.
Already have an account? Log in.