grc
GRC software: what a governance, risk and compliance suite does and how to scope the purchase
Written by Tomas Arkwright Governance, risk and compliance software is the system an organisation uses to keep one shared record of what could go wrong, which controls stop it, which rules apply, and whether the controls actually worked when someone tested them. GRC compliance software is not one feature; it is a database of risks, controls, policies, obligations, audits and third parties, linked so that a failed control shows up against every risk and regulation it was meant to cover. That linking is the whole point. A company can keep a risk register in a spreadsheet, policies on an intranet and audit findings in Word files. What it cannot do with those is answer "which of our top ten risks depend on a control that failed testing last quarter, and which regulator cares?" A GRC suite exists to answer that question in minutes. ## The six modules inside most suites Vendors package differently, but the same building blocks appear across the market. The names below are from vendor sites as they stand today. | Module | What it holds | Who uses it daily | Signal you need it | |---|---|---|---| | Enterprise and operational risk | Risk register, likelihood and impact scoring, risk owners, key risk indicators | Risk team, business unit heads | Board or regulator asks for a risk appetite framework | | Controls and compliance | Controls library mapped to laws, standards and internal policies; test results | Compliance, second line | Same control tested several times for different frameworks | | Policy management | Policy versions, approvals, attestations, exceptions | Compliance, HR | Auditors ask who read which policy version | | Audit management | Audit plans, workpapers, findings, remediation tracking | Internal audit | Findings tracked in email and lost between cycles | | Third-party risk | Vendor inventory, due diligence questionnaires, risk tiering, monitoring | Procurement, security, risk | Regulator or customer asks how you oversee suppliers | | Regulatory change | Feed of new rules, impact assessment, mapping to obligations and controls | Compliance | Rule changes reach the business late or inconsistently | Some suites add resilience and business continuity, IT and cyber risk, ESG reporting and, more recently, AI governance. Archer lists enterprise and operational risk, regulatory and corporate compliance, policy governance, audit management, third-party governance and a regulatory change centre. MetricStream groups its products into risk, compliance, audit, cyber, third party and resilience. ## Who sells governance, risk and compliance tools today A buyer usually meets four kinds of vendor. None is best for everyone; each was built around a different first customer. - Long-standing enterprise GRC specialists. Archer and MetricStream are examples. Deep configurability, large module catalogues, strong in banking, insurance and other heavily supervised sectors. Expect a partner-led implementation.
- Platform vendors with a risk product. ServiceNow sells Integrated Risk Management on the same platform as its IT service management; its documentation still carries the GRC name in places, as its release notes show. The appeal is shared data with IT incidents, assets and change records if you already run ServiceNow.
- Audit-first platforms. AuditBoard, which now trades as Optro (formerly AuditBoard), grew from internal audit and SOX work and lists audit, risk, compliance and third-party risk products. These tend to suit organisations where internal audit is the sponsor.
- Privacy and trust vendors that widened into GRC. OneTrust offers tech risk and compliance and third-party management alongside its privacy and consent products. Security compliance tools such as Drata have also added GRC and vendor risk modules. Pricing across all four groups is mostly quote-based. Do not compare list prices you found on a forum; compare a written three-year quote for the same scope. ## Scoping a first GRC purchase without buying the whole catalogue The common failure is buying six modules, configuring two, and using one. A better sequence: 1. Name the pressure. Write down who is asking: a regulator inspection, an external auditor, the audit committee, a large customer's due diligence team. Their question defines module one.
- Inventory what exists. Count your current risks, controls, policies and third parties, and where each lives. A suite is only as good as the data you load; a register of 900 vendors with no owner field will be a register of 900 vendors with no owner field in the new tool too.
- Fix the taxonomy before configuration. Agree risk categories, control naming, rating scales and entity structure on paper. Changing these after go-live is expensive in every product.
- Pick one module and one business unit. Prove it for a quarter. Measure findings closed on time, controls tested, or third parties tiered.
- Then expand. Add the module whose data the first one already needs, usually controls after risk, or third-party risk after procurement onboarding. | Organisation | Likely first module | Common second module | Usually not needed early | |---|---|---|---| | Regulated bank or NBFC | Operational risk or third-party risk | Regulatory change | ESG | | Listed manufacturer | Internal controls and audit management | Enterprise risk | AI governance | | SaaS company selling to enterprises | Security controls and vendor risk | Policy management | Full regulatory change feed | | Insurer | Risk and controls | Third-party risk | Resilience until regulator asks | | Mid-size services firm | Policy and attestation | Third-party risk | Most of the suite | ## Where contracts feed the GRC record Third-party risk is where GRC and legal meet, and the contract is the evidence. A due diligence questionnaire records what a supplier says. The contract records what the supplier must do. Auditors and supervisors increasingly ask for the second. The clearest example is the EU Digital Operational Resilience Act. Article 30 of DORA sets out key contractual provisions that financial entities must have in their ICT service contracts: a description of services and subcontracting conditions, the locations where data is processed and stored, service level descriptions, assistance during ICT incidents, termination rights and notice periods, and, for critical or important functions, rights of access, inspection and audit plus an exit strategy with a transition period. A GRC third-party record that says "compliant" without checking those clauses in the signed contract is an unsupported assertion. The same pattern appears in India. The RBI's Outsourcing of Information Technology Services Directions, in force for new agreements from 1 October 2023, require the outsourcing agreement to set out audit, monitoring and inspection rights for both the regulated entity and the RBI, as this Khaitan & Co note summarises. Outside regulated finance, large customers write similar clauses into supplier contracts because their own auditors ask for them. The contract terms that usually feed the GRC record: - Audit and inspection rights, including scope, notice and frequency. Our explainer on the audit rights clause covers how these are drafted in India.
- Data location and transfer terms, which map to privacy and resilience controls.
- Incident and breach notice periods, which must match your own regulatory clocks.
- Subcontracting and change-of-provider notice, which affect fourth-party risk.
- Termination, exit assistance and data return, which map to resilience and exit planning.
- Obligations you owe the counterparty, such as reports, certifications to maintain or insurance to hold, which belong in an obligations list as much as in the risk record. Our guide to contract compliance tracking covers keeping those current. ## Running the contract step in practice The work splits cleanly. Procurement or risk owns the third-party record in the GRC tool: tier, questionnaire, monitoring, issues. Legal or a contracts team reviews the agreement and answers a short list of yes or no questions for each tier: audit right present and adequate, data location stated, notice periods within your own obligations, exit plan agreed. That answer set is what gets recorded against the vendor in GRC. When the contract renews or is amended, the review repeats. A worked example. An NBFC tiers a cloud hosting provider as critical. The GRC record needs five answers from the contract: is there an audit and inspection right covering the provider and its subcontractors; are data locations named; is the incident notice period shorter than the NBFC's own reporting window; does the NBFC have a termination right with a workable notice period; and is there exit assistance with data return in a usable format. Legal reads the master agreement and the latest amendment, finds the audit right but no subcontractor coverage and no exit assistance clause, and records two gaps. Those gaps become two remediation items in the GRC tool, each with an owner and a date tied to the renewal negotiation. That is the hand-off working as intended: contract review produces findings, and GRC tracks them to closure, which is what governance, risk and compliance tools are good at. For a portfolio of a few hundred supplier contracts this is a defined project, not a permanent burden, provided the questions are fixed in advance and the results are stored against each vendor. Our page on vendor contract management software covers running that portfolio day to day. ## Adira is not a GRC tool Adira does not hold a risk register, a controls library, audit workpapers or a third-party questionnaire workflow, and it does not provide a regulatory change feed. If you need any of those, buy a GRC suite. What Adira does cover is the contract review step that feeds one. Its Document Intelligence Dashboard opens a supplier agreement and marks each position as favourable, neutral or unfavourable to your company, lists red flags, key dates, obligations and missing clauses (an absent audit right or exit clause shows up there), and flags compliance items. Clause-Level Editing lets your team propose the missing language in plain English and see the diff. The results are exported to PDF or Word for whoever owns the GRC record; Adira claims no connection to any GRC product. More at adiralaw.com. ## Three implementation mistakes that sink GRC projects Copying the old spreadsheet in. If the existing risk register has 400 vaguely worded risks, loading all 400 into a new suite gives you an expensive version of the same problem. Rationalise first. Many teams find that a few dozen well-defined risks, each with a named owner and linked controls, are more useful than hundreds of loosely described ones. Letting the implementation partner design the taxonomy. Partners are skilled at configuration, but they do not know your business. Risk categories, rating scales and control naming should be written by the people who will be asked about them by the board and the regulator. Hand the partner a finished taxonomy and ask them to build it. No owner for third-party records. Third-party risk modules fail most often because nobody is told they own a vendor after onboarding. The questionnaire gets answered once and the record goes stale. Assign each vendor to a business owner, set a review cycle by tier, and tie the cycle to contract renewal dates so that the contract review and the risk review happen together. ## Questions to put to every GRC vendor - Show our three hardest risks and their controls configured in your product, not a demo tenant.
- How is the data model changed after go-live, and who does it: us, you, or a partner?
- What does a third-party record hold, and can it store the outcome of a contract clause review?
- How does regulatory change content reach our controls, and who writes that content?
- What is the three-year cost including implementation, partner fees and additional entities?
- How do we export everything if we leave?
Frequently asked questions
- What is the difference between GRC and integrated risk management?
- Mostly naming. ServiceNow, for example, now sells its suite as Integrated Risk Management, while the older GRC label still appears in its documentation. Both terms describe one platform holding risks, controls, policies, audits and third parties against a shared data model. Compare the modules, not the label.
- Do small companies need GRC compliance software?
- Rarely as a first purchase. A company without an internal audit function or a regulator asking for a risk framework will usually get more from a statutory compliance register or a security framework tool. GRC suites start paying back when several teams (risk, audit, compliance, security, procurement) need to work from one controls library.
- Which GRC module should we implement first?
- Whichever one a regulator, auditor or board is already asking about. For banks and insurers that is often operational risk or third-party risk; for listed companies it is often internal controls over financial reporting and audit management. Starting where pressure already exists gets you real data and sponsorship.
- Can a GRC tool read our vendor contracts?
- Some suites now advertise AI that extracts obligations from regulatory text, and third-party modules store contract records and due diligence. In practice most programmes still review the contract itself in a legal or contract tool and record the outcome (audit right present, exit plan agreed, data location stated) in the GRC third-party record.
- How are GRC suites priced?
- Mostly by quotation, based on modules, users and sometimes the number of entities or third parties covered. Ask for a three-year price including implementation partner fees, which are often a large share of year-one cost for configurable suites.
Sources
- Khaitan & Co: RBI Master Direction on outsourcing of IT services
- Archer: GRC use cases (risk, compliance, audit, third-party, regulatory change)
- MetricStream: GRC products by area
- Optro (formerly AuditBoard)
- OneTrust: tech risk and compliance, third-party management
- Regulation (EU) 2022/2554 (DORA), EUR-Lex
- ServiceNow GRC common feature release notes
See how Adira drafts in your voice and reads contracts from your side.
Explore the showroomWorking through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.
Try Weave — free