Consumer disputes, construction and services
Custom-made furniture not delivered, incomplete or defective
Goal: tell undelivered units apart from units installed differently from the design.
The problem
A significant order isn't delivered on time, or it differs in dimensions, material, finish or how it works.
Identify the order and the unit. Compare the approved design with what was installed, and don't confuse a unit that was never delivered with one installed differently. First raise it with the supplier and keep their reply; in a consumer dispute, you can also contact the consumer authority or regulator in your country.
Custom furniture is usually expensive, paid in instalments and delivered in stages. The first installation is incomplete, parts are missing, a drawer arrives in the wrong colour. The company books a visit, replaces one part, leaves another. With every intervention, the previous state disappears.
When the discussion about a discount, a return or redoing the work arrives, it's hard to show what was delivered at each point and whether the result matches the approved design.
What to preserve
The approved design, the schedule, photos and videos of the installation, defects, messages, visits and the final condition.
Goal: tell undelivered units apart from units installed differently from the design.
Main file: the order, the approved design and a photo of the unit.
When to capture: on the promised date and at each installation or visit.
Supporting sources: the visit work order and the supplier's reference number.
Limit of this scenario: on its own, the Record does not establish complete non-performance, the cause of a defect or any right to a refund.
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 approved design, with its dimensions, materials and colours, is the benchmark. Photos with a tape measure in shot help show a difference in size. Videos show what doesn't work: the door that won't close, the runner that sticks. Keep the scheduling messages and the visit work orders too.
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 the order, the approved design and a photo of the unit as your reference material and check it against the visit work order and the supplier's reference number. The timestamp on a hash does not confirm complete non-performance, the cause of a defect or any right to a refund.
Step by step
- First, raise the issue with the supplier and keep the reference number and their reply. In a consumer dispute, you can also contact the consumer authority or regulator in your country.
- Identify the order and the unit. Compare the approved design with what was installed, and don't confuse a unit that was never delivered with one installed differently.
- Preserve the order, the approved design and a photo of the unit exactly as it is; don't edit the file you register.
- Link the material to the visit work order and the supplier's reference number; 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 complete non-performance, the cause of a defect or any right to a refund. 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 complete non-performance, the cause of a defect or any right to a refund.
How should I organize the files for this case?
Name each unit the way the order does, for example "wardrobe – module 3", and keep its approved design, installation photos and visit work orders together. Register a missing unit and a unit installed differently as separate issues, so one is never mistaken for the other.
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.