Form SC14D9F Files Dataset

The Form SC14D9F Files Dataset is a structured collection of solicitation/recommendation statements filed on EDGAR by foreign private issuers (FPIs) whose equity securities are the target of a third-party tender offer conducted under the cross-border accommodation in Rule 14d-1(b). Each record corresponds to a single EDGAR accession — one Form SC14D9F initial filing or SC14D9F/A amendment — and bundles the parsed filing header (metadata.json) with the main Schedule 14D-9 statement and every attached exhibit (including the home-jurisdiction directors' or trustees' circular that typically carries the substantive disclosure). The dataset is distributed as monthly ZIP containers holding HTML, JSON, and TXT files; image binaries listed as GRAPHIC in the EDGAR manifest are catalogued but excluded. Coverage runs from March 2002, when EDGAR-required electronic filing of Form SC14D9F began, to the present. Form types covered are SC14D9F and SC14D9F/A.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures the U.S.-filed target-side response in cross-border third-party tender offers conducted under Section 14(d)(4) of the Securities Exchange Act of 1934 and Rules 14d-1(b) and Rule 14e-2(c). One record is one EDGAR accession, identified by its eighteen-character accession number, and is materialized as a self-contained directory bundling the parsed filing header together with every document the filer attached, with the single exception of binary image assets. A record therefore captures both the structured "what was filed and by whom" layer and the rendered "what the filing actually says" layer for one solicitation/recommendation statement issued by a foreign private issuer in response to a third-party tender offer.

Form SC14D9F is the foreign-private-issuer counterpart to Schedule 14D-9. The cross-border accommodation permits the subject company to discharge its U.S. solicitation/recommendation obligations by filing a form whose substantive content can be satisfied largely by attaching the home-jurisdiction equivalents — most commonly a Canadian directors' or trustees' circular under provincial securities legislation, but also analogous bidder/target circulars from other jurisdictions. The form lets the subject company's board communicate its position on the offer (accept, reject, express no opinion, or remain neutral) to U.S. security holders while identifying the bidder, the terms of the offer, the securities sought, and any past contacts, transactions, or arrangements that bear on the recommendation. SC14D9F/A is the amendment variant, used to add information, correct a prior filing, or attach updated home-jurisdiction documents.

The dataset is delivered as ZIP archives partitioned by filing month, with file content carried as HTML (the dominant carrier for both the main statement and exhibits), TXT (for the complete-submission stream and the occasional legacy text attachment), and JSON (used exclusively for metadata.json). Coverage begins in March 2002, when EDGAR-required electronic filing of the form took effect, and continues to the present.

Content Structure of a Single Record

What one record represents

One record in the Form SC14D9F Files dataset corresponds to a single EDGAR accession — one Form SC14D9F or Form SC14D9F/A submission as it was accepted by EDGAR and identified by its eighteen-character accession number. The record is materialized as a self-contained directory that bundles the parsed filing header (metadata.json) together with every document the filer attached to that submission, with the single exception of binary image assets.

Container and directory layout

The dataset is distributed as ZIP archives partitioned by filing month. Each archive's name encodes the year and month (for example 2017-02.zip) and decompresses to a single year-month directory of the same name. Inside that directory, each EDGAR accession occupies its own subfolder whose name is the accession number with dashes stripped — the eighteen-character compact form (for example 000166145817000007 for accession 0001661458-17-000007). The accession folder is the unit of a record: everything pertaining to one submission lives inside that one folder, and nothing outside it is required to interpret the record.

          1
          2017-02/
        

          2
            └── 000166145817000007/
        

          3
                  ├── metadata.json
        

          4
                  ├── highlands-schedule14dx92x1.htm     (main SC14D9F document)
        

          5
                  └── tenderofferwebsitenotice.htm       (EX-99.(A)(1) exhibit)
        

Per-accession contents

Within each accession folder the following components appear:

• metadata.json — always present, exactly one per accession. Provides the parsed filing header and an inventory of every document in the original EDGAR submission, including those excluded from the archive.
• Main SC14D9F or SC14D9F/A document — almost always an HTML file (.htm), carrying the body of the Schedule 14D-9 statement. The filename is filer-chosen (for example highlands-schedule14dx92x1.htm) and is resolvable through metadata.json by selecting the documentFormatFiles entry whose type equals SC14D9F or SC14D9F/A.
• Exhibits — zero or more attachments listed in documentFormatFiles under EDGAR exhibit types in the EX-99.(…) family. These are most often HTML; legacy or simple attachments occasionally appear as plain text.
• Complete submission text file — when included, <accession>.txt is the full concatenated SGML submission as received by EDGAR.
• Excluded images — GRAPHIC entries in documentFormatFiles (.jpg, .gif, .png) are catalogued in metadata but are not extracted into the folder; their documentUrl values still resolve to the originals on sec.gov.

