Free companion page

Companion page: How to Read an SEC Comment Letter

Free to print: The Reading Checklist: Forty Questions for Any SEC Comment Letter, from How to Read an SEC Comment Letter.

This page is free and needs no sign-up. It reproduces material from How to Read an SEC Comment Letter by Julian R. Sterling so you can print it or keep it open while you work.

To print it, use your browser's print button. Figures are as stated in the book; check the official source before relying on any of them.

The Reading Checklist: Forty Questions for Any SEC Comment Letter

Forty questions stand between reading a comment letter file and relying on it. They are the last pass, the one a reader makes before quoting the file to a client, putting it in an investment memo, writing it into a story or signing off a response. Each question takes one line to ask. Each comes with one sentence on why it matters. Each points back to the chapter that explains the ground beneath it.

The questions follow the order in which a file is usually read: the file as a whole, the staff's letter, the company's response, then the topics the staff presses most, and finally the way the review closes and becomes public. They work for any reader. A reporting manager uses them to test a draft response before it goes out. An audit committee member uses them to see what the company has promised. A buy-side analyst, a short seller or a financial journalist uses them to separate what the file shows from what it only suggests. Throughout, the case of Oakhanger Logistics and Lytchett & Wrayford serves as the worked example, and Chapter 11 tells it whole.

None of the questions asks whether a disclosure complies with a rule, or how a review should end. They ask what the documents say, what they leave out, and where to look next.

The file (questions 1 to 5)

Before reading any single letter, a reader establishes what the file contains and how it is put together (Chapters 1 and 10).

  1. Which filings did the staff review, and did the letter limit its review to part of them? Why: the scope line tells the reader where the staff looked and, by omission, where it did not.
  2. Are all the staff's letters and all the company's letters present, in date order? Why: a missing round changes the meaning of every answer that follows it.
  3. Is there an extension request, and did the company meet the date it committed to? Why: a promise kept or missed is one of the few signals of pace the public file gives.
  4. Does any letter mention material sent supplementally or under a confidential treatment request? Why: an answer that rests on unseen material can be read only as far as the letter around it.
  5. When did the review close, and when did the file become public? Why: the gap between the two tells a reader how old the story already is.

The staff's letter (6 to 11)

The staff's letter is the starting point of every file, and its structure carries meaning of its own (Chapter 2).

  1. How many comments are there, and how are they grouped by filing and by topic? Why: the number and spread of comments show which parts of the filing drew attention.
  2. Is each comment a request for information, a request to revise, or both? Why: a request to be told something and a request to change something call for different kinds of answer.
  3. Which comments ask the company to tell the staff something, and which ask it to show the analysis? Why: a request for analysis signals that the staff wants to see the reasoning, not just the conclusion.
  4. Does any comment cite a specific rule, item or interpretation, and which one? Why: the citation tells the reader which framework the staff is reading the disclosure against, as the staff's own view.
  5. Does any comment ask about future filings rather than the filing reviewed? Why: a forward-looking request suggests the staff is looking for a change going forward rather than a correction of the past.
  6. Who signed the letter, and whom does it invite the company to call? Why: the roles named show whether the comments are mainly accounting questions, disclosure questions or both.

The response (12 to 17)

The response is the company's own document, and it shows what the company chose to concede, explain or contest (Chapter 3).

  1. Does the response repeat each comment before answering it? Why: a response that answers comment by comment lets the reader match every reply to its question.
  2. For each comment, did the company accept, explain or push back? Why: the triage reveals where the company was confident and where it gave way.
  3. Where the company agreed, is there an illustrative revised disclosure, and in which filing is it promised? Why: a promise without a draft or a date is harder to check later.
  4. Did the company offer to amend a filed report, or only to revise future filings? Why: the choice between the two shapes how a reader treats the reported figures already in the market.
  5. Where the company pushed back, what argument did it give, and which facts support it? Why: a push back built on one characteristic leaves the others open to a follow-up.
  6. Who signed the response, and does it say who reviewed it? Why: the signatures tell a reader which officers have put their names to the answers.

Non-GAAP measures (18 to 22)

