UK operational resilience reporting, computed from your own timestamps.
Qgentic OpRes builds the records the UK PRA and FCA operational resilience rules ask for: the important business services register, third-party dependency mappings and incident reports. Every impact tolerance breach is calculated from system timestamps, so the assessment is arithmetic.
One report, timestamps to export
Data comes in from your existing GRC tools, every tolerance breach is computed, a named person approves, and the package comes out hashed. It plays in your browser, with nothing to install.
How your data gets in: integration and data.
Who it is for
UK-only firms
UK-only entities, such as building societies, that answer to PRA and FCA rules on third-party mapping, impact tolerances and incident reporting, with no DORA overhead to carry.
PRA and FCA regulated firms
UK banks, insurers, investment firms and FMIs: important business services, tolerance tracking and disruption reporting, with every step auditable.
Groups across the UK and EU
UK OpRes and EU DORA run on one architecture, with one evidence portal across both. See the Preferred Partner models.
What it does, and what stays with you
The PRA and FCA obligations interlock across both rulebooks. Qgentic OpRes takes the data and reporting layer; the decisions stay with your own governance.
Reporting and validation
It reads your existing data and builds the service register, third-party mappings and incident reports, checks their integrity, calculates every tolerance breach from the timestamps, and produces the regulatory package for a named person to approve.
These stay with the firm:
Services and tolerances
Deciding which business services are important, and setting their impact tolerances, is the board's job. Qgentic checks the definitions for consistency and leaves the decisions where they belong.
Scenario testing
Scenario testing and the annual self-assessment stay with your team. Qgentic tracks real incidents against your tolerances; it does not simulate scenarios.
Remediation
Post-incident analysis, remediation planning and the changes that follow are internal processes. Qgentic supplies the incident data those reviews start from.
Critical Third Parties (CTPs)
The FSMA 2023 CTP rules apply to designated infrastructure providers, such as the major cloud vendors. A regulated firm filing its own resilience reports sits outside their direct scope.
The outputs become the data your internal testing and regulatory reviews work from. Qgentic prepares the reports; you submit them through the FCA's RegData or Connect, or the PRA's channels.
How a report gets made
- IntakeRaw data arrives from your existing GRC platform by REST API, automated file transfer or CSV upload, with no plugin to install.
- ComputationIncident durations and tolerance breaches are calculated from system timestamps. A manual override that contradicts them is rejected (rule OPRES-TOL-008).
- ValidationDeterministic rules check FRN formats, ISO 17442 LEI checksums, referential integrity across dependencies and the order of events.
- Risk flagsHigh-risk configurations are flagged before submission, such as a material arrangement with no exit plan (OPRES-EXIT-011) or a heavily depended-on sub-outsourcer (OPRES-SUB-012).
- Approval and exportA named approver signs off the data, and Qgentic produces the hashed package (CSVs, JSON and a manifest) for submission.
What the code enforces
| Check | What it does |
|---|---|
| Breach calculation | Incident durations come from the raw timestamps, and a manual change that disagrees is rejected (OPRES-TOL-008). |
| Identifiers | FRN structures are validated, and every LEI is checked against its ISO 17442 checksum. |
| Mapping integrity | A material arrangement not linked to a business service is an error (OPRES-MAT-007). |
| Audit chain | A hash-chained log of every action; nothing is exported until a person authorises it. |
There is no public FRN check-digit algorithm, so validation pairs strict formatting rules with LEI verification to pin the entity down.
What you file
The reports
CSVs for the third-party register and important business services, and JSON for incident reports, formatted to the current regulatory standards. Every file is hashed into a manifest, and nothing is generated until a person authorises it. The dashboard tracks each annual self-assessment deadline.
Filing to the regulator
The PRA and FCA do not currently expose an API for these reports, so the software runs in prepare-only mode: your team uploads the finished outputs to RegData, Connect or the PRA, with proof of how every number was derived.
What it costs
Pilot
Your existing registers, shadowed and validated in full. The fee is credited in full against year one.
Cloud
Base tiers: Starter £1,500, Growth £3,750, Enterprise £7,500. The meter counts material third parties, validated reports and finalised submission packages.
Air-gapped
Runs isolated on your own premises, with no external data transmission. See the air-gapped edition.
Every edition's price is on the pricing page, and consultancies can deliver it through the partner programme. The contract stack: Master Terms, Schedule B (OpRes) and your Order Form.
Frequently asked questions
What defines UK operational resilience reporting?
The continuing evidence obligations the PRA and FCA set (for example in SYSC 15A): firms document their important business services, impact tolerances, third-party dependencies and disruption events.
Who identifies important business services?
The firm's board defines them, based on the potential harm to consumers or to market integrity. Qgentic validates and records those decisions; the decisions stay with the board.
How are impact tolerances managed?
Each tolerance is recorded as a testable limit, usually a duration. Qgentic measures real incident timestamps against it, so breach reporting is a calculation.
How does OpRes differ from DORA?
DORA is EU law built around a reporting format; UK OpRes is PRA/FCA supervision built around impact tolerances. Multinationals run both on one Qgentic engine. See Qgentic DORA.
What specific tasks does Qgentic automate?
Data assembly, deterministic validation, breach calculation and report generation. Policy decisions, scenario testing and remediation stay with the firm.
Why doesn't it submit through an API?
The PRA and FCA do not currently expose an API for these operational resilience submissions. Qgentic runs every step up to the export and prepares the exact files you upload to the regulators' portals.
Operational resilience guides
UK operational resilience reporting, explained
Important business services, impact tolerances, mapping and self-assessment, and how the framework differs from DORA.
Impact tolerances & important business services
Naming important business services and setting tolerances that survive a severe-but-plausible scenario.
Operational resilience scenario testing
Choosing severe-but-plausible scenarios, testing against tolerances, and turning the results into evidence.