Form PREN14A Files Dataset

The Form PREN14A Files Dataset is a complete EDGAR archive of preliminary proxy statements filed by non-management parties under Section 14(a) of the Securities Exchange Act of 1934 and Rule 14a-6, in situations that are not formally contested solicitations. One record corresponds to a single PREN14A submission, identified by accession number and packaged as a self-contained accession folder containing a synthesized metadata.json descriptor and the original EDGAR document files (TXT, HTML, and PDF) — the preliminary proxy statement itself, any separately filed form of proxy, and supporting attachments. PREN14A is filed by the non-management soliciting party, not by the registrant whose security holders are being solicited, and Rule 14a-6(a) requires the preliminary materials to be on file with the SEC at least ten calendar days before definitive proxy materials are first sent to holders. The dataset spans October 1994 through the present, tracking the full EDGAR era for non-management, non-contested preliminary proxy filings, and is distributed as monthly ZIP containers organized as form-pren14a-files/<YYYY>/<YYYY-MM>.zip.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset assembles every Form PREN14A submission accepted by EDGAR from October 1994 forward, where Form PREN14A is the EDGAR form-type wrapper for a preliminary proxy statement filed by a person other than the registrant in a context that is not a contested solicitation. It is the non-management, non-contested counterpart to PRE 14A (registrant-filed preliminaries) and PREC14A (contested preliminaries). The substantive disclosure backbone is Schedule 14A, the SEC's proxy-disclosure schedule, which dictates the line-items the proxy statement must address. PREN14A typically appears in registered-investment-company shareholder solicitations by independent persons, in solicitations by individual security holders advancing matters under Rule 14a-8, and in third-party solicitations supporting or opposing items already on management's agenda — without rising to the level of a contested election.

For each accession the dataset includes a JSON metadata sidecar plus every document filed in the original EDGAR submission, with the single exception of image binaries (GIF, JPG, PNG), which are stripped by design. Documents are preserved inside their EDGAR SGML <DOCUMENT> envelopes, so the file-type repertoire across the entire dataset window is TXT, HTML, and PDF for content, plus the JSON metadata side-car. Records are packaged into monthly ZIP containers, with each accession unzipping into its own directory named after the dashless accession number (for example 000147793225005675/).

Content Structure of a Single Record

1. What one record represents

One record in this dataset is a single Form PREN14A submission to EDGAR, identified by its accession number and packaged as a self-contained accession folder. Each folder bundles two layers of content:

1. a metadata.json descriptor synthesized from the EDGAR submission header, and
2. the original document files exactly as they were filed, minus image binaries (GIF, JPG, PNG), which are the only content category dropped.

Records are grouped into monthly ZIP containers organized as form-pren14a-files/<YYYY>/<YYYY-MM>.zip. Inside the ZIP, each accession unzips into its own directory named after the dashless accession number (for example 000147793225005675/). The unit of analysis is always one accession equals one record, regardless of how many accessions a given monthly container holds.

2. The legal substance of the underlying filing

In legal substance each filing is a solicitation document directed at the registrant's security holders. It identifies the soliciting party, the registrant whose meeting is involved, the matters to be voted on, and the disclosures required by the relevant Items of Schedule 14A. It is almost always accompanied by — or embeds — a form of proxy (the proxy card itself) that holders would mark, sign, and return. Rule 14a-6(a) requires preliminary proxy material to be filed at least ten calendar days before definitive proxy statement materials are first sent to security holders, which gives the staff a window to review and comment before the definitive (DEFN14A) version is disseminated.

3. Two-stratum content layout

Inside one accession folder the content is organized in two strata:

1. metadata.json — a single JSON object that mirrors the EDGAR submission header and inventories every document attached to the filing. It is always present and is the canonical source for filing-level metadata: form type, accession number, filing timestamp, period of report, links back to sec.gov, the per-document file list, and the array of reporting entities (both the Subject issuer and the Filed by soliciting party).
2. One or more document files — the actual filing artifacts the soliciting party submitted. The primary document is the preliminary proxy statement itself, almost always an HTML file in the modern era, optionally followed by a separately filed form of proxy and any supporting attachments (cover letters to shareholders, supplemental exhibits, voting instructions). The file-types found in the dataset are TXT, JSON, HTML, and PDF; image binaries are stripped out. Each document file is wrapped in EDGAR's SGML <DOCUMENT> envelope, with <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> header tags preceding the embedded HTML or text body.

