AI Readiness Assessment Know What Is Actually Blocking You

It is a structured evaluation of whether an organisation can successfully deploy and operate AI, scored across data, process, technology, people and governance. A useful assessment reports those five dimensions separately rather than averaging them into a single maturity score, because the lowest dimension is the one setting the programme's actual pace. The output should name the specific blockers, what each would cost to remove, and which use cases are viable before any of that work happens.

A workflow audit goes deep on one process: it shadows the work, records a time-and-error baseline, and ranks the automation candidates inside that single process. A readiness assessment goes wide across the organisation and asks whether you can operate any AI system at all. If you already know which process you want to automate, the audit is the better spend. If several departments are asking and you need to sequence them, or a previous pilot stalled and nobody can say why, start with readiness.

Most measure how much of a vendor's product suite you have adopted, which is why the recommendation is so often to adopt more of it. A model worth using measures observable facts: whether a baseline exists, whether a system of record is identified, whether an owner is named, whether there is a governance route a use case passes through, and whether anything currently runs in production against a threshold. Every one of those is verifiable by someone outside the organisation, which is the test a maturity claim should have to pass.

It depends on where the programme stalled. Organisations that never get a pilot running are usually blocked on data: the records are incomplete, spread across systems, or in free-text form the use case cannot consume. Organisations that ran a successful pilot and could not scale it are almost always blocked on process and governance, having proved the technology worked and then found nobody accountable for operating it and no route for approving it into production.

Typically two to three weeks depending on how many business units are in scope, most of it spent in interviews and systems review rather than analysis. It is faster than a workflow audit per department because it does not require sustained observation of the work itself, but slower to schedule, because it needs time with people across data, IT, operations, legal and the affected business teams.

Often not. If there is one clear candidate and one department involved, a workflow audit answers the real question faster and gives you a baseline you can hold a vendor to. Readiness assessments earn their cost when there are competing requests to sequence, when a previous attempt failed without a clear diagnosis, or when a board wants a defensible plan across the organisation rather than a single project.

The five dimensions, the four maturity levels and the self-check questions are all published on this page, and you are welcome to run them internally. What an engagement adds is independence and evidence: we verify claims against the systems rather than recording what each team believes, and internal assessments tend to score generously on exactly the dimension that later stops the programme.

The governance dimension is scored against SDAIA's seven AI Ethics Principles and PDPL obligations rather than a generic checklist. In practice that means asking whether a pre-deployment review exists across fairness, privacy and security, humanity, social and environmental benefit, reliability and safety, transparency and explainability, and accountability, whether the lawful basis and retention position is documented, and whether data residency has been settled for the specific workload rather than assumed. As an engineering firm we assess the design; your legal counsel should confirm the final position.