Form PX14A6G Files Dataset

The Form PX14A6G Files Dataset is a complete corpus of "Notice of Exempt Solicitation" filings furnished to the SEC EDGAR system under Rule 14a-6(g) of the Securities Exchange Act of 1934. Each record corresponds to a single PX14A6G accession on EDGAR — one notice furnished by a person conducting a written proxy solicitation that is exempt from the full proxy rules under Rule 14a-2(b)(1) — and bundles a structured metadata.json together with every textual document from the original EDGAR submission, including the cover-page notice and any soliciting-material exhibits. Filers are non-management persons such as activist hedge funds, pension and labor funds, governance and ESG advocacy organizations, faith-based investor coalitions, and individual shareholders, and the form is required of any beneficial owner of more than $5 million of a class of the registrant's securities who transmits written soliciting materials to other holders. The dataset covers filings from March 1994 to the present, distributed as monthly ZIP containers in the path layout <YYYY>/<YYYY>-MM>.zip.

Dataset APIs

Dataset Files

What This Dataset Contains

The Form PX14A6G Files Dataset packages the full text of every PX14A6G "Notice of Exempt Solicitation" submitted to EDGAR since the form first appeared in the modern proxy-rules framework. A PX14A6G filing is the SEC vehicle through which a shareholder (or other person) communicating in writing with security holders to influence a vote — without seeking formal proxy authority and therefore qualifying for the exemption under Rule 14a-2(b)(1) — furnishes copies of those written soliciting materials to the Commission. Under Rule 14a-6(g), any beneficial owner of more than $5 million of a class of the registrant's securities engaged in such an exempt written solicitation must furnish the SEC with the materials no later than three calendar days after they are first transmitted to security holders. The form is also routinely furnished voluntarily by sub-threshold beneficial owners — governance, ESG, and faith-based investor advocates such as As You Sow, ICCR-affiliated orders, public pension funds, and activist hedge funds — that want their materials on the public EDGAR record alongside the registrant's proxy statement.

For each accession the dataset provides a machine-readable metadata.json summary plus every textual document preserved from the EDGAR submission: the SGML-wrapped primary PX14A6G document, any sequence-2+ HTML, PDF, or TXT exhibits, and any supplementary written soliciting materials. Image attachments (EDGAR GRAPHIC documents such as .jpg, .png, and .gif logos, signature scans, and chart raster art) are intentionally excluded, even though the corresponding <IMG SRC="..."> references and documentFormatFiles entries remain visible inside the HTML body and metadata respectively. The container format is ZIP, and constituent file types include TXT, JSON, HTML, and PDF. Coverage runs from March 1994 to present, with new accessions added on the dataset's regular refresh cadence.

Content Structure of a Single Record

What one record represents

One record in the Form PX14A6G Files Dataset corresponds to a single PX14A6G accession on EDGAR — that is, one Notice of Exempt Solicitation furnished under Rule 14a-6(g) of the Securities Exchange Act of 1934 by a person conducting a written proxy solicitation that is exempt from the full proxy rules under Rule 14a-2(b)(1). On disk a record is materialized as a single accession-numbered folder inside the dataset's monthly ZIP archives (<YYYY>/<YYYY>-MM>.zip). The folder name is the 18-digit EDGAR accession number with the dashes removed (accession 0001214659-25-012571 becomes folder 000121465925012571). Each folder bundles one machine-readable metadata.json together with every textual document attached to the original EDGAR submission — the cover-page notice and any soliciting-material exhibits — with image attachments deliberately excluded.

Structural layers

A record has two structural layers. The outer layer is the dataset packaging: an accession-named folder containing a metadata.json plus one or more documents preserved from the EDGAR submission. The inner layer is the SEC content itself: each preserved document is an EDGAR SGML-wrapped body (most commonly HTML, occasionally a wrapped PDF or plain-text exhibit) carrying a Rule 14a-103 cover header followed by the soliciting material. Together the layers provide both a structured handle on the parties, dates, and document index and the full textual body of every written communication transmitted to security holders.

The folder always contains exactly one metadata.json. Beside it sits at least one primary document whose EDGAR document type is PX14A6G and whose SGML sequence is 1; this is the cover-page notice and, in the great majority of filings, also embeds the entire soliciting material in the same file. Some records add further sequence-2+ documents — additional letters, voting recommendation memos, presentation decks rendered as HTML or PDF, press-release attachments, or supplementary text exhibits — when the filer split the submission into multiple documents on EDGAR. Filenames are filer-chosen rather than standardized; common patterns include <filer-stem>_px14a6g.htm, o<digits>px14a6g.htm, or descriptive stems built from the filer's or campaign's name (for example angeloak_px14a6g.htm).

