The Audit, End to End

Lesson 6: The Audit, End to End

Once scope is set and controls exist, the examination follows a predictable arc. Knowing what happens in each phase is what lets you front-load the work instead of discovering requirements in week six, when your auditor's sample request lands and the ticket you needed was closed eighteen months ago.

Phase 1 — Readiness (weeks to months)

You cannot retrofit evidence, so readiness is about finding gaps before they become findings. Two distinct deliverables get conflated:

  • Gap analysis — your own (or a consultant's) comparison of current practice against the in-scope criteria. Output: a list of missing or weak controls with owners.
  • Readiness assessment — usually performed by a CPA firm that does audits, producing a letter estimating how the examination would go today and which controls would appear in the report. It is optional in principle and near-mandatory in practice: it is far cheaper than failing a window you cannot repeat.

Between the two sits remediation, the phase that actually consumes the budget: implementing controls, writing and approving policies, deploying tooling, training people, and — critically — starting the clock so controls operate long enough to be sampled.

Phase 2 — Engagement and scoping with the auditor

Select the firm, then sign an engagement letter that pins down: the criteria and categories in scope, the review period and its exact dates, the system boundary, fees and payment schedule, deliverable dates, the evidence portal and process, and who is responsible for what. Ambiguity here becomes a change order or a re-scope later. Confirm the partner's independence and that the firm is peer-reviewed and licensed where required.

Phase 3 — Writing the system description

This is management's work, and it is the most underestimated task in the project. Under the Description Criteria you describe the system's infrastructure, software, people, procedures, and data; the boundaries; relevant incidents during the period; and then, for each criterion in scope, the control activities, the service commitments and system requirements they address, and any complementary user entity controls. Expect this document to be 30–80 pages, to go through multiple drafts, and to be reviewed by the auditor for fair presentation as well as accuracy. Teams that outsource it wholesale usually find it describes a company they don't work at.

Phase 4 — The window

Controls must operate, and evidence must accumulate as they do. Nothing can be manufactured retroactively. This is the phase where discipline beats heroics: the quarterly access reviews get done on time, the pen test lands inside the period, the DR test is scheduled early enough to be repeated if it fails, and every incident is documented as it happens.

Phase 5 — Fieldwork

Typically one to three months, running in parallel with the tail of the window:

  1. Kickoff and PBC list (“provided by client”) — the evidence request list, often 100+ items. A well-prepared company answers in batches through a portal; a badly prepared one answers in email threads.
  2. Inquiry and walkthroughs — interviews with control owners to confirm the description matches reality.
  3. Inspection — reading policies, tickets, logs, exports, contracts.
  4. Observation — watching a control happen, or inspecting the system's configuration directly.
  5. Reperformance — the auditor does it themselves: attempts a login without MFA, tries to reach a production database from the internet, requests an unauthorized change.
  6. Sampling — populations are requested (all terminations, all production changes, all vulnerability tickets) and a sample is drawn. Frequency drives sample size: an annual control needs one instance, quarterly a couple, monthly a handful, daily or per-transaction many more, with automated controls tested once alongside the IT general controls that protect the automation.
  7. Follow-up — clarifications and additional requests; deviations documented with the client's explanation.
The population is the trap. If you hand over a termination list and your auditor cross-checks it against HR's records and finds someone missing, you have a completeness problem that is far worse than the original deviance — it undermines the reliability of every population you supplied. Never curate a population to look clean. Auditors test completeness, and “the sample was incomplete” reads as an integrity issue, not a clerical one.

Phase 6 — Reporting

You receive a draft; management gets to write a response to any exceptions, including remediation status. Then the report is issued. The opinion can be:

OpinionMeaningCommercial effect
UnqualifiedControls suitably designed and, for Type II, operating effectively; description fairly presentedWhat you want; what buyers expect
QualifiedEffective except for specified matters — e.g. one control that deviatedUsable, but expect questions; may require a remediation narrative
AdverseControls did not meet the criteriaEffectively a fail; re-audit after remediation
DisclaimerAuditor could not obtain sufficient evidenceRare and damaging — indicates the evidence base was unusable

A SOC 2 report is not pass/fail, but a qualified opinion is a negotiating position, and a report with many exceptions gets discounted by sophisticated buyers. Learn what a report looks like before you're in one:

SectionContentsAuthored by
IIndependent service auditor's report — scope, criteria, period, opinionCPA firm
IIManagement's assertion — “we designed and operated these controls…”You (signed by an executive)
IIISystem description — infrastructure, software, people, procedures, data, boundaries, incidents, CUECsYou, reviewed by the auditor
IVCriteria → controls → tests performed → results (with exceptions noted)CPA firm
VOther information (optional, outside the opinion)You

Phase 7 — Distribution and the year after

Reports are restricted-use, shared under NDA with customers and prospects, and they age. Two mechanics matter commercially:

  • Bridge letters. A management-issued letter (not auditor-issued) covering the gap between your report's period end and today, confirming no material changes to controls. Commonly accepted for a few months. A bridge letter that says “several changes occurred” ends the conversation.
  • Continuous certification. The next window should start the day the last one ended. Companies that let a three-month gap open find themselves explaining what happened during it — and buyers who ask for “the most recent report” will reject one older than about 12–15 months.
A first Type II, month by month Readiness gap analysis, scope, auditor selection Remediation policies, tooling, training, tickets start Review period (6–12 months) evidence accrues monthly/quarterly pen test · DR test · risk assessment inside Fieldwork PBC list, samples, draft Report signed Then: distribute under NDA · bridge letters as it ages · next window starts the day this one closed The failure mode is not the audit — it is the 9-month gap between reports where buyers see nothing.

🧠 Knowledge Check

1. Who authors the system description in a SOC 2 report?

2. Your auditor requests the full termination population and finds an employee missing from the list you supplied. What is the most serious implication?

3. A prospect asks for your SOC 2, issued 15 months ago. What is the standard remedy?

Further Reading