The complete-submission concatenation (*.txt) — EDGAR's all-in-one SGML wrapper that bundles the header and every document into one file — is itself listed as an entry inside documentFormatFiles, with sequence and type recorded as a literal single space character.

4. Component-by-component breakdown

4.1 The metadata.json descriptor

The metadata object carries the following fields:

• formType (string) — always "PREN14A".
• accessionNo (string) — the dashed accession number (for example "0001477932-25-005675").
• id (string) — opaque internal record identifier (md5-style hex).
• filedAt (string) — ISO-8601 timestamp of EDGAR acceptance, with timezone offset.
• periodOfReport (string, YYYY-MM-DD) — the reporting period the proxy statement is associated with, typically the meeting date or fiscal-period anchor rather than the filing date.
• description (string) — human-readable label, for example "Form PREN14A - Non-management preliminary proxy statements".
• linkToFilingDetails, linkToTxt, linkToHtml, linkToXbrl (strings) — URLs back to the primary document, the SGML complete-submission text, the EDGAR filing index page, and (when applicable) the XBRL package. For PREN14A linkToXbrl is an empty string because proxy statements carry no XBRL.
• documentFormatFiles (array of objects) — one entry per document in the submission. Each entry exposes:
  • sequence (string) — EDGAR sequence number; a single space (" ") for the complete-submission TXT entry.
  • size (string) — file size in bytes, encoded as a string.
  • documentUrl (string) — direct link to the file on sec.gov.
  • description (string) — EDGAR description.
  • type (string) — document type label such as "PREN14A" or "EX-99.1"; a single space for the complete-submission TXT.
• dataFiles (array) — XBRL/data file list; empty for PREN14A.
• seriesAndClassesContractsInformation (array) — fund series/class identifiers from the EDGAR header; populated for investment-company filings (which are common for PREN14A) and empty otherwise.
• entities (array of objects) — every reporting entity from the EDGAR header. PREN14A submissions are characteristically dual-entity: the Subject entity is the registrant whose meeting is the subject of the solicitation, and the Filed by entity is the non-management soliciting party. The two roles are distinguished by a suffix tag in the companyName value (e.g. "… (Subject)" versus "… (Filed by)"). Per-entity fields:
  • cik (string)
  • companyName (string, with the role-suffix described above)
  • type (string) — same as the parent formType
  • For the Subject issuer, additionally: fiscalYearEnd (MMDD), stateOfIncorporation (two-letter code), act (Securities Act number, typically "34"), fileNo, irsNo, filmNo, and tickers (array of ticker strings).
  • The Filed-by entity is sparse — usually only cik, companyName, and type — because individual filers and small holders lack issuer-level identifiers like state of incorporation or tickers.

4.2 The preliminary proxy statement document

The primary document is the proxy statement itself, in HTML in the modern era (occasionally TXT for very early filings, or PDF as an attachment). Once the SGML envelope is stripped, the body follows standard Schedule 14A structure:

