Form RW Files Dataset

The Form RW Files Dataset is a complete electronic archive of Form RW filings — applications by which Securities Act registrants request Commission consent to withdraw a registration statement (or a pre-effective amendment) under Rule 477 of the Securities Act of 1933. Each record represents one Form RW submission accepted by EDGAR, identified by a unique 18-digit accession number, and captures the withdrawal letter itself together with the structured EDGAR header that ties the filing back to the underlying S-, F-, N-, or SF- registration statement being withdrawn. Filers are always the registrants named on the original Securities Act registration statement, including domestic operating companies, first-time IPO issuers, follow-on and shelf registrants, SPACs, foreign private issuers, blank check and shell entities, asset-backed issuers, and investment companies. The dataset covers filings from January 1994 — the EDGAR phase-in for Securities Act filers — through the present, refreshed regularly as new Form RW submissions arrive. Records are distributed as monthly ZIP containers partitioned by calendar year, with each accession folder holding a metadata.json describing the filing plus the primary RW HTML letter, exactly as filed.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset packages every electronic Form RW submission accepted by EDGAR from January 1994 onward. Form RW is the application by which a registrant requests Commission consent to withdraw a registration statement (or a pre-effective amendment to one) under Rule 477 of the Securities Act of 1933. It is not a registration form, not a periodic report, and carries no financial statements, exhibit schedule, or XBRL payload. The "form" itself has no SEC-prescribed line-item template; it is filed as a free-form letter to the Division of Corporation Finance that must, per Rule 477, identify the registration statement, state that it has not been declared effective, and represent that no securities have been sold thereunder. In practice the letter also invokes Rule 457(p) to request that previously paid filing fees be credited toward a future registration. The filing is administrative and short — primary documents are typically a single page of correspondence-style text plus a signature, in the 5–20 KB range as HTML.

The dataset is distributed as a hierarchy of ZIPs. The top level partitions by calendar year (e.g. 2025/), and within each year there is one ZIP per calendar month (e.g. 2025-07.zip). Each monthly ZIP unpacks into a single month-named folder (2025-07/) containing one subfolder per Form RW filing accepted by EDGAR that month. Accession folders use the 18-digit, dash-stripped accession number (000164117225021730/), while the dashed canonical form (0001641172-25-021730) is what appears inside metadata.json and on EDGAR URLs. This convention makes folder names filesystem-safe and lexicographically sortable while preserving the original identifier in the metadata. Inside each accession folder the dataset includes the JSON metadata file and every document from the original EDGAR submission except images; because Form RW submissions almost always consist of a single primary document, the typical folder contains exactly two files: metadata.json and the RW HTML letter.

Content Structure of a Single Record

What one record represents

One record in the Form RW Files Dataset is a single Form RW submission accepted by EDGAR — that is, one complete registration-withdrawal application identified by a unique 18-digit EDGAR accession number. Physically, a record is an accession-numbered folder containing a metadata.json describing the EDGAR header and entity context plus the primary withdrawal document itself (typically a single .htm letter). The unit of observation is the filing, not the registration statement being withdrawn: an issuer that submits two RW letters on the same day to withdraw two different registration statements produces two distinct records with consecutive accession numbers, each pointing via its fileNo field to a different target.

The metadata.json block

metadata.json is the structured face of the record. It captures filing-level fields plus a nested entities array. Top-level keys:

• formType — always "RW".
• accessionNo — canonical dashed accession (e.g. "0001641172-25-021730").
• filedAt — ISO-8601 timestamp with EDGAR's Eastern-time offset (e.g. "2025-07-31T16:05:05-04:00").
• description — boilerplate "Form RW - Registration Withdrawal Request".
• linkToFilingDetails — absolute sec.gov/Archives/edgar/... URL of the primary RW document.
• linkToTxt — URL of the complete-submission SGML/text bundle on EDGAR (not bundled in the ZIP).
• linkToHtml — URL of the EDGAR filing-index page (...-index.htm).
• linkToXbrl — empty string; Form RW carries no XBRL.
• documentFormatFiles — array of file descriptors. The primary RW entry carries sequence: "1", type: "RW", a size (bytes as a string), a documentUrl, and sometimes a description ("RW", "FORM RW"). A secondary entry pointing to the complete-submission .txt is conventionally included with a blank-space sequence and type and description: "Complete submission text file".
• dataFiles and seriesAndClassesContractsInformation — arrays, empty for Form RW.
• id — 32-character hex hash, the dataset's internal record identifier.

