Ask for the acknowledgement
Require read and understood on any document, at the moment you upload it.
Document libraries
The documents people have to read, where they already work.
Document libraries in e20 hold the SDS, COSHH, RAMS, certificates and policies a field team needs. They are organised by team, on the desktop and in the mobile app.
And when a document has to be read, you can ask for that in writing and see who has done it.
Organised by team
A library belongs to a team, so what opens is what that team needs.
- Types you name yourself: policy, SDS, COSHH, RAMS, certificate, whatever you file.
- Search by name, filter by library or type, and open it in the browser.
- Upload one file or drop a batch in at once.
Read and understood
Tick one box as you upload, and the document stops being a file on a shelf: everyone in scope is asked to acknowledge it.
Tell people it is there
Notify by push, by email, or both, as it goes out.
New version, new acknowledgement
Replace the file and you can require everyone to acknowledge it again.
Proof, not a promise
The read status screen splits everyone in scope into outstanding and acknowledged, and hands you the list an auditor asks for.
- Outstanding and acknowledged counts, with the names under each.
- Filter by team, and export the whole thing to CSV.
- Each receipt carries when it was acknowledged, on what, and how long the document was open.
On the phone, on site
The field app carries the same libraries, so the document sits where the job is.
- Acknowledged or still pending, marked on every document in the list.
- Documents already downloaded stay readable when the signal goes.
- One tap to acknowledge, from the document itself.
What you get
- The right documents in front of the right team
- An acknowledgement you can show
- The same library on the desktop and in the field
Cut the admin. Keep the standards.
Book a 30-minute walkthrough. We'll show you e20 against a real process from your sector.