All 24 axes with their official §5.x codes, grouped under the ten perspectives, with the number of standards beneath each one.
An axis is Qiyas' middle layer: it takes a theoretical perspective and breaks it into operational ground your team can actually assess. Take IT: it splits into three axes — Systems Supporting DT (5.11), Technical Services Infrastructure (5.12), and Cloud Architecture (5.13). Honestly, once you understand the axis properly, you know who owns the gap and what evidence you need ready before verification opens.
We overlay the 24 axes on your organisational structure and assign one named owner per axis.
A fast diagnostic on each axis — complete, minor gaps, or structural gaps. Two weeks.
Under each axis, a gap for every standard beneath it, ordered by impact on the perspective score.
Owner, duration, required evidence, and weekly reviews. The hardest axes start first.
We sit with you through initial verification, the system-reopening window, and final verification, per axis.
We run a gap analysis per axis and per standard beneath it, then build a closure plan ordered by priority. For each axis you know: who leads, what evidence is required, and what the timeline is.
A multidisciplinary team bringing the technical and organisational sides under one roof — so you are not chasing five consulting firms to cover 24 axes.
We know which axes are hardest on the ground: Beneficiary Experience, which needs a real satisfaction survey, and Website Technical Efficiency, which needs a page-by-page audit. We start those early, not in the final month.
Perspective is the top level (10 of them). Axis sits below it and breaks out the operational side (24). The standard is the actual scoring unit (89), each with a 5.18.4 code, a text, and specific evidence.
They added a Digital Procurement axis, split Whole-of-Government Platforms into two, and the new Websites Efficiency perspective brought two more axes with it.
IT covers supporting systems, technical infrastructure, and cloud architecture. Operations became two separate axes after Digital Procurement broke out on its own.
Beneficiary Experience and the Websites Technical Efficiency axis. The first needs a real satisfaction survey tied to published improvements. The second needs a page-by-page technical audit — and most entities push it to the last month.
No. You need a multidisciplinary team — or one partner who brings the technical and organisational sides under one roof so you are not chasing five consulting firms.
We run a gap analysis per axis and per standard beneath it, then build a closure plan ordered by priority. For each axis you know: who leads, what evidence is required, and what the timeline is.
We deliver a map of the 24 axes against your structure with a named owner per axis, and a prioritised closure plan.
Back to all services
