Home › Resources › Glossary › Readiness Score

Resources · Glossary

What is an audit readiness score? How it is calculated

In shortAn audit readiness score is a summary measure of how prepared an organisation is for an audit against a given framework. It is usually built from the share of controls implemented, evidence collected and accepted, and findings closed. No standard defines it, so every score depends on the method behind it.

What does a readiness score tell you?

Readiness is about whether the audit can go ahead and what it is likely to find. A score compresses many items into one number so progress can be tracked week by week.

Treat it as a guide. An auditor does not use your score; they test controls and evidence. A high score with weak evidence review behind it gives false comfort.

What usually goes into a readiness score?

Are they in place?Control implementation

The share of in-scope controls that are implemented and have an owner.

Can you prove it?Evidence

The share of required evidence that is collected, in period and accepted by a reviewer.

What is still open?Findings and actions

Open findings and overdue corrective actions, weighted by severity.

How might a readiness score be built?

An illustrative calculation. The weights are an example, not a standard.

InputExample
Controls implemented81 of 93 in scope: 87%
Evidence accepted210 of 280 required items: 75%
Critical findings open1, which caps the score until closed
How to read itEvidence is the weakest area; focus there before the audit

This is an illustration written for this page, not a customer record.

What do frameworks say about measuring readiness?

FrameworkWhereWhat it asks for
ISO 27001Clause 9.1The organisation decides what to monitor and measure, how, and when, and keeps the results.
ISO 27001Clause 9.3Management reviews performance, including trends in nonconformities and audit results.
SOC 2CC4.1Evaluations are performed to confirm that controls are present and functioning.
NIST CSF 2.0Tiers and profilesCurrent and target profiles are compared to identify and prioritise gaps.

References are to the current editions listed under Sources. Check the edition your auditor is using.

How do readiness scores mislead?

01

Counting uploads as evidence

A file attached counts as done, whatever it shows.

Instead: count only evidence a reviewer has accepted.

02

Averages that hide gaps

A high overall score hides one failing area.

Instead: show the score by control area and by framework.

03

Treated as a pass mark

A target of 90% becomes the goal.

Instead: use the score to find gaps; the audit decides the result.

How does QULDEX handle this?

Compliance Dashboard

Readiness by framework and by audit, built from the controls, evidence and findings recorded in the platform.

See the module

Readiness Score: common questions

Is there a standard formula for audit readiness?

No. Standards require you to monitor and measure, but leave the measures to you. Document how your score is calculated.

Does a high readiness score mean we will pass?

No. It means your own records show few gaps. The auditor tests independently and may find issues your score does not capture.

How often should readiness be measured?

Continuously if your tooling allows, and reviewed at each governance meeting in the months before an audit.

Readiness built from accepted evidence, not uploads

Controls, evidence, findings and corrective actions in one audit workspace.

Schedule
Book a Demo