How it works

From obligation to evidence — one connected compliance lifecycle.

Every regulated industry runs the same underlying cycle. Auregis 2 Comply connects each stage so nothing is re-keyed, nothing is asserted without evidence, and the reported position is always the real one.

1

Understand

Capture the characteristics of the regulated entity, site, facility or asset that determine what applies.

2

Resolve

Determine the applicable requirements using structured, versioned rules rather than assumptions held in spreadsheets.

3

Plan

Schedule inspections, assessments and compliance activities with owners, due dates and escalation.

4

Prove

Connect certificates, reports, readings and photographs directly to the requirement they evidence.

5

Verify

Review the evidence, confirm it satisfies the requirement and identify failures or gaps.

6

Correct

Manage findings and corrective actions through to verified closure.

7

Assure

Provide live compliance visibility, exception reporting and a defensible audit trail.

Rules Engine

Requirements are resolved, not remembered.

Compliance rules are configurable, versioned data. Requirements are resolved from combinations of the characteristics that actually determine what applies — so a change in legislation is a rule change, not a software release.

Every resolved requirement can explain why it applies.
Resolution inputs
JurisdictionEntity or site typeOperational characteristicsServices presentAsset typeAsset configurationRegulatory conditionsOccupancy or use

Each industry supplies its own characteristics. A housing portfolio resolves on tenure, property type, services and fuel source; a facility resolves on operations, hazards and installed systems. The engine is the same.

Architecture principle

Deterministic where compliance must be certain. AI-assisted where intelligence saves time.

Structured rules and verified data determine compliance outcomes. AI accelerates the work around them — it does not decide statutory compliance.

Deterministic
  • Which requirements apply to an entity
  • Frequencies, due dates and statutory windows
  • Whether evidence has been verified by a person
  • Compliance status and reported position
  • Separation of duties on approvals
AI-assisted
  • Extracting key fields from uploaded documents
  • Interpreting and summarising evidence for a reviewer
  • Surfacing the relevant records for a question
  • Drafting narrative from data a person then checks
  • Answering questions about your own compliance records

AI output is always presented for human verification. It never closes a requirement, approves evidence or sets a compliance position on its own.

Evidence and certificates

Evidence isn't storage. It's proof.

Evidence doesn't just get stored. It is connected to the requirement it proves, verified by a person, and carried through to the compliance position.

1Requirement — what must be proved, and by when
2Assessment or inspection — where the requirement calls for one
3Certificate or evidence — captured against that requirement
4Verification — reviewed and confirmed, or rejected with a reason
5Validity and renewal — expiry tracked, next cycle scheduled
6Compliance position — updated from the verified record
Common data model

One structure, many industries.

The reason Auregis 2 Comply can support different regulatory environments without becoming a different product each time.

OrganisationThe regulated body, its group structure and jurisdictions
Portfolio / GroupScheme, region, business unit, operational group
Site / Property / FacilityThe regulated entity that obligations attach to
Asset / SystemPlant, equipment, installation or safety system
Compliance RequirementResolved by the Rules Engine from entity characteristics
Inspection / VerificationThe activity that tests whether the requirement is met
EvidenceCertificate, report, reading, photograph or signed record
Corrective ActionThe finding, its owner, deadline and closure evidence
Compliance PositionThe live, evidenced status reported to leadership and regulators
Capability status

What the platform does today — and what's coming.

Published so buyers can tell the difference between delivered capability and roadmap. Nothing marked planned is available.

Core
Rules Engine with conditions, jurisdictions and versioningAvailable
Requirement resolution from entity characteristicsAvailable
Inspection scheduling, performance and close-outAvailable
Evidence linked to requirements, with verificationAvailable
Certificate register, validity and renewalAvailable
Corrective actions through to verified closureAvailable
Contractor credential and insurance currencyAvailable
Reporting with CSV and print/PDF exportAvailable
Append-only audit trail of every changeAvailable
AI
AI document extraction with mandatory human verificationAvailable
Compliance assistant scoped to your own recordsAvailable
AI-drafted executive summariesIn development
Statutory change monitoringPlanned
Policy gap analysisPlanned
Predictive compliance risk and forecastingPlanned
Field
Mobile inspection captureIn development
Offline capture and geotagged evidencePlanned
Assurance
Curated board and regulator audit packs· Reporting and export available todayIn development
Security
Row-level tenant isolation and role-based accessAvailable
Multi-factor authenticationIn development
Single Sign-OnIn development
Integrations
REST APIPlanned
Microsoft 365, Outlook, Teams, SharePointPlanned
Power BI and analytics exportPlanned
GIS mappingPlanned
Line-of-business system connectorsPlanned

See the lifecycle running on real records.

A 30-minute walkthrough from requirement resolution to reported assurance.

Book a Demo