Nexeris

SOC 2 in Progress: How to Reassure Customers and Keep Deals Moving

A customer asking for your SOC 2 report does not always mean the deal has to stop if the report is still in progress. What matters is being transparent about where you are in the process, what security controls are already operating, and what evidence you can provide while the independent examination continues.

The strongest approach is specific rather than vague. Instead of saying SOC 2 is “almost done,” explain whether you are completing readiness work, operating controls during a Type 2 review period, responding to auditor requests, or waiting for the final report. That gives procurement and security teams something concrete to evaluate without overstating your current status.

What Can You Tell Customers While SOC 2 Is Still in Progress?

Customers usually want to understand two things: how mature your security program is today and how far you are from having independent assurance.

You can address both without implying that the audit is already complete.

Be Specific About Your Current SOC 2 Stage

Avoid simply saying, “SOC 2 is in progress.”

That could mean anything from starting a readiness assessment to completing auditor fieldwork.

A stronger update explains where the organization currently stands, such as:

  • SOC 2 readiness work is underway.
  • Controls have been implemented.
  • The Type 2 review period has started.
  • Auditor fieldwork is in progress.
  • The examination is in final report review.

Specific language makes it easier for a customer’s security team to understand what has actually been completed.

State Whether You Are Pursuing Type 1 or Type 2

Customers should also know which report you are working toward.

A Type 1 report evaluates controls as of a specified date. A Type 2 report also evaluates whether those controls operated effectively over a defined period.

Those reports provide different assurance, so saying only “we are working on SOC 2” may not give the buyer enough information.

Explain Whether Readiness, the Review Period, or Fieldwork Is Underway

Your current stage provides useful context.

During readiness, the organization is reviewing controls and addressing gaps. During a Type 2 review period, controls are operating and producing evidence. During fieldwork, the CPA firm is reviewing that evidence and testing controls.

This is more useful than telling customers the audit is “80% complete,” because percentages do not explain what work actually remains.

Confirm When an Independent CPA Firm Is Engaged

If a licensed CPA firm has been formally engaged, you can say so.

That is different from using compliance software or working with a readiness consultant. The independent CPA firm performs the SOC 2 examination and issues the final report.

Where confidentiality terms allow, evidence of the engagement can also help reassure customers that the formal examination is scheduled or underway.

How Should Your Message Change at Each Stage of SOC 2?

The information you provide should become more specific as the organization moves through the process.

Readiness and Gap Assessment Stage

During readiness, the organization is determining whether controls are appropriately designed, documented, and operating.

You can tell customers that SOC 2 readiness work is underway and explain that the company is reviewing its control environment and addressing identified gaps.

A structured gap assessment can help identify missing controls, documentation weaknesses, and evidence gaps before those issues reach the independent auditor.

Do not present a readiness assessment as though it were a completed SOC 2 examination.

Controls Implemented and Type 2 Review Period Underway

Once controls are operating and the Type 2 review period has begun, you can provide a stronger status update.

For example, you can explain that controls have been implemented, the Type 2 review period is underway, and the organization is collecting evidence that will later be evaluated by the CPA firm.

That shows meaningful progress without implying that the final report already exists.

Auditor Fieldwork in Progress

Once the CPA firm begins testing, tell customers that auditor fieldwork is underway.

At this point, the organization has moved beyond readiness and into the formal examination, but the auditor’s final opinion is still pending.

If the report is later issued, customer messaging should then be updated to identify the report type and the actual scope and period covered.

What Evidence Can You Share Before the SOC 2 Report Is Ready?

When customers ask for SOC 2, they are often trying to answer a broader question: can they trust your security program?

Several types of interim evidence may help answer that question.

Readiness Assessment or Gap Assessment Summary

A readiness or gap assessment summary can demonstrate that the organization has formally evaluated its control environment and is working through identified issues.

You do not necessarily need to provide every internal finding. A summary may be enough to explain the scope of the assessment, areas reviewed, and remediation status.

Detailed internal findings should be treated as sensitive information.

CPA Engagement Letter

An engagement letter can help demonstrate that an independent CPA firm has actually been retained.

Whether the complete document should be shared depends on confidentiality requirements and the firm’s terms.

A redacted version or other confirmation of the engagement may sometimes be more appropriate.

Security Policies, Controls, and Questionnaire Responses

Customers may request selected documentation covering access control, information security, incident response, business continuity, vendor management, employee responsibilities, or other relevant controls.

Good security policy development helps ensure those documents reflect how the organization actually operates rather than serving as generic audit templates.

The customer’s security questionnaire can also provide useful interim assurance. Answer questions based on the environment as it exists today, and clearly distinguish implemented controls from planned improvements.

Sensitive documentation should generally be shared under suitable confidentiality protections.

Penetration Test or Vulnerability Assessment Summary

Independent technical testing can provide another useful source of assurance.

The Trust Services Criteria do not explicitly require penetration testing, but customers often ask for evidence that technical controls and vulnerabilities are being evaluated.

A recent penetration testing executive summary can help demonstrate that weaknesses are being identified and addressed.

