Form DEFS14A Files Dataset

The Form DEFS14A Files dataset is a collection of definitive proxy statements filed on EDGAR for special (non-annual) shareholder meetings under Section 14(a) of the Securities Exchange Act of 1934 and Rule 14a-6(b). Each record is one EDGAR accession-number folder packaging a structured metadata.json summary together with the original primary documents — the proxy statement itself plus any narrative or legal exhibits filed alongside it. The dataset is filed by registrants whose securities are being voted, including domestic operating companies, closed-end funds and business development companies, REITs and MLPs, and acquirers and targets in business combinations requiring a holder vote. Coverage runs from January 1994 through the present, mixing early ASCII/SGML-era filings with modern HTML-based submissions, and is distributed as monthly ZIP containers that include TXT, JSON, HTML, and PDF files.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures the population of definitive special-meeting proxy statements (form code DEFS14A) submitted to EDGAR by U.S. registrants, packaged one filing per accession-number folder inside monthly ZIP containers. The underlying form is the final, voting-ready version of the document that a registrant disseminates to security holders to solicit their proxies on matters that fall outside the ordinary annual-meeting cycle. The matters disclosed cluster around extraordinary corporate transactions and governance events: mergers, acquisitions, asset sales, going-private transactions, reorganizations, recapitalizations, charter or bylaw amendments, name changes, reverse stock splits, plans of liquidation or dissolution, and — for registered investment companies — fund reorganizations, advisory-contract approvals, and changes to fundamental investment policies.

