Overview
GRC Platform
Governance, risk and compliance modules built on one record engine. Design documents are in docs/design.
01 — Modules
Modules
Foundation
The records every other module points to: the people who own things, how the business is organised, and what it runs.
Phase 1PlannedGovernance
Policies, standards and procedures in one library, broken into linkable statements, with a change workflow per document type, comment periods, revision history and an annual review.
Phase 1Design draftedControls
One shared control library at the centre of the platform: requirements map to it, statements require it, it mitigates risks, and assessments test it.
Phase 1Design draftedRisk
The risk register, assessment, appetite and treatment, including exceptions requested against statements and controls.
Phase 2PlannedFindings & Issues
Findings are evidence from a source at a point in time; issues are the problems someone owns and fixes, each with one or more remediation plans.
Phase 2PlannedCompliance
Laws, regulations, frameworks and contractual standards normalised into one requirement tree and mapped to the control library.
Phase 3PlannedAssessments
One assessment engine with two ways in: questionnaires (privacy, vendor, facility) and imports (pen tests, scans), both producing findings.
Phase 3PlannedAdministration
Users, roles per module, record scope, custom fields and lookups, approval matrices, integrations, and the interaction conventions every module follows.
Phase 1Design drafted02 — Principles
How it fits together
One record engine
Every module shares ownership, lifecycle, versioning, history, permissions and links, so records behave the same everywhere.
Controls at the centre
Requirements map to controls, statements require them, they mitigate risks, and assessments test them.
Anything links to anything
One relationship graph across modules, which reports and dashboards walk.
Nothing is deleted
Records are archived or retired, with full history kept.