• Cover page / Schedule 14A header. Identifies the filing as proxy material under Section 14(a). Checkbox-style fields indicate filing posture: "Filed by the Registrant" versus "Filed by a Party other than the Registrant" (the latter is checked for PREN14A); designation of "Preliminary Proxy Statement" (versus confidential preliminary, definitive, additional materials, or soliciting material under Rule 14a-12); and the fee table indicating "No fee required," fee paid previously, or fee computed per Exchange Act Rule 0-11.
• Identification block. Names the registrant (the Subject issuer) and the soliciting person(s) (the Filed-by party). Both names appear on the cover, with addresses and, for entities, jurisdiction of organization.
• Notice of meeting. Date, time, place (or virtual access details), record date for voting eligibility, and the agenda of matters to be voted upon. Non-management filers often reference the registrant's already-noticed meeting rather than calling a new one.
• Proxy statement body. The substantive disclosure required by Schedule 14A, organized around the matters being solicited. Items commonly invoked include Item 1 (date, time, place), Item 2 (revocability of proxy), Item 3 (dissenters' rights), Item 4 (persons making the solicitation, with expanded disclosure for non-management solicitations), 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, when applicable), Item 8 (compensation), Item 9 (independent public accountants), and the substantive Items keyed to the specific matters — for example Item 14 for mergers and acquisitions, Item 19 for amendments to charter or bylaws, Item 20 for other matters, and Item 21 for the vote required.
• Background and reasons for the solicitation. A narrative explaining why the soliciting party is asking for proxies — opposition to a management proposal, support for a shareholder proposal under Rule 14a-8, advocacy for a specific vote on an investment-company matter, etc.
• Information about the soliciting party. Item 4(b) disclosures: identity, background, employment history, share ownership in the registrant, any contracts or arrangements with the registrant, and the costs and methods of the solicitation (mail, telephone, electronic, or in-person; whether paid solicitors are used).
• Voting procedures and instructions. How to vote in person, by mail, by telephone, or via the internet; how to revoke a previously submitted proxy; and the deadlines for return.
• Form of proxy (proxy card). The actual ballot the holder marks. It restates each matter being voted on with FOR / AGAINST / ABSTAIN boxes (or director-by-director voting boxes), provides signature lines, and contains the legend required by Rule 14a-4 indicating how shares will be voted if the card is signed but unmarked. The proxy card may appear either as a separate file in documentFormatFiles or as the trailing section of the primary HTML document; both layouts occur across the dataset.
• Exhibits and supporting attachments. Letters to shareholders, opinion-of-counsel excerpts, supplemental disclosures, or referenced agreements, when included.

4.3 The SGML document envelope

Every document file inside an accession folder retains the EDGAR SGML wrapper. The opening lines name the document type, sequence, filename, and description, the body sits inside a <TEXT> block, and the file closes with </TEXT></DOCUMENT>. A typical primary-document header looks like:

          1
          <DOCUMENT>
        

          2
          <TYPE>PREN14A
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>angeloak_pren14a.htm
        

          5
          <DESCRIPTION>PREN14A
        

          6
          <TEXT>
        

          7
          <html>... preliminary proxy statement HTML body, often including the embedded proxy card ...</html>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

For HTML documents this means a parser fed the raw bytes will encounter several lines of EDGAR header text before the <html> opening tag, plus closing tags after </html>. Stripping the envelope is a prerequisite for clean rendering or DOM parsing.

5. Included content

A record includes:

• the metadata.json descriptor;
• the primary preliminary-proxy-statement document (HTML, occasionally TXT);
• the form of proxy / proxy card, when filed as a separate document;
• supporting exhibits and attachments as filed (cover letters, supplemental materials, referenced documents) in TXT, HTML, or PDF form;
• the EDGAR SGML headers wrapping each document.

6. Excluded or separate content

• Image binaries are excluded by design. GIF, JPG, and PNG files referenced inside the HTML (logos, signature images, charts) are not present, so <img> tags fail to resolve when documents are rendered offline.
• XBRL / structured data files. Proxy statements are narrative documents and are not subject to XBRL tagging; linkToXbrl is an empty string and dataFiles is an empty array on every PREN14A record.
• Subsequent-stage filings. DEFN14A definitive proxy statements, DEFA14A additional materials, DFAN14A non-management additional materials, PREC14A contested preliminaries, and any amendments under PREN14A/A are separate accessions filed under their own form types and are not part of a PREN14A record.
• EDGAR comment letters and staff correspondence generated during the ten-day pre-distribution review window are filed under separate UPLOAD/CORRESP submissions and are not bundled with the PREN14A.

7. Changes in required content and structure over time

The Schedule 14A line-item framework that PREN14A populates has been amended repeatedly since EDGAR phase-in began in 1993, and the substantive evolution of the proxy statement is visible across the dataset's October-1994-to-present span:

• 1992 executive compensation overhaul. The pre-EDGAR rewrite of Item 8's compensation tables (Summary Compensation Table, Option/SAR grants, long-term incentive plans) defines the format that all PREN14A statements inherit at the start of the dataset window.
• Plain English (1998). Rule 421 plain-English requirements reshaped the prose register and reduced legalese in cover-page disclosures and proxy-statement narrative.
• Rule 14a-8 amendments (1998, 2020). Changes to the shareholder-proposal rule altered the procedural recitations a non-management solicitation must include when it is grounded in a Rule 14a-8 proposal.
• Internet availability of proxy materials (2007 "notice and access," Rule 14a-16). Introduced new cover-page and notice-of-meeting language describing how holders can access materials online and request paper copies. PREN14A statements filed after 2007 commonly reflect this option.
• Say-on-pay and related Dodd-Frank disclosures (2011). Expanded compensation-related disclosures and the periodic say-on-pay and say-on-frequency votes affected the agenda items and Item 24 disclosures.
• Compensation-clawback and pay-versus-performance (2022–2023). New tabular disclosures under Item 402(v) and clawback policy disclosures appear in registrant proxy statements; non-management PREN14A filers typically reference these but do not re-create the registrant's full tables.
• Universal proxy card (Rule 14a-19, effective for meetings after August 31, 2022). Although Rule 14a-19 governs contested director elections — which would normally route through PREC14A rather than PREN14A — the boundary between non-contested and contested classification is meaningful in characterizing PREN14A versus PREC14A populations from late 2022 onward.
• Investment-company disclosures. A substantial share of PREN14A activity involves registered investment companies (closed-end funds, mutual funds), where Schedule 14A is supplemented by Items specific to fund matters (advisory-contract approvals, sub-adviser changes, fundamental-policy changes, board reconstitutions). The seriesAndClassesContractsInformation array in metadata.json reflects this fund context when populated.

8. Changes in data format over time

Filings in 1994–2001 are predominantly plain-text (*.txt) submissions in EDGAR's pre-HTML era, with all formatting expressed in monospace ASCII layouts (column-aligned compensation tables, manually drawn proxy cards). HTML adoption began in the late 1990s and became dominant after EDGAR's HTML-acceptance rule changes around 2002. PDF attachments appear from the early 2000s onward, typically for executed exhibits, scanned letters, or graphically heavy supplementary materials. From the mid-2000s the modern pattern stabilizes: an HTML primary document with optional PDF or HTML exhibits, all wrapped in the SGML <DOCUMENT> envelope. The file-type repertoire across the entire dataset window is therefore limited to TXT, HTML, and PDF for content, plus the JSON metadata side-car.

9. Interpretation notes

• Subject vs. Filed-by entity. Code that selects "the issuer" from entities should not blindly take the first array element; it should match on the (Subject) suffix in companyName. The Filed-by entity is the soliciting party — often an individual or a small holder — and its sparse field set reflects that.
• Embedded vs. separate proxy card. The form of proxy may be its own document or appended to the main HTML; downstream extraction logic that targets the proxy card specifically must handle both layouts.
• SGML envelope leakage. Feeding the raw HTML file to a browser or DOM parser without stripping the EDGAR header and trailer will surface non-HTML text. Treat the <TEXT>...</TEXT> block as the renderable body.
• Broken image references. Because images are excluded, <img> tags resolve to nothing offline; this is by dataset design, not corruption.
• String-typed numerics in metadata. size and sequence inside documentFormatFiles are strings, and sequence can be a single space for the complete-submission TXT entry — numeric coercion code must tolerate this.
• Amendments. A PREN14A may be amended; amendments are filed as separate accessions under their own form designation (PREN14A/A) and are not merged into the original record. Reconstructing the full pre-distribution history of a solicitation requires linking accessions across the registrant's CIK and the soliciting party's CIK by date and meeting context.
• Incorporation by reference. Schedule 14A permits incorporation by reference to the registrant's most recent annual report and to financial statements filed elsewhere; non-management filers frequently incorporate registrant disclosures rather than re-stating them, so the proxy statement body may be shorter than its registrant-filed counterpart while still satisfying Schedule 14A.
• Period of report semantics. periodOfReport for PREN14A typically anchors to the meeting date or the registrant's fiscal-period reference, not to the filing date; treat it as a content-relevance date rather than as a submission timestamp.

Who Files or Publishes This Dataset, and When

Who files the record

PREN14A is filed by the non-management soliciting party, not by the registrant whose security holders are being solicited. Under Rule 14a-1, a "soliciting person" is anyone seeking to procure, withhold, or revoke a proxy. Typical PREN14A filers include:

• Shareholder proponents and activist investors soliciting in support of a precatory or binding proposal, a governance or bylaw change, an advisory vote, or a transaction recommendation, where no opposing director slate is being run.
• Institutional or beneficial holders (hedge funds, pension funds, foundations, family offices, individual record holders) campaigning on a specific agenda item.
• Third parties with an economic or strategic stake in the outcome of a merger, asset sale, charter amendment, say-on-pay vote, or similar matter.
• Groups acting jointly under a written or oral agreement to solicit together; each group member is a soliciting person and the group typically files as joint filers.

The registrant whose holders are being solicited is the subject company and is named in the materials, but it is not the EDGAR filer on a PREN14A submission. Management's preliminary proxy materials are filed separately on PRE 14A.

When the record is created or required

PREN14A is event-driven, with no periodic cadence. It is triggered when all of the following are present:

1. A non-management person intends to solicit proxies, consents, or authorizations from holders of a security registered under Section 12 of the Securities Exchange Act of 1934, bringing the solicitation within Section 14(a) and Regulation 14A.
2. The matter being solicited requires preliminary filing under Rule 14a-6(a) and does not fall within that rule's carve-outs for routine annual-meeting items (uncontested director elections, accountant ratification, Rule 14a-8 shareholder proposals included in the registrant's proxy statement, and certain compensation-plan votes).
3. The solicitation is not contested in the Rule 14a-6 sense — there is no opposing slate of director nominees and no parallel contest — which would otherwise route the filing to PREC14A.

