← Back to the category

Work and income

Actual working hours and after-hours messages when the evidence is controlled by the employer

Before copying anything, check that your access and keeping the material are lawful. If you are unsure about confidentiality or authorization, get advice from an employment adviser, your union or a qualified local professional before making any copy. Don't take material out of company systems indiscriminately. Goal: organize communications you can lawfully keep.

Create an account and start

The problem

There is material exposure and a risk of losing access to messages, tasks or communications relevant to a dispute about working hours, availability or routine.

A message outside working hours doesn't show that work was actually done. Link tasks and replies to the context available, without indiscriminate monitoring or broad copying out of company systems.

Company email, task tools, a messaging group run by a manager: almost everything that shows the real work routine is controlled by the employer. An account can be deactivated on the day of a dismissal, a group can be deleted, a history can be wiped. When a dispute about working hours or on-call time comes up, the person no longer has any way to show what they used to receive.

This use case isn't for monitoring colleagues or copying everything. It makes sense when there is material exposure and a real risk of losing access.

What to preserve

Exports or screenshots with context, emails, task records and other lawful material the person already has access to.

Goal: organize communications you can lawfully keep.

Main file: messages, tasks and emails you are allowed to keep.

When to capture: only after checking that your access and keeping the material are lawful.

Supporting sources: time records and advice from an employment adviser or union.

Limit of this scenario: on its own, the Record does not establish hours actually worked, overtime owed, on-call time or employment status.

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.

Only if access and keeping the material are lawful, use context to link a message, a task and a reply. Don't copy confidential or third-party data without authorization and need. A message sent outside working hours doesn't show that work was done during that time.

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 messages, tasks and emails you are allowed to keep as your reference material and check it against time records and advice from an employment adviser or union. The timestamp on a hash does not confirm hours actually worked, overtime owed, on-call time or employment status.

Step by step

  1. Before copying anything, check that your access and keeping the material are lawful. If you are unsure about confidentiality or authorization, get advice from an employment adviser, your union or a qualified local professional before making any copy. Don't take material out of company systems indiscriminately.
  2. A message outside working hours doesn't show that work was actually done. Link tasks and replies to the context available, without indiscriminate monitoring or broad copying out of company systems.
  3. Preserve messages, tasks and emails you are allowed to keep exactly as it is; don't edit the file you register.
  4. Link the material to time records and advice from an employment adviser or union; 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 hours actually worked, overtime owed, on-call time or employment status. Keep the supporting sources and read the Terms of Use.

Frequently asked questions

Can I register my company's internal documents?

Only what is lawful and necessary. Prefer the messages and tasks that show your own routine, without confidential data.

How should I organize the files for this case?

Keep the lawfully kept originals in one Project, one Record per file, and describe the context of each message or task. If you need to share a copy, redact third-party or confidential data in a separate file and note which version's hash you registered.

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.

Only document files you can already lawfully keep

Before copying anything, check that your access and keeping the material are lawful. If you are unsure about confidentiality or authorization, get advice from an employment adviser, your union or a qualified local professional before making any copy. Don't take material out of company systems indiscriminately.

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