What the System Readiness Audit™ measures

The System Readiness Audit™ (SRA™) measures whether the systems an organization runs on can carry more change.

Every workforce operates on a foundation: processes, tools, decision rights, sponsorship, and the workarounds people have quietly built to keep things moving. That foundation has a load limit. The SRA™ reads whether it is sound, whether it is already strained, and whether it will hold under change that is accelerating.

The question it answers is whether people are set up to succeed or set up to fail. A workforce with real capacity, working on systems that are already failing, will still not deliver the change. They will spend their capacity compensating for the foundation instead of carrying the change.

The SRA™ evaluates four domains. A red rating in any single domain caps the overall result, because a foundation is only as sound as its weakest point. An average would hide precisely the thing the audit exists to find.

Why there are two instruments

A structure fails one of two ways. The frame cannot carry the load, or the foundation cannot carry the frame. Both are load bearing. Both are measurable. An engineer who inspected only one of them would be negligent.

PcQ™ reads the frame, which is the people. The System Readiness Audit™ reads what the frame is bolted to. Inspecting one and not the other tells you very little about whether the structure will stand.

The boundary rule

One question separates the two instruments in every case.

Would the reading change if you replaced the people?

If yes, it is PcQ™. If no, it is System Readiness.

Sponsorship that is nominal rather than real stays nominal with a new workforce, so it is System Readiness. Belief that was damaged by how the last change was handled resets with a new workforce, so it is Emotional PcQ™. Fourteen manual workarounds survive any staffing change, so they are System Readiness.

The test also splits change saturation into its two components, which is where most organizations misread it. The decision to run four concurrent initiatives is a property of the system. The depleted state of the particular people carrying them is Adaptive PcQ™. One symptom, two readings, two different responses. The system reading says stop starting things. The people reading says these teams need recovery before anything else is added. An organization holding only one of the two will act confidently on the wrong one.

The Pulse

The Pulse is the combined reading of both instruments: People Change Capacity™ across four dimensions, and System Readiness across four domains, shown together as a single view of an organization’s capacity to carry change.

Neither instrument is interpretable on its own. A PcQ™ score with no System Readiness reading tells you that people are struggling and gives you no way to know why, which reliably produces the wrong conclusion. Low trust inside an organization whose sponsorship is nominal is not a deficit in the people. It is people reading their environment accurately.

A red System Readiness domain caps the Pulse, on the same principle that governs each instrument separately. Where the foundation is failing, the PcQ™ result cannot be attributed to the people at all.

This is what makes the pairing more than coverage. Run PcQ™ alone and it becomes one more instrument producing a number about people, inviting leadership to conclude that the people are the problem. The System Readiness Audit™ is the control that prevents it. People recover systems. Systems do not recover people.