The metadata.json file

metadata.json is a UTF-8 JSON object that distills the EDGAR header and document index for one accession. Top-level fields:

• formType — always the literal string "PX14A6G".
• accessionNo — the dashed 18-digit accession (the on-disk folder uses the un-dashed form).
• effectivenessDate — the EDGAR effectiveness date as YYYY-MM-DD.
• filedAt — the full ISO-8601 acceptance timestamp with Eastern-time offset (e.g. 2025-08-21T17:29:52-04:00).
• description — boilerplate, typically "Form PX14A6G - Notice of exempt solicitation submitted by non-management".
• linkToFilingDetails — absolute URL of the primary document on sec.gov/Archives/edgar/....
• linkToTxt — absolute URL of the EDGAR complete-submission text (the SGML envelope of the entire accession).
• linkToHtml — absolute URL of the EDGAR filing-index page.
• linkToXbrl — empty string; PX14A6G is not an XBRL-bearing form.
• documentFormatFiles — array of objects, one per document logically attached to the accession, each with sequence (string "1", "2", … or a single space " " for the complete-submission wrapper), size (byte count as a string), documentUrl (absolute EDGAR URL), type ("PX14A6G", "GRAPHIC", occasionally "EX-99" family codes, or " " for the wrapper), and an optional description.
• entities — array of party records. The registrant whose securities are the subject of the solicitation appears with its companyName suffixed (Subject); the filing person appears with (Filed by). Subject entries typically carry the rich EDGAR header tail (cik, irsNo, stateOfIncorporation, fiscalYearEnd, act, fileNo, sic, filmNo); filer entries are usually sparser (cik, companyName, type, sometimes irsNo and stateOfIncorporation). A record may carry multiple (Filed by) entities when several investors jointly furnish the same notice.
• id — opaque 32-character hex identifier internal to the dataset.
• seriesAndClassesContractsInformation — array, inert for this form (always empty).
• dataFiles — array, inert for this form (always empty).

Two encoding conventions matter. documentFormatFiles[].size and documentFormatFiles[].sequence are JSON strings, not numbers, and sequence may be a single space character for the complete-submission wrapper entry. The canonical entity fields are listed above; downstream consumers should ignore stray overflow keys that occasionally appear when EDGAR's free-text SIC field bleeds into adjacent properties during header parsing.

The primary PX14A6G document

The sequence-1 primary document is the heart of the record. Despite its .htm (or .html) extension, it is not pure HTML — it is an EDGAR SGML document container wrapping an HTML body. Every primary document opens with a six-to-seven line header of the form:

          1
          <DOCUMENT>
        

          2
          <TYPE>PX14A6G
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>o821253px14a6g.htm
        

          5
          [<DESCRIPTION>PX14A6G]
        

          6
          <TEXT>
        

          7
          <HTML>
        

          8
          ... HTML body ...
        

          9
          </HTML>
        

          10
          </TEXT>
        

          11
          </DOCUMENT>
        

The <DESCRIPTION> line is optional and is sometimes omitted. Any HTML parser must strip the leading SGML wrapper and the trailing </TEXT></DOCUMENT> before treating the body as parseable HTML.

Inside the HTML body the document opens with the standard Rule 14a-103 cover block. This block is conventionally rendered as a centered or boxed header carrying the literal title "Notice of Exempt Solicitation Pursuant to Rule 14a-103" and a small set of labeled fields:

• "Name of the Registrant" — the issuer whose annual or special meeting is being addressed (this is the (Subject) entity in metadata.json).
• "Name of person relying on exemption" — the filer (the (Filed by) entity).
• "Address of person relying on exemption" — the filer's mailing address.
• A boilerplate disclaimer that "Written materials are submitted pursuant to Rule 14a-6(g)(1) promulgated under the Securities Exchange Act of 1934 … Submission is not required of this filer under the terms of the Rule but is made voluntarily in the interest of public disclosure and consideration of these important issues" — voluntary-filing language typical of sub-$5M filers, asserted in prose rather than in any structured field.

After the Rule 14a-103 header comes the soliciting material proper. This portion varies widely in length, layout, and rhetorical form, but it is always written communication directed at the registrant's security holders. Common formats include:

