Start hereDefine the system and report
~190 days leftOpen step
Guide library
Audit report Global

SOC 2

System and Organization Controls 2

Demonstrate how your service protects customer data with an independent CPA examination.

Who it applies to

Service organizations whose customers need assurance about controls relevant to security and any additional Trust Services categories in scope.

What you’ll produce

Restricted-use CPA report with an opinion, management assertion and system description.

Security is the core category. Add availability, processing integrity, confidentiality or privacy according to service commitments. Agree the observation period with the CPA firm.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which customer requirement are we meeting?
Ask Sales for the exact contract or security questionnaire language. Record the service, categories, report type and date the customer needs. The CPA firm should confirm the proposed scope and observation period before Sales promises delivery.
Who has time to run the controls?
Appoint a security or compliance lead and name a backup for each control. Fund engineering time to close gaps and reserve time for operating controls during the report period. Ask the CPA firm to quote fieldwork, extra locations or services, and changes to the engagement separately.
Who signs and who can see the report?
Management owns the system description and assertion. Have Legal and Sales agree a controlled sharing process and the language account teams can use when customers ask about exceptions.

How to spend the first week

  1. Sales brings the customer requests. Engineering brings the production architecture, identity provider, cloud accounts, deployment flow and service vendors. Security turns these into a draft scope memo.
  2. Security and Engineering walk one recent access removal and one production change from request to completion. Capture the original timestamps, approval and system record. Use missing evidence to size the work before setting the Type 2 start date.
  3. The executive sponsor approves the scope, named control owners and budget. The lead gets the firm’s evidence request process, availability and expected dates in writing.

What to review each week

Report control runs due versus completed this month, overdue corrective actions, and any planned changes to the system boundary. Flag gaps that may affect the report period before promising a customer an issue date.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