The file-types found inside a record folder are HTML (the dominant carrier for both the main statement and exhibits), TXT (for the complete-submission stream and the occasional legacy text attachment), and JSON (used exclusively for metadata.json).

metadata.json field anatomy

The metadata file is a single JSON object that combines the parsed EDGAR header with the document manifest. Its primary fields are:

• formType — either SC14D9F or SC14D9F/A.
• accessionNo — the canonical dashed EDGAR accession number (e.g., 0001661458-17-000007).
• filedAt — ISO-8601 timestamp with timezone for EDGAR acceptance time.
• description — short human-readable form description, typically "Form SC14D9F - Solicitation/Recommendation Statements".
• linkToFilingDetails — URL of the primary filing document on sec.gov.
• linkToTxt — URL of the complete submission text file (<accession>.txt).
• linkToHtml — URL of the EDGAR filing index page (<accession>-index.htm).
• linkToXbrl — XBRL instance URL; empty for SC14D9F filings.
• id — internal record identifier (hex hash).
• documentFormatFiles — an ordered array of every document in the EDGAR submission. Each entry contains:
  • sequence — EDGAR sequence number as a string (the complete-submission text file uses a blank sequence).
  • type — EDGAR document type (SC14D9F, SC14D9F/A, EX-99.(A)(1), GRAPHIC, etc.).
  • description — filer-supplied label (e.g., "EXHIBIT 99.(A)(1)", "Complete submission text file").
  • documentUrl — absolute URL of the document on sec.gov.
  • size — byte size as a string.
• dataFiles — reserved for XBRL/financial-data attachments; consistently empty for this form type.
• seriesAndClassesContractsInformation — series/class metadata used by fund filers; typically empty for SC14D9F.
• entities — array of entities parsed from the EDGAR header. Each entity carries cik, companyName (often suffixed with role such as "(Filed by)" or "(Subject)"), type, sic (industry code and label), stateOfIncorporation, fiscalYearEnd, irsNo, and where applicable act, fileNo, and filmNo. Because the foreign private issuer is typically both the filer and the subject company on an SC14D9F response, the array commonly contains at least two entries with role-suffixed names distinguishing the filer role from the subject-company role.

SGML envelope versus HTML body

Every document in the submission — the main statement and each exhibit — is wrapped in EDGAR's standard SGML <DOCUMENT> envelope. The wrapper is not HTML and must be stripped before HTML parsing of the inner body. The envelope structure is:

          1
          <DOCUMENT>
        

          2
          <TYPE>SC14D9F
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>highlands-schedule14dx92x1.htm
        

          5
          <DESCRIPTION>SC14D9F
        

          6
          <TEXT>
        

          7
          <html>... full HTML body of the Schedule 14D-9 statement ...</html>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

The <TYPE> aligns with documentFormatFiles[].type, <SEQUENCE> with documentFormatFiles[].sequence, and <FILENAME> with the on-disk file name in the accession folder. The complete-submission .txt stream, when present, is the concatenation of these envelopes prefixed by an <SEC-HEADER>/<SEC-DOCUMENT> block whose fields mirror the structured contents of metadata.json (CIK, company name, form type, filing date, file numbers, addresses, and so on). The header block provides a parallel, line-oriented view of the same data carried in JSON.

Main document: Schedule 14D-9 item structure

The HTML body of the main SC14D9F document is a Schedule 14D-9 solicitation/recommendation statement adapted for the foreign-private-issuer context. Its conventional structure, in order, is:

• Cover page identifying the subject company, the filing person, the class of securities being tendered and its CUSIP, and the name, address, and telephone number of the authorized representative in the United States.
• Introduction naming the bidder/offeror, summarizing the offer price, identifying the maximum number or proportion of shares sought, citing the Schedule TO under which the third-party offer was made, and stating the expiration time of the tender offer.
• Item 1. Subject Company Information — name, address, and securities of the subject company.
• Item 2. Identity and Background of Filing Person — identification of the person filing the statement and the relationship to the subject company.
• Item 3. Past Contacts, Transactions, Negotiations and Agreements — material agreements, arrangements, understandings, or conflicts of interest between the subject company and either the bidder or the subject company's own officers, directors, or affiliates.
• Item 4. The Solicitation or Recommendation — the substantive core, containing the board's recommendation (accept, reject, neutral, or no opinion), the reasons supporting it, and the intentions of executive officers, directors, and affiliates with respect to tendering their own securities.
• Item 5. Person/Assets, Retained, Employed, Compensated or Used — identification of any person retained to make solicitations or recommendations on behalf of the subject company.
• Item 6. Interest in Securities of the Subject Company — transactions in the subject securities during the prior sixty days by the subject company or its executive officers, directors, affiliates, or subsidiaries.
• Item 7. Purposes of the Transaction and Plans or Proposals — any negotiations or transactions undertaken by the subject company in response to the tender offer.
• Item 8. Additional Information — supplementary disclosures including regulatory approvals, appraisal rights, anti-takeover statutes, litigation, and any other material information necessary to keep prior statements from being misleading.
• Item 9. Exhibits — the list of attached exhibits; the anchor that ties the main document back to the EX-99 files in the accession folder.
• Signature block — execution by the filing person, often through an authorized U.S. representative.