The substance of each filing is governed by Schedule 14A under the Exchange Act, which prescribes the line-by-line informational requirements through its numbered Items (Item 1 — Date, time and place; Item 2 — Revocability of proxy; Item 3 — Dissenters' rights of appraisal; Item 4 — Persons making the solicitation; Item 5 — Interest of certain persons in matters to be acted upon; Item 6 — Voting securities and principal holders; Item 7 — Directors and executive officers, where applicable; Item 14 — Mergers, consolidations, acquisitions and similar matters; Item 19 — Amendment of charter; Item 20 — Other proposed action; Item 22 — Information required in investment-company proxy statement). When a transaction triggers it, Schedule 14A also pulls in large blocks of Regulation S-K and Regulation S-X content — Risk Factors, MD&A, audited and pro forma financial statements, fairness opinions, and background-of-the-transaction narratives. As a result, a single DEFS14A can range from a short fund-policy proxy of a few dozen pages to a merger proxy that runs hundreds of pages with multiple appendices.

The "definitive" qualifier distinguishes this form from PRES14A (preliminary special-meeting proxy) and from DEF 14A (definitive annual-meeting proxy). When a transaction is subject to the preliminary-filing requirement, the definitive version filed as DEFS14A is the one mailed to shareholders and constitutes the operative solicitation document. The dataset covers the entire DEFS14A filing population without subject-matter restriction, and is delivered as monthly ZIP containers structured as <year>/<year>-<month>.zip, with each filing living at <year>-<month>/<accession-no-stripped>/ (dashes removed from the accession number to form the folder name; for example, accession 0000927016-02-001907 becomes folder 000092701602001907).

Content Structure of a Single Record

A single record in the Form DEFS14A Files dataset is one definitive proxy statement filing prepared for a special (non-annual) shareholder meeting. Each record is materialized as one accession-number folder, mapping one-to-one to a unique EDGAR accession number, so the record is the filing as a whole, not an event extracted from it and not a row in a derived table.

Each accession-number folder contains two structural layers:

1. A metadata.json file — the structured, machine-readable summary of the filing's identity, parties, dates, classifications, and document inventory.
2. One or more document files — the actual EDGAR submission contents, each wrapped in EDGAR's SGML <DOCUMENT> envelope. The primary document is the proxy statement; additional documents may include cover letters, notices of meeting, forms of proxy card, plans of merger or liquidation, annexes, fairness opinions, and other exhibits filed alongside the proxy.

Image files (typically .gif or .jpg) referenced by the EDGAR submission are intentionally excluded from the dataset; their entries remain visible in metadata.json under documentFormatFiles, but the binary image is not packaged into the ZIP. The file types found in the dataset are TXT, JSON, HTML, and PDF.

metadata.json

The metadata file is the structured spine of the record. Its top-level fields are:

• formType — fixed string "DEFS14A" for every record in this dataset.
• accessionNo — EDGAR accession number in canonical dashed form (e.g., "0000927016-02-001907").
• id — a 32-character hexadecimal record identifier.
• filedAt — ISO 8601 timestamp of the filing event, including timezone offset.
• periodOfReport — YYYY-MM-DD date corresponding to the special-meeting period the proxy covers; for DEFS14A this typically reflects the meeting date or the record date associated with the solicitation.
• description — human-readable label, e.g., "Form DEFS14A - Definitive proxy statement for special meeting".
• linkToFilingDetails — URL to the primary filing document on sec.gov.
• linkToTxt — URL to the complete SGML submission text file on EDGAR.
• linkToHtml — URL to the EDGAR filing index page.
• linkToXbrl — URL to an XBRL package; empty for DEFS14A because the form does not carry structured XBRL financial data.
• documentFormatFiles — an ordered array describing every document in the original submission. Each entry carries sequence (the EDGAR sequence number), size (bytes), documentUrl (canonical EDGAR URL), description (filer-provided label such as "MAIN PART", "FORM OF PROXY", "ANNEX A"), and type (e.g., "DEFS14A" for the proxy itself, "GRAPHIC" for image exhibits, or a blank type for the complete submission text bundle).
• dataFiles — array reserved for supplemental structured data files; typically empty for DEFS14A filings.
• entities — an array of one or more parties on the filing. Each entity object carries companyName (with a role suffix such as (Filer)), cik (zero-padded ten digits), type (the entity-level form-type label), act (Securities Act/Exchange Act number, typically "34" for proxy filings), fileNo (SEC file number — "811-..." for registered investment companies, "001-..." or "000-..." for operating-company registrants), filmNo (EDGAR film number), fiscalYearEnd (MMDD), stateOfIncorporation (two-letter code), irsNo (IRS employer identification number, occasionally absent), sic (SIC code with industry description), and tickers (an array of ticker symbols, typically populated for operating companies and empty for registered funds).

The proxy statement document

The principal document inside the folder is the proxy statement itself, sequenced as document 1 in the EDGAR submission. Whether it is delivered as .txt (early years and some later text-only filings) or .htm/.html (the modern norm), it is wrapped in EDGAR's SGML <DOCUMENT> envelope:

          1
          <DOCUMENT>
        

          2
          <TYPE>DEFS14A
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>...
        

          5
          <DESCRIPTION>...
        

          6
          <TEXT>
        

          7
            ... body of the proxy statement ...
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

Inside the <TEXT> block, an HTML filing carries <HTML>, <PRE>, and standard tag content (often beginning with monospaced styling carried over from typesetting), while a text filing carries plain ASCII paginated with <PAGE> separators between virtual pages.

The proxy statement body itself follows a recognizable, though filer-customized, ordering:

• Schedule 14A cover page, identifying the registrant and the filing as a definitive proxy under Rule 14a-6, with checkboxes indicating filing type (preliminary vs definitive, fee-paid status), the calculation of the filing fee disclosed under Exchange Act Rule 0-11 where applicable, and the registrant's address and CIK printed at the top.
• Letter to shareholders, signed by the chairman, CEO, or board, describing in plain language the purpose of the special meeting and urging the return of the proxy card.
• Notice of Special Meeting of Shareholders, formally stating the date, time, and location (or, increasingly, the virtual-meeting access details) of the meeting, the record date for determining holders entitled to vote, and a numbered list of the matters to be acted upon.
• Proxy statement narrative, organized around Schedule 14A's required disclosure items: questions and answers; voting and proxy procedures (quorum, required vote, abstentions, and broker non-votes); description of each proposal; background and reasons for any extraordinary transaction; opinion of financial advisor where required; interests of directors and officers in the matters being voted on; appraisal/dissenters' rights where applicable; security ownership of certain beneficial owners and management; and householding and shareholder-proposal information.
• Transaction-specific disclosure blocks, when triggered: agreement and plan of merger summary, regulatory approvals, accounting and tax treatment, financing of the transaction, pro forma and historical financial statements, fairness opinion summary, and risk factors related to the proposed transaction.
• Annexes/appendices, typically lettered (Annex A, B, C…), reproducing the merger agreement, the form of amended charter or bylaws, the fairness opinion, the plan of liquidation, audited financials of an acquired company, or the text of a stock-incentive plan.
• Form of proxy card, the actual ballot-style document with the proposal items and voting boxes.

Additional document files

When the filer chose to submit a parallel PDF rendering of the proxy (a common practice for visually intricate proxies and fund proxies), it appears as a separate .pdf file inside the folder, also wrapped in the SGML <DOCUMENT> envelope. Additional .htm or .txt files may carry exhibits or annexes that the filer split out as separate sequence numbers in the EDGAR submission. Each such file carries its EDGAR-assigned <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> headers, which mirror what metadata.json records under documentFormatFiles.

Included content

The dataset packaging includes, for each accession number:

• The metadata.json structured summary described above.
• All .txt, .htm/.html, and .pdf documents from the original EDGAR submission, with their EDGAR SGML document envelopes preserved and their original EDGAR filenames retained.
• The full body of the proxy statement, including cover page, narrative disclosure items, transaction annexes when present, and the form of proxy card when filed as part of the submission.

Excluded or separate content

Several categories of content sit outside the record folder:

• Image files referenced in the original submission (.gif, .jpg, and similar GRAPHIC-typed exhibits) are not packaged into the ZIP, even though their metadata entries remain visible inside documentFormatFiles. Logos, signatures rendered as graphics, and embedded charts that depend on these images therefore appear as broken references when the HTML is rendered locally.
• The complete SGML submission file (the .txt "submission" bundle that EDGAR concatenates from all documents) is referenced via linkToTxt but is not duplicated inside the folder; the per-document files inside the folder collectively cover the same content.
• XBRL data is not present, because DEFS14A filings do not carry structured financial XBRL exhibits; the linkToXbrl field is therefore empty.
• Other forms in the same family (PRE 14A, PRES14A, PREM14A, DEF 14A, DEFA14A, DEFM14A, DEFR14A) are not part of this dataset, even when they relate to the same transaction. A merger proxy, for example, may also be referenced as part of a related Form S-4 registration and an accompanying prospectus, but those documents are filed under separate accession numbers and are not pulled into the DEFS14A folder.
• Subsequent additional soliciting material (DEFA14A) and any amended definitive proxy (DEFR14A) are likewise filed under their own accession numbers and constitute separate records under separate dataset scopes, not appendices to the DEFS14A record.

Changes in required content and structure over time

The skeleton of Schedule 14A has been stable since the mid-1990s, but several regulatory layers have materially expanded what appears inside DEFS14A filings, especially for transaction-driven proxies:

• Plain English requirements (1998). Rule 421(d) of Regulation C and the SEC's plain-English initiative pushed cover pages, summary sections, and risk-factor language into shorter sentences, active voice, and tabular Q&A formats that became near-universal at the front of merger proxies thereafter.
• Sarbanes-Oxley era (2002–2003). Heightened disclosure of related-party arrangements, auditor independence considerations, and director independence statements began to appear more prominently in special-meeting proxies that asked shareholders to approve governance changes or auditor ratifications outside the annual cycle.
• Executive compensation overhaul (2006). The redesigned Item 402 of Regulation S-K, with its Compensation Discussion and Analysis and standardized Summary Compensation Table, flows into DEFS14A whenever the special meeting touches on compensation arrangements, equity-plan approvals, or change-in-control payments triggered by an M&A transaction (the "golden parachute" disclosures, codified for transaction proxies under Item 402(t) following the 2011 Dodd-Frank rulemaking).
• Dodd-Frank say-on-pay and golden-parachute votes (2011). Rule 14a-21(c) introduced a separate non-binding shareholder vote on compensation tied to merger transactions, and the corresponding tabular disclosure of golden-parachute compensation became a standard block within merger DEFS14A filings.
• Conflict-minerals, mine-safety, and other periodic-style mandates generally do not appear here because they live in 10-K/SD filings, but transaction proxies that incorporate target-company financial statements by reference can pull these adjacent disclosures into appendices.
• Investment-company proxy disclosure (Item 22). Rule amendments and staff guidance over the years have refined what fund-specific DEFS14A filings must disclose about advisory-contract approvals, board considerations under Section 15(c) of the Investment Company Act, and shareholder-vote requirements for fundamental policy changes.
• Universal proxy (2022). Rule 14a-19's universal-proxy regime primarily affects contested director elections (more typical at annual meetings), but where a special meeting includes a contested election, the form of proxy and related disclosures inside DEFS14A reflect the universal-card requirements.
• Virtual-meeting disclosure (2020 onward). Following pandemic-era practice, the "date, time and location" block routinely includes virtual-meeting platform details, dial-in numbers, and instructions for participating and voting electronically.

These layered requirements show up not as new top-level structural sections but as expansions inside existing Schedule 14A items and as additional annexes.

Changes in data format over time

DEFS14A filings have moved through three broad presentation eras inside the dataset's January 1994–present span:

• ASCII/SGML era (1994 to roughly 2001). Filings were submitted as plain text wrapped in EDGAR's SGML <DOCUMENT> envelope, paginated with <PAGE> markers, with monospaced layouts simulating tables through column alignment. Fund proxies and small-cap merger proxies in this era are predominantly .txt files with ASCII-only content.
• HTML era (early 2000s onward). EDGAR began accepting HTML as the primary document format, and DEFS14A filings increasingly arrived as .htm or .html documents — still wrapped in the SGML <DOCUMENT> envelope but containing real HTML markup, embedded tables, and references to graphic files. Many filers continued to file an additional PDF rendering for visual fidelity, and these PDFs are preserved in the dataset where they were part of the EDGAR submission.
• Modern HTML-plus-PDF era (mid-2000s to present). The dominant pattern is a primary HTML proxy document, optionally paired with a PDF mirror, plus separate HTML or text exhibits for annexes. Image references inside the HTML point to .gif/.jpg filenames whose binaries are excluded from the dataset.

DEFS14A is not an XBRL-tagged form, so no inline-XBRL or standalone XBRL adoption arc applies; the structured metadata in the dataset is provided entirely through metadata.json, not through tagging inside the proxy itself.

Interpretation notes

• Record granularity. One folder equals one accession number equals one definitive proxy filing. A single corporate transaction may involve a chain of related filings (PRES14A, PREM14A, DEFM14A, DEFA14A, DEFR14A, S-4, 425, 8-K), and only the DEFS14A links in that chain materialize as records here.
• DEFS14A versus DEFM14A and DEF 14A. DEFS14A is specifically the special-meeting variant. Merger-specific definitive proxies often appear under the DEFM14A code, and annual-meeting definitive proxies appear under DEF 14A; these are separate form codes and are not commingled into this dataset.
• Incorporation by reference. Transaction proxies frequently incorporate by reference large portions of the registrant's or target's Exchange Act reports (Form 10-K, Form 10-Q, Form 8-K). Those incorporated documents are not duplicated inside the folder; the proxy text contains the cross-reference and the reader must follow it to the cited filings.
• Form of proxy card. The proxy card is a distinct document inside the EDGAR submission and may appear as a separate sequence number with its own filename. It is not always visually faithful in HTML rendering, since it was originally designed to be printed.
• Excluded images affect rendering. Because .gif/.jpg files are dropped from the ZIP, opening an HTML proxy locally will produce missing-image placeholders for logos, signature scans, and graphical charts. The metadata's documentFormatFiles array remains the authoritative inventory of what the original submission contained.
• Entity arrays carry roles. The entities array can contain multiple parties — for example, both an issuer and a filer-on-behalf-of — and the (Filer) suffix on companyName is the primary cue for which entity is the operative registrant.
• Investment-company filings. Fund DEFS14A records typically use file numbers prefixed 811-, frequently have empty tickers arrays, and are dominated by Section 15(c) advisory-contract approvals, fund mergers, and changes to fundamental investment policies; their proxy bodies tend to be shorter and more standardized than operating-company merger proxies.
• Machine extraction. Reliable parsing should peel the SGML <DOCUMENT> wrapper first to recover <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION>, and only then parse the inner <TEXT> block as either HTML or paginated ASCII. Section boundaries inside the proxy body are filer-styled (no machine-uniform headers), so robust extraction relies on heading-pattern heuristics combined with the canonical Schedule 14A item taxonomy.

Who Files or Publishes This Dataset, and When

Who files

Form DEFS14A is filed by the registrant whose securities are being voted — the issuer soliciting proxies for a special meeting of security holders. The "DEF" marks the materials as definitive (final, mailed to holders); the "S" marks the meeting as special rather than annual.

Filers are issuers subject to Section 14(a) of the Securities Exchange Act of 1934 — generally those with a class of securities registered under Section 12. In practice this includes:

• Domestic operating companies with equity registered under Section 12(b) (exchange-listed) or Section 12(g).
• Closed-end funds and business development companies holding special meetings on fundamental policy changes, advisory contracts, mergers, or board matters.
• REITs, MLPs, and other registered issuers soliciting holder action outside the annual cycle.
• Acquirers and targets in mergers, acquisitions, or business combinations requiring a holder vote, including joint proxy statement / prospectus filings paired with a Form S-4.

The filer is the soliciting registrant, not the holders being solicited and not the deal counterparty (whose information may dominate the document in M&A votes).

When the record is triggered

DEFS14A is event-driven, not periodic. The trigger is the calling of a special meeting (or other shareholder action outside the annual meeting) on a matter requiring a vote. Typical triggering matters:

• Mergers, asset sales, consolidations, or going-private transactions requiring holder approval under state law or exchange rules.
• Share issuances above NYSE/Nasdaq 20% thresholds tied to acquisitions.
• Charter or certificate amendments (authorized share increases, reverse splits, reincorporations).
• Equity compensation plan approvals timed off-cycle.
• For investment companies, advisory contract approvals, fundamental policy changes, or fund reorganizations under the Investment Company Act of 1940.
• Liquidations, dissolutions, or plans of arrangement.
• Off-cycle contested or board-replacement votes.

Timing logic

DEFS14A has no fixed calendar deadline; timing is governed by the meeting schedule and Rule 14a-6:

• Matters requiring preliminary filing (mergers, acquisitions, contests, and most non-routine items) must first be filed as PRES14A at least 10 calendar days before the definitive materials are released. DEFS14A is then filed at or before first dissemination to holders.
• Matters falling within the Rule 14a-6(a) exemption may be filed directly as DEFS14A on the date of first mailing.
• The special meeting itself usually occurs roughly 20 to 40 days after the definitive mailing, depending on state-law notice rules.

Supplemental disclosures issued after the definitive filing are filed as DEFA14A.

Regulatory framework

DEFS14A is filed under Section 14(a) of the Exchange Act and Regulation 14A. Key rules: Rule 14a-6 (filing mechanics), Schedule 14A (substantive disclosure content), Rule 14a-4 and Rule 14a-5 (form of proxy), and Rule 14a-16 (notice-and-access). Investment company filings carry additional content requirements under the 1940 Act. Merger proxies typically incorporate Form S-4 disclosure as a joint proxy/prospectus.

In transactions where both sides' holders must vote, each registrant files its own proxy statement, though a joint proxy statement is common and may be filed by both parties (each receiving an accession number, or one filing identifying co-filers).

How This Dataset Differs From Similar Datasets or Filings

DEFS14A sits inside the Schedule 14A proxy-solicitation family. The most useful comparisons run along four axes: filing stage (preliminary, definitive, revised), meeting type (annual vs special), transaction context (routine vs merger vs going-private), and solicitor identity (management vs dissident vs non-management). A second comparison axis reaches adjacent shareholder-action regimes: Schedule 14C information statements, Rule 13e-3 going-private filings, Form 8-K Item 5.07 vote results, and Form 6-K submissions by foreign private issuers.

DEF 14A (definitive annual proxy)

The closest sibling. Both are definitive Section 14(a) proxy statements with the same structural backbone: notice of meeting, matters to be voted on, voting procedures, required disclosures. The split is meeting type. DEF 14A covers the annual cycle (director elections, auditor ratification, say-on-pay, equity-plan approvals) and is filed once a year by virtually every domestic reporting company. DEFS14A covers special meetings convened for transactional matters (mergers, asset sales, charter amendments, reverse splits, recapitalizations) and appears only when an off-cycle vote is needed, producing a much smaller, event-driven population. Use DEF 14A for routine governance and compensation; use DEFS14A for transactional approvals.

PRES14A (preliminary special-meeting proxy)

The preliminary counterpart to DEFS14A. Same meeting and usually the same transaction, filed earlier and subject to SEC staff review. PRES14A often carries placeholder language, blank financial figures, or unresolved disclosures that get finalized in DEFS14A. Comparing PRES14A to DEFS14A in the same accession family yields the redline of changes prompted by staff review. PRES14A is never the operative solicitation document mailed to shareholders.

PRE 14A (preliminary annual proxy)

Stands to DEF 14A as PRES14A stands to DEFS14A. Relevant only as a structural analog; substantively it covers annual agendas, not special-meeting transactions.

DEFM14A (definitive merger proxy)

A definitive proxy used specifically for mergers, consolidations, or acquisitions requiring shareholder approval. Heavy subject-matter overlap with DEFS14A because many special meetings are merger votes. The split is form-code choice by the filer: DEFM14A is reserved for business-combination transactions; DEFS14A covers any special-meeting solicitation, merger or otherwise. The boundary is not crisp, and a complete merger-vote dataset usually requires both. DEFM14A filings typically carry merger agreements, fairness opinions, and background-of-the-merger narratives; DEFS14A carries these only when the special meeting is itself a merger.

DEFA14A (additional definitive soliciting material)

Supplemental soliciting material filed after a definitive proxy is distributed: investor presentations, press releases, employee communications, talking points, letters to shareholders. Not a standalone proxy, no meeting notice, no voting card. It supplements a DEF 14A, DEFS14A, DEFM14A, or DEFC14A. For a DEFS14A campaign, the corresponding DEFA14A stream usually contains the bulk of persuasive communications and proxy-fight commentary; DEFS14A itself carries the formal disclosure.

DEFR14A (definitive revised proxy)

A revised definitive proxy issued when material changes occur after the original definitive version. It supersedes or amends a prior DEF 14A or DEFS14A and captures post-mailing revisions: adjourned-meeting disclosures, revised deal terms, updated fairness opinions, corrected disclosures. Low volume, and only exists when a prior definitive filing exists.

DEFC14A (definitive contested proxy)

The definitive proxy used in contested solicitations, typically by dissidents or activists running an opposing slate or proposal. Procedurally similar to DEF 14A or DEFS14A but flagged as contested. In a special-meeting contest, the dissident side may file DEFC14A while the company files DEFS14A or DEF 14A on the same meeting. A full picture of a contested special meeting usually requires DEFS14A (management), DEFC14A (dissident), and DEFA14A (both sides' soliciting material).

DEFN14A (definitive non-management proxy)

Filed by non-management persons soliciting proxies, often in non-contested contexts such as a security holder soliciting on a single proposal. Overlaps with DEFC14A but is not necessarily contested, and can co-exist with a company-filed DEFS14A on the same meeting.

Schedule 14C (information statements)

Filed when shareholder action is taken without a proxy solicitation, typically because a controlling holder or majority block has already delivered written consent. Substantively describes the same corporate actions as DEFS14A (mergers, charter amendments, asset sales) with similar disclosures, but no vote is being solicited. DEF 14C and PRE 14C are the definitive and preliminary forms. The same transaction can appear as DEFS14A at a dispersed-ownership company and as DEF 14C at a controlled company; mapping all special corporate actions requires both.

Schedule 13E-3 (going-private transactions)

Filed in transactions taking a public company private, including management buyouts and certain affiliate-led acquisitions. Almost always filed alongside a proxy or tender-offer document, including DEFS14A or DEFM14A when shareholder approval is required. 13E-3 adds Rule 13e-3-specific content: fairness determinations by the issuer or affiliate, alternatives considered, detailed conflict-of-interest analysis. DEFS14A alone will not contain these elements; going-private vote analysis requires reading the 13E-3 and the proxy together.

Form 8-K Item 5.07 (submission of matters to a vote)

Reports actual vote results within four business days of the meeting. Downstream complement to DEFS14A: the proxy describes what will be voted on, the 8-K reports how the vote came out. Item 5.07 is short, structured, and tabular (proposal, for, against, abstain, broker non-votes); DEFS14A is long-form, narrative, disclosure-heavy. Neither substitutes for the other: 5.07 lacks the underlying disclosure, DEFS14A predates the vote.

Form 6-K (foreign private issuer disclosures)

Foreign private issuers are exempt from Schedule 14A and do not file DEFS14A. Their proxy circulars, meeting notices, and special-meeting materials surface as exhibits to Form 6-K, governed by home-country rules rather than Regulation 14A. The functional cross-border analog to DEFS14A, but with different content standards, less prescriptive U.S.-style disclosure, and a much broader filing scope that also includes non-meeting submissions.

Boundary summary

DEFS14A is uniquely the definitive, U.S.-issuer, management-side, special-meeting proxy statement under Section 14(a). Its identifying attributes: (1) definitive rather than preliminary or revised, (2) special rather than annual meeting, (3) management rather than dissident or non-management solicitor, (4) proxy solicitation rather than written-consent information statement, (5) domestic-issuer rather than foreign-private-issuer regime. Shifting any one attribute swaps the form code: PRES14A (preliminary), DEFR14A (revised), DEF 14A (annual), DEFC14A or DEFN14A (non-management), DEF 14C (written consent), 6-K (foreign issuer). DEFM14A overlaps when the special meeting is a merger vote; 13E-3 layers on for going-private deals. DEFA14A and 8-K Item 5.07 are companions, not substitutes, supplying soliciting material and post-vote outcomes respectively. A complete special-meeting transaction record uses DEFS14A as the disclosure anchor and joins it to its preliminary, revised, supplemental, contested, and post-vote relatives.

Who Uses This Dataset

DEFS14A filings solicit shareholder votes on extraordinary actions: mergers, acquisitions, divestitures, recapitalizations, and charter amendments. Users are event-driven professionals who pull different sections from the same record.

M&A diligence teams

Deal lawyers and corporate development analysts mine the background-of-the-merger narrative, deal terms, treatment of equity awards, closing conditions, termination fees, and no-shop and matching-rights provisions. The attached merger agreement supports precedent research and benchmarking of deal protections.

Disclosure counsel

Securities lawyers drafting their own special-meeting proxies study how peers describe board deliberations, conflicts, advisor engagements, fairness opinion methodology, and Regulation M-A items. Used for templates, comment-letter responses, and disclosure gap checks.

Merger arbitrage and event-driven analysts

Arb desks extract consideration mix, exchange ratios, collars, walk-away rights, regulatory conditions, and meeting dates to size positions and monitor spreads. Disclosed projections and advisor analyses feed downside cases if the deal breaks.

Valuation and fairness opinion practitioners

Investment banking valuation groups and independent valuation firms reference disclosed DCF assumptions, comparable multiples, precedent transaction sets, and management projections to calibrate methodology and benchmark fairness opinion presentations.

Proxy advisors and stewardship teams

Governance analysts at proxy advisory firms and stewardship teams at institutional investors evaluate board recommendations, conflicts disclosures, golden parachute tables, and insider equity treatment to issue vote recommendations and frame engagement on pending deals.

Plaintiffs' counsel and activist investors

Litigation teams scrutinize board process, advisor independence, projections versus prior public guidance, and disclosure adequacy to draft complaints, pursue disclosure-only claims, or assess appraisal actions.

Credit analysts

Fixed income and ratings analysts use pro forma capital structure descriptions, financing commitments, and change-of-control language to size leverage, model recovery, and write rating committee memos on sponsor-backed deals and recapitalizations.

Compliance and proxy voting operations

Operations teams at broker-dealers, asset managers, and custodians track record dates, voting cutoffs, ballot mechanics, and tabulation procedures to run vote processing and client reporting.

IR and corporate development benchmarking

Teams preparing their own special meetings study peer chairman's letters, Q&A inserts, strategic rationale framing, and disclosure sequencing to plan communications and board materials.

Forensic accountants and expert witnesses

Post-deal investigators treat disclosed projections, valuation analyses, and background narratives as contemporaneous evidence of management expectations and board process for expert reports and deposition prep.

Academic researchers

Empirical researchers use the corpus to study deal premia, projection accuracy, fairness opinion practice, and shareholder voting on extraordinary matters.

LLM and RAG engineers

Legal- and finance-tech teams use the HTML, TXT, and PDF mix plus metadata to train and evaluate parsers, section classifiers, and QA systems over transaction proxies.

Specific Use Cases

The Form DEFS14A Files dataset supports event-driven workflows centered on special-meeting solicitations. The use cases below pull specific sections of the proxy and metadata fields to deliver concrete outputs.

Benchmarking deal-protection terms across merger proxies

Corporate development analysts and M&A counsel parse the merger-agreement annex and the "background of the merger" narrative to extract no-shop scope, fiduciary outs, matching rights, termination fees, and walk-away triggers. Records are filtered using the entities[].sic code and filedAt timestamp to assemble industry- and vintage-matched precedent sets, with the documentFormatFiles array used to locate the merger agreement annex by its description label.

Sizing and monitoring merger-arbitrage spreads

Event-driven desks extract the consideration mix, exchange ratio, collar mechanics, regulatory closing conditions, and meeting/record dates from the proxy statement narrative and proxy card. The periodOfReport field anchors the meeting timeline, and disclosed management projections plus the financial advisor's DCF, comparable-companies, and precedent-transaction tables feed break-price downside cases.

Building a golden-parachute and equity-treatment dataset

Compensation researchers and proxy advisors lift Item 402(t) golden-parachute tables, treatment-of-equity-awards descriptions, and named-executive change-in-control payouts from each merger DEFS14A. Combined with entities[].cik and tickers, the output is a structured per-NEO payout table used for vote recommendations on Rule 14a-21(c) say-on-golden-parachute proposals and for executive-pay benchmarking.

Litigation evidence on board process and disclosure adequacy

Plaintiffs' counsel and forensic accountants mine the background-of-the-transaction section, advisor-engagement disclosures, conflicts narratives, and management projections as contemporaneous evidence of board deliberations. Comparing projection figures against the same registrant's prior 10-K/10-Q public guidance (linked through cik) supports disclosure-only complaints, appraisal valuations, and deposition exhibits.

Fund proxy monitoring for advisory-contract and policy changes

Asset-management compliance and fund-of-funds teams filter records on fileNo prefixes starting 811- to isolate registered investment company filings, then extract Item 22 disclosures on Section 15(c) advisory-contract approvals, sub-advisor changes, fund reorganizations, and amendments to fundamental investment policies. The output drives portfolio-level voting decisions and triggers re-underwriting of fund holdings before the meeting date.

Training and evaluating proxy-statement parsers

LLM and RAG engineers use the mixed TXT, HTML, and PDF document inventory plus the metadata.json spine to build section classifiers (cover page, notice of meeting, Q&A, fairness opinion, annexes, proxy card). The 1994-onward span exposes models to ASCII-paginated <PAGE> filings and modern HTML, and the SGML <DOCUMENT> envelope provides reliable document-boundary supervision for extraction pipelines.

Mapping the full lifecycle of a special-meeting transaction

Researchers and deal trackers use DEFS14A as the disclosure anchor and join on cik and meeting date to related filings: PRES14A for preliminary-to-definitive redlines, DEFA14A for additional soliciting material, DEFR14A for post-mailing revisions, Schedule 13E-3 for going-private fairness analysis, and Form 8-K Item 5.07 for actual vote tallies. The resulting per-transaction dossier links proposed terms, staff-driven changes, supplemental communications, and final voting outcomes.

Dataset Access

Dataset Index JSON API: https://api.sec-api.io/datasets/form-defs14a-files.json

This endpoint returns the dataset's metadata, including its name, description, last updated timestamp, earliest sample date (1994-01-01), total record count, total dataset size, covered form types (DEFS14A), container format (ZIP), and included file types (TXT, JSON, HTML, PDF). It also lists every individual container file with its size, record count, last updated timestamp, and direct download URL, alongside the download URL for the full dataset archive. Use this endpoint to monitor which containers were updated in the most recent refresh run and decide on a daily basis which containers to download. No API key is required to call this endpoint.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6959-89a7-d050d420659a",
        

          3
            "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-defs14a-files.zip",
        

          4
            "name": "Form DEFS14A Files Dataset",
        

          5
            "updatedAt": "2026-04-15T07:48:49.663Z",
        

          6
            "earliestSampleDate": "1994-01-01",
        

          7
            "totalRecords": 4294,
        

          8
            "totalSize": 170127061,
        

          9
            "formTypes": ["DEFS14A"],
        

          10
            "containerFormat": "ZIP",
        

          11
            "fileTypes": ["TXT", "JSON", "HTML", "PDF"],
        

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-defs14a-files/2026/2026-04.zip",
        

          15
                "key": "2026/2026-04.zip",
        

          16
                "size": 4218377,
        

          17
                "records": 38,
        

          18
                "updatedAt": "2026-04-15T07:48:49.663Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: https://api.sec-api.io/datasets/form-defs14a-files.zip?token=YOUR_API_KEY

Downloads the full Form DEFS14A Files dataset as a single ZIP archive containing every monthly container from January 1994 to the most recent refresh. This endpoint requires a valid API key.

Download Single Container: https://api.sec-api.io/datasets/form-defs14a-files/2026/2026-04.zip?token=YOUR_API_KEY

Downloads a single monthly container, for example all DEFS14A filings submitted in April 2026, instead of the full archive. This is useful for incremental updates after monitoring the index API for changed containers. This endpoint requires a valid API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form DEFS14A — the definitive proxy statement filed in connection with a special (non-annual) meeting of shareholders under Section 14(a) of the Securities Exchange Act of 1934 and Rule 14a-6(b). It is the final, voting-ready version of the proxy that a registrant disseminates to security holders, distinct from PRES14A (preliminary) and DEF 14A (definitive annual proxy).

What does one record in the Form DEFS14A Files dataset represent?

One record is a single definitive special-meeting proxy filing, materialized as one accession-number folder. Each folder maps one-to-one to a unique EDGAR accession number and bundles a structured metadata.json summary together with the original EDGAR submission's primary documents — the proxy statement itself plus any cover letter, notice of meeting, form of proxy card, plan of merger or liquidation, annexes, fairness opinions, or other exhibits filed alongside it.

Who is required to file Form DEFS14A?

DEFS14A is filed by the registrant whose securities are being voted — the issuer soliciting proxies for a special meeting. Filers include domestic operating companies with equity registered under Section 12(b) or 12(g), closed-end funds and business development companies, REITs, MLPs, and acquirers and targets in mergers, acquisitions, or business combinations requiring a holder vote. Foreign private issuers are exempt from Schedule 14A and instead disclose meeting materials as exhibits to Form 6-K.

When is a DEFS14A filing triggered?

DEFS14A is event-driven, not periodic. The trigger is the calling of a special meeting on a matter requiring a vote, such as mergers, asset sales, going-private transactions, charter or certificate amendments, reverse splits, equity-plan approvals timed off-cycle, fund advisory-contract approvals, or liquidations. Where preliminary filing is required, PRES14A must be filed at least 10 calendar days before the definitive materials; otherwise DEFS14A may be filed directly on the date of first mailing.

What time period does the dataset cover, and what file format is it distributed in?

The dataset spans January 1994 through the present and is distributed as monthly ZIP containers structured as <year>/<year>-<month>.zip. The included file types are TXT, JSON, HTML, and PDF; image files (.gif, .jpg) referenced by the original submission are intentionally excluded from the ZIP, though their entries remain visible in metadata.json under documentFormatFiles.

How does this dataset differ from the DEFM14A merger-proxy population?

DEFM14A is reserved for definitive proxies in business-combination transactions, while DEFS14A covers any definitive special-meeting solicitation, merger or otherwise. The boundary is not crisp because many special meetings are merger votes, and a complete merger-vote dataset usually requires both. This dataset captures the DEFS14A population without subject-matter restriction; DEFM14A filings are not commingled into it.

Does DEFS14A include XBRL-tagged financial data?

No. DEFS14A is not an XBRL-tagged form, and the linkToXbrl field in metadata.json is therefore empty. Structured machine-readable data in the dataset is provided entirely through metadata.json, not through tagging inside the proxy itself; financial statements that appear in transaction proxies are embedded as narrative HTML, text, or PDF rather than as inline XBRL.