These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Policy Management System
- Who it's for
- Multi-entity governance
Multi-entity governance
A governance office may support more than one legal entity while each entity has its own operating units and team members. Start by recording the organization, time zone and currency, then place business units under the right organization. The assessment and policy acknowledgment records both identify an organization, allowing the team to discuss the correct scope and audience for each cycle.
How Policy Management System is set up for you
Entity scope
Give each organization a stable name and code before assigning units and members.
Local ownership
Name the team member responsible for each unit's risk and assessment work.
Version decisions
Keep the policy version and audience on the acknowledgment record for that organization.
Evidence access
Agree when an attachment is internal or shared and which reviewers may read it.
A governance office may support more than one legal entity while each entity has its own operating units and team members. Start by recording the organization, time zone and currency, then place business units under the right organization. The assessment and policy acknowledgment records both identify an organization, allowing the team to discuss the correct scope and audience for each cycle.
Choose one organization and one active business unit. Create its team members and risk owners, then run a short assessment on an active control. Record a policy version for a defined audience, submit it for independent review and capture the decision date. The team can check whether the organization and business unit links remain consistent from risk through test, finding and acknowledgment.
Before extending to another entity, agree how identities and reviewers are assigned across organizations. An App Administrator maintains membership; the Control Owner prepares the working records. The Independent Assurance Reviewer acts on the submitted revision and an Auditor reads the authorized result. These responsibilities should be exercised in the pilot, including a returned review and a restricted attachment.
Features to start with
Roles on the team
- Control Owner
- Prepare assigned operational records and execute eligible reviewed actions.
- Independent Assurance Reviewer
- Review eligible revisions independently and reconcile operational evidence.
- App Administrator
- Maintain organization configuration and membership.
- Auditor
- Read authorized evidence and reports.
- Assigned Tester
- Records assigned control test results, sample details and evidence for assessment review.
Set up Policy Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.