The governing deadline is the ten-calendar-day pre-distribution review window in Rule 14a-6(a): preliminary copies of the proxy statement and form of proxy must be on file with the SEC at least ten calendar days before definitive copies are first sent or given to security holders. The window gives the staff an opportunity (but no obligation) to review and comment. After the period runs and any comments are resolved, the soliciting party files the definitive version on DEFN14A and may begin distribution. A revision to the preliminary materials before going definitive is filed as PRRN14A. Supplemental solicitation communications after definitive filing are made on DFAN14A.

Important distinctions

Soliciting person vs. subject company. The EDGAR filer entity on a PREN14A is the soliciting holder, fund, individual, or group — not the public operating company being voted on, even though that company is the focus of the materials.

Rule 14a-2 exemptions. Communications by persons not seeking proxy authority, and limited solicitations of ten or fewer holders, are exempt from full Regulation 14A and do not generate a PREN14A. The form appears only when the non-management party is subject to the full preliminary-filing requirement of Rule 14a-6(a).

Schedule 13D overlap. Activist filers that cross the five percent beneficial ownership threshold also file Schedule 13D, but the two regimes are independent: 13D reports ownership and intent; PREN14A is the procedural vehicle for soliciting other holders' proxies. Either filing can occur without the other.

Coverage window. The dataset spans October 1994 through the present, tracking the EDGAR era for proxy materials. Pre-EDGAR paper equivalents are not included.