SOC 2 kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Define the system and report · Security lead + executive sponsor [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Sales brings the customer requests. Engineering brings the production architecture, identity provider, cloud accounts, deployment flow and service vendors. Security turns these into a draft scope memo.
2. Security and Engineering walk one recent access removal and one production change from request to completion. Capture the original timestamps, approval and system record. Use missing evidence to size the work before setting the Type 2 start date.
3. The executive sponsor approves the scope, named control owners and budget. The lead gets the firm’s evidence request process, availability and expected dates in writing.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which service and reporting period did the customer ask for?
  • Which controls generate records only when they actually run?

Worked scenario

A hosted invoicing company receives a Type 2 request. Before agreeing dates, its security lead checks that privileged access reviews and release approvals have been running in production and that their records cover the agreed boundary.

What to read next

  • ISO 27001

    Compare an ISMS certification request with a CPA report requirement.

  • SOC 1

    Check whether your service also influences customer financial reporting.

Plan evidence for SOC 2 and other programs Test this project’s launch date Practice reviewing an evidence packet
The whole journeyabout 190 days across 5 steps
  1. 01Define the system and reportSecurity lead + executive sponsor · ~14 days
  2. 02Map and implement controlsControl owners · ~42 days
  3. 03Operate controls and retain evidenceEngineering + operations · ~90 days
  4. 04Complete fieldwork and issue the reportIndependent CPA + management · ~30 days
  5. 05Maintain controls between reportsSecurity lead · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 14 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Define the system and reportSecurity lead + executive sponsorBefore engaging the auditorSet a start dateScope memo; System inventory; Agreed engagementOpen
Map and implement controlsControl ownersBefore the report date or periodSet a start dateControl matrix; Remediation tracker; System description draftOpen
Operate controls and retain evidenceEngineering + operationsThroughout the agreed Type 2 periodSet a start dateEvidence index; Access reviews; Change and incident populationsOpen
Complete fieldwork and issue the reportIndependent CPA + managementAfter the period or as-of dateSet a start dateFinal system description; Management assertion; Issued reportOpen
Maintain controls between reportsSecurity leadOngoingSet a start dateCorrective actions; Next-period scope and datesOpen
0 of 5 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. This estimate assumes a Type 2 report. Check official dates and agree real durations with your team.

  1. 01

    Define the system and report

    Who Security lead + executive sponsor When Before engaging the auditor

    List services, data, infrastructure and vendors in the boundary. Choose report type and criteria with the CPA firm. Document how subservice organizations will be treated.

    How to do this step

    Before you start

    Customer commitments, service catalog, production architecture, hosting agreements and the list of delivery teams.

    1. Pick one customer transaction and trace it through your service, its databases, cloud accounts, support tools and outside providers. Include systems that can change or administer production.
    2. Write down what is in scope and record why each major exclusion is defensible. Ask the CPA firm how the description should treat cloud providers and what controls customers are expected to operate.
    3. Walk Legal, Engineering and Sales through the draft. Ask the firm to confirm the report type, categories, evidence period and scope as part of the engagement.

    What a reviewer should see

    The scope memo identifies the customer-facing service, legal entity, environments, vendors and agreed report period. A cloud account in the diagram can be traced back to the inventory and an owner.

    When to escalate

    Escalate if the report is expected to cover a product or location that Engineering left out, or if the requested customer date leaves insufficient time for the agreed observation period and fieldwork.

    What to produce

    Scope memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    System inventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

    Agreed engagementMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.

    Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.

  2. 02

    Map and implement controls

    Who Control owners When Before the report date or period

    Map criteria to controls and owners. Close gaps in access, change management, logging, incident response and supplier oversight. Draft the system description.

    How to do this step

    Before you start

    Approved scope, applicable Trust Services Criteria, system description draft and results from the first evidence walkthrough.

    1. Write each control as an action someone can perform. For quarterly access review, define which systems and privilege groups count, who exports the populations, who approves access and who closes removals.
    2. Configure recurring tickets and a backup owner. Perform one real run before the audit period. Keep the queries or filters and the source export so the team can establish completeness later.
    3. Give each gap an owner and due date. For anything that cannot be fixed before the planned start, record how it changes the design or bring the date question back to the CPA firm.

    What a reviewer should see

    An access-review ticket contains the dated list of privileged identities, reviewer decisions and links to removal tickets. Its group counts reconcile to the identity-provider export.

    When to escalate

    Raise controls that nobody can run during leave, controls built only on paper, or controls that depend on logs configured to expire before fieldwork.

    What to produce

    Control matrixSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Remediation trackerSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

    System description draftMemo

    Gather first

    • Approved scope and report period
    • Service commitments and system requirements
    • Architecture, data flows, controls and subservice organization decisions

    How to prepare it

    1. Start with how a customer uses the service. Name the service, principal commitments, system requirements and the people, infrastructure, software, procedures and data that deliver them.
    2. Describe the boundary and relevant controls in plain language. Explain the treatment of each subservice organization and any complementary controls expected of customers. Apply current AICPA description criteria with the CPA firm.
    3. Validate each section against the control matrix, diagram and actual operation during the report period. Ask management and the auditor to review the draft before freezing a version for examination.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Report boundary
    Hosted invoicing service in production, including its systems and operations.
    Commitment and requirement
    Only approved operators change production. Release control AC-03 documents approval routing.
    System components
    Billing API, database, identity provider, on-call procedures and hosting provider.
    Subservice organization
    Discuss hosting treatment with the CPA firm and record the chosen method and dependencies.
    Customer responsibilities
    Customer administrators assign their users appropriate roles and remove unused accounts.
    Period or as-of date
    Enter the report dates agreed with the firm and reconcile text to that period.

    Check before handing it over

    The draft agrees with the scope, service commitments and control matrix. Someone who uses the service can understand the boundary.

    Management owns the description. Send the approved version to the CPA firm for its examination.

  3. 03

    Operate controls and retain evidence

    Who Engineering + operations When Throughout the agreed Type 2 period

    Collect contemporaneous records from real control runs and preserve populations for sampling. Escalate missed controls and capture corrective actions.

    How to do this step

    Before you start

    Control calendar, access to source systems, observation dates and the secure evidence request list.

    1. Export the complete population for each period using documented filters and timezone. Keep the query or report parameters and a reconciliation to the source total before review or sampling.
    2. Separate originals from redacted copies. For selected items, attach the system record, timestamp, reviewer approval and remediation. Let the CPA firm choose its samples from the appropriate population.
    3. When a run is missed, open an exception with actual dates, systems affected and a corrective action. Record alternate evidence only when it existed at the time.

    What a reviewer should see

    A sampled production change links from the deployment population to the pull request, reviewer, approval time and deployment log. The approval can be shown to precede release.

    When to escalate

    Tell the project lead promptly if a population is incomplete or a control failed. Agree next steps with the CPA firm and retain the original records.

    What to produce

    Evidence indexSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Access reviewsSpreadsheet

    Gather first

    • Dated identity provider and production entitlement exports
    • HR and contractor roster
    • Review scope and role criteria
    • Ticketing access and an independent reviewer

    How to prepare it

    1. Use the inventory to list systems and privilege groups. Export a snapshot for each named group using the same cutoff timestamp. Preserve the queries and reconcile membership counts, including nested groups, shared accounts, service identities and break-glass access.
    2. Create one row per account and entitlement. Compare identity and job status with the authoritative roster. Have each system owner enter keep, remove or time-limited exception with their name, date and reason. Route self-approvals to a separate reviewer.
    3. Create a removal ticket for each revoke decision. After closure, compare the effective permissions with the original export and verify the user did not retain access through another group. Record exceptions with expiry and a follow-up owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Review and cutoff
    AR-2026-Q3, production billing, 2026-09-30 23:59 UTC
    Population and reconciliation
    Okta group report OK-712 and cloud role inventory CL-042. 28 people and service identities yielded 41 entitlement rows. Counts matched both exports.
    Account and entitlement
    operator-17, Production Billing Administrator through group prod-billing-admins
    Decision and reason
    Revoke. The employee transferred to Customer Support on September 23 and no longer performs billing deployments.
    Reviewer and time
    Maya Chen, Billing Systems Owner, 2026-10-02 14:20 UTC
    Removal and verification
    IAM-114 closed 2026-10-02 16:40 UTC. Follow-up role export CL-048 and effective-permissions check showed no remaining admin access.
    Exception owner and expiry
    None for this row. Two approved exceptions in the full review have owners and October 30 expiry.
    Evidence location
    Restricted assurance library, access reviews / 2026-Q3 / AR-2026-Q3, folder EV-021

    Check before handing it over

    The reviewer can reproduce group counts, trace each decision to an accountable person and confirm effective removal. Unclosed exceptions appear in the same review.

    The identity administrator files source exports, signed review and closure evidence as one packet. The control owner submits the packet reference through the CPA firm’s secure channel when requested.

    Change and incident populationsSpreadsheet

    Gather first

    • Authoritative ticket, event or transaction system
    • Exact scope, time zone and date window
    • Auditor’s population and sampling request

    How to prepare it

    1. Define what counts as one row and agree start and end cutoffs with the auditor. Export all in-scope activity, including failed or cancelled records when relevant.
    2. Save the query and export timestamp. Keep stable source IDs and reconcile totals to an independent report. Explain any legitimate exclusions.
    3. Give the full population to the auditor before sampling. Link selected items to underlying records as requested.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    CHG-0742
    Occurred at
    2026-09-22 15:08 UTC
    System and event
    Billing API, production deploy
    State
    Completed
    Evidence key
    Release job 7242, linked approval PR-881
    Population filter
    Production deploys, Jul through Sep 2026 UTC

    Check before handing it over

    The reviewer can reproduce the count and trace any selected item back to the original system.

    Transfer the export, query, reconciliation and any exclusions to the independent tester.

  4. 04

    Complete fieldwork and issue the report

    Who Independent CPA + management When After the period or as-of date

    Provide samples, respond to exceptions and confirm the accuracy of the description. Management signs its assertion and representation letter.

    How to do this step

    Before you start

    CPA request list, complete populations, management’s draft system description, vendor treatment and exception register.

    1. Assign one owner per request and answer evidence questions in the secure portal. Track requests you received, upload reference, owner, due date and reviewer feedback.
    2. Reconcile the final description and reporting dates to what actually operated. Walk management through exceptions, their effect on the description and the assertion before signing.
    3. Read the issued opinion and exception section with Legal and the lead. Record permitted recipients and approve the response Sales sends when a customer asks what the report covers.

    What a reviewer should see

    Management can locate the signed assertion, issued report, documented exceptions and distribution decision in one restricted location.

    When to escalate

    Send unresolved disagreements about dates, scope or exceptions to management and the CPA firm before the assertion is signed.

    What to produce

    Final system descriptionMemo

    Gather first

    • Approved system boundary
    • Architecture, data flows, controls and service commitments
    • Current reporting instructions or system plan template

    How to prepare it

    1. Explain who uses the system, the commitments it supports and how people, processes, software, infrastructure and data fit together.
    2. Walk through actual transactions or requests and identify the relevant controls and shared responsibilities. Cover dependencies and any criteria or requirements in the agreed template.
    3. Validate each section with the technical owner against live architecture, procedures and evidence. Lock the approved version and reconcile it to diagrams and control records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Service and objective
    Hosted invoice service receives orders, calculates amounts and sends PDF receipts.
    Boundary and inputs
    Accepted production order events, account identifiers and billing records
    How it works
    Payment result updates invoice status. Release pipeline deploys code with approval.
    Shared roles
    Customer controls user configuration. Hosting vendor manages physical infrastructure.
    Evidence and review
    Architecture v3, deployment records and service-owner review

    Check before handing it over

    The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.

    Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.

    Management assertionMemo

    Gather first

    • Final system description and agreed report dates
    • Evidence supporting management’s statements
    • AICPA example and the CPA firm’s current requirements

    How to prepare it

    1. Obtain the applicable illustration and instructions from the CPA firm. Confirm who can sign on behalf of management and which system, criteria and dates they will address.
    2. Reconcile the draft with the final description and applicable examination type. Document the evidence supporting each statement and resolve any known exceptions with management and the CPA firm.
    3. Send the reviewed version for management signature through the agreed channel. Keep the signed record alongside the exact version of the system description.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Examination type
    Type 2, period agreed with the CPA firm
    Named system and period
    Hosted invoicing service, agreed April to June dates
    Supporting records
    Final description v5, control evidence index and exceptions list
    Status before signature
    Management has reviewed all statements and open issues.
    Executed record
    Record signer, date and exact version received by the CPA firm.

    Check before handing it over

    The signer has reviewed the claims, period and supporting evidence. The actual assertion follows the CPA firm’s applicable wording.

    The CPA firm receives the signed assertion from management. Use this worksheet for preparation only.

    Issued reportIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

  5. 05

    Maintain controls between reports

    Who Security lead When Ongoing

    Track exceptions, evaluate scope changes and book the next examination around customer reporting needs.

    How to do this step

    Before you start

    Issued report, findings and exceptions, contract commitments, system change roadmap and upcoming assurance requests.

    1. Turn every finding into a ticket with a business owner, root cause, interim risk decision, fix and retest date. Publish the ongoing control calendar.
    2. Review scope changes when you move hosting, add a product, acquire a team or change how a key control operates. Ask the CPA firm whether they affect the next period.
    3. Agree the next period and customer coverage needs early. Keep evidence capture running while the next engagement is scheduled.

    What a reviewer should see

    The next-period memo records confirmed dates, boundary changes and any corrective action with the retest artifact and reviewer.

    When to escalate

    Bring forward a likely coverage gap, an exception that recurs or a major service change before the next reporting dates are committed.

    What to produce

    Corrective actionsSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

    Next-period scope and datesSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

Common questions

What is the difference between SOC 2 Type 1 and Type 2?

Type 1 examines whether the description is fairly presented and controls are suitably designed as of a given date. Type 2 also tests operating effectiveness over a specified period. Ask the report user what they need before agreeing the dates with a CPA firm.

AICPA · SOC suite of services (opens in a new tab)

Which SOC 2 evidence should we start collecting first?

Start with evidence you can only collect while controls are running, such as dated access reviews, periodic restore tests and change approvals. Save the complete source population, the review decisions and proof that exceptions were resolved.

Who writes the SOC 2 system description?

Management owns the description. Service owners supply the architecture and workflows, the compliance lead reconciles the controls, and management approves the version the CPA firm examines.

AICPA · SOC suite of services (opens in a new tab)
PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes