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
- Features
- Assessments
Assessments
Set assessment scope, period and ownership before testing starts.
OverviewReview queue×
Policy Management System · Assessments
New
Review queue
Assessments
| Record number | Subject | Revision | Status | Owner | |
|---|---|---|---|---|---|
| ASS-46664 | Review ass-511 | 600 | Review | ||
| ASS-40136 | Review ass-396 | 160 | Review | ||
| ASS-56482 | Review ass-525 | 470 | Review | ||
| ASS-82402 | Review ass-808 | 510 | Review | ||
| ASS-32069 | Review ass-755 | 90 | Review |
6 of 6 records
Review ass-511Assessments · ASS-46664
ReviewRevision600
What you can do
Give each cycle a bounded scope
An assessment identifies the organization, operating unit, owner and testing period. The subject and scope statement explain what the team is examining. Planned tests establish a target before the work starts; the revision records which version the reviewer later considers. A dated cycle makes it easier to compare testing evidence with the approved scope.
The Control Owner begins with a draft, names the responsible unit and moves the work into planning. During testing, the assessment gathers test results, findings, attachments and review decisions. Its status gives the team a shared way to see whether the work is being planned, tested, reviewed, remediated or closed. A reviewer should be able to follow the links from the assessment to the individual test and its evidence.
How the work is organized
- Scope. Record the organization, unit, period and subject before committing to planned tests.
- Ownership. Assign one accountable team member so a review question has a clear destination.
- Revision. Preserve the revision used for a review decision and link later changes to a new cycle of review.
What to agree during setup
Choose the naming convention for assessment numbers and the meaning of a testing period. Decide who can move a draft into the planned state, how the planned test count is determined and when a revision is ready for independent review. Agree how approved scope changes are handled so the original accepted record remains understandable.
Use an initial cycle that has a real control owner and a small set of active controls. Set the start and end dates, the unit and the scope statement before entering test results. The schedule should make the work visible to the assigned tester and reviewer. The review queue should identify the exact assessment revision and owner.
Check the handoff on an actual case
Consider a quarterly assessment of one operating unit. The Control Owner records the period, names the unit and owner, and writes the scope. The Assigned Tester adds results for selected controls, including exceptions and evidence references. A failed result leads to a finding linked back to this assessment. The Independent Assurance Reviewer inspects the tested revision and either approves it or returns it with a reason.
If the work enters remediation, the same assessment remains the parent for actions, retests and receipts. The owner can explain what was planned, what was tested and what still needs follow-up without creating a disconnected policy history.
What your team sees
- Assessments by status — Active cycles grouped by their current working state.
- My assessments — The owner’s current assessment scope and dates.
- Assessment schedule — Planned and testing work across start and end dates.
Follow the work through
See assessment and testing and independent review.
What it keeps track of
Data model- Assessments
- Period-scoped control testing engagements.
- Assessment tests
- Individual control tests performed under an assessment.
- Business units
- Operating units that own risk and are assessed.
- Organizations
- Legal entities operating policies under this governance program.
- Team members
- Named people with governance roles inside an organization.
- Findings
- Control failures and exceptions raised by testing.
Who uses it
Permissions- Control Owner
- , Assigned Tester, Independent Assurance Reviewer, Auditor
Set up Policy Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.