Form C-AR-W Files Dataset

The Form C-AR-W Files dataset packages every Form C-AR-W submission accepted by EDGAR — the procedural cover filing by which a Regulation Crowdfunding issuer withdraws a previously filed Form C-AR annual report. Each record corresponds to one EDGAR accession and contains the EDGAR-XML primary document together with a normalized JSON header derived from the SGML submission wrapper. The form is filed exclusively by the issuer of securities sold under Section 4(a)(6) of the Securities Act of 1933 and Title III of the JOBS Act (17 CFR Part 227), and exists only as an electronic EDGAR submission. Coverage begins on 2018-04-01 — the first wave of withdrawal activity after Regulation Crowdfunding became operative in May 2016 — and continues to the present, with monthly ZIP containers organized by EDGAR filing date. Records are distributed in ZIP containers holding XML and JSON files.

Update Frequency
Daily
Updated at
2026-05-06
Earliest Sample Date
2018-04-01
Total Size
20.2 KB
Total Records
14
Container Format
ZIP
Content Types
XML, JSON
Form Types
C-AR-W

Dataset APIs

Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.

Dataset Index JSON API

Download the entire dataset as a single archive file.

Download Entire Dataset:

Download a single container file (e.g. monthly archive) from the dataset.

Download Single Container:

Dataset Files

12 files · 20.2 KB
Download All
2026-05.zip1.5 KB1 records
2026-04.zip1.4 KB1 records
2025-11.zip1.4 KB1 records
2025-05.zip3.0 KB2 records
2023-08.zip1.5 KB1 records
2023-05.zip1.5 KB1 records
2023-04.zip1.4 KB1 records
2022-04.zip1.4 KB1 records
2020-04.zip1.5 KB1 records
2019-10.zip1.4 KB1 records
2018-08.zip1.5 KB1 records
2018-04.zip2.8 KB2 records

What This Dataset Contains

The dataset is a complete archive of Form C-AR-W filings accepted by EDGAR from April 2018 forward. Form C-AR-W is the withdrawal counterpart to Form C-AR, the annual report mandated by Rule 202 of Regulation Crowdfunding (17 CFR 227.202) for issuers that completed a securities offering under Section 4(a)(6) of the Securities Act of 1933 and the Title III rules adopted in 2015 and effective May 2016. Form C-AR-W is the procedural submission by which an issuer asks EDGAR to withdraw a previously filed C-AR. It does not amend, replace, or restate the substantive content of the prior annual report; it records the withdrawal of that report on the EDGAR docket.

Because the form is administrative, its required content is intentionally narrow. It identifies the issuer, identifies the fiscal period covered by the C-AR being withdrawn, and carries the signature attestations needed to authorize the withdrawal. It does not restate offering terms, financial condition, capital structure, ownership, intermediary identification, use of proceeds, or any other disclosure item present in the original C-AR. EDGAR accepts the form as a structured XML submission; there is no HTML body, no PDF, and no narrative attachment. The dataset packages each accepted submission as a per-accession folder grouped into monthly ZIP containers, with content delivered as XML and JSON files.

Content Structure of a Single Record

What one record represents

One record in the Form C-AR-W Files Dataset is a single Form C-AR-W submission accepted by EDGAR. On disk, each record is a per-accession folder named with the digits-only EDGAR accession number (for example 000173870425000008) that holds the EDGAR documents associated with the submission together with a normalized metadata header. Folders are grouped into monthly ZIP containers organized by EDGAR filing date under the path convention YYYY/YYYY-MM.zip. The accession folder is the smallest analytic unit in the dataset; the monthly ZIP is the distribution unit.

Form C-AR-W is a procedural withdrawal filing and is therefore unusually compact. An accession folder for this form type contains exactly two artifacts:

  • metadata.json — the structured normalization of the EDGAR submission header and document index.
  • primary_doc.xml — the EDGAR-XML form payload, bound to the http://www.sec.gov/edgar/formc namespace shared with the rest of the Regulation Crowdfunding form family.