The entities array carries registrant context lifted from the EDGAR header. For Form RW there is typically a single entity object representing the filer. Per-entity fields:

• cik — numeric CIK as string.
• companyName — issuer name with the role suffix appended (e.g. "BARFRESH FOOD GROUP INC. (Filer)").
• type — header-level form type, "RW".
• fileNo — the SEC file number of the registration statement being withdrawn ("333-XXXXXX"); the same identifier cited in the body of the letter.
• filmNo — EDGAR film number.
• act — Securities Act code, "98".
• irsNo — IRS employer identification number; can be "000000000" for shell/SPAC filers.
• sic — SIC code with description text (e.g. "6770 Blank Checks"); ampersands are HTML-encoded as &.
• stateOfIncorporation — two-letter US state or country code; may be absent for foreign filers.
• fiscalYearEnd — MMDD (e.g. "1231"); may be absent.
• tickers — optional array of trading symbols (for SPACs this can include unit and warrant tickers, e.g. ["BCAR","BCARU","BCARW"]).

The fileNo field is the linchpin tying a Form RW record back to the registration statement being withdrawn; combined with the issuer CIK, it permits joining the withdrawal event to the original S-1/S-3/S-4/F-1 (or F-3, S-11, etc.) filing chain.

The primary RW document

The withdrawal document is the substantive content of the record. It is an HTML file wrapped in the SGML envelope that EDGAR places around every primary document:

          1
          <DOCUMENT>
        

          2
          <TYPE>RW
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>form-rw.htm
        

          5
          <TEXT>
        

          6
          <HTML>... withdrawal letter ...</HTML>
        

          7
          </TEXT>
        

          8
          </DOCUMENT>
        

Some filings add a <DESCRIPTION>FORM RW line between <FILENAME> and <TEXT>. The filename itself is not standardized: generic patterns (form-rw.htm, formrw.htm, form_wd.htm), issuer-tagged patterns (mitsubrw.htm, nocera_rw.htm, s-3withdrawal2025.htm), and filing-agent job IDs (tm2519988d1_rw.htm, d65686drw.htm, ea0248844-rw_atlantic.htm, j724254rw.htm) all appear. Consumers should locate the primary document programmatically via the <TYPE>RW SGML tag or the documentFormatFiles[0] entry with type: "RW" rather than guessing by filename.

The body of the letter, despite cosmetic variation across filers and filing agents, follows a near-uniform six-part template:

1. Letterhead — issuer name, mailing address, the filing date, and a VIA EDGAR notation.
2. Addressee block — U.S. Securities and Exchange Commission, Division of Corporation Finance, 100 F Street, N.E., Washington, D.C. 20549, often with an attention line for an assigned staff examiner.
3. Re: line — issuer name, the action ("Request to Withdraw Registration Statement on Form S-1/S-3/S-4/F-1/..."), and the file number 333-XXXXXX.
4. Rule 477 body paragraph — identifies the registration statement and its original filing date, represents that the registration statement has not been declared effective, and represents that no securities have been sold thereunder.
5. Rule 457(p) fee-credit request — asks that filing fees previously paid be credited toward a future registration.
6. Closing, counsel contact line, and signature block — name and title of an executive officer (CEO, CFO, or General Counsel) with an /s/ electronic signature.

The same template covers withdrawals of Forms S-1, S-3, S-4, F-1, F-3, S-11, and other Securities Act registration statements; only the cited form type and file number change.

Included content

For each Form RW accession the dataset record contains:

• metadata.json with the parsed EDGAR header, the entity block, the file-number reference to the registration statement being withdrawn, and the URLs back to the source filing on EDGAR.
• The primary RW HTML document, complete with its SGML wrapper, exactly as filed.
• Any non-image supporting documents that were part of the original submission (uncommon for Form RW, since withdrawal letters rarely carry attachments).

Excluded or separate content

• Image files — any GIF/JPG/PNG referenced inside the HTML (typically issuer letterhead logos) are omitted; the HTML may contain <img> tags whose src no longer resolves locally.
• Complete-submission .txt bundle — the consolidated SGML file EDGAR builds from the submission is not redistributed inside the ZIP; it is reachable via metadata.json.linkToTxt and via the secondary documentFormatFiles[] entry.
• Filing-index HTML — the EDGAR ...-index.htm listing page is not bundled; it is referenced via linkToHtml.
• The underlying registration statement — Form RW carries no copy of, and no full-text incorporation of, the S-1/S-3/S-4/F-1 being withdrawn. Only its file number is cited; resolving the target requires a separate lookup keyed on fileNo and CIK.
• XBRL data — none exists for Form RW.

