SEC Comment Letter Response Best Practices: Close the Review in One Round

Most companies treat an SEC comment letter as a compliance task. The ones that close reviews in a single round treat it as a strategic document. The difference shows in the response letter itself.

This guide is for CFOs, controllers, and securities counsel who want to understand not just the procedural checklist but the decision architecture inside a well-crafted response: when to concede, when to push back, how to use a phone call strategically, and how to write a public document that doesn't hand plaintiffs' counsel a gift.

Key takeaway: The quality of your initial response largely determines whether the review closes in one round or drags into months of back-and-forth. Every choice in drafting should serve that goal.

What Is an SEC Comment Letter and What Does the Staff Actually Want?

An SEC comment letter is a disclosure-improvement tool, not an enforcement action. The Division of Corporation Finance's stated purpose is to "assist the issuer in its compliance with applicable disclosure requirements and enhance overall disclosure in the filing." Understanding this framing changes how you respond.

The staff can make four distinct types of requests, and identifying which one applies is the first decision you need to make:

Many companies get this wrong by treating every comment as requiring an immediate amendment. Agreeing to revise "in future filings" when the staff expects an immediate amendment is equally problematic. Read the comment carefully: the verb tense and phrasing usually signal which type applies. When in doubt, call the staff reviewer to clarify before committing to a written position.

Comments "set forth staff positions and do not constitute an official expression of the SEC's views" and are "limited to the specific facts of the filing in question." That legal nuance matters for how you frame your response, as discussed below.

The 10-Business-Day Deadline and How to Handle Extensions

The standard response window is 10 business days from the date of the comment letter. The letter will typically name the staff reviewer and state the deadline explicitly.

A few practical points on timing:

• Request an extension early, not at the deadline. If 10 days is not realistic, call the staff reviewer as soon as you know. Extensions of a week or two are routinely granted for reasonable requests. For transaction-related filings (IPOs, S-4 mergers), the letter may not specify a deadline, but if you take longer than 90 days to respond, the staff may treat the review as effectively restarting and take up to 30 days to review your response.
• Extensions are not a sign of weakness if the request is reasonable and made promptly. What signals weakness is scrambling to file an incomplete response on day 10 and then needing a second round to fix it.
• For S-1 registration statements, the stakes are higher. The SEC staff will not accelerate the effective date until all comment letter issues are resolved and any confidential treatment applications are complete. A delayed response directly delays your IPO timeline.

Once the review is complete, the entire correspondence thread, including your response letters, becomes public on EDGAR no sooner than 20 business days after the staff completes its review. Plan your drafting accordingly.

How to Structure the Response Letter

The standard structure is non-negotiable and exists for good reason. Deviating from it slows the review because staff must hunt for your answers.

Follow this format, as illustrated in real EDGAR CORRESP filings including the Forum Energy Technologies S-1 response:

1. Opening paragraph: Identify the filing under review, the date of the staff's comment letter, and confirm that you are responding to each numbered comment.
2. Reproduce each comment verbatim in bold or italic, numbered to match the staff's letter.
3. Respond immediately below each comment. Do not group responses or refer the staff to a different section of your letter.
4. Cite specific page numbers in the amended filing where responsive disclosure can be found. Use language like: "Please see page 47 of Amendment No. 1, under 'Critical Accounting Estimates.'"
5. Address every sub-point. The staff's own instruction, embedded in comment letters, is explicit: "If a numbered comment in this letter raises more than one question or lists various items in bullet points, ensure that you fully respond to each question and bullet point."
6. Closing paragraph: Confirm that the company acknowledges its obligations and that the response is complete.

For S-1 reviews, file the response letter (as a CORRESP on EDGAR) simultaneously with the amended registration statement, and provide the staff with a marked copy showing all changes. This concurrent approach, demonstrated in the Palo Alto Networks S-1 response, accelerates the review cycle by giving staff the revised document at the same time as the written explanation.

The Parallel Changes Rule: The Most Common Trigger for Round Two

Failing to make parallel changes across all affected sections is the single most common reason a company receives a second round of comments on the same issue.

The staff's instruction is direct: "Where comments on a section also relate to disclosure in another section, please make parallel changes to all affected disclosure. This will eliminate the need for us to repeat similar comments."

In practice, this means:

• If a comment on your MD&A requires you to add quantitative sensitivity analysis to your critical accounting estimates discussion, check whether the same information is missing from your financial statement footnotes and your risk factors.
• If a comment on your segment reporting requires you to revise how you describe your chief operating decision maker's review process, check every place in the filing where that process is described.
• Before filing, run a search of the amended document for every term related to the comment topic and confirm that each instance is consistent with your response.

A response that fixes the flagged section but leaves the same deficiency in three other places will generate an identical comment in round two.

When to Push Back vs. When to Concede

This is the hardest decision in the process, and almost no published guidance addresses it directly.

The threshold for pushing back on a technical accounting position is whether you have a well-supported, literature-grounded argument that the staff has misread the standard or misapplied it to your facts. As Gibson Dunn partner Brian Lane has put it: "The best way to shut down a review is to say 'we looked at paragraph X and sub-paragraph Y, and we think we followed precisely what GAAP requires.'" Citing the specific codification paragraph is not optional, it is the argument.