How This Dataset Differs From Similar Datasets or Filings

Form PREN14A is defined by three conjoined conditions: the filer is not management, the matter is not a contested election, and the filing is the original preliminary submission. Every adjacent dataset relaxes exactly one of those conditions. Mapping each neighbor against that grid is the cleanest way to bound this dataset.

Closest related filing types

PRE 14A — management preliminary proxy. Same Rule 14a-6 ten-day pre-clearance regime and same preliminary stage, but filed by the registrant's own management on routine corporate matters (director slates, auditor ratification, equity plans, mergers, charter amendments). PRE 14A volume runs in the tens of thousands across the full registrant universe, while PREN14A is a much smaller corpus by design. Differs on the filer-identity axis only.

DEFN14A — non-management definitive proxy. The distribution-ready successor to a PREN14A from the same filer on the same matter, filed no earlier than ten calendar days after the preliminary version. Use PREN14A to study the initial draft, SEC-staff comment cycles, and redline changes; use DEFN14A for the materials actually mailed to security holders. Differs on the filing-stage axis only.

PRRN14A — revised non-management preliminary proxy. A second-round preliminary filing from a non-management party, typically responding to SEC staff comments or updating disclosures before the definitive version. Same filer population and subject matter as PREN14A but a later iteration. PREN14A captures only the first preliminary submission; PRRN14A captures revisions. Differs on the revision axis only.

