Form APP WD Files Dataset

The Form APP WD Files Dataset is a complete EDGAR archive of Form APP WD and Form APP WD/A submissions — the formal notices by which an applicant withdraws a pending application for an SEC exemptive or other discretionary order, almost always under the Investment Company Act of 1940 and Rule 0-5. One record corresponds to a single EDGAR submission, identified by its accession number, and bundles the parsed EDGAR header (metadata.json) together with the original withdrawal letter as HTML or plain text and any accompanying non-image exhibits. The filer population is dominated by registered investment companies, business development companies, investment advisers, and their affiliates acting as co-applicants. Coverage starts in February 2002, when EDGAR adopted the dedicated APP WD form-type code, and continues through the present.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset packages every EDGAR submission tagged with form type APP WD or APP WD/A. Form APP WD is the procedural instrument by which an applicant — an investment company, its adviser, or an affiliated party — withdraws a pending application requesting an SEC order, before the Commission issues a final determination. The overwhelming majority of these withdrawals sit in the Investment Company Act of 1940 context, terminating applications for exemptive relief under provisions such as Section 6(c), Section 17 affiliated-transaction relief, Section 12(d)(1) fund-of-funds relief, multi-class relief, and BDC and closed-end co-investment relief under Sections 17(d) and 57(i). Form APP WD/A is an amendment to a previously filed APP WD, used to correct, supplement, or restate the original withdrawal notice.

The unit of analysis is the individual withdrawal filing — not the underlying application that is being withdrawn, and not any individual document inside the submission. Each accession is delivered as a folder inside a monthly ZIP container; the container format is ZIP and the included file types are HTML, JSON, TXT, and PDF. Coverage begins with EDGAR's adoption of the APP WD code in February 2002. Withdrawals filed earlier under Rule 0-5 exist procedurally but are not classified by this code and therefore are not part of the dataset.

Content Structure of a Single Record

What one record represents

One record in the Form APP WD Files Dataset is a single EDGAR submission of Form APP WD or Form APP WD/A, identified by its EDGAR accession number and packaged as a folder inside a monthly ZIP container. The folder name is the 18-digit accession number with all dashes stripped (for example, 000139834425019029 for accession 0001398344-25-019029). Inside that folder the dataset bundles a metadata.json header file together with the original EDGAR submission documents: typically the primary withdrawal letter as HTML, occasionally a plain-text primary document for older filings, and on rare occasions an accompanying PDF exhibit. Image binaries that were part of the original submission (JPG, PNG, GIF) are deliberately stripped before packaging.

What the underlying filing is

In substance, a Form APP WD filing is a short, formal letter from the applicant or its counsel (commonly a major investment-management law firm such as Dechert, K&L Gates, Ropes & Gray, or Stradley Ronon) addressed to the Secretary of the Commission. The letter identifies the original application by SEC file number and filing date, recites the statutory provisions under which relief had been sought (for example, Section 6(c), co-investment relief, multi-class relief, or relief from various provisions of Sections 12, 17, 18, or 61 of the 1940 Act), states the scope of the withdrawal (full or partial, and which specific applicants are withdrawing), and closes with a counsel signature block. There is no item-by-item disclosure framework, no financial schedule, and no structured data instance — the filing's content is essentially narrative legal correspondence wrapped in EDGAR's submission machinery.

Content layers in a single record

A record has two stacked content layers:

1. A metadata.json file that captures the parsed EDGAR header for the submission: form type, accession number, filing timestamp, EDGAR-side URLs, the document-format manifest, the filer/registrant entity blocks, and ancillary investment-company series/class metadata.
2. The original submission documents themselves, each delivered with EDGAR's SGML <DOCUMENT> wrapper around an inline HTML or plain-text payload.

The folder layout is flat: metadata.json and the primary document sit side by side at the root of the accession folder, with no nested subdirectories. When a filing carried additional non-image exhibits in its original EDGAR submission (for example a supporting PDF), those files are placed alongside the primary document in the same folder. Image files referenced in the document manifest are not materialized on disk because the dataset publisher strips them.

The metadata.json schema

The metadata file is a single JSON object whose top-level fields describe the filing as a whole and whose nested arrays describe its components. The fields that consistently carry meaningful content are:

• formType — Always "APP WD" or "APP WD/A".
• accessionNo — The EDGAR accession number in dashed form (for example 0001398344-25-019029), the canonical identifier.
• filedAt — ISO-8601 timestamp with timezone offset, recording EDGAR acceptance.
• description — Human-readable description of the form, frequently the long-form EDGAR label (for example, "Form APP WD - Withdrawal of an Application for exemption [Section 12(g)] or from filing certain reports [Section 13(a)]").
• linkToFilingDetails — URL to the primary HTML document on EDGAR.
• linkToHtml — URL to the EDGAR filing-index page.
• linkToTxt — URL to the complete-submission .txt file on EDGAR.
• linkToXbrl — Empty string for APP WD filings.
• id — A 32-character hex identifier assigned by sec-api.io.
• documentFormatFiles — Array describing every file in the original EDGAR submission (see below).
• dataFiles — Array reserved for XBRL data files; empty for APP WD filings.
• seriesAndClassesContractsInformation — Array of investment-company series/class metadata; populated only when the EDGAR header carries series/class identifiers.
• entities — Array of filer/registrant blocks (see below).

documentFormatFiles

Each element corresponds to one file enumerated in the original EDGAR submission and carries:

• sequence — String sequence number used by EDGAR (a single space character for the complete-submission text file).
• size — Byte size as a string.
• documentUrl — Direct URL to the file on www.sec.gov/Archives/edgar/....
• type — Document type code, typically APP WD, APP WD/A, GRAPHIC for image attachments, or blank for the complete-submission text file.
• description — Optional EDGAR description, such as GRAPHIC or Complete submission text file.

This array is the authoritative manifest for what the original submission contained. Readers can reconstruct the full original filing by following the documentUrl values back to EDGAR even when, for example, image attachments have been excluded from the local copy.

entities

The entities array carries one block per filer or registrant lifted from the EDGAR header. Investment-company withdrawals frequently list multiple entities — for example, an adviser plus one or more registered funds plus affiliated partnerships — each with its own block. Each block contains:

• companyName — Legal name with a role suffix in parentheses, such as "Partners Group Lending Fund, LLC (Filer)".
• cik — Central Index Key.
• type — Form type for that entity (APP WD or APP WD/A).
• act — Securities-act code; 98 indicates the Investment Company Act of 1940 and predominates in this dataset.
• fileNo — SEC file number, frequently in the 803-... range (registered investment adviser file series) or the 812-... range (exemptive application series).
• filmNo — EDGAR film number assigned at acceptance.
• irsNo — IRS employer-identification number, when reported.
• stateOfIncorporation — Two-letter state or jurisdiction code.
• fiscalYearEnd — MMDD fiscal-year-end date, present on some entities.

The act and fileNo fields are particularly useful for confirming that the underlying application was an Investment Company Act application and for cross-referencing the application being withdrawn.

The SGML document wrapper

The primary withdrawal document is delivered exactly as EDGAR distributed it: an HTML body inside an SGML <DOCUMENT> envelope. The shape is:

          1
          <DOCUMENT>
        

          2
          <TYPE>APP WD
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>fp0095380-1_appwd.htm
        

          5
          <TEXT>
        

          6
          <HTML>
        

          7
          <HEAD><TITLE></TITLE></HEAD>
        

          8
          <BODY> ... withdrawal letter ...
        

          9
          </BODY>
        

          10
          </HTML>
        

          11
          </TEXT>
        

          12
          </DOCUMENT>
        

<TYPE> repeats the form type code, <SEQUENCE> records the document's order in the original submission, <FILENAME> carries the on-disk filename, and <TEXT> wraps the actual HTML payload. The wrapper is identical across vintages; only the payload format inside <TEXT> differs (HTML for modern filings, flat plain text for older ones). Parsers should expect to strip the SGML envelope before treating the inner body as standalone HTML or text.

Section-by-section anatomy of the withdrawal letter

Although Form APP WD has no formal Item-numbered structure, the body of a typical withdrawal letter is organized as the following ordered components:

1. Letterhead and date. Law firm or filer letterhead at the top, followed by the filing date.
2. Address block. Addressed to the U.S. Securities and Exchange Commission, Division of Investment Management (or the relevant division), typically at 100 F Street, NE, Washington, DC.
3. Re: line. A subject line identifying the original application — by applicant name, by the SEC file number assigned to the application (typically 812-XXXXX for Investment Company Act exemptive applications), and by the original filing date.
4. Identification of the application. A short paragraph naming the applicants, summarizing the relief originally requested, and citing the specific statutory provisions and rules involved (commonly Sections 6(c), 17(b), 17(d), 18(a)(2), 18(c), 18(i), or 61(a) of the Investment Company Act, or Section 12(g) / Section 13(a) of the Exchange Act).
5. Statement of withdrawal. The operative sentence requesting that the Commission permit the applicants to withdraw the application, with explicit indication of whether withdrawal is total or partial, and (if partial) which sections of relief or which applicants are being withdrawn.
6. Reason for withdrawal. A brief statement of the reason — for example, that the relief is no longer needed, that the application has been superseded by a subsequent filing, that the applicants no longer intend to pursue the relief, or that an exemption has become available by other means. Some filings give only a perfunctory reason; others are more substantive.
7. Signature block. Signed by counsel or by an authorized officer of the applicant, with name, firm affiliation, and contact information.

