Skip to content
SOC 2 Compliance Software

Home / Guides / The first 30 days on a compliance platform: a four-week operating plan

Guide, read 12 Nov 2026

The first 30 days on a compliance platform: a four-week operating plan

Open the glossarySee the ranked index

Days 1 to 7 go to connecting the systems that produce population lists

Start with the systems an auditor samples from: the identity provider, cloud accounts, source control, ticketing, the HR system and device management. Schellman lists what access controls should cover: production networks, server operating systems, databases, applications, and ancillary applications such as password safes or badge systems. Connect those first, because they produce the new hire, termination, access and change populations that every request list needs.

For each connection, record who approved it, the date, and which account the platform uses. Every integration is also a tool that supports the service, and Schellman's scoping guide says monitoring software, ticketing systems and logging tools belong in the description of the software component. A connection nobody can explain in week six becomes a question in the auditor's walkthrough.

The table lays out all four weeks. Days are calendar days from the start of the contract, and each row ends with an output you can show a colleague. If a row's output is missing at the end of its week, move the date for the later rows instead of skipping the output, because week three depends on what week one found.

WeekDaysWorkOutput at week end
11 to 7Connect identity, cloud, code, ticketing and HR; list systems the platform cannot reachConnection list with approver and date
28 to 14Set the boundary and service commitments; choose categories; tailor policies; name control ownersBoundary draft, approved policies, owner list
315 to 21Work failing tests in window order; run the first access reviewFailing-test list with owners and due dates
422 to 30Run an internal evidence check; confirm the window start and walkthrough dates with the auditorWindow start date in writing

Days 4 to 10 set the system boundary and the service commitments before policies

Write down what the service is. Schellman's five components give the outline: infrastructure, software, people, procedures and data, plus the boundary around them. Then list principal service commitments from contracts, service level agreements, privacy policies and public pages, which Schellman says drive the risk assessment and the choice of categories. If the commitments mention uptime, Availability may belong in scope; if they mention confidential data, consider Confidentiality.

Security is the one category every SOC 2 includes, per Schellman. For others, ask what you have promised and to whom. Schellman reports that many first reports include only Security, or Security plus Availability. Also name the subservice organizations: the cloud host and any vendor that handles in-scope data. Schellman's risk guidance says scope may also require identifying relevant subservice organizations, so list them before the auditor asks.

Change control starts here. Schellman says scope changes after the fact must be reported to the assessor immediately, and some are not allowed by the authoritative guidance. Treat the boundary document as a controlled record: date it, name the approver, and keep the earlier versions. A platform will hold whatever boundary you enter, so the decision to include or exclude a system needs a person's name against it.

Days 8 to 14 tailor policies to what the company does and assign named owners

Platform policy templates are starting text. Edit each one until it matches practice. Schellman says an access review procedure should be documented in a policy, with a frequency, and gives quarterly as a common practice and annual as the minimum. Choose the frequency you will keep, because the auditor tests against your policy, not the template. A policy promising monthly reviews that you run quarterly creates exceptions on its own.

Assign an owner to every control and every evidence item. Schellman's year 1 article says to plan evidence collection around the auditor's request list, naming what to collect and who provides it. Pick people, not teams. For each owner, ask the A-LIGN two-week question: how long would it take to produce this item? A day or two is healthy. About two weeks points to a manual process to fix first.

Tell the owners what the audit will ask of them. Schellman lists lack of knowledge about examination expectations as a common challenge and says sending staff in blind can create delays. A-LIGN advises getting commitments from engineering, IT and HR in writing before the window opens. A thirty-minute briefing in week two, with the list of items each person owns and the dates they fall due, covers both points.

Finish the week by locking the policy set. Record the approver and approval date on each policy, since an undated policy gives the auditor nothing to test against. Schellman recommends documenting procedures in enough detail to guide relevant personnel, and the same standard applies to the platform's tests: each test should map to a control, an owner and a policy sentence. Any test nobody can map to a control should be reviewed and either removed or explained.

Days 15 to 21 are for fixing failing tests in the order the window needs them

Sort failing tests by when they must pass. Schellman says controls must operate for the entire period of coverage, so anything that should run continuously, such as access removal or change approval, comes first. Annual controls come next, since evidence of a prior period does not count for the current one. Cosmetic items, such as a missing label on a device record, go last unless a policy ties them to a control.

Treat a failing test as a signal about a process. Schellman's exception guide recommends correcting the issue, identifying the root cause and building a remediation plan with responsible parties and timelines. Apply the same steps now, before any window exists. If the platform flags ex-employees with live accounts, revoke the access, find why the offboarding ticket missed them, and change the process, not only the account.

Run the first access review this week. Schellman describes the steps: assign a facilitator, obtain full user listings with privileges for each in-scope system, have administrators review privileged users, make corrective changes, and retain the extraction date, review date, reviewer names and approvals. A completed first review proves the procedure works and shows the owners what evidence looks like before the auditor requests it.

Keep a short log of each fix with the date and the person who made it. The log helps in two ways. It shows the auditor that the issue was corrected before the window opened, and it gives owners a record of what the platform checks. Schellman recommends identifying mitigating practices and root causes after an exception; a fix log shows you did that work before any exception existed.

Days 22 to 30 confirm the auditor schedule and open the window only when controls work

Contact the auditor you have selected and settle three dates: the window start, the walkthroughs and the expected report date. Schellman's year 1 article says scoping involves coordinating with service auditors on the covered system and the preferred period. Schellman puts readiness walkthroughs at about 1 week. Do not accept a start date that falls before your week 3 failures are closed.

Run an internal evidence check against the auditor's request list. A-LIGN describes this as a pre-audit: walk each item and ask whether the artifact exists, whether it closes a requirement or creates a gap, and how long it takes to produce. Record every item that fails the question. The result is the work list for the weeks before the window opens, and some items may justify a later start.

Close with a written start date. Schellman says its period decision hinges on whether sufficient evidence will exist, and that a shortened period can suit an organization that wants a Type 2 sooner. Share the date with owners, with the executive who signs the assertion, and with the customers waiting on the report. A date everyone knows is easier to defend than one held in the platform's calendar.

Last, confirm who attends walkthroughs. Schellman's readiness article describes walkthroughs as sessions where your procedures are shown to the service auditor, with gaps in coverage identified and communicated. Each control owner should be able to show their process live, from the platform if that is where the evidence sits. Schedule a rehearsal in the last week so first-time owners see the questions before the auditor asks them.

More guides

Sources

  1. Schellman: three steps for defining the scope of a SOC 2 audit, read 12 Nov 2026
  2. Schellman: how to perform a SOC 2 risk assessment, read 12 Nov 2026
  3. Schellman: what to expect from a SOC 2 readiness assessment, read 12 Nov 2026
  4. Schellman: year 1 versus recurring SOC 2 examinations, read 12 Nov 2026
  5. Schellman: periodic system access reviews, read 12 Nov 2026
  6. Schellman: how to determine your SOC reporting period and report validity, read 12 Nov 2026
  7. Schellman: four common SOC 2 challenges, read 12 Nov 2026
  8. Schellman: how to address a testing exception in a SOC report, read 12 Nov 2026
  9. A-LIGN: SOC 2 Type 2 playbook for first-timers, read 12 Nov 2026
  10. Schellman: the five Trust Services Categories, read 12 Nov 2026

Last reviewed 12 Nov 2026.