Real estate and property condition
Pre-purchase property inspection
Goal: compare the property at the viewing and at handover. 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
Before signing or handover, the buyer wants to document the property's visible condition and the items present.
Compare the viewing and the handover with the offer, the specification and the list of included items. Leave the technical inspection to a qualified professional; images don't replace that assessment.
Weeks or months can pass between the viewing, the offer, the signing and getting the keys. In that time, items are removed, rushed repairs are made and small defects appear or vanish. The buyer remembers it one way, the seller another, and the photos from the viewing are lost in the phone's gallery, with no reliable date.
This applies to existing homes and to new builds, whenever the buyer wants to compare what they saw with what they received.
What to preserve
A continuous room-by-room video, detailed photos, included items, meter readings and relevant documents.
Goal: compare the property at the viewing and at handover.
Main file: photos from the viewing and the list of included items.
When to capture: at the viewing and again at handover when relevant.
Supporting sources: the offer, the specification and a technical inspection by a qualified professional.
Limit of this scenario: on its own, the Record does not establish the property's technical condition, hidden defects or full compliance.
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: walls, floors, window frames, fittings, signs of damp. Items that stay with the property, such as cupboards, light fittings and appliances, deserve their own photos. Meter readings and documents such as the offer and the list of items complete the picture.
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 photos from the viewing and the list of included items as your reference material and check it against the offer, the specification and a technical inspection by a qualified professional. The timestamp on a hash does not confirm the property's technical condition, hidden defects or full compliance.
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.
- Compare the viewing and the handover with the offer, the specification and the list of included items. Leave the technical inspection to a qualified professional; images don't replace that assessment.
- Preserve photos from the viewing and the list of included items exactly as it is; don't edit the file you register.
- Link the material to the offer, the specification and a technical inspection by a qualified professional; 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 property's technical condition, hidden defects or full compliance. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
Do I need to register again when I get the keys?
When there is a gap or a significant change, preserve the handover too. Images from the two moments help the comparison, without certifying the actual date of the scene.
How should I organize the files for this case?
Use one Project per purchase with two milestones, viewing and handover. Name photos by room and item so they can be matched against the list of included items, and add the offer and the specification as Records of their own.
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.