SEC Form 8-K Explained: A Software Engineer's Guide to Real-Time Material Event Disclosures in 2026

This article is for informational and educational purposes only and is not financial, investment, legal, or tax advice. The author is a software engineer who builds public-data aggregators, not a registered investment adviser, broker-dealer, CFA, or CFP. Consult a licensed financial advisor before making any investment decision. References to specific filings or filers are for illustration of public SEC documents, not endorsements.

Why 8-K Matters Before 10-K and 10-Q

When I started building FinanceTrackDaily on top of the SEC EDGAR API, my mental model of US disclosure was the same one most retail investors carry around: annual 10-K, quarterly 10-Q, proxy DEF 14A, done. After a few weeks of ingesting filing feeds for roughly 3,400 US-listed tickers, that picture rearranged itself. The form that lit up the pipeline most often, the one that moved prices after the bell, the one that engineers and quants pay closest attention to — was Form 8-K.

The reason is structural. 10-K is annual. 10-Q is quarterly. Both are scheduled disclosures, meaning the market generally knows roughly when they will land. Form 8-K is the SEC's real-time disclosure vehicle. Whenever a domestic US public company experiences a "material event," it generally has four business days to file an 8-K describing it. That short clock is what makes 8-Ks the highest-signal SEC feed for monitoring corporate change.

This guide walks through Form 8-K from an engineer's perspective: what the SEC defines as a material event, the 32 numbered disclosure items the form supports, how the filings actually look in the EDGAR feed, how I parse them on FinanceTrackDaily, and the surprisingly common edge cases that trip up first-time consumers of this data. It is not a buy/sell guide. It is a primer on a public-records API and the legal artifact behind it.

What Form 8-K Actually Is, Per the SEC

Form 8-K is officially titled "Current Report Pursuant to Section 13 or 15(d) of the Securities Exchange Act of 1934." The SEC's plain-English description, from the agency's own Fast Answers page, is that 8-K is "the report companies must file to announce major events that shareholders should know about." The General Instructions to Form 8-K, codified at 17 CFR 249.308, list the categories of triggering events and the timing rules.

Three properties are worth committing to memory before you touch the data:

• Filing window: generally within four business days of the triggering event. A handful of items (Regulation FD disclosures under Item 7.01, for example) have shorter or differently structured timing.
• Who files it: domestic US registrants reporting under Section 13 or 15(d) of the Exchange Act. Foreign private issuers do not file 8-K; they file Form 6-K under different rules — a separate filing covered in another article in this series.
• What it is not: 8-K is not a financial statement. It is an event notice. Earnings press releases routinely come attached as Exhibit 99 to an 8-K under Item 2.02, but the 8-K itself is the cover sheet and item-by-item narrative.

The 32 Numbered Items — A Working Map

Form 8-K is organized into nine sections, each subdivided into numbered items. Per the SEC's General Instructions to Form 8-K (current as of the 2026 edition I checked while writing this), the item list runs as follows. I am reproducing the full taxonomy because I have not found a single concise table of it anywhere outside the General Instructions themselves, and aggregator engineers tend to need it open on a second monitor.

Section 1 — Registrant's Business and Operations