PREC14A — preliminary contested proxy. Preliminary materials tied to an election contest, typically a dissident director slate or proxy fight for board control. Filer population (activists, shareholder groups) overlaps heavily with PREN14A, but the contest designation triggers Rule 14a-12 procedures. Decision rule: if a competing slate or contested director vote is at issue, the filing is PREC14A, not PREN14A. Differs on the contest axis only.

DEFC14A — definitive contested proxy. The distributable version of PREC14A. Two axes away from PREN14A (contested and definitive) and not a substitute in either direction.

DFAN14A — additional non-management soliciting materials. Supplemental campaign communications filed after the definitive proxy: fight letters, press releases, investor decks, supplemental Q&As. Short, often single-document filings, not full proxy statements. PREN14A contains the structured Schedule 14A disclosure; DFAN14A contains the campaign-period communications layered on top of the definitive solicitation.

DEF 14A — management definitive proxy. The highest-volume proxy form on EDGAR: the registrant's annual or special-meeting proxy statement, with executive compensation tables, beneficial ownership, audit committee disclosures, and management's voting recommendations. Two axes away from PREN14A (non-management and preliminary). Shares only the underlying Schedule 14A framework.

Schedule 14A vs. form type

Schedule 14A (Rule 14a-101) is the substantive content schedule — the items, tables, and disclosures any proxy statement must satisfy. PRE 14A, PREN14A, PREC14A, PRRN14A, DEF 14A, DEFN14A, DEFC14A, and DFAN14A are EDGAR form-type wrappers that encode three things the schedule itself does not: soliciting party, contest status, and filing stage. PREN14A filings address relevant Schedule 14A items, but the dataset is partitioned by the form-type wrapper, not by schedule content.

Adjacent ownership and event disclosures

Schedule 13D / Schedule 13G. Beneficial ownership filings often submitted by the same activist filers who later file PREN14A materials; 13D in particular signals intent to influence control or policy. Content is disjoint: 13D/13G report ownership percentages, acquisition history, and stated purpose, while PREN14A is the proxy statement itself. Complements, not substitutes — a 13D frequently precedes a PREN14A campaign.

Form 8-K Item 5.07. Issuer-filed disclosure of shareholder vote results after the meeting. PREN14A documents what a non-management party asked shareholders to vote on; Form 8-K Item 5.07 documents what was approved or rejected. Pairing the two traces a non-management proposal from earliest preliminary filing through final tabulated vote.

Boundary summary

PREN14A is the unique intersection of non-management filer + non-contested matter + original preliminary stage. PRE 14A relaxes the filer condition, PREC14A relaxes the contest condition, DEFN14A and DFAN14A relax the stage forward, and PRRN14A relaxes it sideways into a revision. None of these is interchangeable with PREN14A. The dataset is the right choice only when the research question specifically concerns the earliest non-management, non-contested proxy disclosure — typically shareholder proposals, third-party solicitations, or non-control campaigns subject to SEC pre-review where the filer is not the issuer's board.

Who Uses This Dataset

The Form PREN14A Files Dataset is consumed by a small set of professional groups, each anchored to specific record components — the metadata.json descriptor, the Schedule 14A disclosure body, the form of proxy, or the participant identification block.

Securities counsel drafting non-management proxies

Outside proxy counsel and in-house disclosure attorneys use the archive as a precedent library. They focus on Schedule 14A item responses (notably Items 4, 5, 6, 7, and Item 22), the rationale narrative, the form of proxy, and accompanying solicitation letters. The workflow is to redline new drafts against accepted disclosure conventions, calibrate participant disclosures, and cite comparable language when responding to SEC staff comment letters.

Shareholder activism and governance research analysts

Research teams tracking activism and proposal-driven engagement use filer/subject metadata, the matters-to-be-voted description, and shareholder letters for event detection and longitudinal coding. The dataset feeds automated alerts on new non-management filings and structured campaign databases that separate PREN14A activity from PREC14A contests.

Proxy advisors and vote-recommendation analysts

