← Back to the category

Insurance claims and loss events

Documenting property safely after a loss event

Put safety, urgent measures and prompt notice to your insurer first, as your policy and its terms require. Don't delay containment, rescue or necessary cleanup to take photos. Take images only when it is safe. Goal: document the condition after a loss event without delaying protection or rescue. 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.

Create an account and start

The problem

After a loss event that may lead to a claim or a coverage dispute, the physical condition can change through cleanup, rescue, removal, repair or disposal.

Take photos only when it is safe, without delaying containment, rescue or urgent measures. Note what changed between images and keep your notice to the insurer.

The water goes down and leaves marks that dry. Firefighters remove what they need to. Soaked furniture goes out to the kerb. The damaged car is towed away. Within days, the scene that showed the extent of the loss no longer exists; response documents and images can help make sense of it, without deciding coverage or compensation.

Safety comes first. Nobody should go back into a dangerous place to take photos.

What to preserve

Wide and detailed photos and videos, response documents, messages, repair quotes and a before-and-after sequence where relevant.

Goal: document the condition after a loss event without delaying protection or rescue.

Main file: photos of the condition taken safely and the response documents.

When to capture: when it is safe, after urgent measures have been taken.

Supporting sources: the notice to the insurer, the policy, the claim reference and any assessor's report.

Limit of this scenario: on its own, the Record does not establish the cause, the technical extent of the damage, who is responsible or insurance coverage.

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.

Wide shots show the extent; details show the damage to each item. If you have photos of the property from before the event, they help the comparison. Response documents, such as the call reference and the report from whoever attended, your messages with the insurer and repair quotes complete the set.

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 of the condition taken safely and the response documents as your reference material and check it against the notice to the insurer, the policy, the claim reference and any assessor's report. The timestamp on a hash does not confirm the cause, the technical extent of the damage, who is responsible or insurance coverage.

Step by step

  1. Put safety, urgent measures and prompt notice to your insurer first, as your policy and its terms require. Don't delay containment, rescue or necessary cleanup to take photos. Take images only when it is safe.
  2. Take photos only when it is safe, without delaying containment, rescue or urgent measures. Note what changed between images and keep your notice to the insurer.
  3. Preserve photos of the condition taken safely and the response documents exactly as it is; don't edit the file you register.
  4. Link the material to the notice to the insurer, the policy, the claim reference and any assessor's report; describe its origin and when it was captured as declared information.
  5. 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, the technical extent of the damage, who is responsible or insurance coverage. Keep the supporting sources and read the Terms of Use.

Frequently asked questions

Will my insurer accept the Record?

That depends on the insurer and on the case. A Record is an extra layer over your photos, not a document your insurer requires.

How should I organize the files for this case?

Once things are safe, create one Project for the event. Register the notice to the insurer, then the wide shots, then the details, and say in each description whether the image was taken before or after cleanup or repairs began.

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.

Start with three free credits

Put safety, urgent measures and prompt notice to your insurer first, as your policy and its terms require. Don't delay containment, rescue or necessary cleanup to take photos. Take images only when it is safe.

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.

Create an account and start

Continue reading