Compliance

Compliance in Eriga indicates whether obligations are being met. It is not an entity you create manually — it is calculated automatically by the system in real time, every time you view the page.

This is an important point: compliance is never stored in the database. Eriga recalculates it on the fly by cross-referencing resources, units, actions, and certificates. This ensures the data is always up to date — there is no risk of seeing a “stale” compliance status.

How an obligation arises

A compliance obligation arises from the intersection of three elements:

1. A resource is assigned to a unit
2. An action is assigned to the same unit
3. The resource type is compatible with the action’s target type

The third condition is critical: if the unit “Production Department” contains both people and equipment, and the action “Fire safety training” targets Person, only the people will acquire that obligation — the equipment will not.

Concrete example

Let’s see how it works with a real case. The “Production Department” unit at Acme Corp has:

Assigned resources:

• John Smith (Person)
• Jane Doe (Person)
• Forklift CAT 01 (Equipment)

Assigned actions:

• Fire safety training (target: Person, validity: 36 months)
• Periodic medical exam (target: Person, validity: 12 months)
• Periodic equipment inspection (target: Equipment, validity: 12 months)

Generated obligations (5 total):

Resource	Action	Why
John Smith	Fire safety training	Person + target Person
John Smith	Periodic medical exam	Person + target Person
Jane Doe	Fire safety training	Person + target Person
Jane Doe	Periodic medical exam	Person + target Person
Forklift CAT 01	Periodic equipment inspection	Equipment + target Equipment

The forklift has no training obligations (incompatible type), and the people have no equipment inspection obligations.

Compliance status

For each obligation, Eriga checks whether a valid certificate exists:

Status	Condition
Compliant	A valid certificate exists with expiry more than 30 days away
Expiring	A certificate exists that expires within 30 days
Non-compliant	No certificate exists, or the certificate has expired or been revoked

Calculation example

Let’s continue the previous example. Suppose today is March 25, 2026 and the certificates are:

Resource	Action	Certificate	Status
John Smith	Fire safety training	Issued 01/10/2026, expires 01/10/2029	Compliant
John Smith	Periodic medical exam	Issued 03/01/2025, expires 03/01/2026	Non-compliant (expired)
Jane Doe	Fire safety training	Issued 03/15/2026, expires 03/15/2029	Compliant
Jane Doe	Periodic medical exam	Issued 01/01/2026, expires 04/01/2026	Expiring (expires in 7 days)
Forklift CAT 01	Periodic equipment inspection	No certificate	Non-compliant

Compliance percentage

The percentage indicates how many obligations are compliant out of the total:

Compliant / Total obligations = Percentage

In the example: 2 compliant out of 5 obligations = 40%

“Expiring” obligations do not count as compliant in the percentage calculation — they are an attention signal indicating the need for imminent renewal.

The percentage is visible on the Dashboard and on the Compliance page, and is always calculated in real time.

How to improve compliance

To bring an obligation to “compliant” status:

1. Go to the Certificates section
2. Issue a certificate for the resource and action in question
3. The system immediately updates the compliance status — no waiting required

When an action has an approaching deadline (“expiring” status), you don’t need to wait for it to expire: you can issue the new certificate in advance.

Learn more

• Guide: compliance — how to read and interpret the compliance page
• Units — the mechanism that links resources and actions
• Resources — the entities subject to obligations
• Actions — the compliance requirements
• Certificates — how to attest the fulfillment of an obligation
• Notifications — how Eriga alerts you about expiry dates