Detailed vulnerability information should not be distributed more broadly than necessary.

How Can You Keep a Deal Moving When the Customer Requires SOC 2?

Before assuming the deal is blocked, find out what the buyer actually means when it says SOC 2 is required.

Find Out Whether SOC 2 Is a Hard Requirement or a Security Review Requirement

Ask whether the requirement comes from a contract, procurement policy, customer security standard, or normal vendor due diligence.

Some organizations genuinely cannot approve a vendor without a current SOC 2 Type 2 report.

Others may accept alternative security evidence while the audit is underway.

That distinction determines what options are available.

Offer Interim Security Evidence Under NDA

If the customer is open to alternative evidence, offer selected security documentation under a nondisclosure agreement or through a controlled trust center.

This may include policies, testing summaries, questionnaire responses, architecture information, or evidence that a CPA examination is underway.

Complete the Customer’s Security Questionnaire Honestly

Do not approach the questionnaire as something that simply needs to be “passed.”

Answer accurately.

If a control is partially implemented, explain that. If remediation is underway, describe its current status when relevant.

An inaccurate answer discovered later can cause more damage to the deal than acknowledging a manageable gap upfront.

Offer a Security or Compliance Review Call

Some enterprise buyers are more comfortable approving an exception after speaking directly with someone who understands the organization’s security environment.

For organizations without a full-time internal security executive, virtual CISO support can help leadership explain security controls, risk decisions, remediation work, and the current SOC 2 status during customer reviews.

Discuss Contractual Security Commitments When Appropriate

In some cases, the buyer may be willing to proceed with specific security commitments in the contract.

These may address security controls, incident notification, delivery of the SOC 2 report when available, or other agreed requirements.

Legal counsel should review these commitments. Avoid promising a report date or security outcome the organization cannot control.

Keep the Buyer Updated as Your SOC 2 Stage Changes

Do not make the customer repeatedly ask whether progress has been made.

If you move from readiness into the Type 2 review period, from the review period into fieldwork, or from fieldwork to report issuance, provide an update.

Short, factual updates show progress without making unsupported promises.

Can SOC 2 Type 1 Help While You Work Toward Type 2?

In some situations, a Type 1 report can provide useful interim assurance.

When a Type 1 Report Can Provide Interim Assurance

Type 1 evaluates whether controls are suitably designed as of a specified date.

It can therefore provide independent assurance before the organization has accumulated enough operating history for a Type 2 report.

Why Some Customers Will Accept Type 1 Temporarily

Some buyers primarily want confirmation that the control environment has undergone an independent examination.

Those customers may accept Type 1 temporarily while the organization completes its Type 2 review period.

Whether that works depends on the customer’s internal requirements.

When the Customer Will Still Require Type 2

Other customers specifically want evidence that controls operated effectively over time.

For them, Type 1 may provide useful interim assurance but will not replace Type 2.

Confirm the customer’s requirement before completing Type 1 solely to unblock a particular transaction.

What Should You Avoid Saying While SOC 2 Is in Progress?

The way you describe your status matters.

Do Not Claim to Be “SOC 2 Certified”

SOC 2 is an attestation examination and report, not a certification issued to the organization.

Use precise language such as “we are undergoing a SOC 2 Type 2 examination” when that statement is accurate.

Do Not Claim You Have a SOC 2 Report Before It Is Issued

Completing readiness work, entering an observation period, or beginning fieldwork does not mean the report already exists.

Wait until the independent CPA firm has formally issued it.

Do Not Present Readiness Software as Proof of an Audit

Compliance software can help manage policies, evidence, controls, and integrations.

It does not provide an independent CPA opinion.

A dashboard showing that controls are complete is not a SOC 2 report.

Do Not Claim Type 2 When You Only Have Type 1

Type 1 and Type 2 are different reports.

A Type 1 report does not provide evidence that controls operated effectively throughout an observation period, so the terms should never be used interchangeably.

Do Not Promise a Report Date You Cannot Control

Your team controls much of the preparation work, but final timing can also depend on auditor availability, testing, follow-up requests, quality review, and report issuance.

Provide a target timeframe rather than guaranteeing a date that depends partly on another organization.

Do Not Hide Known Exceptions or Open Remediation Work

If a customer directly asks about a known issue, answer accurately.

A reasonable open remediation item can often be explained. Hiding it and having the customer discover it later creates a much larger credibility problem.

How Should You Talk About the Expected SOC 2 Timeline?

Customers may need a timeline for procurement planning, but that timeline should reflect the actual stage of the examination.

Give Stage-Based Updates Instead of Hard Dates

An update could say:

“Our Type 2 review period is underway. Auditor fieldwork will follow the end of the reporting period, after which the CPA firm will complete its review and issue the final report.”

This explains the remaining process without promising a date you cannot guarantee.

Explain the Type 2 Observation Period Clearly

A Type 2 examination requires controls to operate over a defined period.

That period cannot simply be removed because a customer needs the report sooner. The auditor needs evidence from the period to determine whether controls operated effectively.

