How to Read a Going-Concern Footnote in a 10-K

Locating and interpreting the warning language buried in the audit opinion, the notes, and the MD&A — before it becomes a corporate default event.

A going-concern footnote in a 10-K is not a disclosure most issuers volunteer prominently. It sits in the audit opinion, reappears in a liquidity note buried deep in the financial statements, and echoes again in the MD&A and Risk Factors — easy to miss if you don't know where to look. For anyone running a distress screen or tracking the precursors to corporate default events dataset entries, reading the footnote correctly is a foundational skill. This post walks through where the language appears, what the trigger phrases mean, how to separate disclosed conditions from mitigation plans, and why the auditor's conclusion and management's assessment are legally distinct.

Where the going concern footnote 10-K language actually lives

Going-concern disclosure is not concentrated in one place. It typically surfaces across three distinct sections of the filing, and you need to read all three together.

• The audit opinion — explanatory or emphasis-of-matter paragraph. Under PCAOB AS 2415 and its AICPA predecessor, the auditor is required to include an explanatory paragraph when substantial doubt exists. It appears immediately after the opinion paragraph or as a separate section labeled "Substantial Doubt About the Company's Ability to Continue as a Going Concern." This is the most authoritative signal: the auditor's voice, not management's.
• Notes to Financial Statements — liquidity and going concern note. Management's version of the same disclosure appears here, typically as one of the first substantive notes or within the Summary of Significant Accounting Policies. It is usually the most detailed: quantified cash balances, upcoming debt maturities, covenant status, and the mitigation plan. Under ASU 2014-15, management is required to evaluate and disclose going-concern conditions regardless of whether the auditor concurs.
• Risk Factors and MD&A liquidity discussion. The Risk Factors section often carries a standalone risk about the ability to continue as a going concern, and the Liquidity and Capital Resources section of MD&A repeats the substance in narrative form. These sections add color but are generally less precise than the note itself.

EDGAR full-text search (discussed below) is the fastest way to confirm whether any of these sections contain the language.

The trigger phrases to search for

Under ASU 2014-15 (codified at ASC 205-40), the operative standard term is "substantial doubt about the entity's ability to continue as a going concern." Auditing standards use slightly different phrasing — AS 2415 refers to "substantial doubt about [the entity's] ability to continue as a going concern" following evaluation of "conditions and events." In practice, the language clusters around a small set of phrases:

• "substantial doubt" — the required phrase under ASC 205-40; if you see this in a 10-K note, you are in the going-concern disclosure
• "ability to continue as a going concern" — the full statutory phrase; appears in both the note and the audit opinion
• "conditions and events that raise substantial doubt" — the auditing-standard formulation
• "alleviated" or "not alleviated" — qualifiers that tell you whether management believes its plans resolve the doubt
• "material uncertainty" — the IFRS equivalent (IAS 1.25); not standard in U.S. 10-K filings but appears in cross-listed issuers

The presence of "substantial doubt" alone is significant. The modifiers matter too: "substantial doubt exists and has not been alleviated" is worse than "substantial doubt was raised but management's plans alleviate it."

Disclosed conditions vs. management's mitigation plans

The note is usually structured in two parts, and they should be read separately.

The disclosed conditions are the objective facts that triggered the evaluation. Common ones:

• Recurring net losses and negative operating cash flows
• Negative working capital (current liabilities exceeding current assets)
• Debt maturities within twelve months of the balance-sheet date with no committed refinancing
• Covenant violations or waivers on existing credit facilities
• Dependence on a single customer, contract, or regulatory approval that is uncertain

The mitigation plans are management's response — what they say they will do to address the conditions. These typically include equity or debt financings, asset sales, cost reduction programs, deferred capital expenditures, or renegotiated credit terms. Judging credibility requires asking: Is the financing already committed (a signed term sheet or executed agreement) or merely contemplated? Has the company successfully raised capital recently, or does it have a history of failed raises? Are cost cuts quantified, and are they enough to close the gap? Are asset sales dependent on third-party buyers in an illiquid market? Plans described in vague terms ("we are exploring strategic alternatives") provide no assurance. Committed capital — particularly a signed credit facility or a completed equity offering, for which reading a 424B5 filing is directly relevant — is a meaningful distinction.

The management-vs-auditor distinction under ASU 2014-15

Before ASU 2014-15 became effective (fiscal years ending after December 15, 2016), going-concern evaluation was primarily an auditing standard obligation. ASU 2014-15 shifted the primary burden to management: under ASC 205-40, management must now evaluate whether conditions and events raise substantial doubt within twelve months of the financial-statement issuance date, and if so, whether its plans alleviate that doubt.

The result is that the note and the audit opinion can diverge. Management may conclude that its plans alleviate the substantial doubt and disclose that conclusion in the note without requiring an explanatory paragraph from the auditor. In this case, the note will describe the conditions and the plans but conclude that doubt has been alleviated. Conversely, if the auditor disagrees — or if management itself concludes that doubt has not been alleviated — the explanatory paragraph appears in the audit opinion. An audit-opinion paragraph is the more severe signal. If both management's note and the audit opinion contain going-concern language, the situation is unambiguous.

This framework is explored in more detail in the overview of going-concern qualification and how it interacts with auditor reporting standards.

Full-text searching EDGAR at scale

EDGAR's full-text search (efts.sec.gov) allows queries against the text of all filed documents. Searching for "substantial doubt" filtered to form type 10-K and a date range returns all annual filings containing the phrase. For a given issuer, you can confirm in seconds whether a going-concern note exists without reading the entire filing.

At scale, parsing this language across thousands of filings requires either an extraction pipeline or a structured dataset. Key fields worth extracting:

Field	Why it matters
Doubt alleviated (yes/no)	Management's formal conclusion under ASC 205-40
Audit opinion paragraph (yes/no)	Auditor concurrence; the more severe outcome
Conditions disclosed	Nature of the triggering facts — debt maturity vs. cash burn vs. covenant
Plan type	Committed financing vs. contemplated; asset sale vs. cost cut
Twelve-month lookforward date	The evaluation window specified in the note

How going-concern language feeds a distress screen

A going-concern note is a leading indicator, not a coincident one. The audit opinion is issued months after the balance-sheet date, but the conditions it reflects — covenant breaches, cash burn rates, debt maturities — were accumulating well before. For a distress screen, the note provides several inputs:

1. Event flag. The first appearance of going-concern language in a filing series is a discrete signal. Tracking the date of first disclosure against subsequent credit events or restructurings establishes the lead time.
2. Severity gradation. "Substantial doubt not alleviated" plus an audit-opinion paragraph is qualitatively worse than "substantial doubt alleviated by management's plans." Screens that treat all going-concern disclosures identically lose resolution.
3. Condition type. A company with a debt maturity in six months and no committed refinancing faces a hard deadline. Recurring losses with no near-term maturity are a slower-moving problem. The disclosed conditions determine urgency.
4. Plan credibility. Committed vs. speculative plans inform the probability distribution of outcomes. A signed credit facility from a commercial bank is evidence; "we intend to raise equity capital when market conditions permit" is not.

Structured event data linking going-concern disclosures to downstream default and restructuring outcomes — as captured in the corporate default events dataset — allows this lead-time and severity analysis to be run systematically rather than filing by filing.