VaultGRC
Domain vault

Governance, risk and compliance, run as one system.

What GRC means, how to structure and run the programme, and which model fits a 25 to 250-person firm. Start here, then go deeper in Risk Management, Compliance and GRC Engineering.

11guides
3stages
Start the journey →Book a call
Where are you?Pick a stage
GRC Fundamentals9 guides→Building the Programme1 guide→GRC at Maturity1 guide→
GRC vaultUpdated October 2026
The status quo

Governance, risk and compliance kept in three spreadsheets give you three answers to the same question.

GRC is how a firm sets direction and accountability (governance), decides which threats it will carry (risk) and proves it meets its obligations (compliance). Run together, each feeds the others. Risk decides what the controls must do, compliance proves they do it, and governance makes someone accountable for both.

For a firm of 25 to 250 people, GRC rarely starts as a department. It starts with one person, a customer questionnaire and a certification deadline. The real question is how to build from there without ending up with three programmes.

Integration isn't a tool. It's one set of owners, one risk method and one evidence base.

This hub covers the programme as a whole. For depth, go to Risk Management, Compliance and GRC Engineering.

What we hear
"GRC is for big companies."The questions aren't. Enterprise customers and regulators ask a 50-person supplier much the same questions they ask a large one. The programme scales down; the questions don't.
"We'll buy a GRC tool."A tool records the programme. It doesn't decide who owns what, how risk is scored or which framework comes first.
"Governance is just policies."Policies are the output. Governance is who decides, who is accountable, and how leadership knows the programme is working.
The Journey

Your path through GRC, level by level.

Every guide in this vault maps to a level. Start where you are.

01

GRC Fundamentals

What GRC is, who owns it, and how the three disciplines fit together.

9 guidesGRC framework: how to structure one in a regulated firm
02

Building the Programme

Build the programme in your first 90 days, on a model and budget that fit your firm.

1 guideGRC implementation: how to build a GRC programme in your first 90 days
03

GRC at Maturity

Measure maturity and run GRC as one integrated, improving system.

1 guideGRC maturity model: the five levels and the evidence that proves each one
Ownership and practice

GRC in practice.

Who owns GRC

Leadership owns GRC. Someone still has to run it: in firms your size, usually a head of compliance, a security lead or an outsourced model.

Clear roles and responsibilities matter more than headcount. Every policy, risk and control needs a named owner in the team that does the work.

The board sets direction and risk appetite, and gets a regular, honest view of how the programme is doing.

Core practices

  • Structure the programme with a GRC framework, and know where policy, procedure and standard each sit.
  • Choose the operating model and budget that fit your size.
  • Know what your market expects, whether you're a B2B tech supplier or in financial services.
  • Build the programme in your first 90 days, then measure it against a maturity model.
  • Decide whether you also need integrated risk management.
  • Go deeper in Risk Management, Compliance and GRC Engineering.

Start with owners. Tools and frameworks come after.

FAQ

GRC, answered.

Short answers to the questions we hear most from firms setting up their first GRC programme.

Governance, risk and compliance. Governance is how a firm sets direction and accountability. Risk management is how it decides which threats to treat and which to accept. Compliance is how it meets and proves its obligations. GRC treats the three as one programme.

If you hold customer contracts with security clauses, a certification or regulated customers, you already have GRC obligations. A programme is how you meet them deliberately rather than one questionnaire at a time.

Integrated risk management puts risk at the centre and links it to strategy and performance. GRC covers governance, risk and compliance together. For most firms your size, a well-run GRC programme covers most of what IRM offers: see GRC vs IRM.

A working foundation of named owners, a risk method, core policies and an obligations register can be in place in about 90 days. Maturity takes longer, and it comes from running the programme, not from documenting it.

It depends on your size, your budget and how specialist your obligations are. A common pattern is a part-time internal owner backed by outside expertise: compare the operating models.

Domain Index

All 11 articles in this vault.

Every guide in one place. Filter by level.

Stage
Fundamentalsguides
GRC framework: how to structure one in a regulated firm
Fundamentalsguides
What GRC costs: a cost model for a 25 to 250-person UK firm
Fundamentalsguides
SaaS compliance for B2B tech firms selling into regulated industries: what your customers' regulators push down to you
Fundamentalsguides
GRC, financial services and the UK rulebook: what the FCA, PRA and DORA expect of a smaller regulated firm
Fundamentalsguides
In-house, consultant or compliance as a service: which GRC model fits a 25 to 250-person tech firm
Fundamentalsguides
GRC roles and responsibilities: who owns what in a lean GRC team
Fundamentalsguides
GRC career path: roles, skills and certifications from analyst to head of GRC
Fundamentalsguides
GRC vs IRM: what integrated risk management adds, and whether a smaller regulated firm needs it
Advancedguides
GRC maturity model: the five levels and the evidence that proves each one
Intermediateguides
GRC implementation: how to build a GRC programme in your first 90 days
Fundamentalsguides
Policy vs procedure: the difference between policy and procedure, and where standards fit
Showing 11 of 11 articles
GRC Programme Accelerator

Ready to run GRC as one system, not three spreadsheets?

Work with a Trust Architect to design a GRC programme that fits a 25 to 250-person firm: scoped, owned and built to run all year rather than in a scramble before each audit.

Book a call →
GRCMANA
  • About
  • Insights
  • Contact
Ask the Trust ArchitectBook a Call →
  • About
  • Insights
  • The Vault
    Compliance VaultCyber Essentials→ISO 27001→SOC 2→ISO 42001→
    Domain VaultGRC Fundamentals→Risk Management→AI Governance→GRC Engineering→
    Other ResourcesFree Tools→Templates→Newsletter→
  • Contact
Book a Call →Ask the Trust ArchitectFixed fee. ISO 27001 in as few as six weeks.
GRCMANA

Helping high-growth B2B tech startups close the Enterprise Trust Gap through security, governance, and AI resilience.

ISO 27001ISO 42001ISO 9001Cyber EssentialsEU AI Act ReadyNIST AI RMF

The Vault

GRC EngineeringAI GovernanceISO 27001ISO 42001All Vault Resources

Resources

BlogFree ToolsTemplatesNewsletter

Company

About GRCMANAContactPrivacy PolicyTerms & ConditionsCookie Policy
© 2025 GRCMANA · All rights reservedRegistered in England & Wales under company registration 16810805. VAT Registration 506308024