Regulatory assurance for software delivery

Know what each regulation means for this project, before it is built.

SDLC OneIQ holds one record of a project's regulatory position, from intake through to go live, so the obligations are known while the design is still open and the evidence exists before anyone asks for it.

10

Regulations and standards covered, named further down this page

EU · UK

Jurisdictions covered today, deployed in the region you choose

One

Record of a project's regulatory position, from intake to go live

Watch the overview

See SDLC OneIQ in under three minutes.

Software delivery is moving faster. This short introduction follows an illustrative banking scenario to show how regulatory assurance can keep pace.

Video · 2:57
Illustrative banking scenario
The problem

Regulation arrives late, in the wrong form, to the wrong people.

Regulation lands on the organisation. Delivery happens in projects. The translation between the two is done by hand, differently each time, and usually too late to change anything cheaply.

Obligations arrive after the design is fixed

The assurance review sits near the end, so the finding that should have changed an architecture decision instead becomes a rework bill weeks before go live. The cost is carried by the delivery budget and the go live date.

Nobody can say what a regulation means for one project

Turning a regulation into what this team must actually do is manual, undocumented and repeated per project. Different people reach different answers, and none of the reasoning survives the project that produced it.

Evidence is reconstructed, not produced

Screenshots, tickets and email threads assembled under deadline, months after the decision, by people who were not in the room. It is expensive, it is weaker than the original, and it happens again at the next audit.

The release decision cannot be reconstructed

Something shipped with an accepted risk. A year later the person who accepted it has left, the expiry was never tracked, and the question of who decided has no answer anyone is comfortable giving.

What this is

An assurance layer over delivery, not another register.

It is

A regulatory position, per project, kept current

  • The regulations that apply to a project, and the stated reason each one does or does not.
  • The control objectives those regulations impose, tracked at every stage of delivery.
  • A release readiness position, owned and dated, with the reasons behind it.
  • Evidence held against the obligation it answers, not filed in a folder.
It is not

Five things people expect it to be

  • ×
    A policy register. Registers hold policy and risk for the organisation. This works at the project and the release, where the decisions are actually made.
  • ×
    A code scanner. Scanners find defects in code. This governs whether a change is fit to release against named regulations.
  • ×
    A coding assistant. It does not write, host or edit your code, and it is not an alternative to the tools your engineers already work in.
  • ×
    A document repository. Evidence is bound to the obligation it satisfies, so the trail holds together without a librarian.
  • ×
    A replacement for your accountable people. It gives them the position and the trail. The decision stays theirs.
What changes

The same work, surfaced while it is still cheap to act on.

Today
With SDLC OneIQ
Today
Regulatory scope is settled in a workshop and remembered in a spreadsheet.
→
With SDLC OneIQ
Scope is a record: which regulations apply to this project, and the reasoning for every inclusion and exclusion.
Today
"Where are we against the regulations?" is answered by asking three people and waiting two days.
→
With SDLC OneIQ
The position of every project in flight is on one screen, current, with the gaps named and owned.
Today
An accepted risk is an email nobody revisits until an auditor finds it.
→
With SDLC OneIQ
An exception has an owner, a justification and an expiry, and it comes back before it lapses.
Today
Audit evidence is reconstructed months later from tickets and screenshots.
→
With SDLC OneIQ
Evidence sits against the obligation it answers, captured when the work happened.
Today
A regulation changes and the impact on projects in flight is a guess.
→
With SDLC OneIQ
A regulation changes and the projects and artefacts it touches are listed.
Capabilities

What you get.

Six things a delivery organisation can do that it could not do with a spreadsheet and a quarterly review.

Capabilities
06 entries
01Scope, with the reasoning

Every project carries a record of the regulations in scope, the obligations they impose, and a stated reason for each one, including the ones deliberately ruled out.

Why it matters

The first question a regulator asks is why you thought this applied to you. The answer is written down before anyone needs it.

02Compliance position by stage

See where a project stands against each control objective at every stage of delivery, from intake through to go live.

Why it matters

The gap is visible while the stage is still open, not at the assurance review when changing it is expensive.

03Release readiness, stated

A release carries a readiness position with the reasons behind it, so the decision to ship or to hold is explicit, owned and dated.

Why it matters

Nobody has to reconstruct, a year later, why a release was judged fit to go.

04Exceptions that expire

Accepted risks are recorded with an owner, a justification and an expiry date, and they surface before they lapse.

Why it matters

An exception nobody revisited is the finding your next audit opens with.

05Evidence bound to the obligation

Artefacts, approvals and sign-offs are held against the control they satisfy, so the line from a named regulation to the proof holds together.

Why it matters

An audit answer read out of the record beats one assembled from memory, and takes a fraction of the time.

06Portfolio oversight

One view across every project in flight, showing where regulatory exposure is concentrated and what is blocking.

Why it matters