Analysts producing vote recommendations rely on the proposal text, supporting statement, rationale narrative, and form of proxy to see exactly how the proponent frames the ballot item. This is weighed against the issuer's DEF 14A response to produce recommendation reports and policy-aligned case files.

Corporate secretary and investor relations teams at issuers

Issuer-side teams use the dataset for defensive monitoring: early identification of filings naming their company as subject, the proposal language, the soliciting party's prior history, and the proposed proxy card. Output is board briefings, opposition statements, and coordinated outreach to retail and institutional holders before definitive mailing.

M&A bankers and event-driven investors

Deal advisors and merger-arbitrage analysts watch filer identity, disclosed economic interest, vote subject matter, and filing timing relative to pending transactions. A non-management PREN14A targeting a deal target is treated as a signal affecting close probability and feeds spread models and position sizing.

Compliance and disclosure consultants

Consultants advising on Section 14(a) and Rule 14a-6 use the dataset to benchmark procedural compliance: the ten-day timing, required Schedule 14A items, participant identification, and proxy-card format. The corpus is used both prospectively for planned filings and retrospectively for audits.

Academic researchers in corporate governance

Researchers build panel datasets from filer identifiers, subject companies, proposal categories, and filing dates. The 1994-onward coverage supports long-horizon studies of shareholder activism, Rule 14a-8 mechanics, and proxy access.

Proxy solicitor firms and proxy-card designers

Specialist solicitors use the form of proxy and cover materials as a design reference: layout, wording of voting choices, framing (for/against, bundled vs. granular), and patterns from repeat filers. Output is voting cards calibrated for retail comprehension and outreach scripts.

Legal informatics and disclosure-tech engineers

Data teams building EDGAR products consume the metadata file alongside TXT, HTML, and PDF documents to train Schedule 14A segmentation models, classifiers separating PREN14A from PREC14A and DEF 14A, and retrieval systems powering governance-event feeds and search tools.

In summary, counsel and compliance consultants treat PREN14A as precedent; activism researchers, proxy advisors, bankers, and event-driven funds treat it as signal; corporate secretaries treat it as a defensive feed; academics treat it as a long-horizon corpus; solicitor firms treat it as design reference; and disclosure-tech teams treat it as structured input. Each group reads a different slice of the same record.

Specific Use Cases

Concrete workflows the Form PREN14A Files Dataset supports, anchored to the specific record components it exposes.

• Building a non-management proxy precedent library for drafting. Securities counsel index the primary HTML proxy statement, the form of proxy, and the Item 4(b) participant disclosures across accessions, then run redline searches to pull comparable rationale narratives and solicitation-cost language when drafting a new PREN14A or responding to an SEC comment letter on Schedule 14A items. The entities array distinguishes Subject from Filed-by parties so precedents can be filtered by soliciting-party type (individual holder, fund shareholder, third-party group).

• Event detection for shareholder proposal and non-control campaigns. Activism and governance research teams monitor monthly ZIP drops, parse metadata.json for filedAt, the Subject CIK and tickers, and the matters-to-be-voted description, and emit alerts whenever a new non-management preliminary names a covered issuer. Because PREN14A is bounded against PREC14A (contested) and PRRN14A (revisions), the feed cleanly isolates first-round non-contested campaigns for downstream campaign databases.

• Issuer defensive monitoring keyed to Subject CIK. Corporate secretary and IR teams subscribe to the dataset filtered on their own CIK in the entities array with the (Subject) suffix, then triage the proposal text, the soliciting party's prior PREN14A history, and the proposed proxy card layout to brief the board and prepare opposition statements before the ten-day window closes and definitive mailing begins.

• Linking solicitations to outcomes through cross-form joins. Event-driven funds and academics join PREN14A accessions to downstream DEFN14A definitives (same filer, same Subject, ten-plus days later), to PRRN14A revisions, and to Form 8-K Item 5.07 vote results, using accessionNo, Subject CIK, and periodOfReport as the meeting anchor. The output is a panel that traces a non-management proposal from first preliminary draft through tabulated vote.

• Training Schedule 14A segmenters and form-type classifiers. Disclosure-tech engineers ingest the SGML-wrapped HTML, strip the <DOCUMENT> envelope, and label sections (notice of meeting, Item 4 participant disclosure, Item 5 interest, form of proxy) for segmentation models. The same corpus, paired with PRE 14A and PREC14A samples, supplies labeled negatives for classifiers that separate non-management non-contested preliminaries from registrant or contested filings.

