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
- Data model
The tables behind Construction GRC
Construction GRC ships with 22 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 22
- Features
- 7, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Organization and ownership
Organizations, business units, team members and Users identify the operating context and people responsible for work.
Assessment and testing
Assessments scope a period and own assessment tests; Controls connect each test to a Risk and a control owner.
Site checks
Site compliance checks records the inspected site, permit reference and open safety issues under an organization and assessment.
Correction and review
Findings point to Assessments and Controls; corrective actions and Retests point to Findings.
Evidence and provenance
Record attachments belongs to Assessments; Documents has document versions, execution history and follow-up records. Operation receipts retains guarded assessment operation results.
Every table, by feature
- Site compliance checks3
- Assessments and scope5
- Risks and controls5
- Control testing4
- Findings and corrective actions5
- Independent retests4
- Evidence and documents6
- Shared and settings5
- Site compliance checks
Site-level compliance checks covering permits and open safety issues.
Linked to Assessments, Organizations - Assessments
Scoped assessment engagements driven through a status lifecycle.
Linked to Organizations, Team members, Business units - Organizations
Legal and operating organizations governed by this workspace.
- Assessments
Scoped assessment engagements driven through a status lifecycle.
Linked to Organizations, Team members, Business units - Assessment tests
Individual control tests executed under an assessment.
Linked to Assessments, Controls - Business units
Operating units and counterparties that assessments and risks attach to.
Linked to Organizations - Organizations
Legal and operating organizations governed by this workspace.
- Team members
Named people who own, prepare and independently review work.
Linked to Organizations, Users
- Risks
Risks held against a business unit on an explicit likelihood and impact scale.
Linked to Business units, Team members - Controls
Controls that mitigate a risk and are executed by a named owner.
Linked to Risks, Team members - Business units
Operating units and counterparties that assessments and risks attach to.
Linked to Organizations - Team members
Named people who own, prepare and independently review work.
Linked to Organizations, Users - Assessment tests
Individual control tests executed under an assessment.
Linked to Assessments, Controls
- Assessment tests
Individual control tests executed under an assessment.
Linked to Assessments, Controls - Assessments
Scoped assessment engagements driven through a status lifecycle.
Linked to Organizations, Team members, Business units - Controls
Controls that mitigate a risk and are executed by a named owner.
Linked to Risks, Team members - Findings
Findings raised from failed or inconclusive control testing.
Linked to Assessments, Controls
- Findings
Findings raised from failed or inconclusive control testing.
Linked to Assessments, Controls - Corrective actions
Remediation actions assigned to a finding owner with due dates and evidence.
Linked to Findings, Team members - Assessment tests
Individual control tests executed under an assessment.
Linked to Assessments, Controls - Assessments
Scoped assessment engagements driven through a status lifecycle.
Linked to Organizations, Team members, Business units - Controls
Controls that mitigate a risk and are executed by a named owner.
Linked to Risks, Team members
- Retests
Independent retests that decide whether a finding may be closed.
Linked to Findings, Team members - Findings
Findings raised from failed or inconclusive control testing.
Linked to Assessments, Controls - Corrective actions
Remediation actions assigned to a finding owner with due dates and evidence.
Linked to Findings, Team members - Team members
Named people who own, prepare and independently review work.
Linked to Organizations, Users
- Record attachments
Evidence files attached to an assessment with a visibility scope.
Linked to Assessments, Team members - Documents
Controlled documents with status, classification and retention.
- Document versions
Immutable versions recorded against a parent document.
Linked to Documents - Execution attempts
Attempt-level execution records for document operations.
Linked to Documents - Operation runs
Durable operation runs for upload, approval and correction workflows.
Linked to Documents - Operation steps
Numbered step trace retained for each operation run.
Linked to Operation runs
Keys and references
Keep organization identifiers stable before loading business units and team members. Preserve each assessment record number and revision when migrating work already in progress. Carry control codes into planned tests, and check every finding’s assessment and control references. A corrective action must point to the finding it addresses; a retest must point to that same finding and name its reviewer. Document versions stay under their parent document. Evidence attachments keep their uploader and visibility choice.
Migration order
- Load Organizations, Users, team members and business units with verified organization links.
- Load Risks and Controls with their owners, status and effective dates.
- Load Assessments and site compliance checks for the agreed periods and locations.
- Load assessment tests, then Findings, corrective actions and Retests in that order.
- Load record attachments and Documents with document versions and relevant execution records.
- Reconcile references, status values, revisions and access before opening the first operating cycle.
Set up Construction GRC your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.