• a vote-recommendation memo, structured with sections such as RESOLVED / THE RESOLUTION, SUMMARY, BACKGROUND, RATIONALE / WHY VOTE FOR, RESPONSE TO BOARD OPPOSITION STATEMENT, and CONCLUSION, urging FOR or AGAINST a specific numbered shareholder proposal or management item at an upcoming meeting;
• a shareholder letter to fellow holders, often signed by a named investor or coalition;
• a "vote no" campaign piece against one or more director nominees, with biographical or governance critiques;
• a slide-deck-style presentation rendered as inline HTML;
• a press release or open letter previously published externally;
• an analytical white paper supporting a contested merger, say-on-pay, ESG, or governance vote.

The body almost invariably names the registrant, the meeting date, the specific item or proposal number, and the requested vote outcome. It typically identifies the filer's beneficial-ownership level (often well below $5 million, accompanied by the voluntary-filing disclaimer) and ends with a contact block — name, title, organization, address, phone, email, and occasionally a URL — and a signature line.

Formatting follows EDGAR-era HTML conventions: inline style="..." attributes on tables, paragraphs, and spans rather than external CSS; Windows-1252-friendly named entities ( , –, ®) and numeric smart-quote entities (“, ”); tables used for layout as well as for data; and embedded <IMG SRC="..."> references for logos, charts, photographs, and infographics. Image references resolve to filenames that were originally submitted to EDGAR as separate GRAPHIC-type documents but, per the dataset's design, are not present on disk (see below).

Additional documents

When a filer split the submission across multiple sequenced documents on EDGAR, each non-image text document is preserved in the accession folder under its filer-chosen filename, with the same <DOCUMENT>…<TEXT>…</TEXT></DOCUMENT> SGML wrapper around the body. Typical secondary documents include additional letters or memos, supplementary EX-99-family textual exhibits, PDF attachments preserved verbatim as .pdf files when the filer submitted them that way, and plain-text exhibits. Each is reflected as its own object in metadata.json's documentFormatFiles array with an integer-string sequence value of "2", "3", etc.

What the dataset includes and excludes

For each accession the dataset includes the metadata.json summary plus every textual document from the original EDGAR submission: the SGML-wrapped primary PX14A6G document, any sequence-2+ HTML, PDF, or TXT exhibits, and any supplementary written soliciting materials the filer attached. The dataset excludes image files. Any document with EDGAR type GRAPHIC (typically .jpg, .jpeg, .png, .gif files used for logos, photographs, signature scans, and chart raster art) is intentionally omitted from the ZIP, even though the corresponding <IMG SRC="..."> references still appear inside the HTML body and the image entries still appear in metadata.json's documentFormatFiles array. Consumers should treat embedded image references as unresolved within the dataset. The EDGAR complete-submission text file (the full SGML envelope of the entire accession, listed in metadata.json with a single-space sequence and type and reachable via linkToTxt) is likewise not copied into the folder; the dataset packages the constituent documents directly rather than the wrapper.

Structural conventions and historical evolution

PX14A6G has existed in essentially its current legal form since the SEC adopted the modern proxy-rules framework in October 1992, and EDGAR submissions of the form are present in the dataset from March 1994 onward. The Rule 14a-103 cover-page schema (registrant name, filer name, filer address, voluntary-submission disclaimer) has been stable across the entire range. What has changed materially over the corpus is the document format used to convey the body, mirroring the broader EDGAR format eras:

• 1994 through roughly 2001 — submissions were typically plain ASCII or lightly formatted text (.txt) wrapped in EDGAR SGML. The Rule 14a-103 cover block appears as a flat text header; the soliciting material is hard-wrapped at ~80 columns; tables are rendered with whitespace alignment; no inline images are present.
• early-to-mid 2000s — HTML-bodied submissions become dominant, still wrapped in the SGML <DOCUMENT><TYPE>PX14A6G<SEQUENCE>1<FILENAME>…<TEXT>…</TEXT></DOCUMENT> envelope. PDF exhibits begin to appear as additional sequenced documents. GRAPHIC exhibits (logos, signature scans, charts) increasingly attach as separate sequence-2+ documents referenced from the HTML.
• late 2000s onward — modern inline-styled HTML with rich tables, embedded images, and external links is the norm. Multi-document submissions become more common when filers attach decks, white papers, or coalition letters as separate sequenced exhibits.

The substantive subject matter has shifted considerably across the same span: early filings skew toward contested-control campaigns and "vote no" letters from institutional investors, while modern filings are heavily weighted toward ESG, climate, human-rights, and corporate-governance proposals routed through advocacy organizations. The Rule 14a-103 content requirements themselves have not been amended in a way that materially changes the cover-page anatomy.

Interpretation and extraction notes

Several conventions matter for downstream extraction:

