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
AI Assurance  ·  Audit Readiness

They will ask. Will you have it?

Every artefact an auditor wants is cheap to keep and expensive to reconstruct. Audit readiness is almost entirely a question of when you decided to start keeping it.

4–8 WEEKSEVIDENCE PACK AND GAP REGISTERREGULATOR-FACING FORMATS
The decisions underneath

Three questions decide the work.

Audit readiness is not a rehearsal. It is the difference between producing the record in a week and producing it in a quarter.

01

Who is going to ask

A regulator, a certification body, and a customer’s third-party risk team want different things in different formats. Preparing for the wrong one is common.

02

What can you produce today

Not what exists somewhere. What could be assembled this week, by somebody who is currently on annual leave.

03

What is the shortest path to the gaps

Some gaps close in an afternoon and some take two quarters. Knowing which is which is most of the value.

What a review asks for

The record, assembled before somebody asks.

Audit readiness is the difference between producing this in a week and producing it in a quarter. 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

Every artefact here is cheap to keep and expensive to reconstruct. Audit readiness is almost entirely a question of when you decided to start keeping it.

What you receive

A pack, and an honest register of what is missing.

Four stages, every engagement. Hover a stage to see what happens in it.

DURATION
4–8 weeks
DELIVERABLE
Evidence pack, dry-run timing, gap register
DELIVERED
Remotely; regulator-facing formats where required
INDICATIVE FEE
[FEE BAND — pending sign-off]
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.
AI Assurance

The rest of this pillar.

Three engagements inside this pillar. Start with the question you can name, or take the whole estate at once.

Questions we are asked

Before you ask us.

We passed our last audit. Is this necessary?
Possibly not, and if the dry run shows you can produce the pack in a week then that is the answer and it costs the same. The engagement is most useful where the last audit predates the AI systems now in production.
Is this the same as certification support?
It overlaps. Certification support is preparation for one specific standard and one specific body. Audit readiness prepares the underlying record, which is what most of the requests draw from regardless of who is asking.
Do you attend the audit with us?
We can, in support. What we do not do is present ourselves as the assurance provider to your auditor, because the pack should stand on the evidence rather than on our presence in the room.
How long does the record stay current?
Not long, which is the uncomfortable part. The pack is a snapshot; the useful output is the change to how the record is captured, so that the next request is retrieval rather than reconstruction.

Start with a dry run.

Thirty minutes. Pick the obligation most likely to be asked about, and we will time how long the pack takes to assemble.

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.