Home / Services / SOC 2 readiness

SOC 2 readiness.Central Valley

A customer asks for a SOC 2 report before it will sign or renew. The report itself is issued by a licensed CPA firm — nobody else can issue it. Everything before that moment is readiness: setting the scope, finding the gaps, writing the policies, and gathering the evidence the auditor will ask for. We do the readiness work for software and services firms in the Central Valley, so the audit contains no surprises.

Every engagement starts with a first look, at no charge.

The work is reviewed and signed by Brian Olson, CMMC Registered Practitioner.

When it comes up

  • A customer or prospect requires a SOC 2 report as a condition of signing or renewing.

  • A Type I report is needed to establish control design before a Type II observation period.

  • A previous readiness effort stalled, or an audit found gaps that should have been found earlier.

  • The firm already holds ISO 27001 and needs the SOC 2 mapping and evidence, not a rebuild.

What you receive

  • The scope

    Which Trust Services Criteria apply (Security plus Availability, Processing Integrity, Confidentiality, and Privacy as the business requires), and which systems are in and out, with a clear boundary.

  • A gap analysis against the SOC 2 criteria

    Current state measured against each criterion in scope, with findings in the places they cluster: unwritten policies, unscheduled access reviews, undocumented vendors, informal change management, unexercised incident response.

  • The list of policies and evidence your auditor will ask for

    Mapped control by control, so the auditor’s request list contains no surprises.

  • A remediation order

    What to fix first, sized to the observation period for Type II.

What we don’t do

We do not issue SOC 2 reports — the report comes from a licensed CPA firm. And if we helped you get ready, we take no part in your auditor’s fieldwork. The firm that prepares you should not be the firm that checks the preparation. We work alongside your CPA firm, not in place of it.

Common questions

Straight answers.

What people ask about SOC 2 readiness.

Type I or Type II — which do we need?

The customer usually decides. Type I reports on design at a point in time; Type II reports on operating effectiveness over a period, usually 3 to 12 months. Most firms start with Type I and run the observation period for Type II. The readiness work is largely the same either way.

How long does readiness take?

Usually measured in weeks for a small firm with usable documentation, depending on scope and starting point. The honest timeline depends on the gap list, which is why readiness starts with the assessment.

We have ISO 27001. Does that help?

Substantially. The control sets overlap heavily, and readiness becomes a mapping exercise plus SOC 2-specific evidence rather than a build from scratch.

What does it cost?

It depends on scope and starting point, so we don’t list prices. The scope is in writing before any work starts. The first look costs nothing.

First look

Start with a first look.

A short review of where you stand against the criteria your customers are asking about, and a short report signed by a person. No charge, no obligation. A person gets back to you within one business day.