Compliance

Every obligation with a deadline, what evidence it needs, and whether you have it.

Compliance in SigmaPointPi
/compliance

Registrations, renewals, filings, insurance, licences and policy reviews. Each carries a due date, a named person accountable for it, and the evidence that proves it was done.

An obligation without evidence is an obligation you cannot demonstrate. Each item names what would satisfy it, so the file is complete rather than assembled under pressure.

Where everything sits

Formally verified core
Formally verified core
property-based tests
property-based tests
replay harness
replay harness
Controls enforced in code today
Controls enforced in code today
Account management
Account management
Protection of audit information
Protection of audit information

How to work this page

Load the obligations that apply to you

Driven by entity type, states of registration, industry and headcount. Obligations you are not subject to are not shown.

Put one name against each

An obligation everybody is responsible for is one nobody does. Every item carries a single name.

Attach the evidence as you go

The filed return, the certificate, the signed policy. Attached at the time, not reconstructed later.

Watch the horizon

Anything due in the next ninety days sits at the top, with the lead time each one actually needs.

On a phone

Compliance on iPhone 15 Pro Max

Every figure from the desktop appears here, stacked rather than reduced. Tables scroll inside themselves so the page never moves sideways, and figures keep their separators and their alignment at every width.

Questions people actually ask

What if an obligation does not apply to us?

Mark it not applicable with a reason. The reason is the record, and it is what you show when somebody asks why it was skipped.

Does it cover industry-specific requirements?

Yes, driven by your trade. A healthcare business gets HIPAA obligations. A contractor gets the ones that apply to contracting.