• Document files cannot be parsed as HTML from byte zero. The leading <DOCUMENT>…<TEXT> SGML preamble must be peeled off and the trailing </TEXT></DOCUMENT> discarded before the body is handed to an HTML parser or serialized.
• The (Subject) and (Filed by) suffixes on entities[].companyName are the canonical way to disambiguate the registrant from the filer; the underlying cik values resolve to two distinct EDGAR entities. A record may carry multiple (Filed by) entities for jointly furnished notices.
• Image references inside the HTML body are unresolved by design. Any rendering pipeline must tolerate missing <IMG> resources and treat the corresponding GRAPHIC entries in documentFormatFiles as informational only.
• The complete-submission .txt wrapper appears in documentFormatFiles (with sequence and type set to a single space) and in linkToTxt, but is not copied into the accession folder; only the constituent documents are.
• The filer's beneficial-ownership level — and, by extension, whether the notice is mandatory under the >$5M threshold or voluntary — is conveyed in body prose rather than as a structured flag. Distinguishing the two requires text inspection of the cover block.
• linkToXbrl, seriesAndClassesContractsInformation, and dataFiles are inert for this form and can be ignored. There is no periodOfReport field; the only date semantics in metadata.json are effectivenessDate and filedAt.
• Filer-chosen filenames, hand-authored HTML, and one-off layout choices flow through verbatim (subject only to the image-stripping rule). Extraction code should be defensive about character encodings, entity escaping, and irregular table structures rather than assuming a normalized schema across filers.

Who Files or Publishes This Dataset, and When

Who files or publishes the record

Form PX14A6G is a notice furnished on EDGAR by a soliciting person other than the registrant. The filer is the third party communicating with shareholders, not the issuer whose securities are at stake; the issuer is identified on the cover page but files its own DEF 14A, PRE 14A, and DEFA14A separately. The filer must be a person relying on the Rule 14a-2(b)(1) exemption — i.e., a solicitor who is not seeking the power to act as proxy and has no substantial interest in the subject matter beyond a security-holder interest.

Recurring filer types include:

• Activist investors and hedge funds running "vote no," "withhold," or vote-against-merger campaigns without distributing a competing proxy card.
• Pension, labor, and union-affiliated funds circulating recommendations on director elections, say-on-pay, and contested proposals.
• Governance and ESG advocacy organizations, including faith-based investor coalitions (e.g., ICCR members) and socially responsible investing groups, supporting or opposing specific shareholder proposals.
• Individual shareholders, including frequent Rule 14a-8 proponents publishing supporting statements and rebuttals to management's opposition.
• Proxy advisors and other commentators in the narrower cases where they distribute written soliciting material beyond ordinary subscription advice.

When the record is created or required

The trigger is event-driven: dissemination of written soliciting materials to security holders in reliance on Rule 14a-2(b)(1). There is no periodic cadence; each qualifying communication generates its own notice.

Mandatory filing is required under Rule 14a-6(g) when the soliciting person:

• relies on the Rule 14a-2(b)(1) exemption,
• beneficially owns securities of the class subject to the solicitation with a market value exceeding $5,000,000, and
• transmits written soliciting materials to other security holders.

Deadline: the materials must be furnished to the SEC within three calendar days of the date the soliciting materials are first sent or given to security holders. The clock runs from first transmission, not from the date the materials are drafted or dated. Each new round of materials in the same campaign generates a separate three-day obligation, so a single shareholder campaign often produces multiple PX14A6G submissions across a proxy season.

Voluntary filings are explicitly contemplated by the SEC's instructions and make up a meaningful share of the population. Sub-threshold owners (at or below $5 million of the relevant class) are not required to furnish notice but routinely use the form to make their materials publicly available on EDGAR. There is no statutory three-day deadline for these voluntary submissions, though filers usually follow the same timing in practice. The dataset does not separately tag mandatory versus voluntary submissions.

Typical underlying events: annual-meeting director elections (including "vote no" / "withhold" campaigns), say-on-pay, Rule 14a-8 shareholder proposals, contested merger or recapitalization votes, governance-related charter or bylaw amendments, and proxy access proposals.

Important distinctions

