Skip to main content

Controls Readiness vs. Framework Readiness vs. Dashboard Readiness

Why the SOC 2 readiness percentage you see on Tasks doesn't match the one on the Frameworks page — they're measuring different things.

Written by Upendra Varma

You'll run into a moment like this: your Tasks page says SOC 2 is 51% ready. You click into Frameworks → SOC 2, and Controls Readiness there says 35%. Same framework, same moment in time, different number — and that's not a bug.

They're measuring different things

Tasks / Dashboard readiness is based on your tasks — the guided, framework-specific checklist. Its percentage is "how many of the tasks toward this framework are complete."

Framework "Controls Readiness" is based on your controls — the underlying safeguards (and the tests/documents mapped to them) that the framework's requirements are actually built from.

A task can be "in progress" while representing several controls, some passing and some not — so the two percentages naturally diverge. Neither one is wrong; they're just answering different questions:

Question

Where to look

"What do I need to do next?"

Tasks

"Is this specific control satisfied?"

Frameworks → [Framework] → Controls

"Are my automated/manual tests passing?"

Tests, or a framework's own Tests tab

The Dashboard's Health rings are a third thing entirely

The Security / Organisation / Risk percentages on your Dashboard aren't framework-specific at all — they're the percentage of tests passing within each of those three areas, across your whole account, independent of which framework(s) you have enabled. Don't try to reconcile a Health ring against a specific framework's readiness number; they're not the same measurement.

The short version

If a number here doesn't match what you expected, check which of these three you're actually looking at before assuming something's broken.

Did this answer your question?