Module
DocumentGuard
Know which certificate expires before the customer's auditor does.
Watch demo
The customer's auditor asks for the supplier's ISO certificate. It expired in June.
The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- Every SDS, TDS, COA, ISO certificate, licence, insurance and contract, with its owner and expiry
- Alerts at 90, 60, 30 and 7 days, and on expiry
- Coverage gaps — the supplier or material with no document at all
A worked example
7 documents expire within 30 days
ISO 9001 · Supplier ABC · expires 11 Sep 2026
SDS · CH-2210 · expires 19 Sep 2026
insurance certificate · Carrier DEF · expired 3 days ago
→ 2 suppliers have no SDS on file at all
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
Certificates expire quietly. A test report, a calibration, a licence, an authorisation — each has a date, each lives in a different folder, and none of them tells anybody. The expiry is discovered by a customer's auditor, or by a consignment that cannot ship. What makes a tracker useful rather than another spreadsheet is knowing what depends on each document: an expiring certificate that nothing references is an errand, and one that eleven open orders reference is the most important thing on the desk this week.
Opened by the supply chain manager, the procurement lead and the administrator — what each of them sees first.
Said before you ask
What we don’t do.
SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.
Documents come in on the compliance_documents template and a daily sweep runs the expiry engine, so a finding exists without anybody opening the page. What a subject ought to hold is yours to state: the requirements table is there and its import lands next, because a missing-document alert measured against a list SIAARU invented would be noise. Findings are recorded on the page today, and delivery to an inbox follows when the notification centre is wired to them.
Where this sits
One of 36 modules, on one engine.
DocumentGuard reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 35 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.