Features / Document management
A controlled document library that remembers the dates for you.
Policies, standard operating procedures, safety data sheet binders, and certificates don't just need a home — they need a review schedule, a retention horizon, and someone reminded before either lapses. SE gives every document a review cadence and a retention horizon, reminds the owners ahead of the deadline, tracks an approval lifecycle and full version history, and rolls the whole library up into one dashboard that shows what's due, what's overdue, and what's approaching its retention date. The records live next to your incidents, hazards, and SDS data — not in a separate document silo.
What's in it
The capability surface.
Central controlled library
- One tenant-wide library for policies, SOPs, SDS binders, certificates, and any controlled record — not a folder tree bolted onto the side.
- Full version history — each document carries its lineage and a reference to the prior version, so "what changed, and when" is answerable without digging.
- Tag every document and search, filter, and sort the whole library by what you actually need to find.
- Access is permission-gated — only people with document-management rights see and manage the library.
Scheduled review cadence
- Give each document its own review cycle — annual policy review, quarterly procedure check, whatever the record needs.
- SE computes the next review-due date and surfaces it on the record and the dashboard, so nothing quietly goes stale.
- Mark a document reviewed with a timestamped note and the reviewer's name on file — the review history travels with the document.
- Overdue reviews are surfaced first, not buried.
Retention horizons — advisory by design
- Set a retention horizon per document; SE computes when retention is reached and surfaces it as status on the record and the dashboard.
- Deletion stays a human decision. SE never purges a record on a timer — a document under legal hold or an active regulatory obligation must not disappear because a clock ran out.
- When a record reaches its retention horizon it's flagged for a disposition decision, not auto-deleted — the safe default for controlled records.
Reminders before the deadline
- Automatic reminders go out 30 days ahead of a document's review-due date and ahead of its retention horizon — well before either lapses.
- If a review or retention date passes without action, the overdue state is reminded on as well.
- Reminders reach the people responsible for the library, so the deadline doesn't depend on someone remembering to check.
Approval lifecycle
- Every document moves through a clear lifecycle — Draft, then Approved or Rejected — with the current status visible on the record.
- Turn on an admin approval gate when a record needs a sign-off before it counts as current.
- The approval state pairs with the version history, so an approved version is always identifiable.
Library dashboard
- One library view with at-a-glance counts — total documents, due for review, overdue, approaching their retention horizon, and a breakdown by approval status.
- Filter chips narrow the list by review status, approval status, tag, or urgency, so "show me everything overdue" is one click.
- Every row deep-links to the document, so the dashboard is the way in, not a dead-end report.
- Everything is computed live off the current state of the library — no stale snapshot to refresh.
Representative workflows
What this looks like in practice.
An annual policy review that never slips
A site safety policy is filed with a yearly review cycle. Eleven months on, the document surfaces on the library dashboard's "due for review" count and the owner gets a reminder — 30 days before the review date, not after it lapsed. The reviewer opens the record, confirms the policy still holds, and marks it reviewed with a short note. The note and the reviewer's name join the document's history, the next review date rolls forward a year, and the record drops off the due list until next time.
A retention horizon that prompts a decision, not a deletion
A training certificate carries a retention horizon set to match the record's required keep-period. As that date approaches, the document is flagged on the dashboard and the owner is reminded. Rather than the system quietly deleting the record, a person decides what happens to it — archive it, extend it, or dispose of it deliberately. If the record is under a legal hold, it stays exactly where it is. Retention informs the decision; it never makes it for you.
How this is different
A controlled library, not a file drawer.
No surprise deletions
Retention is advisory. SE surfaces the horizon and reminds you, but a controlled record is only ever disposed of by a person — the safe default when legal holds and regulatory obligations are in play.
Connected to the rest of the record
Documents live on the same platform as your incidents, hazards, and safety data sheets — controlled records in context, not stranded in a standalone document system you have to cross-reference by hand.
The deadline doesn't depend on memory
Review cadences and retention horizons are tracked by the platform and reminded on automatically. Staying current stops being a calendar someone has to maintain and a date someone has to remember.
Continue exploring
More on the SE platform.
Controlled records sit alongside the rest of the platform. Jump anywhere.
See the document library in the running product.
A 30-minute walk-through against your own controlled records — your review cadences, your retention rules, your approval gates. We'll show the library dashboard surfacing what's due and overdue, the reminders firing ahead of a deadline, and how the records sit next to the rest of your safety data.