Non-GAAP measures draw frequent comments, and the questions follow the reconciliation line by line (Chapter 4).

  1. Which adjustments did the staff question, and are they cash costs of running the business? Why: an excluded cost that recurs as part of operations is the kind of adjustment a reader should test first.
  2. Are any charges described as non-recurring, and did they recur in earlier years? Why: a label contradicted by the company's own history is a point a reader can test in minutes.
  3. Is the tax effect of the adjustments shown on its own line or netted? Why: a netted line hides how much of the adjusted figure comes from tax.
  4. Does the earnings release lead with the non-GAAP measure or with the GAAP figure? Why: prominence is a question of order and emphasis as much as of numbers.
  5. What did the company agree to change, and does the change move the headline measure? Why: an agreement that lowers the measure tells a reader what the old figure was carrying.

MD&A (23 to 27)

MD&A comments ask whether the narrative explains the numbers or merely restates them (Chapter 5).

  1. Does the results discussion quantify each reason it gives for a change? Why: a cause without an amount gives a reader nothing to model.
  2. Are there known trends or uncertainties the response now discloses that the filing did not? Why: a trend added after a comment is information the market lacked when the filing was made.
  3. Does the liquidity discussion explain a change in operating cash flow, or only repeat the cash flow statement? Why: an explanation tells a reader whether the change is likely to persist.
  4. Does the response mention a customer, contract or market condition for the first time? Why: a new concentration or a pending renegotiation can matter more than any number in the original filing.
  5. Are the critical accounting estimates described with their key assumptions and their sensitivity? Why: an estimate disclosed without its assumptions cannot be stress-tested by an outside reader.

Revenue and segments (28 to 32)

Revenue and segment comments go to how the company draws the lines in its own financial statements (Chapters 6 and 7).

  1. Where revenue is reported gross, does the response explain why the company is the principal? Why: the answer can change the size of the top line without changing operating income.
  2. Does the revenue note break revenue down the way management describes the business? Why: a single line covering several kinds of service hides the mix a reader needs.
  3. What does the chief operating decision maker review, and does the segment note match it? Why: a gap between the management package and the note is the starting point of most segment comments.
  4. If operating segments are aggregated, do their margins and cost structures look alike? Why: similar customers do not make similar economics, and the numbers show which is which.
  5. Are significant segment expenses named in the note, and will segments be recast? Why: named expenses and recast periods change what an analyst can compare from year to year.

Impairment, acquisitions and registration reviews (33 to 36)

These questions cover estimates that rest on fair values, the filings an acquisition can trigger, and the special timing of a registration review (Chapters 8 and 9).

  1. For any reporting unit with a thin cushion, are the cushion, the goodwill and the key assumptions disclosed? Why: a statement that fair value exceeds carrying amount says nothing about how close the two are.
  2. Does the sensitivity move every key assumption, and how far must each move to erase the cushion? Why: a table that moves only one input shows only part of the risk.
  3. For an acquisition, how were the significance tests computed, against which year's figures, and with which component? Why: the computation decides which financial statements of the acquired business must be filed.
  4. In a registration review, when did drafts become public relative to the road show and to effectiveness? Why: the timeline shows what investors could read before the offering and what came out only afterward.

Confidentiality, completion and publication (37 to 40)

The last questions concern what the public file leaves out and how the review ends (Chapter 10).

  1. Was confidential treatment requested, and for which pages and which comment? Why: a reader should know exactly which part of the answer stays out of view.
  2. Did the review end with a completion letter or with effectiveness, and what does that letter say? Why: a completion letter closes a review; it does not approve the filing.
  3. Does the next annual report disclose unresolved staff comments, and are the review dates consistent with that? Why: unresolved comments that must be disclosed tell the market a disagreement is still open.
  4. Did any staff letter defer the review because the filing was seriously deficient? Why: such a letter becomes public early and signals a review that has paused, not one that has closed.

Run on Oakhanger's file, the list moves fast through the file, the letter and the response. The questions that take longest are the ones that need numbers from two places: the reconciliation against the release, the management package against the segment note, the sensitivity against the cushion. That is deliberate. A comment letter file rewards a reader who puts documents side by side, and the questions are built to force that comparison.

On the reading desk

Key Takeaway: Forty questions in eight groups take a reader from the shape of the file to the staff's letter, the response, the topics the staff presses most, and the way the review closes and becomes public. Each question points to the chapter that holds its rules. Run them in order, put documents side by side wherever two figures meet, and treat anything supported only by unseen material as unverified.