# GRC Software for UK Mid-Market: Test the Control, Not the Statement **Category:** GRC **Author:** AI Assistant **Published:** 2026-11-15 **Read Time:** 9 min read ## Summary A control description is not evidence that a control operated. A practical assurance test links the risk, control owner, evidence sample, reviewer decision and remediation, then connects the result to the relevant entity, contract and deal records. ## Full Content GRC software for a UK mid-market organisation should do more than store a control statement and show a green status. It should connect a defined risk to a control, the person who performed it, dated evidence, an independent review, any exception and a recorded decision. Then it should carry that result into the relevant entity, contract and M&A records. A control marked “effective” without a test trail is an assertion, not assurance. ![A control test linking risk, evidence, reviewer and board decision](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1794733445591/images/f7c9819ee20a90cbd50629e22415b55bc2c7ad435b955ebd938844b64dda4a8b.jpeg) ## What the market scan covers, and what it leaves open For “GRC software for UK mid-market” and control-assurance searches, the current result set and AI-answer summaries emphasise risk registers, RCSA cycles, control testing, evidence capture, audit work and board reporting. Initia Risk presents a focused risk-management product around risk registers, RCSA, controls and reporting. Verdantix’s 2026 mid-market buyer guide frames the segment around specialist needs, broader functionality and implementation fit. Diligent’s Provision 29 guide focuses on defining material controls and preparing a board declaration. Those are useful entry points, but the operating question is more specific: can a reviewer follow one material control from its risk rationale through a real test and into a decision that changes work? The [FRC’s UK Corporate Governance Code 2024](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/uk-corporate-governance-code/) and its [supporting guidance](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/corporate-governance-code-guidance/) are primary sources for companies that fall within the Code’s scope. The Code page states its application and the timing for Provision 29. Do not turn that listed-company reporting context into a claim that every UK organisation has the same declaration duty. The platform gap is not another risk score. It is maintaining one reviewable trail across GRC, company secretarial, contracts and M&A without flattening who made each decision. ## A control statement is only a hypothesis A useful control record starts with a specific risk and the outcome the control is meant to protect. “Access reviewed” is weak if nobody can say which access, by whom, at what point, using what source and what counts as a failure. “The service owner reviews privileged access against the current employee and supplier list, records challenged entries and approves removal or documented retention” is testable. It identifies an action and an expected record. It still needs an actual test. Keep the control’s design separate from its operation. Design asks whether the stated process could address the risk if performed as intended. Operation asks whether the process was performed, by the right person, over the period being assessed, with the expected result. A policy, procedure or control owner’s confirmation may support design. It does not by itself prove that the control happened in practice. A control record should preserve the underlying evidence or a stable reference to it. Capture the period, source, owner, system or process, reviewer, test approach, result, exception, limitation and follow-up. A PDF attachment with no context is not a reliable audit trail. A green tick with no link to evidence is worse: it suggests assurance without showing its basis. ## A practical test: trace five questions Use this sequence for a sample of important controls. The method is a working discipline, not a substitute for the organisation’s chosen assurance standard or a qualified auditor’s judgement. 1. **What risk is being addressed?** State the event or failure that matters, the objective affected and why this control is relevant. If the risk has changed, review whether the control still addresses it. 2. **Who performs and owns the control?** Separate the person doing the task from the person accountable for its design and operation where the organisation’s model requires that separation. Note any outsourced or system-assisted activity. 3. **What would demonstrate performance?** Identify the expected record before testing. Define the period and population, the source system, required approvals and how exceptions are handled. Avoid deciding after the fact that any convenient document counts as evidence. 4. **What did the reviewer inspect?** Record the sample or other testing basis, the evidence version, the review date and the conclusion. If the reviewer cannot reproduce the conclusion from the record, the evidence chain is incomplete. 5. **What changed because of the result?** Record whether the control operated as expected, what failed or could not be verified, who assessed the impact, what action was authorised and how closure will be evidenced. | Test element | Weak record | Reviewable record | | --- | --- | --- | | Risk link | “Operational risk” | Named scenario, objective affected and related risk owner | | Control | “Access is reviewed” | Defined action, performer, timing, scope and exception route | | Evidence | “Policy attached” | Dated system output or work record tied to the review period | | Conclusion | Green status only | Reviewer, method, outcome, limitation and rationale | | Follow-up | “Discussed” | Owner, agreed action, due date, escalation and closure evidence | ![A control test surfaces an exception and assigns the next action](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1794733445591/images/2adbe7e31a59491b91d97759ab9e7c9f8cdd25a7e8dbf80dea3d1ff643519e37.jpeg) ## Test exceptions without hiding them A failed or incomplete test is not automatically proof of a wider failure. Nor is it harmless because the team has written “low risk” beside it. First describe the observed fact: a review was late, a record was missing, an approval could not be traced, or the control did not identify a known change. Then assess cause, period, impact, compensating controls and whether similar records may be affected. Keep fact, interpretation and decision separate. The reviewer should record what was not tested. If evidence was unavailable, say so. If a sample was selected, explain its scope. If a control was redesigned during the period, distinguish the old process from the new one and identify the date the new process became operative. This prevents a mid-year change from being represented as if one stable control operated throughout. Escalation should be based on the organisation’s authority and risk appetite, not on a software label. A risk owner may recommend treatment; an authorised decision-maker accepts or rejects it. GRC software should preserve the request, approval, rationale, duration or review trigger, and any compensating action. It should not silently convert an overdue task into an accepted risk. Remediation needs a closure test. “Training sent” is an activity. The closure record should show what changed, how the organisation confirmed the change, who reviewed it, and whether the original control gap is resolved or remains subject to monitoring. If an action cannot be completed, record the revised decision rather than rewriting the history. ## Tie control evidence to the business record A material control often sits across records owned by different teams. One legal entity may hold the contract, a separate service team may operate the control, and the company secretary may prepare a board paper about the exposure. A new acquisition may introduce a different control owner or evidence source. If each module uses a different entity name or supplier reference, reconciliation becomes manual and errors are harder to spot. Connect the records with explicit relationships. In GRC, retain the risk, control, test and remediation. In company secretarial, identify the entity and link the relevant approval or board discussion. In contracts, link the obligation or supplier term that the control supports. In M&A, record whether the target has a comparable control, whether that comparison is confirmed, and who owns the transition. “Connected” should mean navigable and permissioned, not that every user can see every document. That cross-module view is useful only if each record preserves its own meaning. A contract clause is not proof that the obligation has been performed. A board minute is not a control test. A diligence note is not proof that an acquired control has been adopted. The relationships help the reviewer find the next piece of evidence; they do not replace it. ## Choosing GRC software: demonstrate the evidence chain Do not accept a generic dashboard tour. Ask the vendor to demonstrate one control from risk identification through design, assignment, evidence capture, review, exception, action and closure. Ask the presenter to change a source document or entity while the workflow is open. Can you see what changed, who changed it, when it changed and which conclusion relied on the earlier version? Ask whether the system distinguishes management attestation from independent review. Ask how a reviewer records a limitation, whether an overdue test remains visible, and whether the organisation can export the full record with attachments and history. Ask what permissions apply to board papers, legal advice and deal materials. A control application that cannot support access boundaries may create a new exposure while solving an evidence problem. The [FRC guidance](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/corporate-governance-code-guidance/) is a relevant reference for boards reporting under the Code. Diligent’s [Provision 29 guide](https://www.diligent.com/resources/blog/uk-corporate-governance-code-provision-29) offers a vendor’s practical explanation. Use the FRC text for the rule and the vendor article as a perspective on workflow, not as a substitute for the primary source. No generic control count or vendor benchmark is required to make the buying decision. ![GRC evidence connected to entities, contracts and M&A work](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1794733445591/images/bd15988a2d563d3fa1c48757a75c0f4b756612bb633463c7c0642cc9939158c4.jpeg) ## Where Simplif-i fits Simplif-i’s [GRC workspace](https://simplif-i.com/solutions/grc) describes risk registers, frameworks, policies, evidence, internal audits, findings and remediation in one place. Its page also says evidence can be mapped across frameworks and that reviewers should check scope and supporting evidence rather than treat a mapping as proof of compliance. That is the right distinction: a platform can organise evidence and expose gaps; the organisation still assesses whether the evidence supports its conclusion. The platform connection is practical. GRC records can sit alongside [company secretarial](https://simplif-i.com/solutions/company-secretary) entity and board records, [contracts](https://simplif-i.com/solutions/contracts) obligations and [M&A](https://simplif-i.com/solutions/ma) findings. Evaluate the permissions, evidence export and review workflow against your own controls before adopting it. Simplif-i should be described as a place to connect records and follow-up, not as a certification or assurance outcome. ## Frequently asked questions ### Does a control description prove the control operated? No. It explains intended design. An operating conclusion needs evidence relevant to the period, scope, performer and required result, together with a documented review. ### What is the difference between control design and control operation? Design considers whether the process could address the identified risk if followed. Operation considers whether it was actually performed and produced the expected result. Record both judgements where they are separately assessed. ### Does Provision 29 apply to every UK organisation? Do not assume that. The FRC Code page identifies the Code’s scope and timing. Check the primary source and the organisation’s reporting status before describing a specific obligation. ### Should a failed test automatically become a high risk? No. Record the observed issue, assess its cause, impact, scope and compensating controls, then route the decision under the organisation’s authority and risk method. Do not let a template score replace judgement. ### What evidence should a GRC platform retain? Keep the source or stable reference, period, owner, reviewer, testing basis, conclusion, limitation, exception, decision and closure evidence. Preserve version and access history where relevant. ### Why link GRC with contracts, company secretarial and M&A? Because risks and controls may depend on a contract, belong to a particular entity or change after a transaction. Linking the records makes relationships and hand-offs visible while keeping review and access controls explicit. ## Sources - [Financial Reporting Council, UK Corporate Governance Code 2024](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/uk-corporate-governance-code/) - [Financial Reporting Council, Corporate Governance Code Guidance](https://www.frc.org.uk/library/standards-codes-policy/corporate-governance/corporate-governance-code-guidance/) - [Verdantix, Buyer’s Guide: Mid-Market GRC Software (2026)](https://www.verdantix.com/venture/report/buyer-s-guide--mid-market-grc-software-2026) - [Initia Risk, Risk Management Software](https://initiarisk.com/risk-management-software) - [Diligent, Provision 29: A practical guide to board declarations on internal controls](https://www.diligent.com/resources/blog/uk-corporate-governance-code-provision-29) - [Simplif-i, Governance, Risk and Compliance](https://simplif-i.com/solutions/grc) --- Source: https://simplif-i.com/api/blog/readable/grc/grc-test-control-not-statement-20261115 Web Version: https://simplif-i.com/blog/grc/grc-test-control-not-statement-20261115 © Simplif-i - Unified Business Management Platform