The Form DFRN14A Files Dataset is a complete EDGAR corpus of revised definitive proxy statements filed by non-management soliciting parties under Section 14(a) of the Securities Exchange Act of 1934 and Rule 14a-6 of Regulation 14A. Each record is one EDGAR submission — an accession numbered folder containing a structured metadata.json index plus the SGML-wrapped HTML proxy document and any non-image exhibits — filed by a dissident shareholder, activist fund, hostile bidder, or other third party who has already filed a definitive non-management proxy statement on Form DEFN14A and is now amending it. Coverage begins April 1, 1995, tracking the phase-in of mandatory EDGAR filing under Regulation S-T, and continues to the present, with records partitioned into one ZIP archive per filing month under the path YYYY/YYYY-MM.zip. The dataset is distributed in ZIP container format and surfaces TXT, JSON, HTML, and PDF file types.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset captures every EDGAR-accepted DFRN14A submission since the form became filable on EDGAR. Form DFRN14A is the EDGAR form code used to file a revised definitive proxy statement under Rule 14a-6 by a soliciting person who is not the registrant. It belongs to the Schedule 14A family. The neighboring codes that frame DFRN14A's role are PREN14A (preliminary non-management proxy), DEFN14A (initial definitive non-management proxy), DFAN14A (additional definitive soliciting material by a non-management party), and the management-side counterparts PRE 14A, DEF 14A, and DEFA14A. DFRN14A is reserved for the case where a non-management soliciting party — typically a dissident shareholder, an activist fund, a competing bidder, or a group challenging the incumbent slate — has already filed a definitive proxy statement and is now amending or revising it. The form is therefore inherently iterative: each DFRN14A explicitly references and supersedes prior numbered amendments, and a single contest may produce a sequence of DFRN14A filings as record dates slip, meetings adjourn, or the dissident's positions evolve.
The substantive content of a DFRN14A is governed by Schedule 14A under Regulation 14A. The Schedule prescribes a cover-sheet structure, identification of the soliciting persons and the subject company, classification of the filing type via check-boxes, a Rule 0-11 filing-fee block, and the body content required by the relevant Items of Schedule 14A — most prominently Item 1 (date, time, and place of meeting), Item 2 (revocability of proxy), Item 4 (persons making the solicitation, including participant disclosures under Instruction 3), Item 5 (interests of certain persons in matters to be acted upon), Item 6 (voting securities and principal holders), Item 7 (directors and executive officers, including biographies of the dissident's nominees), and the Items addressing the specific matters being voted on. Because a DFRN14A is a revision rather than a fresh filing, the document is often shorter than a full proxy statement: it carries the Schedule 14A masthead and cover, then narrates the changes from the prior version, frequently incorporating the unrevised portions of the earlier proxy statement by reference.
The dataset is distributed as monthly ZIP containers. After decompression, each archive expands into a YYYY-MM/ directory whose direct children are the per-accession folders. File types observed across all records are TXT, JSON, HTML, and PDF.
A single record in the Form DFRN14A Files Dataset is one complete EDGAR submission of a revised definitive proxy statement filed by a non-management soliciting party. On disk, each record materializes as one accession-numbered subfolder that bundles two layers of content: a structured metadata.json index capturing the EDGAR header for the submission, and the filing payload itself — the SGML-wrapped HTML proxy document plus any non-image exhibits the filer included. The folder name is the eighteen-digit zero-padded SEC accession number with hyphens stripped (for example 000121390025068310, corresponding to canonical accession 0001213900-25-068310), and every document inside retains the filename it was given when EDGAR accepted the submission.
A record is layered as follows.
Outer layer — accession folder. Contains exactly one metadata.json plus the EDGAR-submitted documents. The number of sibling documents varies: a minimal DFRN14A may contain only the proxy statement, while a richer revision can include exhibits such as press releases, letters to stockholders, supplemental schedules, or proxy-card depictions. Image attachments referenced inline by the HTML (logo files, signature scans, headshots, proxy-card graphics, typically named image_001.jpg and similar) are excluded from the dataset; they remain enumerated in metadata.json but are not present on disk.
Middle layer — metadata.json. A structured index describing the submission as a whole rather than the content of any single document. The fields exposed include:
formType — always DFRN14A.accessionNo — the canonical dashed accession number (NNNNNNNNNN-YY-NNNNNN).filedAt — ISO 8601 EDGAR acceptance timestamp with Eastern timezone offset.description — human-readable form description, "Form DFRN14A - Revised definitive proxy statement filed by non-management".linkToFilingDetails — direct URL to the primary proxy document on sec.gov.linkToTxt — URL to the consolidated SGML submission text bundle on EDGAR.linkToHtml — URL to the EDGAR filing-index landing page.linkToXbrl — present in the schema but typically empty for proxy filings.id — opaque dataset-internal identifier.documentFormatFiles — array of submission documents, each entry carrying sequence, size (bytes, as a string), documentUrl, description (e.g. "DEFINITIVE PROXY STATEMENT", "GRAPHIC", "Complete submission text file"), and type (the EDGAR document type code such as DFRN14A, EX-99.1, or GRAPHIC).entities — structured list of all parties to the submission. For a DFRN14A there is at minimum one entry whose companyName is suffixed (Filed by) (the soliciting party) and one suffixed (Subject) (the registrant whose proxy is being contested). Each entity entry carries cik, companyName, irsNo, stateOfIncorporation, fiscalYearEnd, and type. The subject entity additionally carries act (e.g. 34 for the Exchange Act), fileNo (SEC file number such as 811-23681), and filmNo (the film identifier assigned at acceptance). Multi-party solicitations (a fund plus its principals plus the proposed nominees) produce additional (Filed by) entries.seriesAndClassesContractsInformation — populated only when the subject is an investment company with registered series/classes; commonly empty.dataFiles — reserved for structured data attachments; commonly empty for this form.Inner layer — filing payload. The primary document is the revised proxy statement, almost always rendered as HTML wrapped in EDGAR's SGML document envelope. The wrapper opens with <DOCUMENT>, <TYPE>DFRN14A, <SEQUENCE>1, <FILENAME>..., <DESCRIPTION>DEFINITIVE PROXY STATEMENT, and <TEXT> tags, then contains a full <HTML>...</HTML> body, and closes with </TEXT> and </DOCUMENT>. Additional exhibit documents in the same accession folder follow the same SGML-wrapper convention with their own <TYPE> codes (e.g. EX-99.1 for press releases or supporting communications).
Within the HTML body of the primary DFRN14A document, content is organized along the Schedule 14A template followed by the substantive amendment narrative. The components, in the order they typically appear, are:
When exhibits are filed alongside the proxy statement, they appear as separate SGML-wrapped documents in the same accession folder. Common exhibits include letters or open communications from the dissident to fellow stockholders, press releases (often filed as EX-99.1), supplemental investor presentations, additional biographical material on the nominees, and signed nominee consents.
Each record contains the per-accession metadata.json index and every non-image document from the original EDGAR submission, with original filenames preserved. In practice the payload is the full text of the revised proxy statement as an SGML-wrapped HTML document, plus any TXT, HTML, or PDF exhibits the soliciting party filed under the same accession. For typical DFRN14A submissions a single HTM file constitutes the bulk of the payload, and many records consist of just the metadata file and one HTML document.
Image files. Inline graphics referenced by the HTML — proxy-card images, signature scans, logos, headshots of dissident nominees — are not present in the accession folder. metadata.json's documentFormatFiles array still enumerates them with their original GRAPHIC document type, sequence number, byte size, and EDGAR URL, so consumers who need the images can resolve them through documentUrl.
Consolidated SGML .txt bundle. The full-submission .txt file that EDGAR generates for every accession (concatenating every document under one SGML envelope) is referenced via linkToTxt and appears in documentFormatFiles, but is not redistributed inside the accession folder — the dataset carries the individual decomposed documents instead.
Material incorporated by reference. Content that the proxy statement incorporates by reference — most notably the unrevised portions of the prior definitive proxy, and any annual report or 10-K material the dissident points to — is not embedded in the DFRN14A record. Readers must resolve those references through EDGAR to assemble the complete picture being placed before stockholders.
Other amendments and related filings. Earlier DEFN14A and DFRN14A filings, the registrant's own DEF 14A, and any DFAN14A additional-soliciting-materials filings are stored under their own accession numbers and are not bundled into a single proxy-contest dossier.
Aside from images, no other documents from the EDGAR submission are dropped: every TXT, HTM/HTML, and PDF document the soliciting party included travels with the record.
The Schedule 14A regulatory architecture that frames DFRN14A content has been amended repeatedly across the dataset's coverage, and several amendments materially affect what appears inside the proxy document.
Beyond regulatory change, the structural conventions of DFRN14A documents have evolved with modern activism: voting recommendation blocks have grown more elaborate, "where to find it" sections routinely cite sec.gov plus a dedicated campaign website, and the exhibit ecosystem has expanded to include investor presentations and pre-recorded video transcripts.
The submission-format evolution across the coverage window is material to how individual records render and how machine extraction should be approached.
<TYPE>DFRN14A blocks whose <TEXT> payload is a flat-formatted, fixed-width text rendering of the proxy statement, with tables hand-aligned using spaces. There is no HTML markup.<DOCUMENT> envelope. Early HTML filings are simple, with limited inline XBRL styling.<P STYLE="font: 10pt Times New Roman, Times, Serif; ..."> paragraphs, table-based page layout, and explicit page-break markers (often as HTML comments such as <!-- Field: Page; Sequence: N; Options: NewSection --> paired with <DIV STYLE="break-before: page"> elements) generated by professional EDGAR filing-agent tools. The proxy statement is still wrapped in EDGAR's SGML envelope at the document level.Several nuances matter when working with these records.
(Filed by) entity and one (Subject) entity in entities. The CIK of the soliciting party is the dissident's own filer identifier; the cik of the subject is the registrant being contested. The subject entity also carries the SEC fileNo that ties the entire proxy contest together. Solicitations involving multiple co-filers (a fund, several individual nominees, or affiliated entities) produce additional (Filed by) entries.<DOCUMENT>/<TYPE>/<SEQUENCE>/<FILENAME>/<DESCRIPTION>/<TEXT> SGML headers and trailers. Consumers should strip the SGML wrapper to obtain a parseable HTML body, or otherwise tolerate the wrapper tags during parsing.<IMG SRC="image_001.jpg"> and similar references inside the HTML resolve to absent files when the record is opened locally. This is intentional and does not indicate corruption; the original images are reachable via documentUrl values in metadata.json.ea0250490-dfrn14a_ocean2.htm). There is no canonical naming scheme beyond the accession folder itself; consumers should rely on documentFormatFiles[*].type and description to identify the role of each file rather than parsing filenames.metadata.json.Each DFRN14A is filed under Section 14(a) of the Exchange Act and Regulation 14A (Rules 14a-1 through 14a-21). The filer is never the registrant whose securities are being voted; it is a third party operating outside the issuer's board and management who has already filed a definitive non-management proxy statement on Form DEFN14A and is now revising it.
The filing population is narrow and structurally distinct from the issuer-side proxy population:
The legal filer is each "participant in the solicitation" identified under Schedule 14A, Item 4. Where a group solicits jointly, one nominal filer may submit on behalf of all participants, but disclosure obligations under Schedule 14A run to every participant, including affiliated funds, dissident nominees, and advisors treated as participants under the Schedule 14A instructions.
DFRN14A is event-driven, not periodic. It exists at the intersection of two triggers: (1) the underlying Section 14(a) and Regulation 14A obligation of any non-management party soliciting proxies for a Section 12-registered class, and (2) the specific need to revise materials already filed in definitive form on DEFN14A.
Within the non-management proxy taxonomy under Rule 14a-6, the typical sequence is:
A DFRN14A is generated after dissemination of a DEFN14A when circumstances require revision of the definitive statement itself. Common triggers:
Filing deadlines under Rule 14a-1 and Rule 14a-6:
The earliest EDGAR DFRN14A submissions date to April 1995, tracking the phase-in of mandatory EDGAR filing under Regulation S-T. Pre-EDGAR paper filings under the same Section 14(a) framework are not in the dataset.
DFRN14A occupies a narrow slot inside the Section 14(a) proxy-contest cluster: it is the non-management, definitive, revised proxy statement. Its closest neighbors are the other dissident-side 14A variants, the management-side mirrors that move in parallel during a contest, and two adjacent regimes (exempt solicitations and Schedule 13D) that frequently co-occur with proxy fights.
The direct parent of DFRN14A. DEFN14A is the dissident's final, mailable proxy statement; DFRN14A is the amendment to it after definitive status is reached. Same filer, same Schedule 14A content scope. Distinction: DEFN14A states the opening definitive position; DFRN14A captures what was corrected, supplemented, or materially changed between mailing and the vote. They are read as a pair.
The preliminary-stage analog. PRRN14A revises a PREN14A still under SEC staff review and cannot be used to solicit votes. DFRN14A revises a definitive filing, post-clearance, and is itself a vote-soliciting instrument. PRRN14A reflects pre-mailing iteration; DFRN14A reflects post-mailing revision.
The mirror lifecycle filed by the issuer rather than a dissident. DEF 14A is management's definitive proxy; DEFA14A is additional soliciting material; DEFR14A is the structural twin of DFRN14A — a revised definitive proxy filed by management. Identical disclosure framework, opposite advocacy posture: DEFR14A defends the board's slate and recommendations, DFRN14A challenges them. In a live contest, both tracks run in parallel and must be collected together.
Same filer side, same post-definitive timing, but a different function. DFAN14A adds communications (fight letters, investor decks, press releases, social posts) without amending the proxy statement. DFRN14A changes the proxy statement itself — nominees, proposals, disclosures. DFAN14A filings vastly outnumber DFRN14A in any given contest; one tracks campaign messaging, the other tracks formal substantive amendments.
The dissident's entry filing, submitted for SEC review before becoming definitive. PREN14A cannot solicit votes and reflects the initial framing of the case. DFRN14A is several steps later in the lifecycle: post-PREN14A, post-PRRN14A (if any), post-DEFN14A, and is itself a mailable solicitation. Separated by the SEC-clearance and definitive-mailing milestones.
Adjacent regime under Rule 14a-6(g): filed by holders of more than $5 million in a registrant's securities who publicly urge a vote outcome without seeking proxy authority (activist funds, governance advocates, pension funds). Same shareholder-influence intent as DFRN14A but different legal mechanism — exempt communication with lighter disclosure versus full Schedule 14A solicitation seeking actual proxies. PX14A6G covers "vote no" and recommendation campaigns; DFRN14A covers formal slate-running.
Frequent co-filer in proxy contests because dissidents typically cross the 5% threshold. The overlap is contextual, not substantive: 13D discloses stake and intent (purchase history, financing, plans for the issuer); DFRN14A discloses the solicitation itself (revised proposals, nominees, voting mechanics). Joining 13D with the 14A family reconstructs an activist campaign; DFRN14A specifically captures late-stage corrections to the formal vote-seeking apparatus.
DFRN14A is defined by the precise intersection of three properties — non-management, definitive, revised — and no other 14A category occupies that slot. PREN14A and PRRN14A are preliminary; DEFN14A is definitive but original; DFAN14A adds material rather than amending it; DEFR14A is the management-side twin; PX14A6G is exempt; Schedule 13D is an ownership filing. This narrowness explains the small filing population: true definitive revisions by dissidents occur almost exclusively when something material shifts after a contested mailing. Related datasets complement DFRN14A but cannot substitute for it when the research question is what dissidents formally changed in their final solicitation before the vote.
DFRN14A filings document the live mechanics of a contested vote: who is soliciting, what slate or proposal is now being advanced, and what changed since the prior definitive version. A small, well-defined set of professionals work directly with these records.
Activist and special-situations PMs, along with their outside campaign counsel, communications advisors, and financial advisors, use DFRN14A filings as precedent. They focus on the revised director slate, the amendment narrative, the participants table, and the security ownership and "interest in matters" disclosures. Workflow: building campaign playbooks, drafting nominee bios, modeling settlement and standstill language, and benchmarking timing against comparable contests.
Solicitors retained by either side use DFRN14A filings as operational reference. They focus on meeting logistics, BLUE-card versus WHITE-card mechanics, revocation procedures, universal proxy implementation under Rule 14a-19, and revised vote-required and quorum disclosures. Workflow: solicitation script design, tabulation strategy, voter outreach segmentation, and competitive monitoring of rival card structures.
Vote-recommendation analysts and in-house stewardship teams at large asset managers evaluate dissident cases at the definitive stage. They focus on changes to the slate, the dissident's value-creation thesis, ownership and economic exposure, and any settlement or withdrawal language. Workflow: vote-recommendation reports, engagement case files, and precedent libraries used to calibrate later contests.
Defense counsel for target companies, together with issuer investor relations and the corporate secretary's office, use the dataset to anticipate dissident moves and draft responses. They focus on the revised arguments, board-related claims, participant and ownership disclosures, and supplemental exhibits such as shareholder letters and presentations. Workflow: drafting responsive DEFA14A filings, fight-letter sequencing, board talking points, and litigation-readiness reviews.
Lawyers handling proxy contests, Section 14(a) disclosure claims, and contested-deal injunctions build the disclosure record from these filings. They focus on what changed between the original DEFN14A and the revised DFRN14A, the precise revised wording, omissions or corrections, and participants' interests. Workflow: complaint drafting, motion practice over alleged misstatements, and settlement negotiations.
Analysts at event-driven and arb funds treat DFRN14A as confirmation that a contest has reached active solicitation with a revised position. They focus on the meeting date, updated slate or proposal language, support or opposition to a pending tender-offer or going-private transaction, and the soliciting party's beneficial ownership. Workflow: position sizing, outcome probability modeling, and event-calendar management where vote timing drives spread economics.
Researchers studying activism, board accountability, and disclosure practice use the corpus as a structured record of dissident campaigns since 1995. They focus on contest population over time, dissident identity and type, slate size, issue category, and language patterns. Workflow: empirical studies of activism returns, governance reform analyses, and longitudinal work on rule-cycle effects.
Rulemaking and economic-analysis staff at securities regulators, along with policy researchers, study how solicitation practice responds to rules such as universal proxy and e-proxy delivery. They focus on filing frequency, types of revisions, and compliance with participant and ownership disclosure requirements. Workflow: rule-impact assessments, enforcement referrals, and comment-letter analysis.
Data engineering teams at vendors and buy-side firms ingest the dataset to build structured contest feeds. They use the metadata for accession-level joins to issuer identifiers, parse revised proxy statements and exhibits to extract slate composition and vote items, and reconcile DFRN14A revisions against prior DEFN14A baselines. Workflow: contest-tracking products, alerting feeds, and normalized tables for downstream analyst and compliance users.
Teams building retrieval-augmented systems for governance and proxy-fight question answering use DFRN14A as a high-signal corpus distinct from issuer-filed proxies. They use the full text of the revised statement, the amendment narrative, exhibit letters, and participant disclosures. Workflow: training and retrieval corpora for systems answering questions on contest history, dissident arguments, and slate evolution.
Sell-side activism specialists and corporate-access teams brief institutional clients on active contests and sequence issuer-holder meetings. They focus on the revised slate, contested issues, dissident ownership, and meeting logistics. Workflow: client briefing notes and roadshow planning aligned to the vote calendar.
Across all roles, the load-bearing parts of the record are consistent: the revised slate or proposal, the amendment narrative explaining what changed, participant and ownership disclosures, proxy card and meeting mechanics, and the supporting exhibits used to persuade other shareholders.
The following workflows show how practitioners use DFRN14A records in concrete, day-to-day work. Each is tied to specific parts of the record — the revised slate, the amendment narrative, BLUE/WHITE card mechanics, ownership and participant tables, meeting logistics, and the surrounding exhibits.
Litigators and proxy advisors diff the DFRN14A against the prior DEFN14A under the same subject fileNo to isolate exactly which sections of the proxy were replaced or supplemented. The amendment narrative and the "Reasons for the solicitation" block are the load-bearing components, and the output is a revision ledger used in Section 14(a) disclosure claims, vote-recommendation memos, and precedent libraries that track late-stage corrections (nominee withdrawals, corrected ownership figures, updated meeting dates).
Proxy solicitors and campaign counsel pull DFRN14A filings dated after August 31, 2022 to compare how dissidents present the combined universal card, the 67%-solicitation-threshold language, and revocation instructions. The proxy-card annex, the "Proposals and voting recommendations" block, and the BLUE-versus-WHITE card depictions feed solicitation scripts, tabulator instructions, and template language for new contests where the dissident is mid-campaign and needs to revise its card.
Data engineers at analytics vendors join metadata.json entities (the (Filed by) and (Subject) CIKs plus the subject fileNo) across DFRN14A, DEFN14A, DFAN14A, and PREN14A accessions to assemble per-contest dossiers. Parsed slate biographies, beneficial-ownership tables, and meeting-date fields populate a normalized contest table with fields for amendment number, revised meeting date, slate size, and dissident ownership — feeding alerting products and compliance dashboards.
Merger-arbitrage and event-driven analysts use the meeting-logistics section and any adjournment language in the amendment narrative to update vote-date assumptions on contested deals and standalone activist campaigns. The dissident's revised position on a pending transaction (often the trigger for the DFRN14A) drives directional sizing, while the participants table and ownership disclosures inform borrow and crowding analysis.
Governance researchers treat the corpus since 1995 as a longitudinal panel of dissident-side revisions. Filing frequency by year, slate size from nominee biographies, issue categories from the "Reasons for the solicitation" narrative, and language shifts around universal proxy and the 2022 fee-table modernization support empirical work on activism returns, rule-impact studies, and pre/post comparisons across regulatory inflection points.
LLM and RAG teams index the full text of the revised proxy plus exhibit letters and presentations as a high-signal corpus distinct from issuer-filed proxies. Chunking the amendment narrative, nominee biographies, and participant transaction histories — keyed by accession number, subject CIK, and amendment number — produces retrieval indexes for systems that answer questions on dissident arguments, slate evolution, and what specifically changed between mailings.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-dfrn14a-files.json
This endpoint returns dataset metadata (name, description, last updated timestamp, earliest sample date, total record and size counts, form types, container format, and file types), the download URL for the full dataset archive, and the list of individual container files with per-container size, record count, updated timestamp, and download URL. Use it to monitor which containers were refreshed in the latest run and decide which ones to download on a day-by-day basis. No API key is required for this endpoint.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-699d-b91b-213d5112cb6c",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-dfrn14a-files.zip",
4
"name": "Form DFRN14A Files Dataset",
5
"updatedAt": "2026-04-15T12:02:31.443Z",
6
"earliestSampleDate": "1995-04-01",
7
"totalRecords": 605,
8
"totalSize": 10243177,
9
"formTypes": ["DFRN14A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON", "HTML", "PDF"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-dfrn14a-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 13818783,
17
"records": 154,
18
"updatedAt": "2026-04-15T12:02:31.443Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-dfrn14a-files.zip?token=YOUR_API_KEY
Downloads the complete dataset, covering all DFRN14A filings from April 1995 to present, as a single ZIP archive. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-dfrn14a-files/2026/2026-03.zip?token=YOUR_API_KEY
Downloads one monthly container archive instead of the full dataset, which is useful for incremental updates or partial backfills. This endpoint requires an API key.
The dataset covers Form DFRN14A — a revised definitive proxy statement filed by a non-management soliciting party under Rule 14a-6 of Regulation 14A. It is a member of the Schedule 14A family and sits at the precise intersection of three properties: non-management, definitive, and revised.
One record is one complete EDGAR submission of a DFRN14A filing, materialized on disk as an accession-numbered folder. Each folder contains a metadata.json index describing the submission and the filing payload itself — the SGML-wrapped HTML revised proxy statement plus any TXT, HTML, or PDF exhibits the soliciting party included.
Non-management parties soliciting proxies from holders of a Section 12-registered class — typically activist hedge funds, individual large shareholders or shareholder groups, hostile bidders, and dissident slates — file DFRN14A to revise a definitive proxy statement they previously filed on Form DEFN14A. The registrant itself never files DFRN14A; issuer-side revisions go on DEFR14A or are supplemented via DEFA14A.
Filing is event-driven, not periodic. A DFRN14A is filed on or before the date the revised materials are first disseminated to security holders, after a definitive DEFN14A has already been filed. Common triggers include changes to the dissident slate, changes to proposals, correction of misstatements, updates to participant or ownership disclosures, issuer countermoves that shift meeting dates, and responses to SEC staff comments.
Coverage begins April 1, 1995, tracking the phase-in of mandatory EDGAR filing under Regulation S-T, and continues to the present. The dataset is distributed in ZIP container format, partitioned into one archive per filing month under the path YYYY/YYYY-MM.zip, and surfaces TXT, JSON, HTML, and PDF file types.
A DFRN14A revises a prior definitive proxy statement — substantively replacing or supplementing nominees, proposals, or disclosures. A DFAN14A files additional soliciting materials such as fight letters, press releases, investor decks, and scripts without altering the underlying proxy statement. Activist campaigns produce many DFAN14A filings and far fewer DFRN14A filings; the two live in separate datasets under separate accession numbers.
No. Inline graphics referenced by the HTML — proxy-card images, signature scans, logos, and headshots of dissident nominees — are not present in the accession folder. They remain enumerated in metadata.json's documentFormatFiles array with their GRAPHIC document type and original EDGAR documentUrl, so consumers who need the images can resolve them through that URL.