The accountable executive sees the position without asking twelve delivery leads to prepare a paper.

How it works

Scope it, position it, decide it, prove it.

Four steps. What happens, and what you see on the screen.

1

Scope

A project declares what it is building, what data it touches and where it operates. The applicable regulations and the obligations they impose are established and recorded with their reasoning.

You see: the project's regulatory scope, with a stated reason for every regulation included and every one ruled out.

2

Position

Those obligations become the control objectives the project has to meet, tracked against each stage of delivery.

You see: a current compliance position for the project, and for every stage from intake to go live.

3

Decide

Work proceeds. Findings are raised, owned and closed. Anything accepted rather than fixed is recorded as an exception with an expiry. Release readiness is stated with the reasons behind it.

You see: what is blocking, who owns it, what has been accepted and until when.

4

Prove

Evidence and approvals stay bound to the obligations they answer, and the decision trail is retained on the policy you set.

You see: the line from a named regulation through to the artefact that answers it, readable long after the team has moved on.

The detail is in the demonstration. How applicability is determined for a specific project, and how a release position is reached, are shown in a working demonstration against one of your own programmes. This page states what the product produces. The demonstration shows how it gets there.
Trust and assurance

Built for the person who has to defend the decision.

Human accountability

Determination is never left to a system alone. A named person owns every finding, approves every exception and signs the release position. Anything that cannot be concluded with confidence is routed to a person rather than assumed.

Evidence and audit trail

Who decided what, when, and on what basis, retained on a policy you set. An answer to an auditor is read out of the record rather than rebuilt from memory.

Your tenancy, your data

Single tenant deployment in the region you choose, with data residency in the EU or the UK. Sign-in runs through your own enterprise single sign-on, and your access rules decide who sees which project.

Where accountability sits. SDLC OneIQ identifies applicable obligations with stated reasoning, records who decided what and when, and keeps the evidence. It does not make your organisation compliant, and it does not carry your accountability. That stays with you, which is where the regulator puts it.
Who it is for

Written to the people who carry it personally.

CISO
Role

Chief Information Security Officer

Answers for how a specific release was judged fit to ship, often long after the team has dispersed. Gets a decision trail that stands up without a reconstruction exercise.

DEL
Role

Delivery and engineering leadership

Needs the regulatory constraints early enough to design for them, and a release decision that does not stall while three teams reconcile spreadsheets.

CRD
Role

Compliance, risk and data protection

Needs the position of every project without chasing it, and evidence that was produced by the work rather than assembled for the audit.

Banking
Insurance
Payments
Capital markets
Financial market infrastructure
Regulated technology
Coverage

Regulations and standards.

Named regulations and standards covered today, alongside your own engineering and security standards, which are treated the same way.

EU AI Act
EU GDPR
UK GDPR and DPA 2018
DORA
NIS2
PCI DSS v4.0.1
PSD2 strong customer authentication
ISO/IEC 27001
ISO/IEC 42001
FCA Consumer Duty
+ your own engineering standards
Coverage means the set of regulations and standards the product tracks your projects against. It is not a statement that Regulativ holds certification against any of them.
Questions we are asked

Straight answers.

Can you guarantee we will be compliant?

No, and no product can. What SDLC OneIQ produces is narrower and more useful: the applicable obligations identified with stated reasoning, the work owned and dated, the evidence captured against the obligation it answers, and a decision trail you can reconstruct years later. Compliance remains your organisation's accountability. A supplier who tells you otherwise is selling you a liability.

How do we know a determination is right?

You should not take it on trust, and the product is built on that assumption. Every determination carries its reasoning, so it can be read and challenged rather than accepted. A named person reviews and approves it, and anything that cannot be concluded with confidence goes to a person rather than being applied quietly. If you disagree with a determination you overrule it, and the overrule is part of the record.

We already have a GRC platform. Where does this sit?

Alongside it, not instead of it. A GRC platform holds policy, risk and control for the organisation. SDLC OneIQ works one level down, at the project and the release, which is where a regulation actually turns into a design decision or a hold on a deployment. Fitting it alongside the systems you already run is scoped during the pilot.

Will this slow delivery down?

It front-loads. The regulatory work is the same work you already do. What changes is when it surfaces, and a constraint known at design costs less than the same constraint found at the assurance review. We do not publish a delivery speed figure, because we have not measured yours. Measuring it is part of what a pilot is for.

What does it take to get started?

A pilot on one delivery programme, configured with your regulations, your delivery lifecycle and your approval roles. Fitting it to the systems your teams already work in is scoped as part of it.

Next step

Book a working demonstration.

Bring one delivery programme you are worried about. We will walk it through scope, position, release decision and evidence, and you will see exactly what the record looks like at the end of it.

What happens next

A short qualifying call to understand your regulatory footprint, then a working demonstration against your own scenario. Typically 45 minutes.

Regulativ
SDLC OneIQ