Changes in required content over time

Form RW's substantive content has been remarkably stable since its codification. Rule 477 (17 CFR 230.477) sets out the same three core representations — identification of the registration statement, non-effectiveness, and no securities sold — that withdrawal letters carried in 1994 and still carry today. The most material content change over the dataset's life is the routine inclusion of a Rule 457(p) fee-credit request, which became universal after the 2002 amendments to Securities Act filing fees permitted previously paid registration fees to be credited against future filings; pre-2002 RW letters typically stop after the withdrawal request itself and do not address fees. Otherwise the letter remains a free-form correspondence with no SEC-prescribed line items.

The EDGAR header schema surrounding the letter has evolved more substantially. Early-1990s submissions captured a smaller set of registrant attributes; modern submissions populate richer fields such as SIC with description text, multiple ticker symbols (including SPAC unit and warrant tickers), and film numbers. Filer-role tagging in companyName (the (Filer) suffix) reflects the post-2002 EDGAR convention of attaching role qualifiers to entity names in the submission header.

Changes in data format over time

Form RW filings in the dataset span three EDGAR presentation eras:

• 1994–early 2000s: SGML/ASCII era. Early withdrawal letters were submitted as plain ASCII inside the SGML <DOCUMENT> wrapper, with <TYPE>RW, <SEQUENCE>1, and the body as <TEXT> containing no HTML markup. Line wrapping at 80 columns, monospaced layout, and ASCII signature lines (/s/ John Doe) are typical.
• Late-1990s–2000s: HTML adoption. As EDGAR began accepting HTML primary documents, RW letters migrated to .htm files retaining the SGML envelope but with HTML body markup for letterhead formatting, addressee blocks, and signature lines. The optional <DESCRIPTION> tag entered widespread use during this period.
• 2010s–present: modern HTML. Contemporary filings are HTML produced by filing-agent toolchains (Toppan Merrill, Donnelley, EdgarAgents, RDG Filings, and others), often containing inline CSS, embedded letterhead images, and structured signature blocks. The SGML wrapper persists unchanged across all three eras, providing a stable extraction anchor.

Interpretation and extraction notes

• Identifying the registration statement being withdrawn. The entities[0].fileNo field carries the SEC file number (333-XXXXXX) of the target registration statement; this is the most reliable join key to the original S-1/S-3/S-4/F-1. The letter body also cites this number in the Re: block, but extracting it from prose is fragile compared to reading the structured field.
• Same-day duplicate filings. A single issuer can submit multiple RW letters on the same day to withdraw multiple registration statements, producing back-to-back accessions that share filer identity but differ in fileNo and primary-document content. Deduplicating by CIK and date would incorrectly collapse these.
• SPAC and blank-check filers. Issuers with SIC 6770 Blank Checks frequently file Form RW when an offering does not proceed. These records often have irsNo: "000000000" and multiple tickers covering common shares, units, and warrants.
• Foreign filers. Foreign private issuers withdrawing F-series registration statements may omit stateOfIncorporation and fiscalYearEnd, and may list a non-U.S. address in the letterhead.
• HTML-encoded ampersands. SIC descriptions in entities[].sic preserve raw & entities (e.g. "2030 Canned, Frozen & Preservd Fruit, Veg & Food Specialties"); downstream text comparisons should decode HTML entities.
• documentFormatFiles[] quirks. The primary RW entry's description is occasionally omitted. The secondary .txt entry conventionally uses a single space " " for sequence and type rather than null or empty string; string-equality filters should account for this.
• SGML wrapper as extraction anchor. Because filenames are not standardized, the most robust way to locate the withdrawal letter inside an accession is the <TYPE>RW tag inside the SGML envelope, or equivalently the documentFormatFiles[] entry with type: "RW" and sequence: "1".
• Letter as the only substantive payload. Unlike registration filings, Form RW carries no exhibits index, no incorporation-by-reference of prior documents, no financial statements, and no auditor consents. Everything substantive lives in a single short HTML letter; the metadata fields supply the structured context around it.

Who Files or Publishes This Dataset, and When

Who files Form RW

The filer is always the registrant named on the Securities Act registration statement being withdrawn (or its successor by merger or reorganization). The CIK and file number on the Form RW match those on the underlying S-, F-, N-, or SF- filing. Filing agents, outside counsel, and financial printers may transmit the submission on EDGAR but do not become the filer of record.

