Custody, transfer and logistics handoffs
Car rental, moving, shipping or leaving an item in someone else's custody
Goal: compare the condition before and after someone else had the item.
The problem
A valuable item temporarily changes hands, and damage, missing parts or its condition may be disputed later.
For a rental car, check the vehicle, the mileage and the fuel. For shipping or a move, check the inventory, the number of boxes, the packaging and any damage; don't apply vehicle items to other goods.
At the rental desk, the inspection is quick and done in the car park. On a move, furniture leaves wrapped and arrives days later. When equipment is shipped, nobody checks box by box. When something turns up damaged or missing, the charge comes from one side or the other, and each has its own version of the starting condition.
What to preserve
Systematic before-and-after photos and videos, identifiers, accessories, mileage or fuel where relevant, and handover documents.
Goal: compare the condition before and after someone else had the item.
Main file: the checklist and photos of the item or the boxes.
When to capture: at handover and at return or delivery.
Supporting sources: the custody agreement and the proof of delivery.
Limit of this scenario: on its own, the Record does not establish the cause of the damage or the responsibility of whoever had the item.
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 video walking all the way around the car, with close-ups of the wheels, bumpers and windows, covers most common charges. On a move, photos of the most valuable furniture and a list with the number of boxes help. Mileage and fuel belong only on a vehicle checklist. For shipping or a move, link the boxes, the inventory and the receipts, and keep the relevant handover and return documents.
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 checklist and photos of the item or the boxes as your reference material and check it against the custody agreement and the proof of delivery. The timestamp on a hash does not confirm the cause of the damage or the responsibility of whoever had the item.
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.
- For a rental car, check the vehicle, the mileage and the fuel. For shipping or a move, check the inventory, the number of boxes, the packaging and any damage; don't apply vehicle items to other goods.
- Preserve the checklist and photos of the item or the boxes exactly as it is; don't edit the file you register.
- Link the material to the custody agreement and the proof of delivery; 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 cause of the damage or the responsibility of whoever had the item. 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 the cause of the damage or the responsibility of whoever had the item.
How should I organize the files for this case?
Use one Project per handover, with the "before" and the "after" as separate milestones. For a car, keep the walk-around video and the dashboard photo; for a move or shipment, keep the inventory and photos of the numbered boxes. Don't mix the two checklists.
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.