• Investment-company proxy benchmarking. Fund counsel and compliance consultants exploit the populated seriesAndClassesContractsInformation array to filter PREN14A records to registered investment companies, then extract advisory-contract approval, sub-adviser change, and fundamental-policy-change disclosures to benchmark fund-specific Schedule 14A item responses across closed-end fund and mutual fund solicitations.

Dataset Access

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

This endpoint returns the dataset metadata along with the list of all available container files. The metadata includes the dataset name, description, last updated timestamp, earliest sample date (1994-10-01), total records, total size, form types covered (PREN14A), container format (ZIP), and file types included (TXT, JSON, HTML, PDF). The containers array lists each monthly archive with its key, size, record count, last updated timestamp, and direct download URL. This endpoint does not require an API key.

The index can be polled to monitor which containers were updated in the most recent refresh run, allowing selective day-by-day downloads of only the changed monthly archives.

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69ab-8b5e-3692b19b49a9",
        

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

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

          5
            "updatedAt": "2026-04-15T12:08:53.390Z",
        

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

          7
            "totalRecords": 410,
        

          8
            "totalSize": 9989327,
        

          9
            "formTypes": ["PREN14A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 412384,
        

          17
                "records": 4,
        

          18
                "updatedAt": "2026-04-15T12:08:53.390Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the full dataset as a single ZIP archive, containing every monthly container from October 1994 to present. This endpoint requires an API key.

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

Downloads one monthly container ZIP rather than the full archive. Container paths follow the YYYY/YYYY-MM.zip pattern and can be discovered through the index JSON API. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form PREN14A, the EDGAR form-type wrapper for preliminary proxy statements filed by non-management parties under Section 14(a) of the Securities Exchange Act of 1934 and Rule 14a-6, in situations that are not formally contested solicitations. It is the non-management, non-contested counterpart to PRE 14A (registrant-filed preliminaries) and PREC14A (contested preliminaries).

What does one record in this dataset represent?

One record is a single Form PREN14A submission to EDGAR, identified by its accession number and packaged as a self-contained accession folder. Each folder contains a metadata.json descriptor synthesized from the EDGAR submission header plus the original document files exactly as filed (preliminary proxy statement, any separately filed form of proxy, and supporting attachments), with image binaries (GIF, JPG, PNG) excluded by design.

Who is required to file Form PREN14A?

PREN14A is filed by the non-management soliciting party — shareholder proponents, activist investors, institutional or beneficial holders, third parties with an economic stake in a vote, or groups acting jointly — when soliciting proxies, consents, or authorizations from holders of a Section 12-registered security in a matter that requires preliminary filing under Rule 14a-6(a) and is not a contested election. The registrant whose holders are being solicited is the subject company and is named in the materials, but it is not the EDGAR filer.

When must a PREN14A be filed?

The form is event-driven, with no periodic cadence. Rule 14a-6(a) requires the preliminary proxy statement and form of proxy to be on file with the SEC at least ten calendar days before definitive copies are first sent to security holders, giving the staff a window to review and comment before the definitive DEFN14A version is distributed.

What time period does the dataset cover?

The dataset spans October 1994 through the present, tracking the full EDGAR era for non-management, non-contested preliminary proxy materials. Pre-EDGAR paper equivalents are not included.

What file format is the dataset distributed in?

Records are distributed as monthly ZIP containers organized as form-pren14a-files/<YYYY>/<YYYY-MM>.zip. Inside each container, every accession unzips into its own directory and contains a metadata.json plus the original EDGAR documents in TXT, HTML, or PDF, each still wrapped in the EDGAR SGML <DOCUMENT> envelope.

How does PREN14A differ from PREC14A and PRRN14A?

PREC14A is the preliminary form for contested solicitations involving an opposing slate of director nominees or a parallel proxy fight, which triggers Rule 14a-12 procedures rather than the standard PREN14A track. PRRN14A is a revised non-management preliminary, typically responding to SEC staff comments before the definitive version. PREN14A captures only the first, non-contested preliminary submission from a non-management filer.