A practical decision framework:

• Concede and revise when the staff's comment reflects a genuine disclosure gap, even if you believe the underlying accounting is correct. Improving disclosure costs you nothing and closes the comment.
• Commit to future-filing changes when the staff's comment is about presentation or completeness and does not require an immediate amendment. Be specific: name the filing and the section where the change will appear.
• Push back respectfully when you have a clear technical accounting basis for your position. Cite the ASC paragraph, explain the facts-and-circumstances analysis, and note your auditor's concurrence.
• Escalate to a call before putting a complex pushback in writing. Pre-clearing a position on the phone avoids committing to language that the staff then formally rejects in a second comment letter.

When you do push back, the framing matters. There is a significant difference between these two approaches:

• Capitulation framing (avoid): "We acknowledge the Staff's comment and will revise our disclosure in future filings."
• Respectful disagreement framing (use): "We respectfully advise the Staff that we believe our current disclosure is consistent with ASC [X-XX-XX-X] because [specific facts and circumstances]. We have discussed this position with our independent auditors, who concur. We are happy to discuss further at the Staff's convenience."

The second framing signals confidence, grounds the position in authority, and offers dialogue without appearing adversarial. Adversarial or legalistic responses tend to prolong the process because the staff's goal is disclosure improvement, not winning a debate.

The Strategic Phone Call: When and How to Use It

Calling the staff reviewer before submitting a written response is one of the highest-value tactics in the process, and it is almost never explained in detail.

The call is not a debate. As securities practitioners consistently advise, the staff does not want to argue the merits on the phone. The call serves three specific purposes:

1. Clarification: If a comment is ambiguous about what the staff is actually asking for, call to understand the underlying concern before drafting. Responding to the literal question while missing the underlying concern is a primary trigger for follow-on comments.
2. Pre-clearing a complex position: If you plan to push back on a technical accounting issue, a preliminary call lets you gauge the staff's receptiveness before committing the position to writing. A written pushback that the staff formally rejects in a second comment letter is harder to walk back than a position explored in a phone conversation.
3. Scoping a sensitive topic: For comments that touch on litigation, M&A activity, or other market-sensitive matters, a call can help you understand how much detail the staff actually needs before you put it in a public document.

Before the call, prepare with your external auditors, your audit firm's national office, and outside securities counsel. Develop specific talking points. Do not read from a script, it reduces engagement. After the call, send a brief written follow-up confirming what was discussed, so there is a record.

For sensitive or market-moving topics, Sullivan and Cromwell's 2004 comment letter to the SEC explicitly recommended that "where the staff believes a comment may create significant public or investor relations or disclosure issues, it should consider first resolving or refining the comment through oral dialogue with the issuer." The call is not just acceptable, it is encouraged by sophisticated practitioners.

Writing a Response That Won't Become a Plaintiff's Exhibit

This is the gap that almost no published guidance addresses, and it is the one that keeps general counsel up at night.

Because CORRESP filings are public on EDGAR within 20 business days of review completion, every word in your response letter is a potential exhibit in a securities class action. Sullivan and Cromwell flagged this risk in 2004, recommending that the SEC add language to comment letters clarifying that "changes to disclosure in response to staff comments should not be interpreted as an admission that previous disclosure was defective." The SEC did not formally adopt this language universally, so the risk remains live.

Practical drafting principles for litigation-aware responses:

• Never characterize prior disclosure as wrong. Use language like "to provide additional clarity" or "to enhance the disclosure" rather than "to correct" or "to fix."
• Avoid volunteering information beyond what the comment asks for. Over-explaining opens new lines of inquiry with the staff and creates additional public record. Answer the question asked, completely and precisely, then stop.
• Do not make admissions about materiality. If a comment asks you to add disclosure about a risk, agreeing to add it does not mean you are admitting the risk is material. Your response can say: "We will revise our disclosure to provide additional detail, while noting that we do not believe this item is material to our financial statements."
• For commercially sensitive supplemental information, use Rule 83 (17 C.F.R. § 200.83) confidential treatment requests. File the request separately with the Office of Freedom of Information and Privacy Act Operations, and mark the EDGAR version with [***] placeholders for omitted portions, as Palo Alto Networks did in its 2012 S-1 response. Confidential treatment is not automatic, the staff can deny it, so do not assume protection without filing the request.
• For M&A transactions, be especially careful. Sullivan and Cromwell noted that premature disclosure of staff comments on a pending merger or acquisition could disrupt regulatory approvals and shareholder votes. The 20-business-day release window means your response could go public while the transaction is still live.

Coordinating Legal, Accounting, and Audit Teams

A disorganized response is a slow response, and an internally inconsistent response almost guarantees a second round.

The coordination model that works:

1. Assign a single quarterback (typically outside securities counsel) to own the response letter and ensure consistency across all sections.
2. Route accounting comments to the finance team and auditors immediately. For comments on critical accounting estimates, segment reporting, or revenue recognition, your auditor's concurrence with the proposed response is essential. The response letter should reflect that concurrence explicitly.
3. Loop in the audit firm's national office for complex technical accounting positions. Their sign-off strengthens the response and reduces the risk of the staff escalating.
4. Set internal deadlines that give the quarterback time to review all workstreams before the external deadline. A response assembled from disconnected drafts the night before filing will have gaps.
5. Do not rush. As SEC staff panelists noted at a 2023 conference summarized by KPMG FRV: "To make the comment letter process run smoothly, panelists suggested coordinating with your service providers." A thoughtful and complete response is more valuable than a fast but incomplete one.

2026 Hot Spots: What the Staff Is Focused On Right Now

The procedural best practices above are stable. The substantive content of responses shifts with SEC staff priorities. In 2025 and 2026, the areas generating the most comments include:

• Non-GAAP measures: Reconciliation completeness, prominence of GAAP measures, and whether non-GAAP adjustments are individually tailored or reflect recurring items.
• Critical accounting estimates: SEC Accounting Branch Chief Kevin Woody stated at a 2023 conference that CAE disclosure "should not be a repeat of the significant accounting policy disclosure in the financial statement notes" and must include "the degree to which the estimates and underlying assumptions have changed, and the sensitivity of the estimates to the methods and assumptions." This standard has only intensified since.
• Segment reporting post-ASC 280 amendments: The FASB's 2023 amendments to ASC 280 require significantly expanded segment disclosures. Staff comments are focusing on whether the chief operating decision maker identification and the segment profit or loss measure disclosed are consistent with how management actually runs the business.
• Cybersecurity incident disclosure: Item 1.05 of Form 8-K requires disclosure of material cybersecurity incidents. Staff comments are probing whether materiality determinations are documented, timely, and consistent with risk factor disclosures.
• AI risk factors: Staff is asking whether AI-related risk factors are specific to the company's actual AI use or generic boilerplate. See AI Disclosure in Your Q2 2026 Form 10-Q for the specificity standard the staff is applying.
• Tariff and macroeconomic MD&A: Item 303 requires quantification of known trends and uncertainties. With tariff impacts now a material factor for many companies, staff is pressing for specific quantification rather than generic risk language. See What Your Q2 2026 Form 10-Q Must Say About Tariffs for the current standard.
• SAB 74 disclosures on pending standards: Staff is asking whether companies have adequately disclosed the expected impact of recently issued ASUs not yet adopted. See SAB 74 Disclosure Requirements for the five required elements.

For each of these areas, the best preparation is to review CORRESP filings from peer companies in your SIC code on EDGAR before you file. Searching EDGAR by form type lets you see how similar comments have been resolved, which is far more useful than any generic checklist.

S-1 vs. 10-K vs. 10-Q: Where the Process Differs

The structural best practices above apply across all filing types. The strategic context differs materially:

For S-1 filings, the staff explicitly warns that "the effect of the price range on disclosure throughout the document may cause us to raise issues in areas on which we have not previously commented." First-time issuers consistently underestimate this risk. Build a buffer into your IPO timeline for a potential post-pricing comment round.

FAQ

Do we have to quote the staff's comment verbatim in our response? Yes. Reproducing each comment verbatim, numbered to match the staff's letter, is standard practice and makes the correspondence thread readable when it becomes public on EDGAR. Omitting the verbatim comment forces the staff to cross-reference two documents and slows the review.

What happens if we miss the 10-business-day deadline? The staff does not issue stop orders for late responses to periodic report comment letters. However, for S-1 registration statements, a delayed response directly delays effectiveness. For any filing, a late response without prior communication signals disorganization and can affect the staff's receptiveness. Always call the reviewer before the deadline if you need more time.

Can we request confidential treatment for supplemental materials? Yes, under Rule 83 (17 C.F.R. § 200.83). File the request separately with the Office of Freedom of Information and Privacy Act Operations and mark the EDGAR version with [***] placeholders. Confidential treatment is not automatic, the staff can deny it, so do not include commercially sensitive information in a response without filing the request.

How do we handle a comment that touches on pending litigation? Coordinate with litigation counsel before drafting. Avoid language that could be read as an admission of liability or materiality. Provide the disclosure the staff needs without characterizing the litigation's likely outcome. A preliminary call with the staff reviewer can help scope what level of detail is actually required.

Should we proactively revise other filings if a comment reveals a broader disclosure gap? Yes, if the gap is material. A comment letter is "limited to the specific facts of the filing in question and does not apply to other filings," but that does not protect you from a separate review of another filing with the same deficiency. Proactive remediation across all affected filings is both the right disclosure practice and a risk-reduction measure. See How to Prevent Repeat SEC Comment Letters for a systematic approach.

What is the best way to benchmark our response against peer companies? Search EDGAR for CORRESP filings in your SIC code on the relevant disclosure topic. The EDGAR full-text search displays up to 800 filings per search. Filter by form type (CORRESP), date range, and SIC code to find how companies in your industry have resolved similar comments. This is the most underused research tool in the process.