A freelance SOC 2 consultant gets a company ready for its SOC 2 examination: scoping the trust services criteria and system boundary, running the gap assessment, drafting policies that match how the team really works, organizing evidence, and keeping the auditor relationship clean. You never issue the report. A licensed CPA firm does that, and your work is what lets it go smoothly.
What the client is actually buying
Most companies that hire a SOC 2 consultant were pushed into it by a customer. A procurement team sent a security questionnaire, a deal stalled, and someone was told to "get SOC 2". The person who hires you is often an engineering lead or a COO who has never read a SOC 2 report and is not sure what an auditor will want to see.
That shapes the job. You are part project manager, part translator and part control designer. The client is not paying for a pile of templates. They are paying for someone who can tell them, early and plainly, what the auditor will test, what they already do that counts, and what has to change. Our post on contract SOC 2 and ISO 27001 consulting work in Canada covers how the work reaches you and how to set up. This one is about the work itself.
Scoping the trust services criteria and the system boundary
The first real decision is scope, and it is easy to get wrong in a way that costs the client months later. SOC 2 reports against the AICPA Trust Services Criteria. Security, the common criteria (CC1 to CC9), is always in. Availability, processing integrity, confidentiality and privacy are optional, and the right answer depends on what customers rely on the company for and what they are asking to see.
A good scoping conversation covers:
- Which criteria. Add availability when customers rely on uptime commitments, confidentiality when the company handles customer data under contractual confidentiality terms. Do not add privacy casually; it is a heavy set of criteria and many buyers do not ask for it.
- The system. Which product or service is in scope, which environments, which infrastructure, which people and which processes. The system description has to describe this boundary, so it needs to be real.
- Subservice organizations. Cloud providers, payment processors and other vendors that perform part of the service. Most small clients use the carve-out method, which means the auditor excludes the vendor's controls and the client relies on the vendor's own report. You need to know which vendors matter and whether their reports exist.
- Complementary user entity controls. Things the client's customers must do for the controls to work, such as managing their own user access. These go in the report, so draft them deliberately.
Gap assessment and the findings register
The gap assessment is where you earn trust or lose it. You walk the criteria, interview the people who own each area, look at the actual systems and configuration, and compare what exists against what an auditor would test. The output is a findings register, not a narrative report. Each finding should state the criterion it relates to, what you observed, why it matters, what the fix looks like in this client's environment, who owns it and how you will know it is done.
Look at evidence rather than taking the interview at face value. "We do access reviews" often means someone once looked at a list. Then sort the findings by what blocks the audit and what is merely good practice, because a busy team needs to know which items actually matter.
Policies that match practice
Every client wants to start with policies because they feel like progress. Policies are necessary, but the auditor tests whether the company does what its policies say. A policy that promises quarterly access reviews, annual penetration tests and documented change approval for every deploy creates three controls the client now has to evidence over the whole period.
Write policies after you understand the practice, and write them so they describe what the team will really do. If a startup deploys many times a day through pull requests with required review, the change management policy should describe that, not a change advisory board that will never meet. Keep them short, give each a named owner, and make sure the client reads them before approving them.
Evidence requests and how to run them
Evidence is where SOC 2 readiness turns into operations. For each control, you and the client agree what the evidence is, where it lives and who produces it. Good practice for a consultant:
- Build the evidence list from the controls, not from a tool's default library. Generic lists ask for things the client does not do and miss things they do.
- Ask for system-generated evidence where possible: exports, configuration screenshots with dates and context, tickets, logs. Auditors trust these more than documents written for the audit.
- Collect a sample early and review it yourself. If a screenshot cannot show the date, the system and the setting together, it will come back as an auditor request.
Compliance automation platforms help with collection and reminders. They do not judge whether evidence is sufficient. That is still yours.
Type I, Type II and the observation window
A Type I report covers whether controls are suitably designed and in place at a point in time. A Type II report covers whether they operated effectively over a period. Help the client choose based on what their customers will accept.
Once a Type II observation window starts, the work changes. Controls have to run on schedule and leave evidence every time: quarterly access reviews, onboarding and offboarding tickets, vulnerability scans and the follow-up, backup restore tests, vendor reviews, security training records, incident handling. Missing one occurrence can produce an exception in the report. A good consultant sets up a control calendar, checks in on recurring controls before they are due, and catches gaps while they can still be fixed. Our guide to operating a SOC 2 Type II observation window shows what that looks like from the client's side.
Auditor liaison, without becoming the auditor
You will spend real time with the audit firm: the kickoff, the request list, walkthroughs, follow-up questions, and the draft report review. Be useful to the auditor and clear about your role. You can explain the environment, point to evidence and help the client answer questions accurately. You cannot test controls on the auditor's behalf, and you should not coach staff to give answers that do not match reality.
Independence is the reason. A CPA firm that helped design and implement the controls cannot then examine them, which is why readiness and audit are separate engagements. Clients sometimes ask whether you can "just do the audit too". The answer is no, and the post on SOC 2 consultants versus auditors is a good thing to send them.
When the draft report arrives, check the system description against reality and make sure any exception wording and management's responses are accurate. Every customer will read them.
What clients push back on
The same objections come up on almost every engagement. It helps to have honest answers ready.
- "Can we just buy the platform and skip the consultant?" Some teams can, especially if someone inside has done it before. Explain what the platform does and does not do, and let them decide.
- "Do we really need MFA everywhere / background checks / a formal risk assessment?" Explain what the criteria ask for and what the auditor will look for. Then let the client choose the control design, including accepting a risk where that is a reasonable business decision.
- "Why can't the auditor tell us if we're ready?" Independence again. A readiness assessment is your job.
Never promise a clean report or a date the client cannot control.
Skills worth building
The consultants clients bring back tend to share a few skills:
- Reading the criteria well enough to explain them plainly.
- Cloud and identity fluency. Most evidence comes from AWS, Azure or Google Cloud, an identity provider, a code platform and a ticketing system. You do not need to be an engineer, but you need to know where settings live.
- Control design that fits small teams without inventing process for its own sake.
- Clear writing for findings, policies and the system description.
Credentials such as CISA, CISSP or ISO 27001 Lead Implementer help a CV get read. Clients and firms care more about whether you can show a findings register, a policy set and an evidence plan you would stand behind. If you are earlier in your career, the analyst tasks in contract GRC analyst work are a practical way in.
Where the TrazTech Associate Network fits
We run the TrazTech Associate Network, so weigh this accordingly. The Associate Network is how TrazTech brings independent practitioners into client work, and compliance readiness, including SOC 2, is one of its practices.
Associates are independent contractors, not employees, working remotely from Canada or the US, part-time or full-time. There is no exclusivity, so you keep your other clients. You need at least five hours a week, and if you are employed, your employer has to allow side work. There is no experience minimum, and newer associates are paired with a paid senior mentor.
Applying takes about five minutes. If you hold a verified credential such as CISA, CISSP or ISO 27001 Lead Auditor, you skip the simulated assessment. Otherwise you complete a simulated client engagement of about three hours of work, with 72 hours to submit. A selection call follows, then portal setup with the agreement signed online.
Work is offered as fixed-scope work orders. You see the scope and the fee before you accept, you can decline, and the fee is fixed per milestone and agreed before work starts. Payment goes out every Friday, by Interac e-Transfer or against your own invoice in CAD or USD. Larger engagements run as teams with a Lead, coverage checklists keep the work consistent, and a TrazTech Principal reviews and signs off every deliverable before the client sees it. Associates get paid Lead reviews, paid mentoring, referral bonuses, a TrazTech email address, a verified credential, and a path from Associate to Senior, Lead and the core team. Work follows client demand in your practice, so approval does not guarantee a volume of work. The careers page lists every practice.
Common questions about freelance SOC 2 consulting
Do I need to be a CPA to work as a freelance SOC 2 consultant?
No. Only a licensed CPA firm can issue a SOC 2 report, but readiness work, gap assessments, policy drafting and evidence preparation do not require a CPA designation. Many SOC 2 consultants come from security, IT audit or GRC backgrounds.
Can a SOC 2 consultant also be the client's auditor?
No. The audit firm has to be independent of the controls it examines, so the firm that designs and implements controls cannot then report on them. Keep readiness and audit as separate engagements with separate firms.
How long does a SOC 2 readiness engagement last?
It depends on the client's starting point, the criteria in scope and how quickly the team can fix gaps. A Type II engagement also covers the observation period, so a consultant may stay involved across several months of light, recurring check-ins.
Which certification helps most for SOC 2 consulting?
CISA is widely recognized for audit-facing work, and CISSP or an ISO 27001 credential also help. None is required. Practical evidence, such as a sample findings register or policy set, often carries more weight with firms that engage contractors.
What should a freelance SOC 2 consultant never promise?
A clean report, a specific opinion or an audit date outside the client's control. The CPA firm forms the opinion. You can promise a clear plan, honest findings and evidence that is ready when the auditor asks for it.
Take scoped SOC 2 readiness work as an independent associate. The TrazTech Associate Network offers fixed-scope compliance work orders, and you see the scope and fee before you accept. Applying takes about five minutes.
Apply to the networkSee the role