Because of the Rule 14d-1(b) accommodation, the items themselves are frequently terse and direct the reader to home-jurisdiction documents attached as exhibits. A Canadian target, for example, may answer several items by pointing to the directors' circular filed under provincial securities legislation, which is itself attached as an EX-99 exhibit. Item 4 in particular may consist of little more than a one-sentence recommendation whose full rationale resides in the attached circular.

Exhibits

Exhibits use the lettered SC14D9F exhibit convention EX-99.(A)(1), EX-99.(A)(2), ..., EX-99.(E)(1), grouping materials by category (offer-related documents, financial information, agreements, opinions, and other materials). Each exhibit is independently wrapped in its own SGML <DOCUMENT> envelope, sequenced after the main document, and described in the documentFormatFiles manifest. Typical exhibit content includes:

• Home-jurisdiction filings such as directors' circulars, trustees' circulars, target-company statements, and bidder/target circulars filed by the subject company in its country of incorporation to satisfy local takeover-bid rules. These are the documentary substrate on which the Rule 14d-1(b) accommodation rests and are frequently the longest documents in the record, carrying the bulk of substantive disclosure (board rationale, financial advisor opinions, transaction background, share ownership tables).
• Press releases and letters to security holders announcing or elaborating the board's position on the offer.
• Condensed recommendation notices intended for posting to shareholders — for example, a website notice headed "Recommendation to Reject the Unsolicited Tender Offer..." or an analogous "Recommendation to Accept" caption.
• Fairness opinions, agreements, and supporting materials cross-referenced from Items 3, 4, or 8 of the main statement.

When an exhibit's original HTML embeds image references (<img src="...jpg">), the SGML wrapper for the HTML exhibit is present in the accession folder but the referenced image binaries are not, because images are excluded from the archive.

SC14D9F versus SC14D9F/A