Account for Auditor Fieldwork and Report Review

The end of the Type 2 observation period is not the report issuance date.

Auditor testing, follow-up questions, report drafting, quality review, management review, and final issuance can all occur afterward.

Some CPA firms perform testing during the observation period, which may reduce the amount of fieldwork remaining after it closes.

What Should You Put on Your Trust or Security Page While SOC 2 Is in Progress?

A trust page can communicate progress, but it should remain simple and accurate.

Current Status and Target Report

State whether you are pursuing Type 1 or Type 2 and identify the current stage when appropriate.

Examples include:

“SOC 2 Type 2 examination in progress.”

“SOC 2 Type 2 review period underway.”

Avoid badges or wording that could make visitors believe the report has already been issued.

Available Security Documentation and Review Process

Explain what qualified customers can request, such as selected policies, security questionnaires, penetration test summaries, or other due diligence documentation.

Provide a clear contact process and explain when an NDA is required.

Because customer assurance work continues after the initial report, ongoing compliance support can also help organizations maintain controls, documentation, and evidence instead of rebuilding them every time a customer requests information.

How Nexeris Helps Organizations Prepare for SOC 2 While Supporting Customer Reviews

SOC 2 preparation and enterprise sales often happen at the same time.

Organizations need to become audit-ready while still responding accurately to customers asking for security assurance today.

Readiness and Gap Remediation

Nexeris helps organizations evaluate the existing control environment, identify missing requirements, and prioritize remediation before formal testing.

Addressing these issues early reduces the risk of preventable audit delays.

Control and Evidence Preparation

Controls need to be implemented, responsibilities must be clear, and reliable evidence has to be available when the auditor requests it.

Nexeris helps organize controls, documentation, risk information, and evidence so teams enter the examination with a clearer understanding of their readiness.

Customer Security Review Support During the Audit Process

The period before report issuance can be challenging when prospects are already requesting security documentation.

Nexeris can help teams communicate their current SOC 2 stage, organize interim evidence, respond to customer security reviews, and prepare for the independent examination.

Using SOC 2 compliance consulting can help organizations move toward the final report while continuing to support the sales and procurement processes happening along the way.

FAQs

What Can You Say If Your SOC 2 Is Still in Progress?

State exactly where you are in the process.

You can say that SOC 2 readiness is underway, that the Type 2 review period has started, or that auditor fieldwork is in progress when those statements are accurate.

Avoid wording suggesting the final report already exists.

Can You Say You Are SOC 2 Compliant Before the Report Is Issued?

It is better to describe the actual examination status than make a broad claim that the organization is “SOC 2 compliant.”

The independent auditor’s opinion does not exist until the CPA firm issues the report.

What Proof Can You Give a Customer Before You Have a SOC 2 Report?

Depending on confidentiality requirements, you may provide readiness information, evidence of a CPA engagement, selected policies, questionnaire responses, penetration test summaries, control documentation, or a security review call.

The evidence should accurately reflect the current environment.

Can You Share a SOC 2 Readiness Assessment With Customers?

Potentially, but assess the sensitivity of the document first.

Readiness assessments can contain detailed weaknesses and remediation information. A summary or redacted version shared under NDA may be more appropriate than the complete assessment.

Can a SOC 2 Type 1 Report Help Keep a Deal Moving?

Yes, if the customer accepts Type 1 as interim assurance.

It can demonstrate that controls were suitably designed as of a specified date, but customers that require evidence of operating effectiveness over time may still require Type 2.

What Should You Do If a Customer Will Not Sign Without SOC 2 Type 2?

Confirm whether the requirement is truly non-negotiable.

If it is, explain the current audit stage and provide an accurate timeline. Unless the customer approves an exception or alternative evidence, the deal may need to wait until the Type 2 report is issued.

Should You Give Customers an Exact SOC 2 Completion Date?

Avoid guaranteeing a date you do not fully control.

Provide a realistic target timeframe and explain the current stage, remaining observation period, expected fieldwork, and report-review process.

When Can You Tell Customers That You Have a SOC 2 Report?

Once the independent CPA firm has formally issued it.

At that point, identify the report type accurately and make sure customer-facing claims match the scope and period actually covered.

Zach Tracy, Nexeris founder and CEO

Zach Tracy, CISA, CISSP

Zach Tracy is the CEO and a cybersecurity executive with more than 10 years of experience in security program management and regulatory compliance. He has served as a fractional Chief Information Security Officer for over 40 organizations and has led more than 100 audits across frameworks including SOC 2, CMMC, NIST CSF, ISO 27001, HIPAA, and HITRUST.

Zach specializes in helping defense contractors and regulated organizations build practical, audit-ready security programs that protect contract eligibility and reduce operational risk. He holds CISA, CISSP, CMMC-RP, and ISO 27001 and 9001 Lead Implementer certifications, along with a B.S. in Cybersecurity from Thomas College.

A Marine Corps veteran and former law enforcement officer, Zach brings a mission-focused, disciplined approach to cybersecurity leadership.

Connect with Zach on LinkedIn

Scroll to Top