Module

DocumentGuard

Know which certificate expires before the customer's auditor does.

Beta — live for pilot tenants₹15,000 / month
See pricing

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 figures. 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 is not finished.

BETA rather than AVAILABLE. Documents import through the compliance_documents template and a daily sweep runs the expiry engine, so a finding now exists without anybody opening the page. Two things are honestly still missing: requirements — what a subject *ought* to hold — have a table and no import, so the missing-document sweep has nothing to compare against on a live tenant; and findings are recorded rather than delivered, so nothing reaches an inbox until the notification centre is wired to them.

Where this sits

One of 16 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 15 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.

Get started

Bring one month of data. Leave with your own control tower.

A demo runs on your material master, your purchase orders and your stock — not on ours. Thirty minutes, and you see your own exceptions rather than a scripted one.

Ask a question

Book a demo

Thirty minutes, on your own data. Six fields — the rest only helps us prepare.

Not binding. Tell us the size and we will say which one fits.

The demo connects to it, so this shapes the whole session.

Add context, and the demo runs on your problem rather than a scripted one

We reply within one working day.