• Item 1.01 — Entry into a Material Definitive Agreement
• Item 1.02 — Termination of a Material Definitive Agreement
• Item 1.03 — Bankruptcy or Receivership
• Item 1.04 — Mine Safety — Reporting of Shutdowns and Patterns of Violations
• Item 1.05 — Material Cybersecurity Incidents (added by the SEC's 2023 cybersecurity disclosure rule, effective for most registrants December 2023)

Section 2 — Financial Information

• Item 2.01 — Completion of Acquisition or Disposition of Assets
• Item 2.02 — Results of Operations and Financial Condition (this is where most earnings press releases live)
• Item 2.03 — Creation of a Direct Financial Obligation or an Obligation under an Off-Balance Sheet Arrangement
• Item 2.04 — Triggering Events That Accelerate or Increase a Direct Financial Obligation
• Item 2.05 — Costs Associated with Exit or Disposal Activities
• Item 2.06 — Material Impairments

Section 3 — Securities and Trading Markets

• Item 3.01 — Notice of Delisting or Failure to Satisfy a Listing Standard; Transfer of Listing
• Item 3.02 — Unregistered Sales of Equity Securities
• Item 3.03 — Material Modification to Rights of Security Holders

Section 4 — Matters Related to Accountants and Financial Statements

• Item 4.01 — Changes in Registrant's Certifying Accountant
• Item 4.02 — Non-Reliance on Previously Issued Financial Statements (the "restatement" item, also called a Big R or little r notice in audit slang)

Section 5 — Corporate Governance and Management

• Item 5.01 — Changes in Control of Registrant
• Item 5.02 — Departure of Directors or Certain Officers; Election of Directors; Appointment of Certain Officers; Compensatory Arrangements of Certain Officers
• Item 5.03 — Amendments to Articles of Incorporation or Bylaws; Change in Fiscal Year
• Item 5.04 — Temporary Suspension of Trading Under Registrant's Employee Benefit Plans
• Item 5.05 — Amendments to the Registrant's Code of Ethics, or Waiver of a Provision of the Code of Ethics
• Item 5.06 — Change in Shell Company Status
• Item 5.07 — Submission of Matters to a Vote of Security Holders
• Item 5.08 — Shareholder Director Nominations

Section 6 — Asset-Backed Securities

• Item 6.01 — ABS Informational and Computational Material
• Item 6.02 — Change of Servicer or Trustee
• Item 6.03 — Change in Credit Enhancement or Other External Support
• Item 6.04 — Failure to Make a Required Distribution
• Item 6.05 — Securities Act Updating Disclosure
• Item 6.06 — Static Pool

Section 7 — Regulation FD

• Item 7.01 — Regulation FD Disclosure

Section 8 — Other Events

• Item 8.01 — Other Events (the catch-all)

Section 9 — Financial Statements and Exhibits

• Item 9.01 — Financial Statements and Exhibits (typically references the Exhibit 99 press release and the Exhibit 104 cover-page Inline XBRL)

Counting strictly, that is 32 numbered items across nine sections. When you aggregate 8-K filings at scale, the distribution is heavily skewed. From my own pipeline observations across roughly 12 months of 8-Ks for ~3,400 US tickers, the items I see most often are 2.02 (earnings releases), 5.02 (executive departures and appointments), 7.01 (Reg FD), 8.01 (other), and 9.01 (the exhibit pointer). 1.05 (material cybersecurity incidents) is genuinely rare per ticker but extremely high-signal whenever it does fire, which is exactly why the 2023 rule was controversial when it landed.

How an 8-K Looks in the EDGAR Feed

From an engineering standpoint, EDGAR exposes 8-Ks through several entry points. The two I use on FinanceTrackDaily are the per-filer JSON submissions endpoint and the cross-filer RSS/Atom full-text feed. Both are documented on the SEC's developer page at sec.gov/edgar/sec-api-documentation.

A typical per-filer call looks like this:

GET https://data.sec.gov/submissions/CIK0000320193.json
User-Agent: FinanceTrackDaily/1.0 [email protected]

That returns the most recent 1,000 filings for the given Central Index Key (CIK) — leading zeros padded to ten digits is mandatory; the API silently misbehaves with shorter CIK strings, which is a tax I paid the hard way during my first import run. Inside the JSON, the filings.recent object is a column-store layout: parallel arrays for form, filingDate, accessionNumber, primaryDocument, and so on. To get only the 8-Ks, you zip the arrays and filter where form == "8-K".

The User-Agent header is not optional. The SEC's Fair Access policy requires a descriptive User-Agent that includes a contact email, and the EDGAR rate limit is 10 requests per second per source IP. Exceed it and you get a 403 with an HTML page telling you to slow down and identify yourself. I have hit this exactly once, on the day I forgot to put the throttle back after a local test, and it took roughly two minutes for traffic to resume after I lowered the rate.

Once you have a hit, the next step is downloading the filing index, then the primary document. The primary document for an 8-K is normally a file named like aapl-20250131.htm: the ticker, a hyphen, and the filing date, in the issuer's chosen format. The HTML contains the cover page (item checkboxes that mirror the 32-item map above) and the narrative for each triggered item. Exhibits hang off the same accession number in separate URLs.

Parsing the Item Triggers Reliably

The single most useful piece of structured information on an 8-K cover page is the set of item checkboxes. Programmatically extracting them is the difference between "we tagged this filing as 'something happened'" and "we tagged this filing as 'CFO departed and earnings released simultaneously.'" There are two parsing strategies I have used:

1. Regex over the narrative headings. Each item begins with a heading like Item 2.02 Results of Operations and Financial Condition. A pattern like r"Item\s+(\d\.\d{2})\s+([A-Z][^ ]+)" across the cleaned HTML catches them with ~98% recall in my experience.
2. Inline XBRL cover-page facts. Since 2019, 8-K cover pages have been tagged in Inline XBRL with the dei: namespace. The element dei:DocumentPeriodEndDate gives the event date, and a series of boolean items report which 8-K items were triggered. Pulling these from the iXBRL gives you 100% machine-readable item labels, at the cost of needing an iXBRL parser. I use arelle in batch mode for backfills and regex for live feed processing.

A combined approach — regex first, iXBRL reconciliation on a nightly cron — has worked well for me. The reconciliation step catches the small number of filings where amenders, supplements, or unusual formatting throw off the regex.

Item 1.05 — The Cybersecurity Item That Changed the Feed

The SEC's final cybersecurity disclosure rule, adopted July 26, 2023, added Item 1.05 to Form 8-K. The compliance date was December 18, 2023, for most registrants (smaller reporting companies got an extra 180 days). Under Item 1.05, a registrant must disclose a cybersecurity incident determined to be material, generally within four business days of the materiality determination — not of the incident itself.

From an engineer's perspective on the feed, the rule did three measurable things during 2024 and 2025:

• It created an entirely new filing tag that older 8-K corpora simply do not contain, so any longitudinal study has to handle the "before December 2023, Item 1.05 did not exist" cliff.
• It introduced a new ambiguity: "materiality determination date" is not the same as "incident date." Two 8-Ks can describe incidents months apart that were filed on the same day because the determinations happened to be made on the same day.
• It produced a small but real cluster of amendments. Item 1.05 explicitly contemplates 8-K/A amendments when information that was unknown at the original filing becomes available, and the SEC's own staff guidance has reinforced this. My pipeline now expects amendments and rebuilds the merged incident record rather than treating the original as canonical.

This is not investment commentary. It is a notice that if you ingest the 8-K feed, your schema needs columns to handle the cybersecurity item or you will lose information on the filings that arguably matter most.

How 8-Ks Show Up in After-Hours Price Action

One of the consistent observations from running aggregation on US equities is that 8-K filings cluster heavily in the after-market window. Issuers prefer to release earnings (Item 2.02) and CFO departures (Item 5.02) after the close so the market has time to digest before the next open. EDGAR timestamps the receipt; if you save the receipt time alongside the trading-day mapping, you can reconstruct which 8-Ks landed during regular hours, in the extended session, or overnight.

For pure educational engineering purposes — to be clear, again, not as a trading recommendation — building a pipeline that joins 8-K receipt timestamps to OHLC data is a useful exercise in understanding market microstructure. The SEC's Division of Economic and Risk Analysis has published several working papers using exactly this kind of join for academic research, and they are a more rigorous read than most retail finance commentary.

Common Aggregator Mistakes I Made (So You Don't Have To)

In rough order of how much time each cost me:

1. Treating 8-K/A as a separate filing instead of an amendment. The "/A" suffix means amendment; the original accession number is still the canonical event reference. I now key on the accession number's first eighteen characters and treat the /A as a revision in a versioned table.
2. Forgetting that CIKs map many-to-one with tickers over time. Spinoffs, name changes, and ticker reuses mean that historical 8-Ks for "AAPL" might belong to multiple CIKs if you look back far enough. The SEC's ticker.txt and company_tickers.json are the source of truth; I refresh both nightly.
3. Hardcoding the item list. I shipped the first version with the pre-2023 31-item map. Item 1.05 broke a regex assumption and threw silent KeyErrors for a week before I noticed. Now the item list comes from a config file with the effective date, and the parser switches based on filing date.
4. Believing the press release matches the 8-K narrative. Sometimes the Exhibit 99 press release says "record quarter" while the actual 8-K Item 2.02 narrative is a one-paragraph cross-reference. The numbers live in the exhibit. If you only parse the cover document, you miss them.
5. Skipping the index.json. EDGAR provides an index.json for every accession number that enumerates all files in the filing. Walking that index is far more reliable than guessing exhibit filenames.

Frequently Asked Questions

How many 8-Ks does a typical S&P 500 company file per year?

Based on my pipeline data over the trailing twelve months as of the time of this writing, the median S&P 500 issuer files between roughly 18 and 30 8-Ks per year, dominated by quarterly earnings (Item 2.02), Reg FD disclosures (Item 7.01), and director/officer changes (Item 5.02). This is an observation from my own aggregation, not an SEC-published statistic.

Is Form 8-K required for every material event?

Form 8-K is required for the specific triggering events enumerated in the General Instructions. Materiality is a legal standard set in part by US Supreme Court precedent (notably TSC Industries v. Northway, 426 U.S. 438), and what is material for one filer may not be for another. This is a legal question; if you need a definitive answer for a specific company, consult securities counsel.

Where do I get historical 8-K data without paying for it?

EDGAR is free. The EDGAR full-text search, the per-filer JSON submissions endpoints, and the bulk archive at https://www.sec.gov/Archives/edgar/data/ are all public. Paid providers add convenience layers (parsed item triggers, ticker mapping, alerts) but the underlying corpus is openly available.

Do private companies file 8-K?

Generally no. Form 8-K is for registrants reporting under Section 13 or 15(d) of the Exchange Act, which broadly covers public reporting companies. A purely private company with no public debt or equity registered does not file 8-K. Some private companies that have publicly registered debt do file 8-K, however.

How fast does the EDGAR feed publish a new 8-K?

EDGAR makes filings public effectively immediately after acceptance. The acceptance timestamp and the filing's appearance in the public index are very close together — typically within a minute. If you operate near real time, monitor the https://www.sec.gov/cgi-bin/browse-edgar?action=getcurrent&type=8-K feed.

What I Would Tell Past-Me on Day One

If I were starting an SEC 8-K integration over again, I would: (1) build the item-trigger parser before the storage schema, because the schema follows the items; (2) version the item list by effective date, not as a static enum; (3) treat amendments as first-class revisions; (4) save the raw HTML plus a hash, not just the parsed fields, so I can reparse without re-downloading; and (5) wire alerting on parse failures, because the 0.5% of filings that break your regex are the ones that matter.

None of this is investment advice. It is what running a free public-data aggregator on top of a forty-year-old US disclosure system actually looks like. The 8-K feed is one of the cleanest, most consequential, and most underrated free data sources on the internet, and engineers building anything that touches US capital markets should know it by heart.

Authoritative References

• SEC Fast Answers — Form 8-K: sec.gov/fast-answers/answersform8khtm.html
• 17 CFR 249.308 — Form for current report pursuant to Section 13 or 15(d) of the Exchange Act
• SEC EDGAR API Documentation: sec.gov/edgar/sec-api-documentation
• SEC final cybersecurity disclosure rule, adopted July 26, 2023: sec.gov/news/press-release/2023-139
• SEC Division of Economic and Risk Analysis (DERA) working papers: sec.gov/dera
• FINRA Investor Education: finra.org/investors

Final reminder: nothing in this article is a recommendation to buy, sell, or hold any security. SEC filings are public records. Reading them is a research activity, not an investment decision. If you want investment advice tailored to your situation, work with a licensed financial advisor or registered investment adviser, not an aggregator built by an engineer.