• Notice of exempt solicitation, not a proxy solicitation. PX14A6G is furnished (not filed for Section 18 liability purposes) and does not seek a proxy card. A formal proxy solicitation by an outside party — one with a competing proxy card or substantial interest beyond a security-holder interest — cannot use Rule 14a-2(b)(1) and instead must file a full Schedule 14A and contested-solicitation forms such as PREN14A, DFAN14A, or DFRN14A. Those filings are outside this dataset.
• Rule 14a-2(b)(1) is conditional. Board nominees, certain affiliates, persons soliciting their own election, and parties with a financial stake in a transaction beyond their shares cannot rely on the exemption and therefore cannot use PX14A6G.
• Antifraud still applies. Rule 14a-9, which prohibits materially false or misleading proxy statements, applies to PX14A6G materials despite the procedural exemption.
• $5M threshold is distinct from 13D/13G. The PX14A6G threshold is a market-value test tied to the class being solicited. It is independent of the 5%-of-class beneficial-ownership threshold for Schedule 13D/Schedule 13G; a filer can be obligated under one regime without the other.
• No registrant obligation is triggered. A PX14A6G filing imposes no filing duty on the subject company, though the issuer may respond with its own DEFA14A.
• Amendments are uncommon. Corrections are typically made by submitting a fresh PX14A6G rather than a PX14A6G/A.
• Foreign private issuers are generally outside Regulation 14A, so PX14A6G filings almost exclusively involve solicitations of holders in domestic Exchange Act reporting issuers.

How This Dataset Differs From Similar Datasets or Filings

Form PX14A6G sits between proxy regulation, beneficial-ownership reporting, and exempt-solicitation activism. It is neither a proxy statement nor an ownership schedule, and the most useful comparisons run along three axes: the proxy-statement family (DEF 14A, PRE 14A, and the contested DFAN/PREN/DFRN14A series, all governed by Schedule 14A), the beneficial-ownership schedules (13D, 13G), the Rule 14a-8 shareholder-proposal regime, and Form 8-K Item 5.07 vote-result disclosures.

DEF 14A and PRE 14A (registrant proxy statements)

DEF 14A is the registrant's definitive proxy statement; PRE 14A its preliminary version. Both are filed under Section 14(a), accompanied by a form of proxy, and subject to the full Schedule 14A line-item disclosure regime, dissemination rules, and Rule 14a-9 antifraud liability.

PX14A6G overlaps only in subject matter: both concern matters being voted on at a meeting. The contrasts are categorical:

• Filed vs furnished. DEF/PRE 14A are filed; PX14A6G is furnished under Rule 14a-6(g).
• Schedule 14A burden. DEF/PRE 14A carry full line-item disclosure; PX14A6G has none.
• Form of proxy. DEF/PRE 14A solicit proxy authority; PX14A6G never does.
• Voice. DEF 14A is management's affirmative ask; PX14A6G is a non-management notice that may align with or oppose management.

DFAN14A, PREN14A, DFRN14A (non-management proxy materials)

These are the workhorses of contested fights: dissidents file definitive or preliminary non-management proxy statements, fight letters, and supplemental soliciting materials under Schedule 14A, often running competing director slates.

This is PX14A6G's closest functional cousin and the most important boundary:

• Solicitation status. DFAN/PREN/DFRN14A filers are conducting actual proxy solicitations and frequently seek proxy authority. PX14A6G filers rely on the Rule 14a-2(b)(1) exemption: no proxy card, no request for authority.
• Filed vs furnished. The DFAN series is filed under Schedule 14A with full participant, cost, and interest disclosures. PX14A6G is a furnished notice triggered only by the $5 million ownership threshold under Rule 14a-6(g).
• Antifraud reach. Rule 14a-9 applies to both, but PX14A6G filers escape the procedural Schedule 14A apparatus.

Campaigns often begin as PX14A6G letters and escalate to DFAN14A filings if they ripen into formal contests; researchers studying activism short of a contest should treat PX14A6G as the lower-intensity sibling.

Schedule 14A (the underlying schedule)

Schedule 14A governs the content of any 14a proxy statement filed by registrants or dissidents. It mandates detailed disclosure of participants, interests in matters to be acted upon, voting securities, and related items.

PX14A6G has no Schedule 14A obligation. The filer identifies itself, the registrant, the proposal, and certifies the >$5 million ownership level. That is the disclosure asymmetry that makes the exemption attractive: extensive public communication is permitted, antifraud liability under Rule 14a-9 still attaches, but the Schedule 14A line-item regime does not.

Schedule 13D and Schedule 13G (beneficial ownership)

13D and 13G report beneficial ownership above 5% of a class of registered voting equity. 13D requires disclosure of plans to influence control; 13G is the passive/qualified-institutional short form.

Two crisp distinctions:

• Threshold metric. 13D/13G use a percentage-of-class trigger (>5%); PX14A6G uses a dollar trigger (>$5 million of the class). A mega-cap holder can clear $5 million while sitting far below 5%; a small-cap holder can be a 5% reporter without owning $5 million worth.
• Position vs communication. 13D/13G disclose the existence, size, and intent of a stake. PX14A6G discloses a public communication about how to vote. A 13D filer often also furnishes PX14A6G; a 13G filer rarely does, because exempt solicitation activity is generally inconsistent with 13G's passive eligibility.