Records with formType SC14D9F are initial filings; records with formType SC14D9F/A are amendments to a previously filed solicitation/recommendation statement. The structural anatomy of an amendment is identical to the initial filing — the same accession-folder layout, the same metadata schema, the same SGML envelopes, and the same Item 1–9 framework. What differs is the substantive content: an amendment typically narrows to the items being amended, often restating only the items affected by new developments, and carries new or updated exhibits (a supplementary directors' circular, an updated press release, an additional letter to shareholders following a revised bid, or a notice of variation). Amendments do not reproduce unchanged items from the initial filing; reconstructing the full state of the recommendation at any point in the offer's life requires assembling the original SC14D9F with all subsequent SC14D9F/A accessions. Because each amendment is a distinct EDGAR accession, a single tender offer can produce multiple records in the dataset, each as its own folder.

Included content

Each record includes the parsed metadata.json, the main SC14D9F or SC14D9F/A document, every exhibit document filed under the submission (other than image binaries), and — when carried by the source submission — the complete-submission .txt stream. File types found inside a record folder are HTML, TXT, and JSON.

Excluded content

Image attachments listed as GRAPHIC in documentFormatFiles — typically .jpg, .gif, or .png files referenced from within HTML exhibits (scanned signatures, logos, slide imagery) — are deliberately omitted from the archive. The manifest still enumerates them so that their existence, sequence, byte size, and original documentUrl on sec.gov remain discoverable, but their binary content is not bundled. HTML exhibits that reference excluded images will render with broken <img> tags when viewed locally; the text and tabular content of those exhibits is unaffected.

Historical structure and format

Form SC14D9F has been received on EDGAR since the form's electronic-filing requirement took effect in March 2002. Across the dataset's history the form's item structure — Items 1 through 9 framing identity, prior contacts, the recommendation, retained persons, security-interest disclosures, transaction purposes, additional information, and exhibits — has remained stable, as has the underlying Rule 14d-1(b)/14e-2(c) accommodation that permits home-jurisdiction documents to carry much of the substantive disclosure. From the start of the EDGAR-required era, filings have been submitted as HTML wrapped in EDGAR's SGML envelope rather than in the older ASCII-only style of pre-2002 paper-era filings, so file formats are consistent across the dataset. Variation between records is driven primarily by issuer practice and home-jurisdiction document conventions rather than by changes to the form itself.

Interpretation and extraction notes

Several nuances matter when reading or extracting from these records.

• Distributed substance. The substance of an SC14D9F is typically split between a terse main document and one or more home-jurisdiction exhibits. Reading Item 4 in isolation may yield only a short recommendation sentence whose reasoning sits in an attached directors' circular; full analysis requires the exhibits.
• Filer-and-subject duality. Because the foreign private issuer is usually both filer and subject, the entities array carries role-suffixed company names ("(Filed by)", "(Subject)") that should be parsed as role labels rather than treated as distinct legal persons.
• Amendment chaining. Amendments (SC14D9F/A) must be linked to their parent SC14D9F by file number or by the bidder/target identity in order to reconstruct the complete state of the recommendation across the offer's life.
• Manifest as source of truth. metadata.json's documentFormatFiles is the authoritative inventory of what was filed — including the image assets excluded from the archive — and should be the basis for completeness checks; the archive itself supplies the textual and tabular content needed to read the filing.
• Envelope stripping. The SGML <DOCUMENT> wrappers around each file are not HTML and should be stripped (or the inner <TEXT> block isolated) before HTML parsing. When consuming the complete-submission .txt stream, the leading <SEC-HEADER> block provides a parallel, line-oriented view of the same header fields available structurally in metadata.json.
• Image-aware rendering. Local rendering of HTML exhibits will show broken image references for any GRAPHIC entries listed in the manifest; downstream consumers that need imagery should resolve them from documentUrl against sec.gov.

Who Files or Publishes This Dataset, and When

Who files

Form SC14D9F is filed by the subject company in a third-party tender offer — specifically, a foreign private issuer (as defined in Exchange Act Rule 3b-4) whose equity securities are the target of the bid. The filer is the target issuer, not the bidder, not the dealer-manager, not the depositary, and not any security holder group. Directors and officers sign on behalf of the issuer entity.

Eligibility depends on qualifying for the cross-border tender offer framework in Rule 14d-1(b). In practice this is dominated by Canadian issuers, because Rule 14d-1(b) was designed to dovetail with Canadian provincial takeover-bid regimes, but any qualifying foreign private issuer may use the form.

The bidder side of the same transaction files SC14D1F (with SC14D1F/A amendments) under Rules 14d-1(b) and Rule 14d-3. That is a separate filer and a separate dataset.

Triggering event

The obligation is triggered when a third-party tender offer is made for an FPI subject company's equity securities under circumstances where Rule 14d-1(b) applies.

• Section 14(d)(4) of the Exchange Act prohibits the subject company (or persons acting on its behalf) from soliciting or recommending action on the offer unless the prescribed disclosures accompany or are filed with that solicitation.
• Rule 14e-2 requires the subject company to communicate its position on the offer no later than 10 business days after the tender offer is first published, sent, or given to security holders.
• Rule 14e-2(c) and Rule 14d-1(b) route the FPI subject company's recommendation onto Form SC14D9F instead of Schedule 14D-9, and permit the substantive content to be satisfied by the issuer's home-jurisdiction takeover-bid response document (such as a Canadian directors' circular).

Under Rule 14e-2, the board's statement must take one of four positions: (i) recommend acceptance, (ii) recommend rejection, (iii) express no opinion and remain neutral, or (iv) state that it is unable to take a position — together with the reasons for the position taken or for the inability to take one.

The U.S. filing tracks the home-jurisdiction timeline: the issuer files Form SC14D9F by the time it disseminates its directors' circular or equivalent response document under local law. For Canadian bids this typically falls within the 14e-2 10-business-day window, since provincial rules require delivery of a directors' circular shortly after commencement of the bid.

Regulatory framework in brief

• Section 14(d)(4) — statutory basis for subject-company solicitation/recommendation disclosure.
• Regulation 14D (Rules 14d-1 to 14d-11) — third-party tender offers for Section 12-registered equity securities. Rule 14d-1(b) defines the cross-border accommodation and the "F" forms (SC14D1F, SC14D9F).
• Regulation 14E (Rules 14e-1 to 14e-8) — applies to all tender offers. Rule 14e-2 imposes the recommendation duty; Rule 14e-2(c) provides the cross-border carve-out.

The regime exists to avoid forcing the FPI to prepare a duplicative U.S.-style Schedule 14D-9 when local takeover-bid rules already require a substantively equivalent directors' circular. Form SC14D9F functions largely as a wrapper that attaches the home-jurisdiction document and supplies the limited U.S.-specific information.

SC14D9F/A amendments

An SC14D9F/A is required whenever a material change occurs in the information previously disclosed. Common triggers:

• change in the board's recommendation (e.g., neutral to rejection, or rejection to acceptance following a bid increase or negotiated deal);
• amendment to the price or terms of the bid;
• emergence of a competing or superior proposal;
• entry into a support, lock-up, or alternative transaction agreement;
• material litigation or regulatory developments affecting the board's analysis;
• extension, expiration, or withdrawal of the bid;
• filing of supplementary directors' circulars or notices of change under local law (typically attached as exhibits).

A contested cross-border bid often produces several SC14D9F/A amendments in addition to the initial SC14D9F.

Important distinctions

• Domestic subject companies (non-FPIs, or FPIs where U.S. holder ownership exceeds Tier I thresholds and the cross-border exemption is unavailable) file Schedule 14D-9, not SC14D9F.
• Bidders in cross-border third-party offers file SC14D1F; domestic third-party bidders file Schedule TO (SC TO-T); issuer self-tenders use SC TO-I. None of these belong in this dataset.
• The dataset captures only the target-side filings in cross-border third-party tender offers conducted under Rule 14d-1(b), filed by FPI subject companies. It excludes domestic 14D-9 filings, issuer self-tender responses, and all bidder-side documentation.

How This Dataset Differs From Similar Datasets or Filings

Form SC14D9F occupies a narrow corner of the tender offer regime: target-board responses filed by foreign private issuers under the Rule 14d-1(b) cross-border framework. It shares vocabulary, statutory citations, and deal context with several adjacent forms. The comparisons below isolate the nearest neighbors and the exact line where SC14D9F begins and ends.

Schedule 14D-9 (SC 14D9) — the domestic target response

The U.S. domestic analogue. Both forms carry the board's recommendation (accept, reject, neutral, or unable to take a position), reasoning, fairness opinions, conflicts, and bidder arrangements under Section 14(d)(4) and Rule 14d-9.

Differences:

• Filer population: SC 14D9 is for U.S. domestic targets; SC14D9F is restricted to issuers meeting the Rule 3b-4 FPI definition.
• Structure: SC 14D9 requires item-by-item responses on the SEC's prescribed schedule. SC14D9F is built to wrap or incorporate a home-jurisdiction directors' circular or equivalent local document.
• Volume: SC 14D9 is a high-volume population; SC14D9F is a thin specialty dataset.

Schedule 14D-1F (SC14D1F) — the bidder-side cross-border twin

The mirror image of SC14D9F. Same exemptive framework, same Rule 14d-1(b) eligibility, frequently filed in matched pairs in the same deal.

Difference is purely directional: SC14D1F holds the bidder's offer terms, financing, plans, and conditions; SC14D9F holds the target board's response to that offer. A complete cross-border deal file requires both, matched by subject company and offer date.

Schedule TO (SC TO-T, SC TO-I, SC TO-C) — the modern domestic offer statements

Schedule TO replaced Schedule 14D-1 in 2000 for domestic tender offers: TO-T (third-party), TO-I (issuer self-tender), TO-C (pre-commencement communications). All three are offeror-side statements.

SC14D9F is not a Schedule TO analogue. The procedural parallel is one level removed: Schedule TO triggers an SC 14D9 response domestically; SC14D1F triggers an SC14D9F response in qualifying cross-border deals. Researchers pair TO with SC 14D9 for U.S. deals, and SC14D1F with SC14D9F for cross-border deals.

Form CB and Form F-X — the Tier I / Tier II exemption pathway

Form CB is the lightweight notification used by bidders or targets in cross-border tender offers, rights offerings, and business combinations relying on the Tier I or Tier II exemptions (Rule 13e-4(h)(8), Rule 14d-1(c), Rule 14d-1(d)). Form F-X is the accompanying appointment-of-agent-for-service-of-process filing for non-U.S. filers using Form CB.

Distinction is regulatory pathway, not direction:

• Form CB rides the exemption regime: home-country documents are simply furnished, with minimal U.S.-specific content.
• SC14D9F rides the full-form Rule 14d-1(b) regime: prescribed U.S. content requirements apply, even though home-country circulars may be incorporated.

In current practice Tier I / Tier II has largely supplanted the full-form path, which is why the SC14D9F population is small and grows slowly. A complete view of FPI target responses requires SC14D9F plus the relevant Form CB filings.

SC14D9F/A — amendments to the same disclosure thread

The "/A" suffix is an amendment to a prior SC14D9F, triggered by a changed recommendation, supplemental information, or revised offer terms. Not a distinct regime: SC14D9F/A belongs to the same event as the underlying SC14D9F and should be linked to it for event-study or longitudinal work. Both are included in this dataset.

SC 14D9/A — domestic amendments

The domestic counterpart to SC14D9F/A. Volume is far higher because the underlying SC 14D9/A population is far larger. Filer eligibility and structural differences track those of the underlying forms.

Form 6-K — FPI ongoing disclosure (peripheral)

The catch-all current report FPIs furnish whenever they release material information in their home jurisdiction. Overlap with SC14D9F is incidental: both can carry tender offer information, and an FPI target may furnish home-country bid coverage on Form 6-K alongside its SC14D9F.

Sharp differences:

• Trigger: 6-K is furnished on home-country publication of any material event; SC14D9F is mandatory under Section 14(d)(4) and tied specifically to a third-party tender offer.
• Legal effect: 6-K is furnished (not filed); SC14D9F is filed with prescribed content liability.
• Scope: 6-K is open-ended subject matter; SC14D9F is confined to the board's position on a specific offer.

Boundary summary

SC14D9F is the only dataset that combines all four distinguishing axes simultaneously:

1. Target-side, not bidder-side (separates it from SC14D1F and all Schedule TO variants).
2. Full-form Rule 14d-1(b), not exemption-based (separates it from Form CB / Form F-X).
3. Foreign private issuer-only (separates it from SC 14D9 and SC 14D9/A).
4. Tender-offer-specific, not general disclosure (separates it from Form 6-K).

No other SEC filing type sits at this intersection. SC14D9F is the exclusive source for the official U.S.-filed board recommendation of an FPI target responding to a Rule 14d-1(b) third-party bid. When the cross-border deal instead uses Tier I or Tier II relief, the equivalent target response appears in Form CB or is furnished via 6-K, so SC14D9F captures only a slice of the global FPI takeover-response universe and must be combined with Form CB and selected 6-K filings for full coverage.

Who Uses This Dataset

SC14D9F is low volume but precisely consumed. The dataset serves a narrow but defined set of professionals, each working a specific layer of the record — the metadata, the main Schedule 14D-9 item structure, the attached home-jurisdiction circulars, or the SC14D9F/A amendment chains.

Cross-border M&A lawyers and disclosure counsel

Used as a precedent library for Rule 14d-1(b) and Rule 14e-2(c) compliance. Counsel mines Items 1-3 for how peers framed FPI status and the offeror relationship, Item 4 for recommendation language ("recommend," "reject," "neutral," "unable to take a position") and supporting rationale, attached home-jurisdiction circulars for wraparound treatment, and SC14D9F/A chains for sequencing of supplemental disclosure. Output: the recommendation statement and exhibit package.

Sell-side M&A bankers advising the target

Banking teams retained by the subject board use Item 4 reasoning and any reproduced fairness opinion exhibits to benchmark comparable-transaction analysis, premium ranges, DCF references, and scope/qualifications language across cross-border deals. Metadata fields (CIK, filing date, amendment count) build peer sets by industry and deal structure. Output: a defensible Item 4 narrative, the fairness opinion, and pitch decks citing precedent FPI responses.

Merger arbitrage and event-driven analysts

Treat SC14D9F as a primary signal in cross-border tender trades. They read Item 4 for recommendation direction and conviction, Item 8/additional information for conditions and regulatory hurdles, and the rationale for references to competing bids or go-shop activity. SC14D9F/A timestamps in metadata.json track stance changes as the offer is revised or extended. Output: spread-trade theses sized to probability of close and cross-border friction (foreign investment review, multi-jurisdiction antitrust, exchange controls).

Proxy solicitors and information agents

Solicitation firms align telephone scripts and shareholder letters with Item 4's stated position, plan outreach against filing-date and amendment cadence captured in metadata, and pull prior press releases and shareholder letters from exhibits as templates. Output: solicitation schedules and communication scripts for a multi-jurisdiction holder base.

In-house compliance at FPI targets

Securities-law staff at FPIs that could become tender targets use the dataset to build response playbooks. They map Items 1-9 against an internal filing checklist, confirm Rule 14d-1(b) eligibility and Rule 14e-2(c) home-jurisdiction document treatment, and study SC14D9F/A patterns to set triggers for supplemental disclosure. Output: tender-offer response playbooks, disclosure controls procedures, and director briefings.

Securities litigators and plaintiffs' counsel

Used for breach-of-fiduciary-duty and disclosure claims. Item 4 language is compared across rejected-offer cases; Item 5 (persons retained and compensation) and Item 6 (interest in securities of directors and officers) are screened for conflicts; SC14D9F/A diffs are matched to litigation timelines to identify pressured disclosures. Output: complaint exhibits, expert reports on disclosure adequacy, and benchmarking memos.

Academic researchers and policy analysts

Researchers in corporate finance and securities law treat the dataset as a structured population of FPI tender responses since 2002. They code Item 4 for recommendation direction and rationale, classify home-jurisdiction regimes from exhibits, and use amendment frequency as a proxy for contentiousness. Output: working papers and comment letters on cross-border takeover regulation.

Data engineers and quantitative researchers

Engineering teams ingest metadata.json fields (accession, CIK, form type, filing date, period of report, amendment flags) into relational tables keyed on subject company and offer. SGML timestamps align SC14D9F with concurrent SC14D1F, SC TO-T, and 6-K filings. Filing text feeds NLP pipelines that classify Item 4 sentiment, extract advisor names, and flag named regulatory approvals. Output: event-study tables, recommendation classifiers, and features for arbitrage signal libraries.

LLM and RAG developers

Teams building M&A and securities-law assistants index Item 4 reasoning for question answering, separate home-jurisdiction circulars from U.S. wraparound disclosure for jurisdiction-aware retrieval, and follow SC14D9F/A lineage so retrieval returns current rather than superseded text. Output: drafting and research copilots for cross-border tender offers.

Specific Use Cases

Concrete workflows that the SC14D9F Files dataset supports, grounded in the record contents (metadata.json fields, Items 1-9 of the main statement, EX-99 exhibits, and SC14D9F/A amendment chains).

Build a precedent library of FPI board recommendation language

Extract the Item 4 ("The Solicitation or Recommendation") block from every main SC14D9F document and classify each filing as accept, reject, neutral, or no-position. Pair the extracted recommendation sentence with the supporting rationale that typically lives in the attached home-jurisdiction directors' circular (EX-99.(A) family). The resulting precedent table is used by cross-border M&A counsel drafting a new SC14D9F to find peer phrasing for "inadequate," "opportunistic," or "fair from a financial point of view" language and the reasoning structures that accompany each verdict.

Reconstruct full recommendation timelines across SC14D9F/A amendment chains

Group records by subject-company CIK from metadata.json.entities (the "(Subject)"-suffixed entry) and order them by filedAt. Walk the SC14D9F together with every subsequent SC14D9F/A accession to assemble a complete view of how the board's position evolved across bid revisions, extensions, and competing offers. Event-driven analysts use this timeline to flag stance changes, supplemental disclosures, and notices of variation; litigators use it to align amendment timestamps with allegations of pressured or delayed disclosure.

Pair cross-border deal filings into matched bidder/target packages

Use metadata.json fileNo, subject-entity CIK, and filedAt to match each SC14D9F to its companion SC14D1F (bidder-side) filing in the same cross-border tender offer, and where applicable to concurrent Form CB and Form 6-K filings furnished by the same FPI. This produces a complete deal file in which the bidder's terms, financing, and conditions sit next to the target board's response, suitable for arbitrage spread analysis, regulatory-hurdle mapping, and academic event studies on Rule 14d-1(b) deals.

Mine home-jurisdiction directors' circulars for fairness-opinion benchmarking

Locate the longest EX-99 attachments in each record (typically the Canadian or other home-jurisdiction directors' or trustees' circular) and extract the financial advisor's fairness opinion, comparable-transaction tables, premium calculations, and DCF references. Sell-side bankers use this to benchmark premium ranges, valuation methodologies, and scope/qualification language across cross-border FPI deals when drafting their own opinions or pitching target-side mandates.

Screen conflicts and insider intentions disclosed in Items 3, 5, and 6

Parse Item 3 (past contacts, transactions, and arrangements), Item 5 (persons retained and compensation), and Item 6 (transactions in subject securities by officers, directors, and affiliates in the prior sixty days) across the population. The output supports plaintiffs' counsel screening for breach-of-fiduciary-duty claims, compliance teams auditing advisor-compensation disclosure, and researchers studying insider trading patterns around announced cross-border bids.

Feed jurisdiction-aware retrieval and classification pipelines

Use the SGML envelope and documentFormatFiles[].type to separate the U.S. wraparound SC14D9F main document from the attached home-jurisdiction circulars, then index each layer with appropriate jurisdiction tags. Downstream, this supports RAG assistants that return current rather than superseded recommendation text (by following SC14D9F/A lineage), NLP classifiers for Item 4 sentiment and recommendation direction, and named-entity extractors that pull bidder, offeror, financial advisor, and U.S. authorized representative from the cover page and Item 5.

Dataset Access

The dataset is accessible through three endpoints: a JSON index for metadata and discovery, a full archive download, and individual per-month container downloads. All download endpoints accept the SEC API key either as an Authorization header or as a ?token=YOUR_API_KEY query parameter.

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

This endpoint returns the dataset metadata together with the list of available containers. Each container entry describes one monthly ZIP file with its key, size, record count, last updated timestamp, and direct download URL. The index is the recommended way to monitor which containers were refreshed in the latest run, so client systems can selectively download only updated months. This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a1e-8c55-acbb370f2f18",
        

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

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

          5
            "updatedAt": "2026-05-11T02:51:19.000Z",
        

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

          7
            "totalRecords": 179,
        

          8
            "totalSize": 3221172,
        

          9
            "formTypes": ["SC14D9F", "SC14D9F/A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 13818783,
        

          17
                "records": 4,
        

          18
                "updatedAt": "2026-05-11T02:51:19.000Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Returns the full dataset as a single ZIP archive containing all monthly containers from the earliest sample date (2002-03-01) onward. Because the dataset is compact, downloading the full archive in one request is usually the simplest option. This endpoint requires an API key.

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

Each container holds the filings for one calendar month, named by year and month under the containers[].downloadUrl field of the index. Use this endpoint to incrementally fetch only the months that have changed since the last sync. This endpoint requires an API key.

Example with curl:

          1
          # Fetch the dataset index (no API key required)
        

          2
          curl https://api.sec-api.io/datasets/form-sc14d9f-files.json
        

          3
          
        

          4
          # Download one monthly container using the Authorization header
        

          5
          curl -H "Authorization: YOUR_API_KEY" \
        

          6
            -o 2026-03.zip \
        

          7
            https://api.sec-api.io/datasets/form-sc14d9f-files/2026/2026-03.zip
        

          8
          
        

          9
          # Or the same download using the token query parameter
        

          10
          curl -o 2026-03.zip \
        

          11
            "https://api.sec-api.io/datasets/form-sc14d9f-files/2026/2026-03.zip?token=YOUR_API_KEY"
        

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form SC14D9F and its amendment variant SC14D9F/A — the solicitation/recommendation statement that a foreign private issuer files in response to a third-party tender offer under Section 14(d)(4) of the Exchange Act and Rules 14d-1(b) and 14e-2(c). It is the cross-border counterpart to the domestic Schedule 14D-9.

What does one record in this dataset represent?

One record is one EDGAR accession — a single Form SC14D9F initial filing or SC14D9F/A amendment, identified by its eighteen-character accession number. The record is materialized as a self-contained folder bundling metadata.json, the main Schedule 14D-9 HTML document, every attached EX-99 exhibit, and, when included, the complete-submission .txt stream.

Who is required to file Form SC14D9F?

The filer is the subject company in a third-party tender offer, where that subject company is a foreign private issuer (as defined in Exchange Act Rule 3b-4) qualifying for the cross-border framework in Rule 14d-1(b). In practice this population is dominated by Canadian issuers, because Rule 14d-1(b) was designed to dovetail with Canadian provincial takeover-bid regimes. Bidders file the separate Form SC14D1F.

When must Form SC14D9F be filed?

Rule 14e-2 requires the subject company to communicate its position on the offer no later than 10 business days after the tender offer is first published, sent, or given to security holders. In practice the U.S. filing tracks the home-jurisdiction timeline: the issuer files Form SC14D9F by the time it disseminates its directors' circular or equivalent local response document.

What time period does the dataset cover?

The dataset begins on 2002-03-01, when EDGAR-required electronic filing of Form SC14D9F took effect, and runs to the present. The form's item structure (Items 1 through 9) and the underlying Rule 14d-1(b)/14e-2(c) accommodation have remained stable across that entire span.

What file formats are included in the dataset, and what is excluded?

Each record contains HTML (the main SC14D9F document and most exhibits), JSON (the metadata.json filing header and manifest), and TXT (the optional complete-submission stream and legacy text attachments). Image binaries listed as GRAPHIC in documentFormatFiles — typically .jpg, .gif, and .png files such as scanned signatures or logos — are deliberately excluded from the archive but remain enumerated in the manifest with their original sec.gov URLs.

How does Form SC14D9F differ from Schedule 14D-9?

Schedule 14D-9 is the domestic U.S. solicitation/recommendation statement and requires item-by-item responses on the SEC's prescribed schedule. Form SC14D9F is restricted to foreign private issuers using the Rule 14d-1(b) cross-border accommodation and is built to wrap or incorporate a home-jurisdiction directors' circular or equivalent local document, with the main SC14D9F often serving as a terse U.S. cover for the substantive home-country filing attached as an EX-99 exhibit.