Four situations
Does this describe you?
Four situations Sidefile fits. Each one says what the product produces, not what the outcome will be.
The four situations
- 01
A manufacturer whose accommodation requests arrive by email to shared inboxes
Requests reach an HR address that several people monitor, alongside payroll questions and shift swaps. A doctor's note is forwarded to a second address so somebody can act on it while the first person is away, and printed once so it can be read on the floor.
The document is now in three places, and the list of people who can open each one is a list of mailbox permissions nobody has read in a year.
Sidefile produces one store for the document outside the personnel record, with row level policies deciding who can reach it and a named entry in the access ledger for every opening.
- 02
An employer facing a request to produce who accessed a medical file
The question is not whether the file was handled carefully. It is who opened it, when, and for what stated purpose. Mail systems and shared drives answer the first part poorly and the third part not at all.
What the answer usually rests on is recollection, assembled after the request, by the people who are themselves the subject of it.
Sidefile produces an append-only ledger of every access to the file, each entry carrying the name, the role, the timestamp, the object and the purpose recorded at the time, including the attempts that were refused.
- 03
An organisation where supervisors ask for restrictions and receive certifications
A supervisor needs to know what the employee can do this week. What reaches them is the certification itself, because the certification is the document that arrived and forwarding it is the fastest thing to do.
The diagnosis travels with it. Nobody intended that, and nothing in the mail path was built to prevent it.
Sidefile produces a functional capacity record that can be published to the supervisor while the certification stays in the separate store, and refuses the supervisor's attempt on the certification at the database layer rather than at the screen, logging the refusal.
- 04
An employer running leave programs across several states
Each program asks for its own forms, its own timing and its own documentation, and each one generates medical paper that arrives through a different route. The programs are administered by different people, sometimes in different systems.
The record of the process is therefore spread across those systems, in the shape each system happened to impose, which is not a shape anybody can read end to end.
Sidefile produces one dated record per employee file across the programs in scope: the documents in the separate store, the interactive process log, and the access ledger the employee reads from their own phone.