Rule 14a-8 shareholder proposals (embedded in DEF 14A)

Rule 14a-8 lets qualifying small holders place a proposal inside the registrant's own DEF 14A, capped at 500 words of supporting statement. There is no standalone form; the proposal lives as a section of the registrant's filing.

PX14A6G is structurally opposite:

• Container. 14a-8 proposals are embedded in the registrant's filing under registrant control. PX14A6G is a freestanding furnishing by an unrelated holder.
• Constraints. 14a-8 is length- and eligibility-limited. PX14A6G has no length cap, no upper ceiling, and no registrant editorial control — only the $5 million floor.
• Use pattern. PX14A6G is often used to amplify, attack, or expand on a 14a-8 proposal already on the ballot, with sharper rhetoric and recommendations spanning multiple ballot items.

Form 8-K Item 5.07 (vote results)

Item 5.07 reports realized vote results within four business days of a meeting: votes for, against, abstain, broker non-votes, and director-election certifications.

PX14A6G is upstream of Item 5.07. PX14A6G documents pre-meeting attempts to influence outcomes; Item 5.07 documents the outcome itself. They are complements, not substitutes, and Item 5.07 is the most direct measure of whether a PX14A6G campaign moved votes.

Key differences at a glance

Boundary summary

PX14A6G's distinguishing posture: a notice, not a proxy statement; furnished, not filed; dollar-triggered, not percentage-triggered; available only to persons not seeking proxy authority; tethered to Rule 14a-9 antifraud despite the Rule 14a-2(b)(1) procedural exemption.

It occupies the middle band between 13D-style activist positioning and a full DFAN14A contest — broader than 14a-8 (no length limit, no registrant curation) and narrower than DFAN14A (no proxy card, no Schedule 14A apparatus). No other dataset substitutes for it: 13D/13G miss the communication content, DEF 14A misses non-management voices outside 14a-8, DFAN14A misses everything below the formal-solicitation threshold, and Item 5.07 reports only outcomes. PX14A6G is the disclosure footprint of large holders who shape votes through public argument while staying outside the formal proxy-rule regime.

Who Uses This Dataset

PX14A6G filings sit at the intersection of shareholder activism, proxy contests, and exempt solicitation rules. Each record names a registrant, identifies a filer above the $5 million threshold, references a specific ballot item, and attaches the soliciting materials. Different roles draw on different layers of that record.

Corporate secretaries and proxy defense leads

In-house corporate secretaries, IR officers, and proxy defense counsel at registrants monitor exempt solicitations targeting their own issuer and peers. They pull the filer identity, the proposal addressed, and the full exhibit text to brief the board, draft rebuttal language, and coordinate outreach to top holders. Across peers, they study arguments and vote recommendations to anticipate what may be filed against them in upcoming meetings.

Securities and proxy lawyers

Outside counsel and in-house securities lawyers use the dataset to assess compliance with Rule 14a-2(b)(1) and Rule 14a-6(g) and to gauge Rule 14a-9 anti-fraud exposure in dissident statements. They focus on the notice cover page, beneficial ownership disclosures, and the substantive exhibit text. Outputs include exempt solicitation notices for clients, disclosure-adequacy memos, and precedent libraries for contested-vote litigation.

Stewardship and proxy voting analysts

Stewardship teams at asset managers and asset owners review any PX14A6G letters on a contested ballot before casting a vote. They weigh the dissident's exhibit content against issuer disclosures, document the reasoning in internal vote rationale records, and archive the exhibits alongside voting decisions for client and regulatory reporting.

Governance and ESG research analysts

Analysts at governance research groups and ESG-focused asset owners treat the filing flow as a leading indicator of contested votes and thematic campaigns. They mine exhibits for proposal type, sponsor identity, vote recommendations, and supporting argumentation, then merge the content into engagement notes and thematic reports on board accountability, executive pay, climate, and capital allocation.

Proxy advisory and governance research providers

Firms producing vote recommendations integrate PX14A6G filings into meeting-by-meeting analysis. Cover-page metadata links each notice to a specific ballot item; exhibit text captures the dissident's case. This feeds vote recommendation memos, meeting reports for institutional clients, and longitudinal dissent datasets licensed to asset managers.

Activist investors and their advisers

Activist funds, concerned shareholder groups, and the financial and PR advisers supporting them study how prior solicitations were framed, how ownership was disclosed, and which arguments produced traction. The rhetorical structure of attached letters drives campaign design, message testing, and benchmarking against comparable prior campaigns.