The reporting population is co-extensive with Securities Act registrants and includes:

• Domestic operating companies filing Form S-1, Form S-3, Form S-4, Form S-8, or Form S-11 — including emerging growth companies, smaller reporting companies, and well-known seasoned issuers.
• First-time IPO issuers withdrawing an S-1 before pricing.
• Existing reporting issuers withdrawing follow-on, secondary, resale, or shelf registration statements where no takedown occurred.
• SPACs withdrawing IPO registration statements, Form S-4 business combination registrations, or resale registrations for PIPE and founder shares.
• Foreign private issuers withdrawing Form F-1, Form F-3, Form F-4, or Form F-10 (including Canadian MJDS filers).
• Blank check, shell, and development-stage entities whose registration statements were never declared effective or never used.
• Asset-backed issuers (depositors, sponsors under Regulation AB) withdrawing SF-3 or other ABS shelf registrations.
• Investment companies and BDCs withdrawing Securities Act registrations such as Form N-2 where no shares were sold.

Selling security holders and underwriters are not filers, even when they drive the decision to withdraw; the issuer named on the cover of the original registration statement signs and files Form RW.

Regulatory framework

Form RW is the application required by Rule 477 under the Securities Act of 1933 (17 CFR 230.477), "Withdrawal of registration statement, amendment or exhibit." Rule 477 permits the registrant to withdraw a registration statement (or any amendment or exhibit) with Commission consent, which the rule conditions on a finding that withdrawal is "consistent with the public interest and the protection of investors."

Three operative features shape who files and when:

• No-sales certification. The application must state that no securities were sold under the registration statement. If sales have occurred, Rule 477 is unavailable.
• 15-day deemed-grant mechanism. Under Rule 477(b), the application is deemed granted at the time of filing unless the Commission, within 15 days, notifies the registrant that it will not consent. Most Form RW filings clear automatically without affirmative staff action.
• Staff override. Consent may be withheld if the registrant or any underwriter made unauthorized offers, or if the staff has reason to believe the offering involves fraud (Rule 477(c)).

Rule 477 implements the Commission's general authority over registration under Securities Act Section 6 (which governs the filing, effectiveness, and disposition of registration statements). Withdrawal under Rule 477 differs from abandonment-by-lapse: a withdrawn registration statement is treated as never having been filed for purposes of subsequent registration, while a stale, never-withdrawn filing remains on the registrant's record.

Rule 457(p) links directly to Form RW. It allows a registrant that withdraws under Rule 477 to apply unused filing fees as a credit against fees on a subsequent registration statement filed within five years of the initial filing date of the withdrawn registration statement, subject to identifying the prior filing and the fees paid. Registrants seeking this credit typically include the Rule 457(p) request and fee schedule in the Form RW itself.

Triggering events

Form RW is event-driven, not periodic. A filing arises whenever a registrant affirmatively decides to abandon a registration statement before any sale. Typical triggers:

• Market conditions — IPOs or follow-ons pulled or postponed indefinitely.
• Change of financing strategy — pivot to Rule 144A, Regulation D, direct listing, or private capital.
• Material corporate events — acquisition, change of control, reorganization, or strategic shift that moots the offering.
• Replacement filings — withdrawing an S-1 to refile on S-3 after eligibility is achieved, or replacing the structure of the deal.
• SPAC-specific events — abandoned SPAC IPO, terminated de-SPAC business combination (S-4), or collapsed PIPE resale.
• Unresolvable staff comments leading to abandonment rather than further amendment.
• Shelf cleanup — terminating an unused S-3 or SF-3 before the Rule 415 three-year limit.
• Dissolution, bankruptcy, or merger out of existence before the offering is consummated.

The unconditional precondition is that no securities have been sold under the registration statement being withdrawn.

Timing

No fixed deadline applies. Form RW may be filed at any time after the registration statement is filed and before any sale, whether or not the registration statement has been declared effective. In practice the filing appears at three points in the lifecycle:

• Pre-effective — staff review never cleared, or the registrant abandoned the process.
• At or near pricing — last-minute deal pull.
• Post-effective, pre-takedown — typically shelf registrations (S-3, SF-3) terminated before any offering.

Once filed, consent is deemed granted 15 calendar days later absent staff notice to the contrary. Dataset coverage begins January 1994, consistent with the EDGAR phase-in for Securities Act filers; Rule 477 itself long predates EDGAR, but earlier paper Form RW applications are not in this electronic dataset.

Important distinctions

