All insights
ComplianceNovember 20, 2026

SOC 2 readiness, for a first audit

The controls take a quarter. The observation window takes months and cannot be compressed, which is why the thing to do today is start the clock.

Most organisations start thinking about SOC 2 because a customer asked. That is a reasonable trigger, and it usually comes with a timeline that is shorter than the process allows, because the constraint is not how fast you can implement controls.

It is that a Type 2 report describes how controls operated over a period. That period is typically three to twelve months, and there is no way to buy your way past it.

Type 1 and Type 2

A Type 1 report says the controls were designed appropriately and existed at a point in time. It can be produced relatively quickly and it demonstrates intent.

A Type 2 report says the controls operated effectively across an observation window. It is what customers actually want, and it is the one that takes time.

A common and sensible path is a Type 1 at around month five, which gives you something to show the customer who is asking, followed by a Type 2 covering the subsequent period. Some firms skip the Type 1 to save cost, which is reasonable if nobody needs evidence in the interim.

Scope first

Security is mandatory; each additional criterion adds cost and controls
Security is mandatory; each additional criterion adds cost and controls

The most common first mistake is including criteria nobody asked for, usually because more sounded better. Each additional criterion brings its own controls to implement, evidence to collect and audit time to pay for.

Ask the customer who prompted this what they actually need. Very often the answer is Security alone, and a Security-only report is a completely normal deliverable.

The second scope decision is which systems and which parts of the organisation are covered. Narrower is cheaper and faster. The constraint is that the scope has to cover the service your customers care about, or the report does not answer their question.

The timeline

The observation window is the constraint, and it can only be started earlier
The observation window is the constraint, and it can only be started earlier

Twelve months from a standing start to a first Type 2 is realistic. Organisations with decent controls already in place can compress the early phases, but the observation window remains.

The practical implication: if a customer needs a report in six months, the conversation to have now is about a Type 1 plus a committed Type 2 date. Most customers accept that if it is offered early and honestly. Very few accept it when it arrives as an excuse at month five.

What readiness actually involves

The gap for a typical organisation is not technology. It is three things.

Controls that exist but are not evidenced. You do review access, but there is no record. You do patch, but nothing produces a report. The remediation is to attach an artefact to things you already do.

Policies that do not match practice. Either the policy is aspirational or practice has drifted. Auditors test against your stated policy, so a policy you do not follow is worse than a less ambitious one you do. Write them to describe what you actually do, then improve both deliberately.

Things nobody owns. Vendor management, risk assessment, security awareness training, change management. Each needs a named owner and a cadence, and in a small organisation that is frequently the same person for several of them, which is fine as long as it is written down.

Evidence is the whole game

The thing to internalise: an auditor does not assess whether your controls are good. They assess whether you can demonstrate the controls operated, consistently, throughout the window.

If your control says access is reviewed quarterly and you have evidence for three of the four quarters, that is an exception in the report. Not a catastrophe, and not nothing.

So the single most valuable thing you can do at the start is build the evidence habit. Every recurring control gets a calendar entry, an owner, and a defined artefact saved to a defined place. Access review: quarterly, named owner, exported list with annotations, saved to a folder. The same for vulnerability scanning, backup testing, security training, vendor review and incident log.

Compliance platforms automate a good deal of this and are worth their cost for most organisations doing this for the first time, though they automate collection rather than the underlying operation. A tool cannot perform your access review.

Choosing an auditor

Only a licensed CPA firm can issue a SOC 2 report. Beyond that:

Ask how many reports they have issued for companies of your size in your sector. Ask what their process looks like and how much of your time it consumes. Ask for a sample report, redacted, and read how clearly the exceptions are described.

Price varies widely. For a first Type 2 at a small company with Security-only scope, expect a five-figure engagement, plus readiness support if you use it, plus the tooling. Significantly cheaper quotes usually mean less fieldwork, and a report that an informed customer will read sceptically.

Keeping it

A SOC 2 report covers a period that ends, so customers will ask for a current one annually. That makes this a recurring programme, not a project.

The organisations that find year two easy are the ones that built the evidence habit in year one rather than assembling everything in a scramble before fieldwork. Year two should cost less in internal effort than year one by a wide margin. If it does not, the controls are not actually operating between audits.

Work with us

Want a second set of senior eyes on your Microsoft 365 environment?

Book a free call