Proxy solicitation firms

Solicitors retained by issuers or dissidents map the full population of exempt solicitations on a registrant, identify recurring filers, and time outreach to large holders. They focus on filing date relative to the meeting, filer identity, and exhibit content to advise on counter-messaging, vote projection, and sequencing of issuer communications.

Event-driven and quantitative funds

Event-driven analysts and quant researchers running activism or governance signals use the filing flow as a structured event feed. Features built from filing date, filer identity, target registrant, ownership disclosure, and proposal type are tested against post-filing returns, meeting outcomes, and subsequent corporate actions. The dataset supports signal construction, activism backtests, and real-time alerts on watchlist names.

Academic researchers in finance, law, and governance

Researchers studying shareholder voice, retail-investor mobilization, and the effects of Rule 14a-2(b)(1) use the time-stamped corpus going back to 1994. Metadata supports panel construction; exhibit text supports content analysis, often joined with proxy contest filings, 13D records, and meeting outcomes for empirical work on campaign success and dissident framing.

Financial journalists and data reporters

Reporters covering boardroom disputes, executive pay, and ESG controversies use the dataset to surface newly filed solicitations, read shareholder letters in full, and trace recurring filers across companies and years. Cover-page identification supports filer-target tracking; exhibit narrative supplies direct quotation for breaking coverage and longer-form patterns reporting.

Compliance and market surveillance teams

Compliance officers at broker-dealers and investment advisers, plus exchange surveillance staff, monitor PX14A6G filings around contested votes. They use filer identity, ownership disclosures, and filing timing relative to trading to flag potential coordination, selective disclosure, or market-moving statements for escalation.

LLM and RAG engineering teams

Engineers building proxy-season copilots and vote intelligence tools use the dataset as a training and retrieval corpus. HTML, PDF, and TXT exhibits provide clean shareholder-letter text for chunking and embedding; JSON metadata supports structured filtering by registrant, filer, and date. Outputs include question-answering over dissident arguments, automated exhibit summarization, and classification of campaign themes.

Specific Use Cases

The PX14A6G corpus is most valuable when paired with proxy season workflows, contested-vote tracking, and text mining over dissident soliciting materials. The use cases below tie to specific record fields and exhibit content.

Pre-meeting opposition monitoring for a registrant

Corporate secretaries and proxy defense counsel filter incoming PX14A6G accessions on the (Subject) entity CIK to detect any exempt solicitation targeting their issuer ahead of the annual meeting. The cover-page filer name, filedAt timestamp, and the body's named proposal number drive board briefings, while the soliciting-material text feeds rebuttal drafting and outreach scripts to top holders before the record date.

Vote rationale documentation for stewardship teams

Stewardship analysts at asset managers join PX14A6G records to upcoming meeting calendars by registrant CIK and proposal reference, then archive the full exhibit text alongside the internal vote decision. The recommendation language (FOR / AGAINST / WITHHOLD) and the filer's stated rationale support client-mandated vote rationale records and regulatory reporting on stewardship activity.

Activism campaign benchmarking

Activist funds and their PR advisers query the corpus by recurring (Filed by) CIK to assemble a precedent library of prior campaign letters from peer activists. The attached vote-no memos, white papers, and slide decks supply rhetorical templates, ownership-disclosure phrasing, and structural patterns (RESOLVED / SUMMARY / RESPONSE TO BOARD) that inform message testing and campaign sequencing for the next solicitation.

Event-driven signal construction

Quant researchers transform the filing flow into a structured event feed keyed on effectivenessDate, subject CIK, and filer identity. Features such as filer recurrence, proposal type extracted from exhibit text, and time-to-meeting are tested against post-filing equity returns, Item 5.07 vote outcomes, and subsequent activist escalations into DFAN14A contests.

Retrieval corpus for proxy season copilots

LLM engineering teams chunk and embed the SGML-stripped HTML, PDF, and TXT exhibits to power retrieval over dissident arguments. The metadata.json fields (accessionNo, subject and filer entities, effectivenessDate) provide structured filters for tenant-scoped retrieval, while the exhibit text supports question answering, automated summarization of opposition cases, and classification of campaigns by theme (climate, say-on-pay, director opposition, M&A).

Longitudinal research on shareholder voice

Academic researchers build panels from the 1994-onward corpus by joining subject-entity CIK to CRSP/Compustat identifiers and filer CIK to 13D/13G filer histories. The stable Rule 14a-103 cover schema across format eras supports content analysis on campaign framing, while joins to 8-K Item 5.07 vote tallies enable empirical studies of whether exempt solicitations shifted voting outcomes.

