What we do
01  Advanced Infrastructure 02  Applied AI & Data 03  AI Cybersecurity 04  AI Assurance
Engagements
AI estate inventory Assurance review
Industries
Financial Services Government & Public Sector Energy & Utilities Telecommunications Healthcare & Life Sciences Transport & Logistics Industrial & Manufacturing Retail, Hospitality & Real Estate
Research
The Trust Maturity Model The GCC Assurance Index Readiness self-assessment Case studies Perspectives Sector briefings Technology evaluations
Company
About us Partners Events Careers Contact العربية Talk to our team
What we do  ·  AI Assurance

Can you prove it when asked?

Assurance is not an opinion about your intentions. It is a question about what you can put on a table when somebody asks — and we do not build the systems we are asked to examine.

4–8 WEEKSEVIDENCE, NOT A POLICY DOCUMENTWE EVALUATE · WE DO NOT BUILD
Why this pillar exists

Governance is judged on what it produced.

Every organisation we meet has policies. Very few can produce, at speed, the artefacts that show a decision was actually governed at the moment it was taken.

01

The inventory is always partial

AI arrives as a feature of something already bought. It is running long before it appears on any register, and the register is the first thing asked for.

02

The decision record does not exist

Somebody approved this system. Reconstructing who, when, and on what information, two years later, is expensive and rarely convincing.

03

The builder wrote the opinion

An assurance report produced by the party that built the system is a marketing document. It will be read as one.

What a review asks for

Six artefacts. Pick an obligation and see which ones you hold.

Assurance is not an opinion about your intentions. It is a question about what you can put on a table. Choose an obligation.

THE INVENTORY
ARTEFACT 01

System inventory

Everything in scope, counted
ARTEFACT 02

Risk classification

Applied the same way twice
THE MAPPING
ARTEFACT 03

Control mapping

Obligations held against systems
ARTEFACT 04

Decision record

Who approved, on what information
THE PROOF
ARTEFACT 05

Testing evidence

That the control actually ran
ARTEFACT 06

Reporting pack

In the form it will be asked for
EVIDENCE LEDGER— OF 6 EVIDENCED
Select an obligation

Six artefacts. Every obligation on this list draws on the same six, which is why preparing for one of them prepares you for most of the others.

HELDPARTIALABSENT

The pattern is consistent across every obligation on this list: inventory is usually partial, and the decision record is usually absent. Those two gaps account for most of the work.

AI Assurance

Three ways in.

Three engagements, sold independently and architected as one. Start with the question you can name.

The boundary

We evaluate it. We did not build it.

Three moves. Two of them are ours, and the one in the middle deliberately is not.

MOVE 01 — OURS

We test and we write it down

We evaluate the system against what it was claimed to do and against the obligations that apply to you, and we record what the test showed — including where the answer was that no record exists.

MOVE 02 — NOT OURS

Your builder does the fixing

Remediation is performed by whoever built or runs the system. We do not take the build work, because taking it would mean the next evaluation is us examining our own hands.

MOVE 03 — OURS

We re-test on a cycle

The system is re-examined against the same tests on a schedule, because an evaluation is a statement about a configuration on a date, and configurations move.

If a finding of ours turns into a build contract for us, the finding stops being evidence and starts being a sales instrument. We would rather keep the evidence.
How we engage

Defined engagements with a deliverable at the end.

Every engagement in this pillar is scoped, fixed-fee and finishes with something you can put in front of somebody else.

TYPICAL DURATION
4–8 weeks
DELIVERABLE
Evidence pack and gap register
DELIVERED
Remotely; regulator-facing formats where required
INDICATIVE FEE
[FEE BAND — pending sign-off]
Questions we are asked

Before you ask us.

Do you also build the systems you assess?
No, and this is a hard line rather than a preference. If a finding of ours reliably turns into a build contract for us, the finding stops being evidence and becomes a sales instrument. Where remediation is needed, it is performed by your builder or by a third party.
Is this a certification?
No. We are not a certification body. We produce the evidence and the gap register that a certification, a regulator or a customer questionnaire will ask for, and we are explicit about which of those we are preparing you for.
How fast can this be done?
A scoped review against one obligation typically runs four to eight weeks. The pace is usually set by how complete your inventory is on day one, which is why the inventory is where we start.

Start with the artefact you could not produce.

Thirty minutes. Pick the obligation you are most likely to be asked about and we will tell you which rows you can already fill.

Book a 30-minute scoping call

ORVIX · INDEPENDENT AI & TECHNOLOGY ASSURANCE · WE DISCLOSE EVERY COMMERCIAL RELATIONSHIP ON THE PAGE FOR THE SERVICE IT BELONGS TO. WHERE LICENSING IS REQUIRED, DELIVERY IS PERFORMED BY NAMED PARTNERS UNDER THEIR OWN LICENCE.