Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Compliance Management
- Authority sources
- Evidence repository
- File access
Compliance Management organizes an organization's obligations, rated risks and owned controls around periodic assessments. A compliance lead sets the assessment scope and period, assigns an owner and records planned tests.
review waits for the compliance lead
| Record number | Subject | Status | Period start | Period end | Owner | |
|---|---|---|---|---|---|---|
| ASS-46170 | 2026 vendor access review | Planned | 27 Oct | 02 Nov | Clara Mensah | |
| ASS-11740 | Quarterly payment control testing | Testing | 15 Oct | 23 Oct | Irene Salgado | |
| ASS-72809 | Data retention policy assessment | Review | 25 Oct | 29 Oct | Tariq Iwata | |
| ASS-14030 | Warehouse safety compliance review | Remediation | 17 Oct | 21 Oct | Luis Park | |
| ASS-52015 | Annual privacy controls assessment | Planned | 27 Oct | 31 Oct | Evan Farouk |
Independent Reviewer decides with a reason and source revision.
Every feature works on the same records. Pick one to see the screen your team works in.
Track regulatory scope and review decisions against an assessment.
Approval conditions
| Id | Status | Revision | Jurisdiction | Authority source | Parent | |
|---|---|---|---|---|---|---|
| OBL-2026-0041 | Submitted | 730 | California | State privacy statute | Customer record access audit | |
| OBL-2026-0042 | Submitted | 810 | New York | Workplace safety regulation | Warehouse safety compliance review | |
| OBL-2026-0043 | Submitted | 250 | Ontario | Payment services rule | Quarterly payment control testing | |
| OBL-2026-0044 | Submitted | 520 | England and Wales | Data retention policy | Quarterly payment control testing | |
| OBL-2026-0045 | Submitted | 730 | New South Wales | Supplier contract standard | Incident response readiness check |
Connect rated business risks to owned safeguards.
Controls
| Control code | Description | Effective from | Risk | Owner | |
|---|---|---|---|---|---|
| ACCESS-REV-01 | Former contractor account stayed active | 31 Oct | Single-person payment approval | Clara Mensah | |
| PAY-APR-02 | Require two approvals for payments | 23 Oct | Unreported warehouse safety hazards | Asha Benali | |
| DATA-RET-03 | Archive owner is missing from schedule | 14 Oct | Outdated customer privacy notice | Luis Park | |
| SAFE-INS-04 | Inspect warehouse exits each week | 14 Oct | Unvetted third-party data access | Hana Okonkwo | |
| PRIV-NOT-05 | Privacy notice uses an older version | 27 Oct | Outdated customer privacy notice | Evan Farouk |
Plan an assessment period, scope and accountable owner.
Assessments
| Record number | Subject | Status | Period start | Owner | |
|---|---|---|---|---|---|
| ASS-50829 | 2026 vendor access review | Draft | 01 Nov | Evan Farouk | |
| ASS-24887 | Quarterly payment control testing | Planned | 23 Oct | Clara Mensah | |
| ASS-63208 | Data retention policy assessment | Testing | 25 Oct | Nico Shah | |
| ASS-96289 | Warehouse safety compliance review | Review | 11 Oct | Tariq Iwata | |
| ASS-77326 | Annual privacy controls assessment | Approved | 27 Oct | Evan Farouk |
Record tested samples, exceptions and evidence.
Assessment tests
| Control code | Tested at | Sample size | Exception count | Evidence reference | Parent | |
|---|---|---|---|---|---|---|
| ACCESS-REV-01 | 22 Oct | 930 | 6 | TEST-2026-0184 | Annual privacy controls assessment | |
| PAY-APR-02 | 16 Oct | 680 | 16 | TEST-2026-0185 | Annual privacy controls assessment | |
| DATA-RET-03 | 25 Oct | 40 | 20 | LOG-2026-0412 | Incident response readiness check | |
| SAFE-INS-04 | 30 Oct | 820 | 26 | LOG-2026-0413 | Annual privacy controls assessment | |
| PRIV-NOT-05 | 25 Oct | 460 | 16 | DOC-2026-0221 | Warehouse safety compliance review |
Assign a correction and check the result independently.
Approval conditions
| Finding | Status | Due at | Completed at | Evidence | Owner | |
|---|---|---|---|---|---|---|
| Privacy notices use an older version | Submitted | 12 Oct | offboarding_access_review.pdf | Asha Benali | ||
| Privacy notices use an older version | Submitted | 29 Oct | payment_approval_log.xlsx | Irene Salgado | ||
| Former contractor retains system access | Submitted | 20 Oct | retention_schedule_v3.pdf | Asha Benali | ||
| Incident drill actions remain open | Submitted | 24 Oct | safety_inspection_oct.pdf | Luis Park | ||
| Privacy notices use an older version | Submitted | 01 Nov | privacy_notice_signoff.pdf | Nico Shah |
Keep decisions, attachments and operation outcomes traceable.
Operation receipts
| Operation key | Action | Result state | Occurred at | Failure reason | Parent | |
|---|---|---|---|---|---|---|
| test-access-2026q4 | Open finding | Failed | 29 Oct | Evidence file could not be opened | Customer record access audit | |
| approve-payment-2026q4 | Assign remediation | Needs review | 14 Oct | Control owner has not signed off | Third-party risk review | |
| check-retention-2026q4 | Verify evidence | Failed | 14 Oct | Test sample is incomplete | Annual privacy controls assessment | |
| inspect-safety-2026q4 | Approve assessment | Needs review | 14 Oct | Remediation due date has passed | Incident response readiness check | |
| review-privacy-2026q4 | Close corrective action | Failed | 01 Nov | Policy version needs approval | Third-party risk review |
Assessment to verified correction ships ready to use. One step needs a named approval before the work moves on: Approve obligation (Independent Reviewer).
Set the period, scope and owner before testing begins.
Record the sample, exceptions and evidence for the safeguard checked.
Turn failed tests into described issues with severity and ownership.
A reviewer records a reasoned decision on the submitted revision.
An owner submits the correction and its evidence.
A separate reviewer tests the result before closure.
Open any assessment to see its assessment tests, the roles that work on it, its process stages and its approvals on one page.
Period start, Period end and Owner.
Each line is linked to this assessment.
Admin, Compliance Lead and Control Owner, each with their own permissions.
Plan assessment and Test control, with the role that acts.
Approve obligation, with who decides.
Planned
| Control code | Tested at | Sample size |
|---|---|---|
| ACCESS-REV-01 | 22 Oct | 930 |
| PAY-APR-02 | 16 Oct | 680 |
| DATA-RET-03 | 25 Oct | 40 |
Signed in as Independent Reviewer
| Decision | Approver | |
|---|---|---|
| Approve obligationA reviewer records a reasoned decision on the submitted revision. | Independent Reviewer |
Everyone opens Compliance Management to the work that is theirs. Pick a role to see what it starts with.
Sets organization access and maintains the people and business units used to scope work.
Owns assessment scope, obligation review routing and the operating record for the compliance program.
This is the first screen this role sees.
Assessments · Compliance Lead
| Record number | Subject | Period start | Period end | Status | |
|---|---|---|---|---|---|
| ASS-56165 | 2026 vendor access review | 23 Oct | 25 Oct | Planned | |
| ASS-73096 | Quarterly payment control testing | 15 Oct | 22 Oct | Testing | |
| ASS-92607 | Data retention policy assessment | 03 Nov | 10 Nov | Review | |
| ASS-50901 | Warehouse safety compliance review | 04 Nov | 07 Nov | Planned | |
| ASS-78679 | Annual privacy controls assessment | 25 Oct | 27 Oct | Testing |
Maintains a control and the risk it addresses, then responds to test exceptions.
This is the first screen this role sees.
Controls · Control Owner
| Control code | Description | Effective from | Risk | Owner | |
|---|---|---|---|---|---|
| ACCESS-REV-01 | Former contractor account stayed active | 31 Oct | Single-person payment approval | Clara Mensah | |
| PAY-APR-02 | Require two approvals for payments | 23 Oct | Unreported warehouse safety hazards | Asha Benali | |
| DATA-RET-03 | Archive owner is missing from schedule | 14 Oct | Outdated customer privacy notice | Luis Park | |
| SAFE-INS-04 | Inspect warehouse exits each week | 14 Oct | Unvetted third-party data access | Hana Okonkwo | |
| PRIV-NOT-05 | Privacy notice uses an older version | 27 Oct | Outdated customer privacy notice | Evan Farouk |
Records control tests and identifies findings for assessment review.
This is the first screen this role sees.
Assessments · Tester
| Record number | Subject | Period start | Period end | Status | |
|---|---|---|---|---|---|
| ASS-56165 | 2026 vendor access review | 23 Oct | 25 Oct | Planned | |
| ASS-73096 | Quarterly payment control testing | 15 Oct | 22 Oct | Testing | |
| ASS-92607 | Data retention policy assessment | 03 Nov | 10 Nov | Review | |
| ASS-50901 | Warehouse safety compliance review | 04 Nov | 07 Nov | Planned | |
| ASS-78679 | Annual privacy controls assessment | 25 Oct | 27 Oct | Testing |
Plans and completes corrective work assigned to a finding.
This is the first screen this role sees.
Findings · Remediation Owner
Decides submitted obligation reviews and records independent follow-up tests.
This is the first screen this role sees.
Corrective actions · Independent Reviewer
| Finding | Status | Due at | Completed at | Evidence | Owner | |
|---|---|---|---|---|---|---|
| Privacy notices use an older version | Submitted | 12 Oct | offboarding_access_review.pdf | Asha Benali | ||
| Privacy notices use an older version | Submitted | 29 Oct | payment_approval_log.xlsx | Irene Salgado | ||
| Former contractor retains system access | Submitted | 20 Oct | retention_schedule_v3.pdf | Asha Benali | ||
| Incident drill actions remain open | Submitted | 24 Oct | safety_inspection_oct.pdf | Luis Park | ||
| Privacy notices use an older version | Submitted | 01 Nov | privacy_notice_signoff.pdf | Nico Shah |
Read progress, exceptions and review outcomes from operating records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 42 | ||
| Planned | 22 | 52% | |
| Testing | 13 | 59% | |
| Review | 9 | 69% |
Sample counts per stage
Group assessments by Status and Owner for the selected period.
Compare assessment tests Result and exception count beneath each Control.
Count Findings by Severity and Status for an assessment.
List corrective actions by due at, Owner and Status.
Show Retests Result and tested at beneath each Finding.
Group regulatory obligations by Status, Jurisdiction and decision at.
Compare Risks Likelihood and Impact beneath each business unit.
List operation receipts with Failed or needs review result state and their failure reason.
See how Compliance Management fits your kind of team.
Each stage of assessment to verified correction names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare compliance records and review the next decision.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 15 tablesStart with one team and one process, then add the rest once the basics are running.
Create the organization, business unit and linked people who will own the first review.
Choose a real risk, record its rating scale and assign an active safeguard to a Control Owner.
State the period, scope and planned tests; identify the Tester and Independent Reviewer.
Record a test with evidence, create a finding for an exception and assign corrective work.
Submit an obligation for a reasoned decision and have a different person retest the correction.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Compliance Management for your business. Begin with one organization, one business unit, a scoped assessment and a control whose owner can supply test evidence.
Record the subject, owner, business unit, period, scope statement and planned tests. Link tests, obligations, findings and supporting attachments to that assessment.
A risk belongs to a business unit and has a named owner, likelihood, impact and scale version. A control links to that risk and has its own owner, description and effective date.
The Tester records a control test with sample size, exception count, result and evidence reference. A finding then describes the issue and links to the affected assessment and control.
The Independent Reviewer examines the submitted obligation and records a decision, reason and source revision. The Compliance Lead handles a returned or rejected item.
An Independent Reviewer records a separate retest result and evidence against the finding. The team can then verify a passing correction or continue work after a failed or inconclusive result.
Record attachments belong to assessments and carry a visibility choice. Test and corrective action records can also hold evidence references that the team agrees how to resolve.
Operations Overview shows tests performed, failed tests, pending review decisions and failed operations for the authorized scope. Working lists show submitted obligations, findings and corrective actions.
Yes, review likelihood and impact with the scale version used for each risk. Agree on how to interpret different versions before comparing ratings.
Open its receipt, review the action, expected revision, failure reason and effect references, and compare those with the assessment records before treating the work as complete.
Start free, then use Proto to change fields, steps and approvals before your team goes live.