Professional work and service delivery
Professional deliverables, scope and requested changes
Goal: link scope, deliverables and requested changes.
The problem
On a valuable project, there is disagreement about what was requested, delivered, approved, changed or present in a particular version.
Link each deliverable to the scope and to proof of sending. Register significant changes together with the request behind them, and tell a reply apart from an acceptance.
Scope starts as a document and keeps shifting through messages, meetings and emails. The client asks for "just a small tweak", then another. The approved version is replaced by a new one, and the earlier one gets lost in a shared folder the client controls. When payment is late or the client says the work wasn't ready, it's hard to show which version existed on which date and what was requested after the scope was agreed.
This applies to anyone who builds software, creates a visual identity, designs spaces, writes reports or delivers any service in stages.
What to preserve
The approved scope, main deliverables, significant versions, approvals, change requests and the final delivery.
Goal: link scope, deliverables and requested changes.
Main file: the approved scope and the delivered file.
When to capture: at each delivery and at significant changes.
Supporting sources: proof of sending, a reply or an acceptance.
Limit of this scenario: on its own, the Record does not establish complete performance, quality, acceptance or a right to payment.
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 scope is the baseline. Each main deliverable should be kept as a closed file, such as a PDF of the presentation or a ZIP of the code. Approvals and change requests, as exported emails or screenshots with context, show how the agreement changed. A package rebuilt from the same material may come out different, so keep the exact file you sent.
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 approved scope and the delivered file as your reference material and check it against proof of sending, a reply or an acceptance. The timestamp on a hash does not confirm complete performance, quality, acceptance or a right to payment.
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.
- Link each deliverable to the scope and to proof of sending. Register significant changes together with the request behind them, and tell a reply apart from an acceptance.
- Preserve the approved scope and the delivered file exactly as it is; don't edit the file you register.
- Link the material to proof of sending, a reply or an acceptance; 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 performance, quality, acceptance or a right to payment. 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 performance, quality, acceptance or a right to payment.
How should I organize the files for this case?
Use one Project per engagement. Register the approved scope first, then each delivered file with its proof of sending, and each significant change request next to the version it produced. In the description, say whether the client's message was a reply or an explicit acceptance.
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.