Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Policy Management System
- Identity
- Policy distribution
- Evidence storage
A governance team can keep a policy version beside the assessment that prompted its review. The assessment identifies the organization, operating unit, owner, period and scope.
testing waits for the assigned tester
| Record number | Subject | Status | Period start | Period end | Owner | |
|---|---|---|---|---|---|---|
| ASS-85938 | Q1 access controls review | Planned | 04 Nov | 08 Nov | Fatima Bello | |
| ASS-55089 | Annual vendor oversight assessment | Testing | 29 Oct | 06 Nov | Ibrahim Diallo | |
| ASS-32451 | Quarterly privacy controls test | Review | 25 Oct | 30 Oct | Jonah Reed | |
| ASS-22030 | Records retention review | Planned | 26 Oct | 31 Oct | Camila Torres | |
| ASS-96235 | Payment approval controls test | Testing | 25 Oct | 02 Nov | Daniel Cho |
Independent Assurance Reviewer decides on the assessment revision.
Every feature works on the same records. Pick one to see the screen your team works in.
Review a named policy version and track its audience acknowledgment.
Approval conditions
| Policy version | Audience | Revision | Status | Decision at | |
|---|---|---|---|---|---|
| Version 1.0 | All employees | 960 | Submitted | 21 Oct | |
| Version 1.1 | Finance approvers | 290 | Submitted | 22 Oct | |
| Version 2.0 | System administrators | 330 | Submitted | 28 Oct | |
| Version 2.1 | Vendor managers | 510 | Submitted | 02 Nov | |
| Version 3.0 | People operations | 90 | Submitted | 19 Oct |
Set assessment scope, period and ownership before testing starts.
Assessments
| Record number | Subject | Revision | Status | Owner | |
|---|---|---|---|---|---|
| ASS-46664 | Q1 access controls review | 600 | Review | Sofia Alvarez | |
| ASS-40136 | Annual vendor oversight assessment | 160 | Review | Fatima Bello | |
| ASS-56482 | Quarterly privacy controls test | 470 | Review | Fatima Bello | |
| ASS-82402 | Records retention review | 510 | Review | Meera Patel | |
| ASS-32069 | Payment approval controls test | 90 | Review | Jonah Reed |
Connect unit risks to active controls and named owners.
Controls
| Control code | Description | Effective from | Risk | Owner | |
|---|---|---|---|---|---|
| AC-01 | Two reviews lacked manager signoff | 21 Oct | Missing privacy acknowledgments | Nikolai Varga | |
| AP-02 | Payment sample had no second approval | 21 Oct | Unapproved supplier payment | Linh Tran | |
| VR-03 | Vendor review expired before renewal | 17 Oct | Records kept beyond retention | Linh Tran | |
| BC-04 | Restore test evidence was not retained | 13 Oct | Late incident notification | Fatima Bello | |
| IR-05 | Escalation contact list was outdated | 30 Oct | Backup restore failure | Aisha Rahman |
Capture sampled results, exceptions and evidence under each assessment.
Assessment tests
| Control code | Sample size | Exception count | Evidence reference | Parent | |
|---|---|---|---|---|---|
| AC-01 | 480 | 31 | Q1-access-review.xlsx | Records retention review | |
| AP-02 | 750 | 36 | payment-sample-04.pdf | Payment approval controls test | |
| VR-03 | 270 | 22 | vendor-review-may.pdf | Quarterly privacy controls test | |
| BC-04 | 120 | 19 | restore-test-log.txt | Annual vendor oversight assessment | |
| IR-05 | 800 | 31 | incident-drill-notes.pdf | Third party data handling review |
Assign corrective work and keep independent retest evidence.
Corrective actions
| Finding | Status | Due at | Completed at | Owner | |
|---|---|---|---|---|---|
| Payment approval evidence incomplete | Planned | 03 Nov | Aisha Rahman | ||
| Vendor questionnaire expired | In progress | 25 Oct | Ibrahim Diallo | ||
| Vendor questionnaire expired | Submitted | 31 Oct | Fatima Bello | ||
| Departed account disabled late | Verified | 01 Nov | Meera Patel | ||
| Training exceptions lack owner | Planned | 29 Oct | Camila Torres |
Tie independent decisions, attached files and operation receipts to the case.
Operation receipts
| Operation key | Action | Expected revision | Result state | Failure reason | |
|---|---|---|---|---|---|
| approve-q1-access-r2 | Approve assessment | 290 | Needs review | Approval evidence is missing | |
| test-payment-ap-02 | Record test result | 680 | Needs review | Control owner is inactive | |
| close-vendor-finding-03 | Open finding | 300 | Needs review | Test period has closed | |
| publish-retention-v3 | Close remediation | 730 | Needs review | Policy version has changed | |
| record-backup-test-04 | Publish policy version | 650 | Needs review | Remediation proof is incomplete |
Reviewed policy and assurance cycle ships ready to use. 2 steps need a named approval before the work moves on: Review revision (Independent Assurance Reviewer) and Record policy decision (Independent Assurance Reviewer).
Set the unit, period and owner for the cycle.
Record samples, exceptions and evidence against active controls.
Carry failed results into assigned corrective work.
An independent reviewer decides on the submitted assessment revision.
An independent reviewer decides on the submitted policy version.
Compare the operation receipt with persisted effects.
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.
Control Owner and Assigned Tester, each with their own permissions.
Scope assessment and Test controls, with the role that acts.
Review revision and Record policy decision, with who decides.
Planned
| Control code | Sample size | Exception count |
|---|---|---|
| AC-01 | 480 | 31 |
| AP-02 | 750 | 36 |
| VR-03 | 270 | 22 |
The Control Owner maintains the assessment and supporting operational records in the scope they own.
Signed in as Independent Assurance Reviewer
| Decision | Approver | |
|---|---|---|
| Review revisionAn independent reviewer decides on the submitted assessment revision. | Independent Assurance Reviewer | |
| Record policy decisionAn independent reviewer decides on the submitted policy version. | Independent Assurance Reviewer |
Everyone opens Policy Management System to the work that is theirs. Pick a role to see what it starts with.
Prepare assigned operational records and execute eligible reviewed actions.
This is the first screen this role sees.
Assessments · Control Owner
| Record number | Subject | Period start | Period end | Status | |
|---|---|---|---|---|---|
| ASS-89217 | Q1 access controls review | 31 Oct | 05 Nov | Planned | |
| ASS-84688 | Annual vendor oversight assessment | 25 Oct | 28 Oct | Testing | |
| ASS-19736 | Quarterly privacy controls test | 23 Oct | 30 Oct | Planned | |
| ASS-13625 | Records retention review | 04 Nov | 12 Nov | Testing | |
| ASS-48254 | Payment approval controls test | 25 Oct | 30 Oct | Planned |
Review eligible revisions independently and reconcile operational evidence.
This is the first screen this role sees.
Policy acknowledgements · Independent Assurance Reviewer
| Policy version | Audience | Revision | Status | Decision at | |
|---|---|---|---|---|---|
| Version 1.0 | All employees | 960 | Submitted | 21 Oct | |
| Version 1.1 | Finance approvers | 290 | Submitted | 22 Oct | |
| Version 2.0 | System administrators | 330 | Submitted | 28 Oct | |
| Version 2.1 | Vendor managers | 510 | Submitted | 02 Nov | |
| Version 3.0 | People operations | 90 | Submitted | 19 Oct |
Maintain organization configuration and membership.
Read authorized evidence and reports.
This is the first screen this role sees.
Policy acknowledgements · Auditor
Records assigned control test results, sample details and evidence for assessment review.
This is the first screen this role sees.
Assessments · Assigned Tester
| Record number | Subject | Period start | Period end | Status | |
|---|---|---|---|---|---|
| ASS-89217 | Q1 access controls review | 31 Oct | 05 Nov | Planned | |
| ASS-84688 | Annual vendor oversight assessment | 25 Oct | 28 Oct | Testing | |
| ASS-19736 | Quarterly privacy controls test | 23 Oct | 30 Oct | Planned | |
| ASS-13625 | Records retention review | 04 Nov | 12 Nov | Testing | |
| ASS-48254 | Payment approval controls test | 25 Oct | 30 Oct | Planned |
Read assessment throughput, exceptions, decisions and follow-up from the records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 49 | ||
| Planned | 22 | 45% | |
| Testing | 8 | 36% | |
| Review | 4 | 50% |
Sample counts per stage
Show assessments by organization and status for each operating cycle.
Compare sample size and exception count for each control's tests.
List failed test records with their control and parent assessment for review.
Show open remediation demand by severity.
List owners, due dates and completion dates for assigned actions.
Show reviewer, date and result for each finding's retest.
Show version, audience, revision, decision date and status.
Show operations whose result needs review or failed.
See how Policy Management System fits your kind of team.
Each stage of reviewed policy and assurance cycle 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
Ask Proto to prepare policy and assessment work for a human 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 team members. Assign the Control Owner, Independent Assurance Reviewer, App Administrator and Auditor.
Name the risk scale, control codes, evidence visibility rule and policy version convention.
Set a period and scope, record passing and failing tests, and follow the failed case into a finding.
Submit an assessment revision and a policy version for independent decisions. Record reasons and dates.
Check the corrective action and retest, then compare each operation receipt with the effects it expected.
$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 Policy Management System for your business. Begin with one organization, one policy audience and a short assessment cycle.
The Control Owner prepares the version, audience and supporting assessment before an independent decision.
The Independent Assurance Reviewer records the dated decision on the submitted revision. The review reason remains with the decision.
The policy record holds the version, audience, required reader count and acknowledgment date. Agree what counts as completion for your audience during setup.
Yes. The Control Owner prepares a corrected revision and submits it for a new decision while the earlier decision stays visible.
Each test points to an assessment and control. A finding records the exception against the same assessment and control.
A corrective action records the work. An independent retest with a passing result supports closing the finding.
The Auditor reads authorized evidence and reports. The Independent Assurance Reviewer owns the decision.
An operation receipt records the action and expected revision. The reviewer compares actual effects before marking it completed.
Start free, then use Proto to change fields, steps and approvals before your team goes live.