Sub-threshold voluntary-filer identification

Securities lawyers and governance researchers detect voluntarily furnished notices by scanning the cover-page prose for the standard "Submission is not required of this filer" disclaimer rather than relying on a structured flag. Segmenting the corpus into mandatory (>$5M) versus voluntary filers isolates the ESG-advocacy and faith-based-investor subset for compliance precedent work and for thematic analysis of retail-aligned shareholder voice.

Dataset Access

The dataset is accessible through three endpoints: a JSON index for metadata and discovery, a full archive download, and per-container downloads for incremental access.

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

This endpoint returns dataset-level metadata (name, description, last updated timestamp, earliest sample date, total record and size counters, form types, container format, and file types) along with the full list of container files. Each container entry includes its download URL, key, size, record count, and last updated timestamp. Poll this endpoint to detect which monthly containers changed in the most recent refresh and download only those that updated. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6943-94fa-97b3cf14fdcb",
        

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

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

          5
            "updatedAt": "2026-05-06T02:50:44.239Z",
        

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

          7
            "totalRecords": 3561,
        

          8
            "totalSize": 115847929,
        

          9
            "formTypes": ["PX14A6G"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 1842310,
        

          17
                "records": 12,
        

          18
                "updatedAt": "2026-05-06T02:50:44.239Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Returns a single ZIP archive covering all PX14A6G filings from March 1994 to present. Given the modest size of this dataset, downloading the full archive in one request is a practical approach for initial loads or full rebuilds. This endpoint requires an API key.

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

Containers are organized by year and month. Use this endpoint to fetch only one monthly archive, for example to refresh the current month after a daily update or to backfill a single historical period without redownloading the full dataset. The exact container paths are listed in the JSON index. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form PX14A6G, the SEC's "Notice of Exempt Solicitation" furnished under Rule 14a-6(g) of the Securities Exchange Act of 1934. It is the disclosure vehicle through which a non-management person conducting a written proxy solicitation exempt from the full proxy rules under Rule 14a-2(b)(1) furnishes the soliciting materials to the SEC.

What does one record in this dataset represent?

One record is a single PX14A6G accession on EDGAR, materialized as an accession-numbered folder containing one metadata.json plus every textual document from the original EDGAR submission — the cover-page notice and any soliciting-material exhibits. The folder name is the 18-digit EDGAR accession number with the dashes removed.

Who is required to file Form PX14A6G?

Mandatory filing under Rule 14a-6(g) applies to any soliciting person who relies on the Rule 14a-2(b)(1) exemption, beneficially owns securities of the class subject to the solicitation with a market value exceeding $5,000,000, and transmits written soliciting materials to other security holders. Sub-threshold beneficial owners are not required to file but routinely furnish PX14A6G voluntarily — this voluntary subset (often ESG advocacy organizations, faith-based coalitions, and individual Rule 14a-8 proponents) makes up a meaningful share of the corpus.

What is the deadline for filing PX14A6G?

Materials must be furnished to the SEC within three calendar days of the date the soliciting materials are first sent or given to security holders. Each new round of materials in the same campaign generates its own three-day obligation, so a single shareholder campaign often produces multiple PX14A6G submissions across a proxy season.

What time period does the dataset cover?

The dataset includes all Form PX14A6G filings submitted to EDGAR from March 1994 to present. The Rule 14a-103 cover-page schema has been stable across the entire range, though the document body has migrated from plain ASCII text in the 1990s, to SGML-wrapped HTML in the early-to-mid 2000s, to modern inline-styled HTML with rich tables and PDF exhibits from the late 2000s onward.

What file formats are included, and what is excluded?

Each accession folder contains a metadata.json plus every textual document from the original EDGAR submission, with file types spanning TXT, JSON, HTML, and PDF. Image files (EDGAR GRAPHIC documents such as .jpg, .png, and .gif logos, signature scans, and chart raster art) are intentionally excluded, even though <IMG SRC="..."> references in the HTML body and the corresponding entries in documentFormatFiles remain present. Containers are distributed as monthly ZIP archives organized by year and month.

How does this dataset differ from DFAN14A and DEF 14A datasets?

DEF 14A is the registrant's filed proxy statement under the full Schedule 14A regime, and DFAN14A is the dissident's filed non-management proxy statement, typically accompanied by a competing proxy card. PX14A6G is neither: it is furnished (not filed), seeks no proxy authority, carries no Schedule 14A line-item burden, and is triggered by a $5 million dollar threshold rather than the full active-solicitation regime. Campaigns often start as PX14A6G letters and escalate to DFAN14A only when they ripen into a formal proxy contest.