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.
- Construction GRC
- Features
- Assessments and scope
Assessments and scope
Define the assessment period, responsible owner and controls to test.
OverviewMy assessments×
Construction GRC · Assessments and scope
New
My assessments
Assessments
| Record number | Subject | Status | Period start | Period end | Owner | |
|---|---|---|---|---|---|---|
| ASS-99641 | Draft ass-746 | Draft | 17 Oct | 24 Oct | ||
| ASS-65409 | Planned ass-330 | Planned | 26 Oct | 30 Oct | ||
| ASS-35408 | Testing ass-731 | Testing | 27 Oct | 05 Nov | ||
| ASS-46874 | Review ass-451 | Review | 16 Oct | 25 Oct | ||
| ASS-52410 | Approved ass-484 | Approved | 24 Oct | 01 Nov |
6 of 6 records
Draft ass-746Assessments · ASS-99641
DraftPeriod start17 Oct
Period end24 Oct
What you can do
Make the assessment boundary explicit
An Assessment Owner starts with a subject, operating organization, business-unit counterparty and period. The scope statement tells testers which work is in the engagement. A planned test count makes the intended coverage visible before results arrive. A construction project may have several packages underway at once; a named assessment helps the team avoid treating a test from one period or business unit as evidence for another.
The scoping workflow checks that the organization is the authenticated one, that the owner belongs to it and that the revision still matches the caller’s expectation. It then creates or advances the assessment and creates test lines for planned controls in sequence. A repeated operation key resolves to the same work, so an interrupted request should not quietly add a second set of test lines.
How the work is organized
- Boundary. Agree the period and scope statement that distinguish this assessment from a later review of the same site.
- Ownership. Identify the person responsible for the assessment and the business unit whose activity is being assessed.
- Coverage. Agree which controls are planned and how to reconcile the planned count to the created test lines.
What to agree during setup
The Assessment Owner and Compliance Manager should rehearse how this work is assigned and reviewed. Agree which organization and business unit own the first case, who may update it, and where its supporting evidence lives. Set a clear handoff when the person preparing the record is different from the person checking its outcome. Use the same rule for routine work and exceptions so an urgent item does not lose its owner or history.
For the pilot, use an assessment with a defined subject and period, then ask the owner to explain why each control belongs in scope. Check the business unit against the risk register and the planned test count against the created lines. A stale revision should leave the newer scope intact.
Check the handoff on an actual case
Try a single assessment for a defined inspection period. Set its organization, owner and business unit, then select controls tied to the relevant risks. Check that each test line points back to the assessment and the intended control, and that its line number reflects the plan. Repeat the same scoping request to confirm the result is not duplicated. Change the expected revision in a stale request and confirm that the newer assessment is protected.
Open My assessments as the owner and compare the subject, period and business unit with the planned test lines. If a scoping request times out, inspect the assessment and operation receipt before retrying with the same key. The line numbers should still describe one plan.
What your team sees
- My assessments — The owner’s assessments with period and current state.
- Assessment period schedule — Assessments placed against their period start and end dates.
Follow the work through
See the related process for the stage-by-stage handoff. Use the data model to inspect the record relationships and implementation to plan the first rehearsal.
What it keeps track of
Data model- Assessments
- Scoped assessment engagements driven through a status lifecycle.
- Assessment tests
- Individual control tests executed under an assessment.
- Business units
- Operating units and counterparties that assessments and risks attach to.
- Organizations
- Legal and operating organizations governed by this workspace.
- Team members
- Named people who own, prepare and independently review work.
Who uses it
Permissions- Assessment Owner
- , Compliance Manager, Admin.
Set up Construction GRC your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.