The letters are short — typically a single page of substantive text — and contain little or no tabular content. For Form APP WD/A amendments, the letter additionally references the prior withdrawal notice by date and explains what is being amended, typically a correction to the scope of withdrawal, the addition or removal of a withdrawing applicant, or a clarification of the statutory citations.

Included content

For each accession number, the dataset includes:

• The parsed EDGAR header as metadata.json.
• The primary withdrawal document, almost always an .htm/.html file delivered inside the SGML wrapper.
• For older filings, a plain-text primary document under the same SGML wrapper (with <TEXT> wrapping flat letter text rather than HTML markup).
• Any non-image exhibits that accompanied the original submission, including occasional .pdf attachments.
• The documentFormatFiles manifest, which preserves an authoritative record of every file in the original submission, including those excluded locally.

The file types found in the dataset are HTML, JSON, TXT, and PDF.

Excluded or separate content

Several elements of the original EDGAR submission are not materialized inside the record folder:

• Image files. Graphics referenced as GRAPHIC documents in the manifest (JPG, PNG, GIF) are stripped by the dataset publisher. The documentFormatFiles entry is retained so the existence of the graphic is still discoverable, and documentUrl can be used to retrieve the binary from EDGAR if needed.
• The complete-submission .txt file. EDGAR generates a single concatenated .txt file representing the entire SGML submission. It is referenced via linkToTxt and listed in documentFormatFiles, but is generally not copied into the record folder because the individual constituent documents are already present.
• The original underlying application. The withdrawal record contains only the withdrawal letter and its associated header. The original application being withdrawn (and any prior amendments to that application) is a separate EDGAR submission and is not part of this record. The fileNo field in entities and the Re-line in the letter body are the cross-reference points.
• Structured data. Form APP WD does not carry XBRL or any other machine-readable schedule; dataFiles is empty and linkToXbrl is an empty string.

Stability of structure across the coverage window

The disclosure substance of Form APP WD has been stable since EDGAR began accepting these filings in February 2002. Because the form has no item-level disclosure schedule and is fundamentally a short request letter, there have been no material revisions to required content over the dataset's coverage window. Filings from 2002, 2010, and 2025 share the same essential anatomy: a letter to the Commission identifying the application, citing the statutory provisions, stating the scope and reason for withdrawal, and signed by counsel or an officer.

What has shifted is the file format of the primary document. Earlier filings are more likely to ship a plain-text primary document (.txt) inside the SGML <DOCUMENT> wrapper, reflecting EDGAR's pre-HTML conventions; later filings predominantly use inline HTML (.htm) inside the same SGML wrapper. The wrapper itself — <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <TEXT> — is unchanged across the period, which makes parsing uniform regardless of payload format. The metadata.json representation of the header is a dataset-side artifact and applies uniformly to every record.

Interpretation and extraction notes

• Cross-referencing the underlying application. The most useful join key for connecting a withdrawal record to the application being withdrawn is the SEC file number cited in the Re-line (typically 812-... for Investment Company Act exemptive applications). The entity-level fileNo may instead reflect the registrant's own 803-... adviser file number, so the body of the letter is often the more reliable pointer to the application than the entity block.
• Multiple filers per record. A single Form APP WD frequently lists several co-applicants in entities — an adviser plus one or more affiliated funds, for instance — each with its own CIK, file number, and state of incorporation. The first entity is not necessarily the lead applicant; the role suffix in companyName (for example "(Filer)") and the textual structure of the letter clarify roles.
• Amendments. APP WD/A filings should be linked back to the prior APP WD by the application file number cited in the Re-line, since EDGAR does not always carry an explicit accession-level pointer between the amendment and the original withdrawal.
• Image-stripped manifests. The documentFormatFiles array can list files that are not present on disk. When a GRAPHIC entry appears with no corresponding local file, this is by design rather than missing data.
• Letter-style content for extraction. Because the body is unstructured legal correspondence, machine extraction of fields like reason for withdrawal, statutory sections cited, or scope of withdrawal (full versus partial) requires natural-language parsing rather than schema-based extraction. The HTML body has minimal semantic tagging — paragraphs and basic formatting only — so positional cues (Re-line, opening paragraph, signature block) are the practical anchors for extraction.
• No financial schedules. The dataset's analytic value lies in the population of withdrawn applications and the textual reasons for withdrawal, not in numeric disclosures. Readers should not expect quantitative financial data in these records.

