Compliance in Alloovium

Construction teams already hold the evidence an auditor wants: safety plans, ITPs, permits, inductions, registrations and certificates. The problem is rarely that the evidence is missing — it is that a plan quietly expired, a record was never signed, or a commitment made in a specification has no proof behind it. Compliance in Alloovium is the lens that reads for exactly those signals.

By default the lens is deliberately light. It watches documents as they arrive, detects a small set of deterministic signals — expiry dates, incomplete or unsigned records, blank templates — and raises a plain, trackable finding for each. No configuration and no separate console are required to get value on day one.

Everything in Alloovium sits inside one product built around your project documents. Compliance is one way of looking at that same corpus — a risk lens — rather than a place you go to do separate work. The findings it raises become items you act on in the flow you already use, and they link straight back to the source document and the exact page.

Two levels of depth are available. The light lens described above is always on. A heavier conformance engine — which extracts the commitments a project makes, searches the corpus for proof, and judges whether each is satisfied — is available when the compliance engine is enabled for your workspace.

The backbone of the light lens is expiry. When a document arrives, Alloovium reads it for expiry language — phrases such as expires, valid until or a recertification date — and parses the date next to it. If that date has passed, or is close, the lens raises a finding attributed to whoever uploaded the document.

Registered professionals are tracked the same way: a registration expiry on an engineer or other licensed role becomes a signal the lens can watch. The point is not to build a separate register you have to maintain, but to notice the dates that are already written into the documents you hold.

A finding is the unit of work the lens produces. Whether it comes from a light signal or from the deeper engine, it carries the same shape: a short title, a severity, a status, and — critically — a citation back to the document and page it came from. You can assign it, add resolution notes, resolve it, or dismiss it.

When the compliance engine is enabled, findings are computed as gaps between what a project promises and what the corpus proves. That deeper analysis — conformance gaps, contradictions and the Attention surface that routes each gap to the person who can close it — is covered on the conformance and attention page.

When the compliance engine is enabled, findings can be organised against management-system standards. The built-in rubrics cover the three ISO systems most construction and engineering teams carry.

Each standard is broken into hierarchical clauses with evidence hints, so a gap can point at the specific clause it relates to. The light lens does not require any of this — it works on raw document signals alone.

Compliance is one of the lenses on Today. Rather than living behind a separate menu, expiring credentials, unsigned records and open gaps flow into the same feed of things that need your attention, tagged as compliance so you can filter to them.

1. 1

   A signal is detected

   A document arrives with an expiry date or an unsigned record, and the lens raises a finding.

2. 2

   It routes to a person

   The finding is attributed to the uploader and appears in the Today feed as something to act on.

3. 3

   You close the loop

   Assign, resolve or dismiss the finding. Resolved items leave the feed; dismissed ones stop resurfacing.

Two companion pages go deeper into the engine-gated capabilities:

• Conformance and attention — how project conformance gaps are computed, routed and war-gamed.
• Audit pack and evidence — assembling a point-in-time evidence dossier for an auditor.