Public services and physical conditions
A public-service problem that persists after a complaint
Goal: organize your observations and the response to a public-service problem.
The problem
A condition that could cause damage, an accident or a loss remains after a report or complaint.
Organize the first observation, the complaint reference, the response deadline and a new observation. Two photos show two moments; they don't show the whole interval in between. Contact the responsible body or service provider first, then its ombudsman or complaints-review channel, if there is one.
Problems in streets and public spaces change gradually. The pothole grows, the pavement sinks, the damp spreads. When damage finally happens, such as a burst tyre, a fall or a flooded shop, the discussion turns to what was already known and since when. Loose photos on a phone, in no order and not linked to the complaint reference, are of little help.
What to preserve
Photos and videos, the complaint reference, new images at significant milestones and documentation of any resulting damage.
Goal: organize your observations and the response to a public-service problem.
Main file: the first photo, the complaint reference and a new observation.
When to capture: at the first observation and after the stated deadline.
Supporting sources: the responsible body or service provider and its ombudsman.
Limit of this scenario: on its own, the Record does not establish that the problem persisted continuously between two photos, who is responsible or a causal link.
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.
Photos that show the problem with something in the background that identifies the place, such as a sign, a house number or a street corner, help locate it. The complaint confirmation, as a screenshot or PDF, shows when you reported it. New images at each significant change show how it evolved. If there is damage, register photos and documents of it 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 first photo, the complaint reference and a new observation as your reference material and check it against the responsible body or service provider and its ombudsman. The timestamp on a hash does not confirm that the problem persisted continuously between two photos, who is responsible or a causal link.
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.
- Organize the first observation, the complaint reference, the response deadline and a new observation. Two photos show two moments; they don't show the whole interval in between. Contact the responsible body or service provider first, then its ombudsman or complaints-review channel, if there is one.
- Preserve the first photo, the complaint reference and a new observation exactly as it is; don't edit the file you register.
- Link the material to the responsible body or service provider and its ombudsman; 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 that the problem persisted continuously between two photos, who is responsible or a causal link. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
Does a Record replace the complaint to the responsible body?
No. A complaint through the body's own channel is still the first step. The Record organizes what you have gathered.
How should I organize the files for this case?
Keep one Project per problem. Register the first photo, the complaint confirmation, a new photo after the stated deadline and any escalation, in that order. Shoot from the same spot each time so the images can be compared.
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.