Who Files or Publishes This Dataset, and When

Who files the record

The filer is the applicant (or group of co-applicants) in a pending SEC application proceeding who has decided to withdraw that application before the Commission acts on it. Form APP WD is the withdrawal notice; APP WD/A is an amendment to a previously filed APP WD, not a withdrawal of a different application.

Because the underlying applications are overwhelmingly Investment Company Act of 1940 matters, the filer population is dominated by 1940 Act regulated entities and their affiliates:

• Registered investment companies registered under Section 8 of the 1940 Act, including open-end funds (mutual funds), closed-end funds, ETFs organized as registered funds, and unit investment trusts.
• Business development companies (closed-end companies that have elected BDC regulation under Sections 55 through 65 of the 1940 Act).
• Investment advisers registered under the Investment Advisers Act of 1940, typically appearing as co-applicants alongside the funds they advise.
• Affiliated principal underwriters, distributors, and broker-dealers, when the relief sought covered their conduct (for example, affiliated transaction relief under Section 17).
• Insurance company separate accounts registered as UITs or management companies for variable insurance products.
• Operating-company or other non-1940-Act applicants in the small minority of cases where the underlying application sought relief under another statute that EDGAR routes to the APP WD code.

The EDGAR filing of record is associated with the CIK used to submit it; co-applicants are listed in the body of the notice and in the EDGAR header entities block. Most 1940 Act applications are joint, so most APP WD records list multiple parties even though one CIK is the submitter.

What triggers the filing

Form APP WD is event-driven, not periodic. It is filed when the applicant voluntarily abandons a pending application before the SEC issues a final order. There is no statutory deadline; withdrawal can occur any time while the application is pending. Common triggers include:

• Decision not to launch the fund, share class, ETF, or transaction structure for which relief was sought.
• Liquidation, merger, or reorganization of the applicant fund, mooting the requested relief.
• Supersession by a new or broader application that replaces the pending one.
• Adoption of a rule that codifies the relief, eliminating the need for an individualized order. The clearest example is Rule 6c-11 (adopted 2019), which prompted many ETF sponsors to withdraw pending exemptive applications.
• Staff comments indicating that the order will not issue in the requested form, or will require conditions the applicant will not accept.
• Changes of control at the adviser or sponsor that change the applicant set or moot the relief.

Withdrawals can be filed before the SEC issues a notice of application, after a notice but before an order, or in clusters following a codifying rulemaking.

Regulatory framework

The procedural basis for withdrawal lies primarily in Rule 0-5 under the Investment Company Act of 1940 (17 CFR 270.0-5), which governs the procedure for applications for orders under the 1940 Act and authorizes an applicant to withdraw a pending application by written notice. Parallel application-and-withdrawal procedures exist under analogous SEC rules when the Commission's order-issuing authority is invoked under another federal securities statute (for example, applications under the Advisers Act, the Exchange Act, or the Trust Indenture Act).

The statutory backdrop is the SEC's authority to issue exemptive and other discretionary orders, principally:

• Section 6(c) of the 1940 Act, the general exemptive authority that underpins most fund industry applications.
• Sections 17(b), 17(d), Section 10(f), Section 12(d)(1)(J), Section 18, Section 22(d), Section 23(c), and Section 57 of the 1940 Act, which authorize specific orders, plus Rules 17d-1 and 17a-7 for affiliated transaction and joint enterprise relief.
• The Commission's analogous order-issuing authority under the Advisers Act, Exchange Act, and Trust Indenture Act in the small subset of non-1940-Act cases.

Common categories of relief in the underlying applications include Section 6(c) exemptive orders, Section 17 affiliated-transaction and joint-enterprise relief, Section 12(d)(1) fund-of-funds relief, multi-manager (manager-of-managers) relief, BDC and closed-end fund co-investment relief under Sections 17(d) and Section 57(i), and historically ETF exemptive relief (now largely superseded by Rule 6c-11).

When the record is filed