There are no exhibits, HTML attachments, financial statements, narrative documents, or auxiliary structured data files associated with a C-AR-W record.

Content layers in a single record

A record carries two parallel content layers:

  1. Normalized header layer (metadata.json) — derived from the EDGAR submission's SGML header and document index. Provides query-friendly access to filing identifiers, timing, the filer-entity attributes EDGAR maintains for the issuer, and back-references to EDGAR copies of the underlying documents.
  2. Form-payload layer (primary_doc.xml) — the EDGAR-XML body of the C-AR-W itself. Carries the issuer name, the fiscal period reference to the withdrawn C-AR, the live/test flag, processing flags, and the signature blocks.

There is no third content layer for C-AR-W: no separate exhibits, financial data files, R-files, FilingSummary, cover-page artifacts, or rendering artifacts exist for this form type, and image files that may have been part of the original EDGAR submission are excluded from the dataset packaging.

metadata.json — section by section

metadata.json is the structured rendering of the EDGAR submission header. The fields of analytic interest are:

  • formType — Always the literal string C-AR-W for every record in this dataset.
  • accessionNo — The EDGAR accession number in dashed canonical form (for example 0001738704-25-000008); the digits-only variant is the accession folder name on disk.
  • filedAt — ISO 8601 timestamp with timezone offset for EDGAR acceptance.
  • periodOfReport — ISO date (for example 2018-12-31) identifying the fiscal period covered by the C-AR being withdrawn. This is the canonical pointer to the prior annual report; it is not the date the withdrawal was filed.
  • description — Human-readable form label, typically Form C-AR-W - Annual Report Withdrawal.
  • linkToFilingDetails — URL to primary_doc.xml on EDGAR.
  • linkToTxt — URL to the complete EDGAR submission .txt (SGML) wrapper.
  • linkToHtml — URL to the EDGAR filing index page (-index.htm).
  • linkToXbrl — Empty for C-AR-W.
  • documentFormatFiles[] — One entry per attached document, each with sequence, size, documentUrl, and type. For C-AR-W this typically contains the XML primary document (with type C-AR-W) and the complete SGML submission text file.
  • entities[] — One or more filer-entity records. Each carries cik, companyName with a role suffix such as (Filer), irsNo, fileNo (the issuer's 020- Regulation Crowdfunding file number), stateOfIncorporation, fiscalYearEnd (as MMDD), act (33, for the Securities Act of 1933), filmNo, and type.
  • seriesAndClassesContractsInformation[] — Empty for C-AR-W.
  • dataFiles[] — Empty for C-AR-W.
  • id — A 32-character hexadecimal internal record identifier.

primary_doc.xml — section by section

The primary document is an EDGAR submission XML rooted at <edgarSubmission> and bound to the http://www.sec.gov/edgar/formc namespace. The root has two children, <headerData> and <formData>.

<headerData> — EDGAR submission header

  • <submissionType> — Always C-AR-W.
  • <filerInfo> — Wraps the filer identification and submission-control flags:
    • <filer><filerCredentials> — Carries the filer CIK and a redacted CCC placeholder (the EDGAR confirmation code is not exposed in the public document).
    • <period> — The fiscal period of the withdrawn C-AR in MM-DD-YYYY form. This element mirrors periodOfReport in metadata.json.
    • <liveTestFlag> — Distinguishes live submissions (LIVE) from EDGAR test filings (TEST).
    • <flags> — Boolean processing flags including confirmingCopyFlag, returnCopyFlag, and overrideInternetFlag.

<formData> — form body

  • <issuerInformation><issuerInfo> — A thin issuer block whose only payload is <nameOfIssuer>. C-AR-W deliberately does not repeat the broader issuer-identification fields (mailing address, jurisdiction, website, CIK, industry codes) that Form C and Form C-AR carry; the fuller issuer identity travels through the EDGAR header and the entities[] array of metadata.json.
  • <signatureInfo> — Carries two parallel signature structures:
    • <issuerSignature> — Identifies the issuer entity and the natural person signing on its behalf. Contains <issuer> (the issuer's legal name), <issuerSignature> (the typed signature of the signing person), and <issuerTitle> (the signer's role, for example Founder and CEO).
    • <signaturePersons> — A repeating block of one or more <signaturePerson> elements, each containing <personSignature>, <personTitle>, and <signatureDate> in MM-DD-YYYY form. This mirrors the multi-signature pattern across the Regulation Crowdfunding form family, in which the issuer signature is supplemented by the signatures of the principal executive officer and a majority of the board where applicable.

Notably absent from primary_doc.xml are narrative disclosure blocks, financial schedules, offering terms, intermediary identification, ownership tables, related-party transaction disclosures, and use-of-proceeds statements. Form C-AR-W is structurally a thin attestation: it points at the prior C-AR through the <period> element and authorizes the withdrawal through the signature blocks.

What the dataset record includes

Each record packaged in this dataset contains the EDGAR-XML primary document for the C-AR-W and the normalized JSON header derived from the EDGAR submission's SGML wrapper and document index. Together these two files carry the issuer's legal name and CIK, the fiscal period of the withdrawn annual report, the live/test status of the submission, the processing flags applied at acceptance, the typed signatures and titles of the issuer signatory and any additional signing persons, the EDGAR accession number, the acceptance timestamp, the filer-entity attributes (state of incorporation, IRS employer identification number, Regulation Crowdfunding file number, fiscal year end), and the URLs that link back to the EDGAR copies of the primary document, the index page, and the complete SGML submission file.

What is excluded or structurally separate

  • Image files that may have been part of the original EDGAR submission are excluded from the dataset. This is rarely material for C-AR-W in practice because the form does not call for graphical content.
  • The full SGML .txt wrapper that EDGAR retains for each submission is referenced from metadata.json through linkToTxt but is not copied into the accession folder; only its document index is reflected in documentFormatFiles[].
  • The original Form C-AR being withdrawn is a separate filing on EDGAR with its own accession number and is not bundled into the C-AR-W record.
  • Subsequent amendments, refilings, or re-submissions of the annual report are likewise distinct EDGAR filings outside the scope of a given C-AR-W record.
  • The Form C offering filing, Form C-U progress update, and any prior C-AR amendments (Form C-AR/A) for the same issuer are not packaged with the C-AR-W; they remain independent accession folders within their own dataset products.

Schema stability and historical context

Form C-AR-W has existed only since the Regulation Crowdfunding regime became operative in May 2016 under Title III of the JOBS Act, with C-AR-W filings appearing on EDGAR from April 2018 onward. The form was introduced alongside Form C, Form C-U, Form C-AR, Form C-TR, and the corresponding withdrawal forms (Form C-W, C-AR-W, C-TR-W), and was structured from inception as an EDGAR-XML submission rather than a text or HTML document. It has not gone through the ASCII-to-HTML evolution that older form types experienced. The XML schema and the element set within the formc namespace have remained stable across the dataset's coverage period, so the section-by-section anatomy described above applies uniformly across all records.

Interpretation and extraction notes

  • Linking back to the withdrawn C-AR. Neither file in the record carries the accession number of the underlying C-AR. The canonical pointers are <period> in primary_doc.xml and periodOfReport in metadata.json. Reconstructing the link to the prior annual report requires matching the issuer CIK and the period of report against the EDGAR filing history for that issuer. When a single issuer has filed C-AR for multiple fiscal years, periodOfReport is the disambiguator.
  • Multi-filer submissions. entities[] typically holds a single filer record for Regulation Crowdfunding issuers, but the schema permits more than one role-tagged record when joint filers are involved.
  • Signature handling. Signatures appear only as typed strings in the XML payload, never as scanned images or attached graphical attestations. Signature extraction is therefore a string-level operation against <issuerSignature>, <personSignature>, <issuerTitle>, <personTitle>, and <signatureDate>. Be aware that <issuerSignature> is overloaded as both a wrapper element under <signatureInfo> and a leaf element holding the signing person's name; XPath expressions must qualify the path accordingly.
  • Date format mismatch. Dates in primary_doc.xml use MM-DD-YYYY (<period>, <signatureDate>), while metadata.json uses ISO 8601 (filedAt, periodOfReport). Code that joins or compares the two layers must normalize formats.
  • Live versus test filings. The <liveTestFlag> element should be checked when building production workflows; only LIVE submissions correspond to effective EDGAR filings.
  • Sparsity. The form is rarely used because the population of issuers that have first filed C-AR and then chosen to withdraw it is itself narrow. Monthly ZIP containers are correspondingly small, and many months hold zero accession folders.

Who Files or Publishes Form C-AR-W, and When

Who files

Form C-AR-W is filed exclusively by the issuer of the securities. The filer must meet all of the following:

  • previously sold (or attempted to sell) securities in reliance on Section 4(a)(6) of the Securities Act of 1933, the crowdfunding exemption added by Title III of the JOBS Act (Pub. L. 112-106, April 5, 2012);
  • became subject to the ongoing annual reporting obligation under Rule 202 of Regulation Crowdfunding (17 CFR 227.202); and
  • previously submitted at least one Form C-AR annual report on EDGAR that is now being withdrawn.

The filer population is dominated by small, early-stage, privately held domestic operating companies (LLCs, corporations, and other Reg CF-eligible legal forms). These issuers are not Exchange Act registrants and do not file Forms 10-K, 10-Q, or 8-K; their entire SEC reporting footprint sits inside the Form C family (C, C/A, C-U, C-AR, C-AR/A, C-AR-W, C-TR, C-W).

The funding portal or registered broker-dealer that intermediated the original offering is not the filer. The annual reporting and withdrawal obligations rest solely with the issuer. Issuers that used Regulation A, Regulation D, Regulation S, or registered offerings do not file in the Form C series, and Reg CF issuers that subsequently became Exchange Act reporting company move to the Exchange Act periodic regime instead.

What triggers a filing

Form C-AR-W is event-driven and discretionary. There is no calendar deadline and no periodic schedule. A filing exists only when the issuer affirmatively decides to withdraw a specific previously submitted Form C-AR. Typical triggers:

  • The issuer has determined that its Reg CF annual reporting obligation has terminated under one of the conditions in Rule 202(b) of Regulation Crowdfunding (e.g., one annual report filed and fewer than 300 holders of record; three annual reports filed and total assets at or below the rule's threshold; repurchase of all Section 4(a)(6) securities; liquidation or dissolution; or becoming an Exchange Act reporting company), and is cleaning up the prior submission.
  • The previously filed Form C-AR contained material errors, was filed under the wrong CIK, was filed prematurely, or was duplicated, and the issuer chose to withdraw rather than amend via Form C-AR/A.
  • The issuer is winding down, dissolving, or has been acquired and is removing the prior annual report from its active EDGAR record.
  • The issuer has filed (or is concurrently filing) Form C-TR to terminate Reg CF reporting and is withdrawing prior C-ARs in connection with that termination.

There is no statutory or regulatory deadline. The submission is timestamped when filed. The withdrawal does not erase the prior C-AR from EDGAR's historical record; the C-AR-W itself becomes part of the public filing history and identifies the C-AR being withdrawn. Form C-AR-W is prescribed under 17 CFR 239.900 and submitted on EDGAR with submission type "C-AR-W."

Important distinctions

  • Not an amendment. Issuers correcting (rather than withdrawing) a prior annual report use Form C-AR/A. C-AR-W removes the submission as an active filing; C-AR/A supplements or restates it.
  • Not Form C-TR. Form C-TR prospectively terminates the ongoing Reg CF annual reporting obligation. Form C-AR-W withdraws one specific previously filed annual report. The two may be used together but address different actions.
  • Not Form C-W. Form C-W withdraws a Form C/A offering statement; Form C-AR-W withdraws a Form C-AR annual report. Each is anchored to its parent filing.
  • Withdrawal is an EDGAR housekeeping action only. It does not unwind the underlying crowdfunding offering, the securities sold under Section 4(a)(6), or any investor rights.
  • An issuer that never filed a Form C-AR cannot file Form C-AR-W; the form requires identification of an existing C-AR as its object.
  • Foreign issuers and investment companies are categorically ineligible for Reg CF under Rule 100(b) of Regulation Crowdfunding, so the entire filer population consists of domestic, non-investment-company issuers that previously used the Section 4(a)(6) exemption.
  • No pre-EDGAR history. Regulation Crowdfunding became effective May 16, 2016; Form C-AR-W has only ever existed as an electronic EDGAR submission. The dataset's earliest sample date of April 2018 reflects the first wave of withdrawal activity roughly two years after the rule's effectiveness.

How This Dataset Differs From Similar Datasets or Filings

Form C-AR-W is a narrow procedural filing within Regulation Crowdfunding (17 CFR Part 227): a cover form that withdraws a previously filed annual report. Confusion typically arises with other Form C-series filings that share the Reg CF regime, and with withdrawal or termination forms in adjacent regimes that serve structurally similar functions. The distinctions below turn on three axes: what is being withdrawn, when, and under which legal regime.

Form C-AR (the annual report being withdrawn)

C-AR is the direct target of every C-AR-W. It is the substantive Rule 202 annual report carrying updated financials and business information; C-AR-W is a thin cover that points back to a specific C-AR accession and removes it from the active EDGAR record. The two datasets are complementary, not substitutable: C-AR holds the disclosure content, C-AR-W records the unwinding event.

Form C-AR/A (amendment to the annual report)

C-AR/A revises or supplements an existing C-AR while leaving the original on the record. C-AR-W removes the original entirely. Errors are normally corrected via C-AR/A; C-AR-W is reserved for filings that should not have been made or otherwise warrant retraction. Treating the two as equivalent yields wrong conclusions about which disclosure remains effective.

Form C-TR (termination of reporting)

C-TR is the form most often confused with C-AR-W. C-TR is forward-looking: it ends the prospective Rule 202(b) duty to file future C-ARs. C-AR-W is backward-looking: it retracts one specific past C-AR submission. An issuer wanting both effects must file both forms.

Form C-W (withdrawal of the offering)

Form C-W withdraws the underlying Form C offering statement, typically before or during the offering window. C-AR-W operates one stage later in the lifecycle, on the annual report that follows a completed offering. Both are Reg CF withdrawals, but they target different documents and imply very different issuer-status facts; combining the datasets without preserving this distinction is unsafe.

Form C (initial offering statement)

C is the originating Reg CF disclosure document and a logical prerequisite: only issuers that completed a Reg CF offering on Form C ever become subject to the C-AR obligation that C-AR-W withdraws. C is a substantive multi-page disclosure with financial statements; C-AR-W carries essentially no disclosure beyond identification of the prior C-AR.

Form 15 (Exchange Act termination or suspension)

Form 15 ends Section 13(a) or Section 15(d) reporting obligations (10-K, 10-Q, 8-K). It is the Exchange Act analogue of C-TR, not C-AR-W: forward-looking and obligation-ending, not retrospective and submission-retracting. Filer populations are essentially disjoint — Exchange Act registrants versus Reg CF Section 4(a)(6) issuers.

Form RW (Registration Withdrawal Request)

Form RW withdraws a pending Securities Act registration statement (e.g., S-1, S-3) under Rule 477, before effectiveness. Both RW and C-AR-W are short withdrawal covers, but RW targets a public-offering registration in the registered-offering regime, while C-AR-W targets an annual report in an exempt-offering regime. RW filings often signal halted IPOs or shelves; C-AR-W filings are typically routine Reg CF housekeeping.

Form AW (Application Withdrawal)

Form AW withdraws a prior application, most often under the Investment Advisers Act or Investment Company Act. It shares the cover-form mechanic with C-AR-W but operates in the adviser/fund regulatory space rather than crowdfunding annual reporting.

Boundary summary

C-AR-W is uniquely defined by three attributes simultaneously: (1) withdrawal rather than amendment or termination, (2) targeted at a prior Form C-AR annual report rather than an offering statement, registration, or application, and (3) confined to Regulation Crowdfunding under 17 CFR Part 227. C-TR matches on regime but is prospective; C-W matches on mechanism but targets the offering; Form 15 mirrors the obligation-ending purpose in the Exchange Act regime; RW and AW share withdrawal mechanics but apply to unrelated filing classes. No other dataset captures the act of retracting a previously filed C-AR from EDGAR.

Who Uses This Dataset

Form C-AR-W marks the moment a Regulation Crowdfunding issuer withdraws a previously filed annual report on Form C-AR. The dataset is small but functions as a status-change signal, and a narrow set of professionals rely on it for compliance, monitoring, and research workflows.

Reg CF disclosure counsel

Securities attorneys advising small-issuer clients use the dataset as a precedent set when drafting their own withdrawals. They focus on the cover-page structure, the accession number and period of the original C-AR being withdrawn, and the issuer CIK on the metadata file. Output: client memos, withdrawal cover letters, and internal precedent libraries under 17 CFR Part 227.

Compliance officers at funding portals

Portal compliance teams cross-reference issuer CIKs in the dataset against their internal issuer rosters to flag accounts that have pulled their annual report. Withdrawal date and the reference to the original C-AR drive issuer-status tagging on offering pages and notifications to subscribed investors.

Reg CF data vendors and analytics teams

Vendors maintaining commercial Reg CF databases ingest C-AR-W metadata to update fields such as "annual report withdrawn" and "ongoing reporting status," and use the original-C-AR accession reference to preserve filing lineage. Supports issuer timelines and "currently reporting" filters in their APIs.

Forensic accountants and fraud investigators

Investigators treat a withdrawn annual report as a review trigger, especially when paired with auditor changes or terminated offerings. They use the CIK and withdrawal date to build watchlists, then pull the underlying C-AR financials and related-party disclosures to assess restatement or concealment risk. Output: investigative case files and red-flag scoring inputs.

Academic researchers on Reg CF lifecycle

Finance and accounting researchers use the dataset for attrition and disclosure-quality studies. Population-level fields matter most: count of withdrawals, time elapsed between original C-AR and withdrawal, and joins to issuer characteristics from Form C and C-AR. Supports survival analyses and policy work on the ongoing-reporting regime.

Diligence teams at crowdfunding intermediaries

Underwriting analysts screening issuers for follow-on or secondary offerings consult the dataset to confirm whether an applicant has previously withdrawn an annual report. The CIK lookup and original-C-AR reference feed diligence memos that affect onboarding decisions and investor-facing disclosure.

SEC examination and enforcement staff

Regulatory staff monitor issuers exiting ongoing reporting using issuer CIK, the withdrawn report's accession number, and timing relative to the original filing. Records feed sweep exams, enforcement intake screening, and pattern analyses of withdrawals clustered around specific intermediaries or sectors.

EDGAR pipeline engineers

Data engineers building EDGAR ingestion pipelines treat C-AR-W as a low-volume but functionally distinct event type. They use the metadata JSON and XML primary document to define schema mappings and reconciliation logic that flip issuer-status fields in downstream warehouses against the original C-AR.

LLM and RAG developers for Reg CF assistants

Teams building retrieval systems for Regulation Crowdfunding index C-AR-W records alongside Forms C, C-U, C-AR, and C-TR so that questions about an issuer's current reporting status resolve correctly. Used in evaluation corpora and structured tool calls returning issuer-status tags.

Specific Use Cases

Each Form C-AR-W filing is a discrete status-change event for a Regulation Crowdfunding issuer. The use cases below show how the compact records are consumed in practice.

Flipping issuer reporting-status flags in downstream warehouses

Reg CF data vendors and EDGAR pipeline engineers consume each new C-AR-W to update an issuer's "annual report withdrawn" and "currently reporting" fields. The workflow keys on entities[].cik and periodOfReport from metadata.json, joins back to the prior C-AR for the same CIK and fiscal year, and writes a status transition row tied to filedAt. Output: corrected reporting-status flags surfaced in commercial Reg CF APIs and issuer timelines.

Funding-portal account flagging and investor notification

Portal compliance teams ingest the monthly ZIP, match entities[].cik against their internal issuer roster, and trigger an account-level alert when a hit lands. The acceptance timestamp and the <period> element drive the wording of investor-facing disclosure that the prior C-AR is no longer on the active EDGAR record, plus any required notice to subscribed investors of the offering page.

Reconstructing the withdrawn-C-AR linkage for lineage tables

Because no field in primary_doc.xml or metadata.json carries the accession number of the underlying C-AR, analytics teams build a reconstruction job that joins entities[].cik plus periodOfReport against the EDGAR filing history for that issuer. The result is a (C-AR-W accession, original C-AR accession, period) lineage table that feeds disclosure-history pages and powers "show the report this withdrew" navigation in vendor UIs.

Withdrawal-event watchlists for forensic review

Forensic accountants and SEC examination staff treat a C-AR-W as a trigger for case review. They extract issuer CIK, signer name and title from <issuerSignature> and <signaturePersons>, and the elapsed time between periodOfReport and filedAt, then merge the result with auditor-change events and Form C-TR / Form C-W activity for the same issuer. Output: a ranked watchlist that informs sweep-exam selection and investigative file openings.

Precedent corpus for drafting C-AR-W cover filings

Reg CF disclosure counsel use the dataset as a precedent library when preparing a withdrawal for a client. They read primary_doc.xml for signature-block patterns (single issuer signature versus multi-<signaturePerson> blocks with director titles), the <liveTestFlag> and processing flags used in accepted live submissions, and the issuer-name conventions inside <issuerInformation>. Output: model XML, internal drafting checklists, and cover memos cited under 17 CFR 227.202.

Attrition and lifecycle research on Regulation Crowdfunding

Academic researchers studying Reg CF attrition use the population-level statistics of the dataset: counts per year, distribution of periodOfReport values, and the gap between the prior C-AR's filing date and the C-AR-W's filedAt. Joined with Form C-AR, Form C-U, and C-TR data on the same CIKs, the dataset supports survival analyses on the ongoing-reporting regime and policy work on small-issuer compliance burden.

Form-type coverage for Reg CF retrieval assistants

LLM and RAG developers building Regulation Crowdfunding assistants index the C-AR-W records so that questions like "is this issuer's 2019 annual report still on file?" resolve correctly. Each record contributes the issuer name, CIK, and the period of the withdrawn C-AR to the retrieval index, and is wired into structured tool calls that return reporting-status tags alongside results from C, C-U, C-AR, and C-TR.

Dataset Access

Dataset Index JSON API: https://api.sec-api.io/datasets/form-carw-files.json This endpoint returns dataset metadata such as name, description, last updated timestamp, earliest sample date, total record and size counters, covered form types (C-AR-W), container format (ZIP), and file types (XML, JSON). It also returns the full dataset download URL and the list of individual container files with their size, record count, updated timestamp, and per-container download URL. Poll this endpoint to detect which containers changed in the most recent refresh and decide which ones to re-download. No API key is required.

Example
1 {
2 "datasetId": "1f13365b-9ae0-6a6b-acde-c0ee26f79378",
3 "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-carw-files.zip",
4 "name": "Form C-AR-W Files Dataset",
5 "updatedAt": "2026-04-16T08:52:17.000Z",
6 "earliestSampleDate": "2018-04-01",
7 "totalRecords": 12,
8 "totalSize": 17349,
9 "formTypes": ["C-AR-W"],
10 "containerFormat": "ZIP",
11 "fileTypes": ["XML", "JSON"],
12 "containers": [
13 {
14 "downloadUrl": "https://api.sec-api.io/datasets/form-carw-files/2026/2026-03.zip",
15 "key": "2026/2026-03.zip",
16 "size": 4821,
17 "records": 2,
18 "updatedAt": "2026-04-16T08:52:17.000Z"
19 }
20 ]
21 }

Download Entire Dataset: https://api.sec-api.io/datasets/form-carw-files.zip?token=YOUR_API_KEY Downloads the complete Form C-AR-W Files dataset, covering filings from April 2018 to present, as a single ZIP archive. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-carw-files/2026/2026-03.zip?token=YOUR_API_KEY Downloads one individual monthly container ZIP rather than the full dataset, which is useful for incremental syncing of specific time periods. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form C-AR-W, the Regulation Crowdfunding annual-report withdrawal form prescribed under 17 CFR 239.900 and submitted on EDGAR with submission type C-AR-W. It is the procedural cover filing by which an issuer asks EDGAR to withdraw a previously filed Form C-AR annual report.

What does one record in this dataset represent?

One record is a single Form C-AR-W submission accepted by EDGAR, packaged as a per-accession folder named with the digits-only EDGAR accession number. Each folder contains exactly two artifacts: metadata.json (the normalized EDGAR submission header) and primary_doc.xml (the EDGAR-XML form payload bound to the http://www.sec.gov/edgar/formc namespace).

Who is required to file Form C-AR-W?

Only the issuer of the securities files Form C-AR-W. The issuer must have previously sold securities under Section 4(a)(6) of the Securities Act of 1933 (Title III of the JOBS Act), become subject to the ongoing annual reporting obligation under Rule 202 of Regulation Crowdfunding (17 CFR 227.202), and previously submitted at least one Form C-AR that is now being withdrawn. Funding portals and broker-dealers do not file the form.

When is Form C-AR-W filed?

Form C-AR-W is event-driven and discretionary — there is no calendar deadline and no periodic schedule. A filing exists only when the issuer affirmatively decides to withdraw a specific previously submitted Form C-AR, typically in connection with terminated reporting obligations under Rule 202(b), erroneous prior submissions, wind-downs, or concurrent Form C-TR filings.

How does Form C-AR-W differ from Form C-AR/A and Form C-TR?

Form C-AR/A amends or supplements an existing C-AR while leaving the original on the record; Form C-AR-W removes the original entirely. Form C-TR is forward-looking and terminates the prospective duty to file future C-ARs, while Form C-AR-W is backward-looking and retracts one specific past C-AR submission. An issuer that wants both effects must file both Form C-TR and Form C-AR-W.

What time period does the dataset cover?

The dataset covers Form C-AR-W filings accepted by EDGAR from 2018-04-01 to the present. Form C-AR-W has only ever existed as an electronic EDGAR submission since Regulation Crowdfunding became operative in May 2016, and the April 2018 earliest sample date reflects the first wave of withdrawal activity roughly two years after the rule's effectiveness.

What file format is the dataset distributed in?

Records are distributed in monthly ZIP containers organized by EDGAR filing date under the path convention YYYY/YYYY-MM.zip. Each accession folder inside a container holds two files: an XML primary document (primary_doc.xml) and a JSON metadata header (metadata.json).