← Back to the category

Consumer disputes, construction and services

A vehicle, appliance or piece of equipment left for repair

Goal: compare drop-off, collection and any recurring fault.

Create an account and start

The problem

A valuable item is handed over for repair, and later there is a dispute about its earlier condition, new damage, parts, mileage or the work done.

Check the identifiers, the condition at drop-off, the itemized parts and the collection document. If the fault comes back, start a new milestone with the corresponding service visit.

When dropping something off, hardly anyone looks closely. The work order notes the main fault and little else. When the item comes back, questions arise: was that dent already there? Isn't the mileage higher than it should be? Is the replaced part new? Did the fault return because the repair was poor, or for another reason?

Each side has its own memory, and the work order rarely describes the overall condition.

What to preserve

Photos and videos before drop-off, serial numbers, mileage where relevant, existing defects, the work order and the condition on return.

Goal: compare drop-off, collection and any recurring fault.

Main file: the drop-off work order and photos of the item.

When to capture: when you drop it off and when you collect it.

Supporting sources: the collection document and the parts itemized on the work order.

Limit of this scenario: on its own, the Record does not establish the technical quality of the repair or the cause of a recurring fault.

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 full walk-around video of the car or the equipment shows its overall condition. Photos of the dashboard showing the mileage, of the label with the serial number and of any existing defects complete the "before". The work order and the quote show what was requested.

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 drop-off work order and photos of the item as your reference material and check it against the collection document and the parts itemized on the work order. The timestamp on a hash does not confirm the technical quality of the repair or the cause of a recurring fault.

Step by step

  1. Define your goal and check that your access is legitimate, which permissions apply and whether any deadlines are running before you collect anything.
  2. Check the identifiers, the condition at drop-off, the itemized parts and the collection document. If the fault comes back, start a new milestone with the corresponding service visit.
  3. Preserve the drop-off work order and photos of the item exactly as it is; don't edit the file you register.
  4. Link the material to the collection document and the parts itemized on the work order; 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 technical quality of the repair or the cause of a recurring fault. Keep the supporting sources and read the Terms of Use.

Frequently asked questions

Isn't the work order enough?

It records the request, but it usually says little about the overall condition. Photos and video complete the picture.

How should I organize the files for this case?

Keep one Project per repair, with three clear milestones: drop-off, collection and, if needed, recurrence. Register the work order and the photos at each one, and note in the description which parts the work order lists as replaced.

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