• Form RW vs. Form AW. Form RW withdraws a Securities Act registration statement under Rule 477. Form AW is the EDGAR submission type for withdrawal of a different application (commonly used in Regulation A and related contexts). They cover different filings and are not interchangeable; this dataset contains only RW.
• Form RW vs. Form 15. Form 15 terminates or suspends Exchange Act reporting obligations under Sections 12(g) and 15(d) (and certifies that a class of securities is no longer §12(g)-registrable). It does not withdraw a Securities Act registration statement. An issuer that completed its offering and now wants to exit Exchange Act reporting files Form 15, not RW.
• Form RW vs. post-effective deregistration. If any securities were sold, Rule 477 is unavailable; the registrant deregisters unsold securities through a post-effective amendment (often citing the "Section 10(a)(3) undertaking" or the registrant's deregistration undertakings) rather than via Form RW.
• Partial withdrawals. Rule 477 also permits withdrawal of a single amendment or exhibit; such partial withdrawals are filed as Form RW and appear in the dataset, though they are uncommon.
• Form RW/A. Amendments to a previously filed Form RW/A (typically to correct identifying information or supplement the request) appear under the RW/A form type and reference the same underlying registration statement.
• Investment Company Act filings. Rule 477 governs Securities Act withdrawal. Withdrawals from registration as an investment company under the 1940 Act (Form N-8F) or as an investment adviser (Form ADV-W) follow separate regimes and are not Form RW filings.
• Implied no-sales fact. Because the filer must certify no sales occurred, the existence of a Form RW in this dataset is itself evidence that no securities were sold under the underlying registration statement.

How This Dataset Differs From Similar Datasets or Filings

Form RW sits in a narrow family of filings that all step out of, terminate, or unwind a registration or reporting obligation. The shared word "withdraw" causes most of the confusion, but each form addresses a different statute, a different stage of the registration lifecycle, and a different downstream consequence.

Closest related withdrawal and termination filings

Form AW (Application for Withdrawal under the Exchange Act)

The Exchange Act counterpart to Form RW. AW withdraws a class-of-securities registration filed on Form 10 or Form 8-A under Section 12. RW withdraws a Securities Act offering registration under Rule 477. An issuer that filed an 8-A in anticipation of a listing it then abandoned files AW; an issuer that filed an S-1 it then abandoned files RW. Same structural shape (short application, request for Commission consent), different statute, different object, different downstream effect: AW terminates the trigger for Section 13 reporting; RW unwinds an unconsummated offering.

Form RW/A and Form RW WD

Both live on the same filing thread as the RW itself. RW/A amends a pending RW to correct or supplement the original withdrawal request. Form RW WD withdraws the RW request itself, leaving the underlying registration statement alive. A complete view of withdrawal activity requires pulling all three form types; filtering on RW alone captures only the initial application.

Form 15, 15-12B, 15-12G, 15-15D

Exchange Act termination filings, not Securities Act withdrawals. Form 15 (and variants) terminates or suspends Section 12(g) or Section 15(d) reporting once thresholds are met or following deregistration. The variant designates the predicate: Form 15-12B for securities registered on a national exchange under Section 12(b), Form 15-12G for Section 12(g) registrations, Form 15-15D for suspension of the Section 15(d) reporting duty. All operate on issuers whose securities are already registered and trading. RW operates upstream, before effectiveness, on an offering that never reached the market. The two rarely appear together for the same fact pattern.

Form 25

Removes a class of securities from a national exchange under Section 12(b) and Rule 12d2-2. Filed by the exchange (or, in delisting-at-issuer-request cases, by the issuer). Like Form 15, it concerns securities already listed and trading. Unlike RW, it does not touch the Securities Act registration; an issuer that delists via Form 25 may still have an effective shelf registration in place.

Form N-8F

Application by a registered investment company to deregister under Section 8(f) of the Investment Company Act of 1940. Exits the fund from the 1940 Act entirely. A closed-end fund that wants to abandon a specific N-2 before effectiveness still files RW for that N-2; N-8F addresses the much broader question of leaving 1940 Act status.

The underlying registration statements that RW withdraws

Forms S-1, S-3, S-4, S-11, F-1, F-3, F-4, N-2

These are the Securities Act registration statements that RW targets. S-1 and S-3 are domestic long-form and short-form; S-4 covers business combinations and exchange offers; S-11 covers real estate issuers; F-1, F-3, and F-4 are the foreign-issuer analogs; N-2 covers closed-end funds and certain BDCs. Each RW references one such filing by file number. The substantive offering disclosure (issuer description, use of proceeds, financials, underwriting terms) lives in the referenced S-, F-, or N- filing, not in the RW itself, which is short and procedural. Researchers reconstructing abandoned offerings must join RW records to the parent registration filing on file number.

Pre-effective and post-effective amendments as alternative exits

Not every abandoned offering is unwound through Form RW. An issuer can instead file a pre-effective amendment that reduces the offering to zero, or a post-effective amendment removing unsold securities from registration. These are amendments to the parent S-/F-/N- form, not a distinct form type. They achieve a similar economic outcome (no securities sold) without invoking Rule 477. Identifying all abandoned offerings therefore requires looking beyond the RW form-type filter into amendment activity on the parent registration.

Rule 477 vs Rule 478

Form RW is the application mechanism under Rule 477, which permits withdrawal of a registration statement or pre-effective amendment before effectiveness, subject to Commission consent and a no-sales condition. Rule 478 is a different rule entirely: it governs the powers, duties, and exemptions of the Commission with respect to registration statements and has been used historically in the context of post-effective treatment. The clean rule of thumb: Rule 477 covers the pre-effective withdrawal case that produces an RW filing; once a registration is effective, issuers typically deregister unsold securities through a post-effective amendment to the parent form rather than through a separate withdrawal filing.

Boundary summary

Form RW is narrow: a Securities Act, pre-effective, no-sales application asking the Commission's consent to pull a specific registration statement under Rule 477. It is not:

• a reporting-termination filing (Form 15 variants)
• an exchange-deregistration filing (Form 25)
• a fund deregistration (Form N-8F)
• an Exchange Act registration withdrawal (Form AW)
• the underlying offering document (S-, F-, or N- filing)
• the mechanism for clearing unsold securities off an effective registration (post-effective amendment to the parent form)

The Form RW Files Dataset is therefore best understood as a single-purpose record of intent-to-abandon events on the Securities Act registration side of EDGAR from 1994 onward. It complements, but does not substitute for, datasets of the parent registration statements, Form 15 and Form 25 deregistration data, Form AW filings, and amendment-level data needed to capture abandonments executed through pre- or post-effective amendments rather than through Rule 477.

Who Uses This Dataset

Form RW documents the withdrawal of a registration statement. Each record carries the registrant CIK, the fileNo and formType of the abandoned statement, its original filing date, the Rule 477 letter body, the no-securities-sold representation, and any Rule 457(p) fee-credit language. Different teams read different fields.

ECM origination and syndicate desks

Bankers reconstruct deal mortality from CIK, fileNo, formType (S-1, F-1, S-4, S-11), and original filing date, measuring days-on-file before withdrawal. Output: sector and vintage attrition tables, peer pulled-deal rates, pitch slides on market windows, post-mortems on failed bookbuildings.

SPAC and de-SPAC coverage

Analysts use formType to split failed SPAC IPOs (S-1) from collapsed de-SPAC mergers (S-4), then join CIK across filings to track sponsor and trust outcomes. Feeds sponsor outreach lists and SPAC mortality dashboards.

Securities lawyers and disclosure counsel

Outside counsel mine the Rule 477 letter body as a precedent library: phrasing of the consent request, specificity of the stated reason, the no-securities-sold representation, and Rule 457(p) fee-credit language for reapplication. Supports first drafts, know-how systems, and client guidance on staff-acceptable explanations.

Fee-credit and treasury specialists

Specialists chain the fileNo of the withdrawn statement to subsequent registrations by the same CIK to map Rule 457(p) carryovers. Output: unused-fee inventories, advisory memos comparing withdrawal versus amendment cost.

IPO and registration researchers

Academics use the full 1994-forward population, CIK, formType, and original filing date to build survival curves and cross-sectional withdrawal models. The Rule 477 narrative provides coded reasons (market conditions, change of control, alternative financing) for content analysis.

Financial journalists

Reporters pair registrant identity, formType, and original filing date for same-day "company pulls IPO" stories, and aggregate withdrawal counts by quarter and sector for trend pieces on offering stress.

Event-driven and quant researchers

Quants build event-study panels on accession number, filing date, CIK, and formType. For already-public issuers (S-3, S-4, S-8 withdrawals), the CIK ties to CUSIP for price, volume, and short-interest tests. Sector withdrawal density and underwriter pulled-deal rates become features in IPO-pricing models.

Underwriter risk and compliance

Compliance reconciles internal deal blotters against fileNo, CIK, and withdrawal date to confirm syndicate exposure is extinguished, release restricted-list and research-blackout flags, and track expected Rule 457(p) credits.

Issuer-side corporate development and treasury

Issuers contemplating their own withdrawal read peer Rule 477 letters for framing, check whether fee credits were requested, and measure intervals between withdrawal and refiling by CIK. Inputs to board memos on timing and optics.

Regulatory and policy researchers

Staff and policy analysts measure attrition over time using formType, original filing date, and the Rule 477 and 457(p) text to study how withdrawal mechanics are used in practice. Feeds retrospective reviews and rulemaking files.

Data vendor engineering

Pipeline teams join fileNo and CIK back to the original S-1, F-1, S-4, or S-11 to flip tracked deals from "on file" to "withdrawn" and recompute withdrawal-rate metrics for subscribers.

LLM and RAG developers

Teams building registration-lifecycle assistants index the Rule 477 letter body alongside the structured CIK, fileNo, formType, and original filing date fields. The consistent letter format yields a clean corpus for precedent retrieval and Rule 457(p) question answering.

Audit and forensic accounting

Auditors confirm via fileNo, formType, and original filing date that a statement on the issuer's books was formally withdrawn, and use the Rule 457(p) language to verify carryover of registration fees and treatment of capitalized issuance costs.

Activist and short research

Short and activist desks group RW filings by CIK to flag serial withdrawers, then read formType and original filing dates as a signal of distressed capital needs or unstable governance.

Specific Use Cases

Each use case below ties a concrete workflow to specific fields in the record: the registrant CIK, the fileNo and formType of the withdrawn registration statement, the original filing date, the Rule 477 letter body, the no-securities-sold representation, and any Rule 457(p) fee-credit language.

• Pulled-deal mortality tracking for ECM desks. Aggregate records by formType (S-1, F-1, S-4, S-11) and SIC, compute days-on-file between the original filing date of the withdrawn statement and the RW filedAt timestamp, and produce sector-and-vintage attrition tables. Output feeds pitch decks on market windows, peer pulled-deal benchmarks, and post-mortems for specific failed bookbuildings keyed on issuer CIK.

• Rule 457(p) fee-credit reconciliation. Join the fileNo of the withdrawn registration to subsequent S-/F- filings under the same CIK, extract the Rule 457(p) carryover language from the RW letter body, and build a fee-credit ledger per issuer. Treasury and outside counsel use this to confirm unused-fee balances before drafting a replacement registration and to advise on the cost trade-off between withdrawal and a pre-effective amendment.

• SPAC and blank-check failure dashboards. Filter records where entities[].sic equals 6770 Blank Checks, split S-1 withdrawals (failed SPAC IPOs) from S-4 withdrawals (collapsed de-SPAC mergers), and pivot the tickers array to follow common, unit, and warrant symbols through trust liquidation. Output: sponsor-level mortality tables, distressed-trust outreach lists, and de-SPAC break-rate series.

• Precedent library for Rule 477 drafting. Index the body of the RW HTML letter locating the consent request, the stated reason, the non-effectiveness representation, and the no-securities-sold representation. Disclosure counsel and know-how systems retrieve precedents by formType and SIC to draft new withdrawal letters with phrasing aligned to recent staff-accepted language.

• Event-study panels for already-public issuers. Restrict to S-3, S-4, and S-8 withdrawals where the CIK has prior reporting history, then join CIK to CUSIP and run abnormal-return, volume, and short-interest tests around the RW filedAt date. Sector and underwriter pulled-deal density built from the same panel become features in IPO-pricing and shelf-takedown models.

• Underwriter blotter and restricted-list reconciliation. Compliance teams match internal syndicate records against the dataset on CIK, fileNo, and withdrawal date to confirm that exposure on the withdrawn statement is extinguished, release research blackouts and restricted-list flags, and queue expected Rule 457(p) credits for the deal accounting system.

• Serial-withdrawer screens for short and activist research. Group records by CIK to surface issuers with multiple Rule 477 withdrawals across formType values, plot intervals between original filing date and withdrawal, and flag patterns suggestive of distressed capital needs, governance churn, or repeated SPAC-sponsor failures. The screen feeds candidate lists for deeper diligence.

Dataset Access

The Form RW Files Dataset is available through three access methods: a public JSON index endpoint that describes the dataset and its containers, a single ZIP archive containing the full dataset, and per-container ZIP downloads for incremental retrieval. The dataset is refreshed regularly as new Form RW filings are submitted to EDGAR, so the index is the source of truth for current container listings and updated timestamps. Because the dataset is compact, many users will find it practical to pull the entire archive in one request; the per-container endpoints exist for workflows that prefer to fetch only the most recently updated slices.

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

This endpoint returns dataset-level metadata (name, description, updatedAt, earliestSampleDate, totalRecords, totalSize, formTypes, containerFormat, fileTypes), the full-dataset download URL, and the list of container files with their individual key, size, records, updatedAt, and downloadUrl. Polling this endpoint on a schedule lets you detect which containers changed in the most recent refresh and download only those. This endpoint does not require an API key.

          1
          curl https://api.sec-api.io/datasets/form-rw-files.json
        

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-691f-a340-45cf075d59b7",
        

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

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

          5
            "updatedAt": "2026-05-16T03:03:16.655Z",
        

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

          7
            "totalRecords": 13809,
        

          8
            "totalSize": 35241357,
        

          9
            "formTypes": ["RW"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 412338,
        

          17
                "records": 21,
        

          18
                "updatedAt": "2026-05-16T03:03:16.655Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Returns the full dataset, covering all Form RW filings from January 1994 onward, as a single ZIP archive. This endpoint requires an API key passed via the token query parameter.

          1
          curl -o form-rw-files.zip "https://api.sec-api.io/datasets/form-rw-files.zip?token=YOUR_API_KEY"
        

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

Returns one container ZIP, typically scoped to a single month. Use the downloadUrl values from the index response to pull only the containers that were updated in the latest refresh. This endpoint requires an API key passed via the token query parameter.

          1
          curl -o 2026-05.zip "https://api.sec-api.io/datasets/form-rw-files/2026/2026-05.zip?token=YOUR_API_KEY"
        

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form RW, the application by which a Securities Act registrant requests Commission consent to withdraw a registration statement (or pre-effective amendment) under Rule 477 of the Securities Act of 1933. Only filings with EDGAR form type RW are included; amendments (RW/A), rescissions of the withdrawal request (RW WD), and the Exchange Act counterpart (Form AW) are separate form types not bundled here.

What does one record in this dataset represent?

One record is a single Form RW submission accepted by EDGAR, identified by a unique 18-digit accession number. Physically, each record is an accession-numbered folder containing a metadata.json describing the EDGAR header and entity context plus the primary withdrawal letter (typically a single .htm file).

Who is required to file Form RW?

The filer is always the registrant named on the underlying Securities Act registration statement being withdrawn — for example, the company that filed the S-1, S-3, S-4, S-11, F-1, F-3, F-4, or N-2 being abandoned. Selling security holders, underwriters, and filing agents are not filers, even when they drive the decision to withdraw.

When is Form RW filed?

Form RW is event-driven, not periodic. It may be filed at any time after the registration statement is on file and before any securities have been sold, whether or not the registration statement has been declared effective. The unconditional precondition under Rule 477 is that no securities have been sold under the registration statement being withdrawn.

What time period does the dataset cover?

Coverage begins in January 1994, consistent with the EDGAR phase-in for Securities Act filers, and continues through the present. The dataset is refreshed regularly as new Form RW filings are accepted by EDGAR; the JSON index endpoint reports the latest updatedAt timestamp and per-container update times.

What file format is the dataset distributed in?

The dataset is distributed as ZIP containers, partitioned by calendar year at the top level and by calendar month inside each year (e.g. 2025/2025-07.zip). Inside each monthly ZIP, accession folders contain a metadata.json and the primary RW HTML letter; declared file types across the dataset include TXT, JSON, HTML, and PDF.

How does this dataset differ from Form AW and Form 15 datasets?

Form RW withdraws a Securities Act offering registration under Rule 477, before any sale. Form AW withdraws an Exchange Act class-of-securities registration (Form 10 or 8-A) and terminates the trigger for Section 13 reporting. Form 15 (and its 15-12B, 15-12G, 15-15D variants) terminates or suspends Exchange Act reporting once thresholds are met. All three address different statutes and different stages of the registration lifecycle; this dataset contains only Form RW filings.

How do I locate the primary withdrawal document inside a record?

Filenames for the RW letter are not standardized — they range from generic patterns like form-rw.htm to filing-agent job IDs like tm2519988d1_rw.htm. The robust way to locate it is the documentFormatFiles[] entry in metadata.json with type: "RW" and sequence: "1", or equivalently the <TYPE>RW tag inside the SGML envelope around the document.