What does a readiness assessment catch that months of prep miss?

A founder messages me. Their dashboard is all green. Every check says "compliant." They want to know how fast we can issue the report.

Then I ask one question. "Show me eight people who left this year, and prove each one lost access inside your policy window." Silence.

That gap is the whole article.

Collecting evidence is reading the textbook

Before AI, a founder getting a first SOC 2 had two hard options. Hire a traditional firm and pay for months of back-and-forth coordination. Or do the evidence collection by hand, which is slow and easy to get wrong. Then the compliance platforms showed up (Vanta, Drata, Secureframe, Sprinto) and organized that evidence continuously, instead of in a frantic month right before the audit. That was a real advance. Pulling system configurations automatically, watching whether multi-factor authentication is on, keeping all your policies in one place. Genuinely useful work.

Here is the one thing worth being clear about. Collecting and organizing evidence is reading the textbook. It is necessary. It is not the exam.

The exam is when someone independent tests whether your controls actually worked. A platform is built to answer one question: does this control exist? MFA is toggled on. The offboarding policy is uploaded. An auditor answers a different question: did this control operate, consistently, over a period of time? Those are not the same question, and the second one is the only one your customer's security team cares about. The platforms know this. They say it themselves. Only a licensed CPA firm can sign the report, because only the CPA performs the examination, which is the audit and the formal opinion that comes out of it.

What a readiness assessment actually is

A readiness assessment, which founders often call a mock exam, is a real auditor running the real examination procedures against your evidence before the formal examination. Sampling. Inspecting documents. Reperforming a control to see if it does what it claims. Walkthroughs, where I trace one transaction end to end. The same toolkit the standard requires in the actual examination, pointed at you early, on purpose, to find where you would fail.

It is diagnostic. The point is to surface problems while they are still cheap to fix.

Why can only an auditor run this? Because testing whether a control operated effectively over a period is audit judgment, and the attestation standard is explicit that inquiry, which just means asking, is never enough on its own. Under AT-C section 205, the auditor has to pair asking with inspecting, observing, or reperforming. A platform reads a system through its API and reports the current state. It does not sample your terminations, chase down the one exception, and decide whether some other control makes up for the gap. That is the work. Inquiry is not enough, and a green checkmark on a dashboard is not a tested control.

The termination that slipped

Here is the difference in one example.

The platform was not wrong. The policy does exist. But "the policy exists" and "it worked for every person who left" are different claims, and only the second one survives an audit. You want to learn this from me in a readiness assessment. Not from a customer's security reviewer three weeks before a deal closes.

This is also why a clean run from a fast, lightly tested process should make you curious, not relaxed. The profession is openly thinking about this. A 2026 Journal of Accountancy piece noted that pressure for "fast and easy" SOC reports can push examiners to "rely too heavily on inquiry," which is exactly the failure mode a readiness assessment is designed to catch. If you want to know what that looks like when it ships, read what a stamp audit is.

The speed argument, said plainly

Studying the textbook for six months is not what makes you pass. A diagnostic that finds your specific weak spots, followed by targeted fixes, is. That is true for the bar exam, and it is true here.

The order I would run it:

1. Readiness assessment. Real procedures, real sampling. Find the actual gaps.
2. Remediate. Fix the specific findings. Usually days, not months, because the list is short and concrete.
3. Real audit. Now it is clean, because the problems already got caught and closed.

Assume there are findings. First-time companies almost always carry real gaps. In my fieldwork the usual ones are predictable: the termination that slipped, access that lingered after someone changed roles, a policy nobody follows, a review that is supposed to happen quarterly and happened once. None of those show up red on a dashboard. All of them show up under sampling. For the full pattern, see what a first-time audit actually finds.

One line on independence

A readiness assessment finds problems. It does not fix them for you. I present findings and options, you decide and own every fix, and the AICPA Code requires exactly that separation: the client makes the management decisions and accepts responsibility for the results. I will tell you where you would fail. I will not implement the fix and then turn around and bless my own work.

That distinction is not bureaucracy. It is the reason the opinion means anything.

The thing a platform cannot give you is the test. A real auditor running real procedures before the real audit is the fastest honest route to a clean report.