Education, exams and selection processes
A preliminary answer key or exam page that may change
Goal: compare versions of documents in a selection process.
The problem
This use only adds value when the exam body doesn't reliably keep the official versions of a high-stakes selection process.
Check the deadline and the appeal channel in the official exam notice first; don't delay your appeal to capture or register anything. Compare the PDF, any correction notice and the identification of the test or booklet, and keep the appeal reference number.
In high-stakes selection processes, a single question can decide a place. Exam bodies publish answer keys, notices and corrections on pages that change, and they don't always keep a clear history of what was published before. A PDF can be replaced at the same address, and a page can be edited without notice. When you need to support an appeal, you have to show which version you saw.
If the exam body already keeps a clear version history, this use case adds little.
What to preserve
The official PDF, a full capture and the URL.
Goal: compare versions of documents in a selection process.
Main file: the official PDF, any correction notice and a capture with the URL.
When to capture: after first checking the deadline and the channel in the exam notice.
Supporting sources: the exam notice, the test or booklet identification and the appeal reference number.
Limit of this scenario: on its own, the Record does not establish that the exam body published that version or that an appeal will succeed.
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.
Download the answer key or notice PDF as soon as it is released and don't alter the file. Take a full-page capture with the address visible in the browser bar and, if possible, the computer's date and time on screen. Note the exact URL you downloaded the file from.
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 official PDF, any correction notice and a capture with the URL as your reference material and check it against the exam notice, the test or booklet identification and the appeal reference number. The timestamp on a hash does not confirm that the exam body published that version or that an appeal will succeed.
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.
- Check the deadline and the appeal channel in the official exam notice first; don't delay your appeal to capture or register anything. Compare the PDF, any correction notice and the identification of the test or booklet, and keep the appeal reference number.
- Preserve the official PDF, any correction notice and a capture with the URL exactly as it is; don't edit the file you register.
- Link the material to the exam notice, the test or booklet identification and the appeal 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 that the exam body published that version or that an appeal will succeed. Keep the supporting sources and read the Terms of Use.
Frequently asked questions
Can I use the Record instead of an appeal?
No. The appeal follows the rules in the exam notice. A Record is a complement.
How should I organize the files for this case?
File your appeal first. Then register the original PDF as downloaded, the full-page capture and a note with the URL as separate Records, and add any correction notice as a new Record so the two versions can be compared. Include your test or booklet identification in the description.
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.