Filing on Form APP WD is voluntary and applicant-initiated. There is no filing deadline, no fiscal-period trigger, and no look-back or look-forward window. The submission consists of a short notice or letter to the Secretary of the Commission identifying the original application by SEC file number and date, the applicants, the statutory provisions originally invoked, and a brief reason for withdrawal. EDGAR-tagged APP WD records in this dataset begin in February 2002, when EDGAR adopted the dedicated form-type code; withdrawals filed earlier under Rule 0-5 exist procedurally but are not classified by this code.

Important distinctions

• Filer vs. subject: the filer is the applicant. A fund that is the subject of the application but is not itself an applicant is not the APP WD filer.
• Withdrawal is not a denial: APP WD reflects applicant abandonment, not SEC denial. Formal denials are rare; staff concerns more often produce a withdrawal or a substantial amendment.
• Distinct from registration withdrawals: APP WD is not the same as [RW](https://www.sec.gov/submit-filings/filer-support-resources/how-do-i-guides/withdraw-registration-or-certification-statement) (Securities Act registration withdrawal under Rule 477), [AW](https://www.sec.gov/submit-filings/filer-support-resources/how-do-i-guides/withdraw-registration-or-certification-statement) (withdrawal of a registration statement amendment), or [N-8F](https://www.sec.gov/files/formn-8f.pdf) (deregistration of a registered investment company under Rule 0-2). Each addresses a different procedural posture.
• Distinct from no-action and interpretive requests: those are handled through staff correspondence, not on Form APP WD.
• APP WD/A scope: an amendment is filed by the same applicant population to correct or supplement a prior APP WD (for example, to fix the application file number, adjust the co-applicant list, or supplement the stated reason). It is not a new withdrawal.
• Generic EDGAR description text: the human-readable description on some APP WD records references Exchange Act sections (e.g., 12(g), 13(a)) because EDGAR uses a shared label across application-withdrawal contexts; the actual statutory basis for any given record is whatever the underlying application cited, most often the 1940 Act.

How This Dataset Differs From Similar Datasets or Filings

Several adjacent forms share either the "withdrawal" label or the 1940 Act application workflow, and are routinely confused with APP WD. The comparisons below isolate each on four axes: governing Act, filer, trigger, and outcome.

APP NTC (notice of application)

• Act / actor: Same 1940 Act proceeding, but issued by SEC staff, not the applicant.
• Trigger: Staff has reviewed the application and is prepared to publish notice that an order is contemplated, opening the hearing-request window.
• Outcome: Forward motion toward issuance of an exemptive order.
• Distinction: APP NTC advances the proceeding; APP WD ends it. Both reference the same underlying application, but never substitute for one another. A given application may produce an NTC and no APP WD, an APP WD and no NTC, or both (withdrawal after notice).

Underlying application (40-APP, APP, and amendments on /A)

• Act / actor: Filed by the applicant under the 1940 Act (or, less often, the Advisers Act, Exchange Act, or Trust Indenture Act).
• Trigger: The applicant seeks an order granting exemptive or other discretionary relief.
• Outcome: Opens a docketed proceeding.
• Distinction: 40-APP is the request; APP WD is the retraction. The APP WD dataset captures terminations only and contains no record of the application's substance, so analyzing exemptive-relief activity requires pairing APP WD with the 40-APP population.

Investment Company Act exemptive orders (IC Releases)

• Act / actor: Issued by the Commission under the 1940 Act.
• Trigger: Staff and Commission have approved the requested relief.
• Outcome: An affirmative, published order granting the exemption.
• Distinction: The order and APP WD are mutually exclusive outcomes for any single application. APP WD is the negative-space dataset: the proceedings that closed without an order. APP WD does not capture later modification, supersession, or rescission of orders already issued.

Form RW (registration withdrawal under Securities Act Rule 477)

• Act / actor: Securities Act of 1933; filed by an issuer with a pending registration statement (S-1, S-3, S-4, F-1, etc.).
• Trigger: Issuer abandons or restructures a planned offering before effectiveness.
• Outcome: The registration statement is withdrawn; no securities are sold under it.
• Distinction: Form RW withdraws an offering registration; APP WD withdraws an application for an SEC order. Different Act, different filing being withdrawn, and largely different filer populations (broad issuer universe for RW vs. funds and fund affiliates for APP WD).

Form AW (withdrawal of an Exchange Act application or amendment)

• Act / actor: Securities Exchange Act of 1934; filed by a prospective broker-dealer, transfer agent, municipal securities dealer, or similar registrant.
• Trigger: Withdrawal of a pending registration application (e.g., Form BD) before approval, or withdrawal of an amendment.
• Outcome: The pending intermediary registration is abandoned.
• Distinction: Form AW and APP WD are both pre-decision withdrawals of pending applications, but on entirely separate tracks: market-intermediary registration (Exchange Act) vs. exemptive relief (1940 Act). They are not substitutes and can coexist for an integrated firm filing in different proceedings.

Form N-8F (deregistration of a registered investment company)

• Act / actor: 1940 Act Section 8(f); filed by a registered investment company.
• Trigger: The fund has liquidated, merged, or otherwise ceased to be an investment company.
• Outcome: Termination of the entity's registration as an investment company.
• Distinction: Both are 1940 Act fund-side filings, but Form N-8F dissolves the entity's registered status, while APP WD merely abandons one pending application and leaves registration intact. A wind-down can produce both filings sequentially, but they capture different legal effects at different lifecycle stages.

Forms 15-12B and 15-12G (Exchange Act deregistration)

• Act / actor: Exchange Act Sections 12(b)/12(g); filed by a public-company issuer.
• Trigger: Issuer becomes eligible to suspend or terminate Section 13/15(d) reporting (e.g., fewer than 300 holders, delisting).
• Outcome: End of public reporting obligations for the class of securities.
• Distinction: Different Act, different filer universe (operating issuers, not fund applicants), and different effect (exit from public reporting vs. closure of one application proceeding). A Form 15 filer is leaving the public-reporting system; an APP WD filer remains fully registered and active.

APP WD/A versus APP WD

APP WD/A is an amendment to a previously filed APP WD. It corrects identifiers, citations, joint-applicant lists, or the stated reason for withdrawal; it does not initiate a separate withdrawal. For accession-level analysis, each APP WD/A should be linked to the original APP WD it amends rather than counted as a distinct termination event.

Boundary summary

APP WD is uniquely scoped to one procedural moment: the applicant-initiated termination of a pending SEC application for an order, almost exclusively under the 1940 Act and Rule 0-5, before any order issues. It does not withdraw securities offerings (RW), intermediary registration applications (AW), investment-company registration (N-8F), or Exchange Act reporting status (Form 15). It does not record the application itself (40-APP), its public notice (APP NTC), or the resulting exemptive order (IC Release). It is the negative-outcome counterpart to a granted exemption, and the only EDGAR record that specifically marks the closure of a 1940 Act application proceeding without an order. A full lifecycle view of exemptive relief requires pairing APP WD with the underlying 40-APP filings, APP NTC notices, and published orders; on its own, APP WD answers only which applications were abandoned and, often, why.

Who Uses This Dataset

Form APP WD and APP WD/A filings mark the end of a pending exemptive application under the Investment Company Act of 1940. The dataset serves professionals tracking application lifecycles, fund product strategy, and SEC exemptive-relief practice. Across roles, four fields do most of the work: the entities array (applicant and affiliates), the inline HTML withdrawal letter (stated reason), the filing date (time-to-withdrawal), and the statutory citations (relief category).

1940-Act regulatory counsel

Investment Company Act lawyers use the dataset to track abandoned applications by their clients and competing applicants. The entities array identifies the applicant; statutory citations classify the relief (multi-class, ETF, fund-of-funds, co-investment, interfund lending, manager-of-managers, joint transactions); the HTML letter signals whether withdrawal followed unresolvable staff comments, a superseding rule, or a restructured transaction. Counsel use this to calibrate drafting strategy on live applications and advise clients on whether to refile or pursue an alternative route.

Fund compliance officers and CCOs

In-house compliance teams check whether relief their complex relies on, or relief sought by sub-advisers and affiliates, was withdrawn rather than granted. Filer name, affiliated entities, and statutory citations feed exemptive-order inventories and the periodic review of conditions on outstanding orders.

Asset-management strategy and product-development teams

Product strategists treat APP WD filings as a competitive-intelligence signal. A competitor withdrawal, dated and tied to a relief category, indicates a shelved or restructured product (new ETF wrapper, interval-fund mechanic, non-transparent ETF, novel share class, closed-end structure). Time-to-withdrawal, computed from original application date to APP WD date, proxies staff friction in specific product categories and informs filing timing.

Former Division of Investment Management staff in private practice

Former staff now advising fund clients use the corpus to maintain pattern recognition on which relief types tend to be withdrawn, typical duration before withdrawal, and the language applicants use to characterize reasons. This shapes counsel on whether to pursue an order, seek no-action relief, or wait for rulemaking.

Competitive-intelligence and fintech analysts

Analysts covering asset management and digital-asset products use applicant CIK, filing date, and implied relief category to flag when a sponsor abandons a regulatory pathway, particularly for crypto-related funds, tokenized structures, and novel ETF mechanics. Joined to the original applications, the data supports abandonment-rate dashboards over time.

M&A counsel doing adviser and fund-sponsor diligence

In acquisitions of registered advisers or fund complexes, deal counsel verify whether relief a target describes as "pending" still exists. A withdrawal can materially change deal value when the target's product roadmap depended on the requested order. Diligence teams match the entities array to target affiliates, compare filing dates to the deal timeline, and read the letter to assess whether the application can be refiled. The findings feed reps and warranties, indemnification, and post-closing integration.

Fund deregistration and wind-down specialists

Lawyers and consultants managing terminations, mergers, and adviser wind-downs use the dataset to confirm that pending applications tied to a winding-down complex have been formally withdrawn. Entity identifiers, original application references, and filing dates surface orphaned applications. APP WD/A amendments matter when an original withdrawal required correction.

Outside counsel and fund administrators preparing APP WD filings

Drafters use the historical archive of inline HTML letters as a precedent library: how to characterize the reason for withdrawal, how to reference the underlying application, and how to format multi-applicant withdrawals where several entities appear in the entities array. The dataset is low-volume but precise, which makes prior letters a practical drafting model.

Academic researchers in securities regulation and financial economics

Researchers use the full record set to study the exemptive-application process empirically: time-to-withdrawal distributions, withdrawal rates by relief category, the effect of rulemaking events (such as ETF rule adoption) on abandonment, and repeat-applicant patterns. CIK, filing date, and statutory citations anchor quantitative work; letter text supports content analysis of stated reasons.

RAG and LLM teams indexing EDGAR

Engineers building retrieval systems over EDGAR use APP WD records to link applications, withdrawals, and resulting orders across filing types. Metadata JSON, the HTML letter, and entities cross-references support entity linking, application-lifecycle reconstruction, and grounded answers about the status of specific exemptive requests.

Specific Use Cases

Building a precedent library of withdrawal letters by relief type

Drafters preparing a new APP WD or APP WD/A pull the inline HTML letters and group them by the statutory citations in the Re-line and opening paragraph (Section 6(c), 17(b), 17(d), 18, 61(a), and so on). The letter bodies serve as templates for phrasing the reason for withdrawal, scoping a partial withdrawal, and listing multiple applicants from the entities array. The output is a curated, citation-indexed letter bank that shortens drafting time on live withdrawals.

Tracking time-to-withdrawal as a proxy for SEC staff friction

Joining each APP WD record to the underlying 40-APP application by the 812-... file number cited in the Re-line yields a duration from initial filing to withdrawal. Bucketing those durations by relief category (multi-class, co-investment, interfund lending, non-transparent ETF, crypto) surfaces categories where the staff review pipeline is stalling. Product and legal teams use the resulting distributions to set realistic filing timelines and to decide whether to pursue an order, seek no-action relief, or wait for rulemaking.

Identifying applications mooted by Rule 6c-11 and other rulemaking events

Filtering APP WD filings around the September 2019 effective date of Rule 6c-11 (and similar later rulemakings) isolates the cohort of ETF exemptive applications withdrawn because the requested relief became codified. The reason language inside the letter confirms whether the trigger was the new rule, a superseding application, or a sponsor pivot. The result is a clean event-study cohort linking rulemaking to abandonment behavior.

Competitive intelligence on shelved sponsor products

Filtering by sponsor CIK in the entities array and reading the relief category from the letter reveals which product attempts a competitor abandoned and when. Recurrent withdrawals from a single complex on the same relief category suggest a structural product roadblock; an isolated withdrawal followed by a new application points to a re-scoped filing. Strategy teams feed this into competitive product trackers and abandonment-rate dashboards.

M&A diligence on a target's pending exemptive relief

In acquisitions of advisers or fund complexes, deal counsel match target affiliates against the entities array and fileNo values to confirm whether relief the target describes as "pending" has in fact been withdrawn. The letter clarifies whether withdrawal was full or partial and whether refiling remains viable. The finding directly affects deal value when the target's product roadmap depended on the order, and feeds reps and warranties and post-closing integration plans.

Populating a RAG index of withdrawal reasons

Engineers chunk the HTML letter body, attach accessionNo, applicant CIKs, statutory citations, and filedAt as metadata, and index the result alongside the underlying 40-APP and any APP NTC notices. The index answers grounded questions such as "is application 812-XXXXX still alive?" and "why did sponsor X abandon its co-investment relief request?" Cross-references via the Re-line file number stitch application, withdrawal, and order across filing types.

Academic analysis of the application/withdrawal lifecycle

Researchers use the full corpus, joined to 40-APP filings and IC Releases, to estimate withdrawal rates by relief category, time-to-withdrawal distributions, repeat-applicant behavior, and the response of abandonment rates to specific rulemakings or staff guidance. The entities array, filedAt, and statutory citations anchor the quantitative work; the letter text supports content analysis of stated reasons.

Dataset Access

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

This endpoint returns dataset-level metadata and the list of available container files. The metadata includes the dataset name, description, last update timestamp, earliest sample date (2002-02-01), total record and size counts, covered form types (APP WD, APP WD/A), the container format (ZIP), and the included file types (HTML, JSON, TXT, PDF). For each container, the response includes its key, size, record count, last update timestamp, and direct download URL. Use this endpoint to monitor which containers were refreshed in the most recent run and to decide which containers to download incrementally.

This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-696e-90e6-31a30ca53e39",
        

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

          4
            "name": "Form APP WD Files Dataset",
        

          5
            "updatedAt": "2026-04-21T02:55:39.149Z",
        

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

          7
            "totalRecords": 389,
        

          8
            "totalSize": 1677304,
        

          9
            "formTypes": ["APP WD", "APP WD/A"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

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

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

          16
                "size": 18432,
        

          17
                "records": 3,
        

          18
                "updatedAt": "2026-04-21T02:55:39.149Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

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

Downloads the full dataset as a single ZIP archive containing every container file. This endpoint requires an API key.

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

Downloads one individual monthly container instead of the full archive, which is useful for incremental updates. This endpoint requires an API key.

Frequently Asked Questions

What forms does this dataset cover?

The dataset covers Form APP WD and Form APP WD/A submissions on EDGAR. APP WD is the formal notice by which an applicant withdraws a pending application for an SEC exemptive or other discretionary order; APP WD/A is an amendment to a previously filed APP WD.

What does one record in this dataset represent?

One record is a single EDGAR submission of Form APP WD or APP WD/A, identified by its accession number. Each record is delivered as a folder containing a parsed metadata.json header file alongside the original withdrawal letter (HTML or, for older filings, plain text) and any non-image exhibits such as occasional PDF attachments.

Who is required to file Form APP WD?

There is no mandatory filing requirement; APP WD is voluntary and applicant-initiated. Filers are the applicants in pending SEC application proceedings — predominantly registered investment companies, business development companies, investment advisers, and their affiliates — who choose to abandon a pending application before the Commission acts on it, most often pursuant to Rule 0-5 under the Investment Company Act of 1940.

What time period does the dataset cover?

The earliest sample date is February 2002, when EDGAR adopted the dedicated APP WD form-type code. Coverage continues through the present. Withdrawals filed under Rule 0-5 before February 2002 exist procedurally but were not classified under this code and are therefore not part of the dataset.

How is APP WD different from Form RW or Form N-8F?

Form RW withdraws a pending Securities Act registration statement for a securities offering; Form N-8F deregisters an investment company under Section 8(f) of the 1940 Act. APP WD does neither — it terminates a single pending application for an SEC order while leaving the applicant's registration status fully intact. APP WD is also the negative-outcome counterpart to a granted exemptive order (an IC Release): the two outcomes are mutually exclusive for any single application.

What file formats does each record contain?

Each record contains a metadata.json file (parsed EDGAR header), the primary withdrawal document as HTML (or plain text for older filings) inside an SGML <DOCUMENT> wrapper, and any non-image exhibits that accompanied the original submission, including occasional PDFs. The dataset's overall file types are HTML, JSON, TXT, and PDF, and containers are distributed as monthly ZIP archives. Form APP WD does not carry XBRL, so dataFiles is empty and linkToXbrl is an empty string.

How can I link an APP WD record to the underlying application that was withdrawn?

The most reliable join key is the SEC file number cited in the Re-line of the withdrawal letter, typically in the 812-... series for Investment Company Act exemptive applications. The entity-level fileNo in entities may instead reflect the registrant's 803-... adviser file number, so for cross-referencing the application being withdrawn the letter body is generally more authoritative than the entity block.