← Back to the category

Consumer disputes, construction and services

Delayed, abandoned or poorly executed building or renovation work

Goal: tell delays, visible defects and substituted materials apart.

Create an account and start

The problem

Building work is late, incomplete or defective, and its condition keeps changing as contract milestones and repair attempts come and go.

Separate delays in the work, visible defects and materials that differ from what was agreed. Link each issue to the relevant contract clause and to the schedule. First raise it with the contractor and keep their reply; in a consumer dispute, you can also contact the consumer authority or regulator in your country.

The schedule said three months and it's been six. The builder disappeared after the second payment. The wall is crooked, the flooring was swapped for something cheaper, the damp came back after the "fix". Meanwhile, the work goes on: someone else comes in to finish, the defect is covered up, the material is thrown away.

When the argument about payment or redoing the work starts, what was there at each stage is no longer there. Loose photos on a phone, in no particular order, say very little.

What to preserve

The relevant contract or schedule, photos and videos at each milestone, defects, substituted materials, messages and attempts to fix the work.

Goal: tell delays, visible defects and substituted materials apart.

Main file: a photo of the item and the agreed schedule.

When to capture: at the scheduled milestone and when you notice the discrepancy.

Supporting sources: the contract clause, the schedule and the contractor's reference number.

Limit of this scenario: on its own, the Record does not establish the cause of the delay, a technical defect or any duty to pay compensation.

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.

The contract and the schedule show what was agreed. Photos and videos at each milestone show what was done. Defects deserve one wide shot, for context, and one close-up, for detail. Receipts and photos of the packaging help when the material delivered differs from what was agreed. Messages with the contractor show the requests and the promises to fix things.

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 a photo of the item and the agreed schedule as your reference material and check it against the contract clause, the schedule and the contractor's reference number. The timestamp on a hash does not confirm the cause of the delay, a technical defect or any duty to pay compensation.

Step by step

  1. First, raise the issue with the contractor and keep the reference number and their reply. In a consumer dispute, you can also contact the consumer authority or regulator in your country.
  2. Separate delays in the work, visible defects and materials that differ from what was agreed. Link each issue to the relevant contract clause and to the schedule.
  3. Preserve a photo of the item and the agreed schedule exactly as it is; don't edit the file you register.
  4. Link the material to the contract clause, the schedule and the contractor's reference number; 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 of the delay, a technical defect or any duty to pay compensation. Keep the supporting sources and read the Terms of Use.

Frequently asked questions

Do I need to take photos every day?

No. Register the milestones and the significant problems. The sequence is more useful than the volume.

How should I organize the files for this case?

Use one Project per job. Give each problem its own Records and say in the description whether it is a delay, a visible defect or a substituted material, along with the contract clause or schedule date it relates to. Add the contractor's reference number and reply when you have them.

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

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