The Form C-TR-W Files Dataset is a structured collection of every Form C-TR-W submission accepted by EDGAR — the SEC filing that withdraws a previously filed Form C-TR "Termination of Reporting" notice under Regulation Crowdfunding (17 CFR Part 227, implementing Title III of the JOBS Act). Each record represents one withdrawal-of-termination event by a single Reg CF issuer, identified by an 18-digit accession number, and the legal effect of the filing is to reinstate the issuer's ongoing obligation to file annual Form C-AR reports under Rule 202. Filings are made by the Reg CF issuer itself (not the funding portal or intermediary), are EDGAR-only with no paper precursor, and are distributed in monthly ZIP containers carrying XML and JSON file types. Dataset coverage begins August 2018 — the point at which Reg CF issuers had completed enough annual reporting cycles for termination-and-reversal events to begin appearing — and continues to the present.
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:
The dataset packages every accepted Form C-TR-W submission from EDGAR as one record per filing. Form C-TR-W is a procedural retraction form: it carries no offering disclosures, financial statements, risk factors, use-of-proceeds narrative, governance discussion, or exhibit attachments. It is one of the shortest and most narrowly scoped form types EDGAR accepts, containing only filer credentials, the issuer's legal name, and signature blocks attesting to the withdrawal. Every record covers the entire eligible filer population — Reg CF issuers that previously filed a Form C-TR and then chose to rescind it — so the dataset is exhaustive rather than sampled.
The form has been XML-only throughout its existence on EDGAR. There is no ASCII-era predecessor, no HTML migration, and no transition to inline XBRL. The structured XML schema in the EDGAR formc namespace has been stable since the dataset's earliest sample in August 2018, and the form has retained the same minimal anatomy — filer credentials, live/test flags, issuer name, signatures — with no addition of new required disclosures across that period. Records are delivered in month-partitioned ZIP archives; the two file types present are XML (primary_doc.xml) and JSON (metadata.json).
A single record in the Form C-TR-W Files Dataset is one Form C-TR-W submission accepted by EDGAR, identified by its 18-digit accession number. Each record is materialized as a folder named after the dash-stripped accession number (for example, 000177476525000007) inside a month-partitioned ZIP archive. The folder contains exactly two artifacts that together constitute the complete filing: a metadata.json sidecar derived from the EDGAR submission envelope and a primary_doc.xml carrying the structured form body the issuer transmitted. The record unit is therefore a single, self-contained crowdfunding withdrawal-of-termination notice: one issuer, one accession number, one act of retraction.
Form C-TR-W is the withdrawal counterpart to Form C-TR within the family of crowdfunding forms created by Regulation Crowdfunding (Regulation CF), adopted by the Commission under Title III of the Jumpstart Our Business Startups (JOBS) Act and codified at 17 CFR Part 227 under the Section 4(a)(6) exemption of the Securities Act of 1933. Form C-TR is the notice an issuer files under Rule 202(b) of Regulation CF to terminate its ongoing reporting obligation. Form C-TR-W rescinds that termination notice, with the legal effect of reinstating the issuer's continuing duty to file the annual report on Form C-AR until eligibility for termination is satisfied by another route (acquisition, registration under the Exchange Act, dissolution, or completion of the requisite annual-report filings).
The filing is procedural rather than substantive. It carries no offering disclosures, no financial statements, no risk factors, no use-of-proceeds narrative, no governance discussion, and no exhibit attachments. It is one of the shortest and most narrowly scoped form types EDGAR accepts: filer credentials, the issuer's legal name, and signature blocks attesting to the withdrawal. The form is filed exclusively as an XML document conforming to the EDGAR formc namespace (http://www.sec.gov/edgar/formc); there is no HTML rendition, no separate cover page, no exhibits, and no XBRL/iXBRL payload. The structured XML and the EDGAR submission header together comprise the entire filing.
Each accession-number folder contains two files:
metadata.json — a JSON sidecar describing the EDGAR submission envelope: form type, accession number, acceptance timestamp, filer/issuer entity attributes, document inventory, and constructed URLs back to EDGAR.primary_doc.xml — the EDGAR-accepted XML submission containing the structured form body: filer credentials, live/test flags, the issuer's legal name, and signature blocks.No HTML, PDF, image, or auxiliary files appear in the record. Image files are excluded by dataset policy across the form family in any case, and Form C-TR-W has historically not carried any such attachments. The two file-types present in the dataset are XML and JSON, matching this two-file-per-record shape. Payloads are very small; a primary XML is on the order of 1 KB.
metadata.json sidecarThe sidecar exposes the EDGAR submission envelope as a flat JSON object with a small set of nested arrays:
formType — the literal C-TR-W.accessionNo — canonical dashed accession number (for example, 0001774765-25-000007).filedAt — ISO 8601 timestamp with timezone offset reflecting EDGAR acceptance time.description — human-readable label, typically Form C-TR-W - [Termination of Reporting Withdrawal](https://www.sec.gov/resources-small-businesses/regulation-crowdfunding-guidance-issuers).id — opaque hex record identifier assigned during dataset packaging.linkToFilingDetails — direct URL to the primary XML on sec.gov/Archives/edgar/....linkToTxt — URL to the consolidated .txt submission bundle on EDGAR.linkToHtml — URL to the -index.htm filing index page on EDGAR.linkToXbrl — empty string. Form C-TR-W carries no XBRL payload.documentFormatFiles[] — array describing each document in the EDGAR submission. Each entry carries sequence, size, documentUrl, type, and (for the txt bundle) a description. Sequence "1" is the primary C-TR-W XML; a second entry, with whitespace values for sequence and type, represents the consolidated submission text file.dataFiles — empty array. Form C-TR-W has no XBRL, R-files, or other auxiliary data files.seriesAndClassesContractsInformation — empty array. Series/class metadata is not applicable to crowdfunding withdrawals.entities[] — array of one entity object per registrant on the filing (almost always one). Each entity exposes:
cik — issuer CIK as an unpadded integer string.companyName — issuer legal name with the EDGAR role suffix appended in parentheses, typically (Filer).type — the form type as recorded against the entity, C-TR-W.act — Securities Act designation, typically 33.fileNo — SEC file number, e.g., 020-34967 for Regulation CF registrants.filmNo — EDGAR film number assigned at acceptance.stateOfIncorporation — two-letter state or jurisdiction code.fiscalYearEnd — four-digit MMDD.Several issuer attributes that are not encoded in the structured XML body — state of incorporation, fiscal year end, file number, film number — are present only in the sidecar because they originate from the EDGAR header rather than the form schema. Consumers extracting issuer attributes therefore depend on the JSON sidecar in addition to (or instead of) the XML.
primary_doc.xml form bodyThe XML root is <edgarSubmission xmlns="http://www.sec.gov/edgar/formc">. The schema is shared across the Regulation CF form family (C, C/A, C-AR, C-AR/A, C-TR, C-TR-W, C-U, C-U/A, C-W); for Form C-TR-W only a small subset of fields is populated. The document is divided into two top-level branches: headerData and formData.
headerDatasubmissionType — the literal C-TR-W.filerInfo/filer/filerCredentials/
filerCik — zero-padded ten-digit CIK (for example, 0001774765).filerCcc — the issuer's CIK Confirmation Code; on EDGAR-public copies this is masked as XXXXXXXX and never disclosed.filerInfo/liveTestFlag — LIVE for production submissions, TEST for test filings (production records dominate).filerInfo/flags/ — three boolean string flags: confirmingCopyFlag, returnCopyFlag, overrideInternetFlag.formDataissuerInformation/issuerInfo/nameOfIssuer — the issuer's legal name. This is the only issuer-identifying field encoded in the structured form body. There is no street address, jurisdiction, contact information, SIC code, CIK echo, or pointer back to the specific Form C-TR being withdrawn; that linkage is implicit in form-type semantics combined with the issuer's CIK and prior filing history.signatureInfo/
issuerSignature/ — the issuer's attestation block, with three child elements: issuer (the entity's name as signer), issuerSignature (the printed name of the natural person executing on behalf of the issuer), and issuerTitle (the executing person's role, e.g., CEO).signaturePersons/signaturePerson[] — one or more individual signatory blocks, each with personSignature (printed name), personTitle (role), and signatureDate formatted as MM-DD-YYYY.Reduced to its essence, the form body declares: who is filing (CIK plus issuer name), confirmation that the submission is live, the issuer's legal name reasserted, and the signatures attesting to the withdrawal. There is no narrative section, no tabular section, no financial section, no exhibit list, and no incorporation by reference.
Each record includes the complete EDGAR submission envelope (via metadata.json) and the complete structured form body (via primary_doc.xml). Every field the issuer transmitted in the form, every signature block, every header flag, and every entity-level attribute EDGAR records on the filing is present. URLs back to the original EDGAR documents — primary XML, consolidated .txt bundle, and -index.htm index page — are reproduced in the sidecar for traceability back to the source on sec.gov.
Image files are excluded as a matter of dataset policy across the crowdfunding form family, though Form C-TR-W does not in practice carry image attachments. The CIK Confirmation Code is masked by EDGAR itself and therefore appears only as XXXXXXXX. There is no XBRL payload to exclude — Form C-TR-W has never carried structured financial tagging — so linkToXbrl is empty and dataFiles is an empty array on every record. The previously filed Form C-TR being retracted is not embedded or cross-referenced inside the C-TR-W record; locating it requires looking back at the same issuer's prior filings on EDGAR by CIK. Likewise, the subsequent Form C-AR filings that the withdrawal reinstates are not present in the record and must be discovered separately from the issuer's filing history.
Form C-TR-W has been accepted by EDGAR since the operational rollout of Regulation CF's reporting-termination machinery, and the dataset's coverage starts in August 2018. The structured XML schema in the formc namespace has been stable across that period, and the form has retained the same minimal anatomy — filer credentials, live/test flags, issuer name, signatures — with no addition of new required disclosures. Because the form carries no offering, financial, or governance content, Regulation CF rulemaking activity (such as the 2020 amendments raising the offering ceiling to USD 5 million and adjusting investor eligibility) did not alter the C-TR-W body. The dataset's content shape is therefore effectively uniform from 2018 to the present.
A handful of practical considerations matter for downstream extraction:
documentFormatFiles array in metadata.json contains a second entry whose sequence and type values are whitespace strings rather than meaningful tokens; this entry represents the consolidated .txt submission bundle and parsers should tolerate the whitespace placeholders.companyName field in the entity object carries an EDGAR role suffix in parentheses (typically (Filer)) appended to the legal name; consumers normalizing issuer names usually strip this suffix.MM-DD-YYYY, not ISO 8601, and should be normalized at parse time if downstream systems expect a standard date format.Each record in the dataset is a single Form C-TR-W submission filed on EDGAR by a Regulation Crowdfunding issuer to withdraw a previously filed Form C-TR. The legal filer is always the issuer itself, identified on EDGAR by its CIK and company name, not the funding portal or broker-dealer that hosted the original offering and not any investor.
The eligible filer population is narrow:
C-TR-W is a strict subset of the C-TR filer population: only an issuer that previously filed a C-TR can file a C-TR-W. Foreign issuers, investment companies, BDCs, blank check companies, and Exchange Act reporting companies are excluded from Reg CF under Rule 100(b) and so do not appear here. Funding portals and broker-dealer intermediaries file under separate regimes (Form Funding Portal and the intermediary Form C series) and never file C-TR-W.
The form is event-driven and entirely voluntary. There is no statutory or rule-based deadline; the trigger is the issuer's own decision to rescind a prior C-TR. Typical triggers:
The filing is short and operative: issuer identifying information (CIK, name, address), a reference to the C-TR being withdrawn, and an authorized officer's signature. No fee, no audit, and no narrative disclosure are required.
The legal effect on acceptance is that the prior Form C-TR is treated as withdrawn and the Rule 202 annual report obligation is reinstated. Any Form C-AR that would otherwise have been due is again required, generally within 120 days after fiscal year-end under standard Rule 202 timing.
Because Reg CF only took effect on May 16, 2016, and termination filings did not accumulate until issuers had completed at least one annual cycle, the dataset's earliest C-TR-W records appear in August 2018. All Form C-series filings are EDGAR-only; there is no paper precursor.
Form C-TR-W is a withdrawal of a withdrawal: it rescinds a previously filed Form C-TR and restores the issuer's Regulation Crowdfunding annual reporting obligation under Rule 202. That narrow function places it next to two clusters of forms — the Reg CF lifecycle filings it operates within, and the broader family of SEC withdrawal and termination-of-reporting mechanisms.
Form C-TR (Termination of Reporting under Reg CF). The direct counterpart C-TR-W is built to retract. C-TR ends an issuer's Rule 202 annual reporting obligation once a statutory exit condition is met (e.g., at least one Form C-AR filed plus fewer than 300 holders of record, or repurchase of all crowdfunded securities). C-TR-W shares C-TR's filer population, regulatory regime, and identifying metadata, but produces the opposite legal effect: C-TR ends ongoing disclosure; C-TR-W reinstates it. Any C-TR-W record is meaningful only when joined to the specific C-TR accession it reverses.
Form C, C-U, C-AR, C-AR-W (Reg CF offering and annual reporting forms). These carry the substantive Reg CF disclosure: Form C (offering statement), Form C-U (offering progress update), C-AR (annual report), and Form C-AR-W (withdrawal of an annual report). C-TR-W contains none of their content — no financials, offering terms, or narrative — only filer identification, withdrawal date, and a reference to the prior C-TR. Critically, C-AR-W withdraws a single annual report; C-TR-W withdraws the termination of the entire annual reporting duty. C-TR-W is best treated as a reporting-status flag layered on top of the C and C-AR datasets. See also Form C/A, Form C-AR/A, Form C-U/A, and Form C-W within the same family.
Form RW (Registration Statement Withdrawal, Rule 477). Both are short procedural withdrawal forms, but they operate in different regimes and on different objects. RW pulls a pending Securities Act registration statement (S-1, S-3, etc.) before effectiveness; C-TR-W rescinds an already-effective Reg CF termination notice for periodic reporting. RW unwinds an offering registration; C-TR-W reinstates a recurring disclosure obligation. This is the Registration Statement Withdrawal mechanism in formal terms.
Form AW (Application Withdrawal). Like C-TR-W, AW is a minimal-content procedural retraction. The object differs: AW pulls back an application still awaiting SEC action (e.g., confidential treatment or exemptive relief), whereas C-TR-W rescinds a self-effective filing and affirmatively restores ongoing reporting duties.
Form 15, Form 15-12B, Form 15-12G (Exchange Act termination/suspension of reporting). Form 15 is the Exchange Act analog of C-TR, not of C-TR-W: it terminates or suspends Section 13(a)/15(d) duties (10-K, 10-Q, 8-K). The Exchange Act regime has no single named "withdrawal of Form 15" — reinstatement happens via a new registration statement or expiration of a suspension. C-TR-W is therefore distinctive in providing a clean, regime-specific reversal form that no Exchange Act analog matches.
Form 1-Z (Reg A Tier 2 termination of reporting). 1-Z is the Reg A counterpart to C-TR, ending Form 1-K and Form 1-SA obligations. Both Reg A and Reg CF arose from the JOBS Act and use compact termination notices. Two differences isolate C-TR-W: 1-Z terminates rather than reverses a termination, and it sits under Reg A Tier 2 framework rather than Reg CF's Rule 202. Reg A has no named "1-Z-W," again underscoring C-TR-W's unusual role.
What makes Form C-TR-W distinct is the intersection of three properties no other SEC form combines: it is confined to Reg CF issuers, it acts solely on a prior C-TR, and it restores rather than ends a periodic reporting obligation. It is not a substitute for any disclosure dataset and cannot answer questions about what an issuer raised, disclosed, or owed. Its value is as a status-timeline complement to the C, C-U, C-AR, C-AR-W, and especially C-TR datasets, enabling precise identification of which Reg CF issuers remain subject to annual reporting at any point in time.
The user base for the Form C-TR-W Files Dataset is small and concentrated in roles that track Reg CF reporting status, advise small issuers, or maintain derived datasets that depend on accurate issuer state.
In-house compliance officers and outsourced compliance providers use the record to confirm a withdrawal posted correctly and to restart the annual reporting clock. Key fields: issuer CIK, company name, filed date, signature date, and the cross-reference to the original C-TR. Workflow: rebuilding compliance calendars for reinstated C-AR deadlines and maintaining a documentary trail showing the issuer is a current, not terminated, reporter.
Outside counsel drafting a C-TR-W or opining on whether an issuer remains subject to Reg CF reporting use the dataset as precedent. Because the form is rare, attorneys mine prior filings for narrative phrasing, signatory blocks, and how the link back to the original C-TR is structured. The dataset supports drafting, opinion letters, and enforcement-defense work where reinstatement timing is material.
Compliance staff at registered funding portals and broker-dealer intermediaries that hosted the original offering rely on C-TR-W to keep platform-side issuer profiles accurate. They use issuer CIK, company name, and withdrawal date to update post-offering disclosure pages, restore "active reporter" tags, and feed internal monitoring tools that flag status changes among previously hosted issuers.
Data engineering teams at filing-monitoring and market-data vendors ingest C-TR-W as part of broader EDGAR pipelines. They consume structured XML metadata, accession number, CIK, form type, and filed date to maintain a derived "current Reg CF reporting status" field and to fire alerts when a terminated issuer reactivates.
Analysts maintaining Reg CF league tables, cohort statistics, and lifecycle datasets use C-TR-W to correct for issuers re-entering the reporting universe. They focus on issuer CIK, withdrawal date, and the implied set of future C-AR filings to recompute active-issuer counts and adjust attrition and survivorship metrics for non-linear reporting trajectories.
Researchers studying the JOBS Act Title III experiment use C-TR-W to characterize rare reversal events. They focus on time elapsed between the C-TR and its withdrawal, issuer characteristics via CIK linkage, and any narrative rationale. The dataset supports empirical work on voluntary disclosure behavior and comment-letter input on Reg CF policy reviews.
Product teams behind investor-facing Reg CF research tools use C-TR-W so that an issuer's profile reflects "annual reporting reinstated" rather than "terminated." Issuer CIK, company name, and withdrawal date drive status corrections, holder alerts, and secondary-market diligence flags.
Examiners and surveillance analysts use C-TR-W as supporting evidence when reviewing whether issuers and intermediaries correctly characterize Reg CF reporting status. They cross-check signature date, CIK, and the link to the prior C-TR against subsequent C-AR filings to confirm consistency between claimed and actual EDGAR state.
Engineers building retrieval systems and assistants for Reg CF filings use C-TR-W to give their indexes coverage of the full form family. Structured metadata, document text, and the C-TR cross-reference let models answer reporting-status questions correctly and avoid misclassifying reactivated issuers as terminated.
Form C-TR-W records are narrow but operationally important: each one flips a Reg CF issuer back from "terminated" to "active reporter." The use cases below all flow from that status-flip semantics and from the small set of fields the record actually carries (issuer CIK, issuer legal name, signature dates, live/test flag, and the implicit pointer to a prior C-TR under the same CIK).
Reinstating Form C-AR deadlines on issuer compliance calendars. Compliance teams ingest each new C-TR-W, read entities[].cik, nameOfIssuer, and the signatureDate from the signature block, then reopen an annual C-AR cadence for that CIK starting from the issuer's fiscalYearEnd in the metadata sidecar. The output is a corrected internal calendar entry and a tickler for the next C-AR filing window.
Maintaining a derived "current Reg CF reporting status" field in EDGAR pipelines. Data engineers join C-TR, C-TR-W, and C-AR streams by CIK and use the C-TR-W filedAt timestamp to flip a per-issuer status flag from terminated back to active. The flag drives downstream alerts ("previously terminated Reg CF issuer just reactivated") and prevents stale "terminated" labels in vendor feeds and league tables.
Reconstructing the C-TR to C-TR-W reversal pair. Because the C-TR-W body does not carry a cross-reference accession, researchers and counsel pull every prior C-TR for the same CIK from EDGAR, pick the most recent one preceding the C-TR-W signatureDate, and treat that pair as one reversal event. This produces a clean dataset of reversal events with elapsed-time-to-withdrawal, used in policy research on voluntary disclosure behavior and in enforcement-defense timelines.
Auditing intermediary and platform "active reporter" tags. Funding portals and broker-dealer compliance teams cross-walk their hosted-issuer rosters against the C-TR-W stream by CIK, and use the withdrawal signatureDate to restore "active reporter" badges, re-enable post-offering disclosure pages, and re-subscribe the issuer to internal C-AR-due monitoring.
Drafting precedent for new C-TR-W filings. Securities counsel preparing a withdrawal mine the primary_doc.xml bodies of historical C-TR-W records for signatory-block structure, issuerTitle conventions, and MM-DD-YYYY date formatting. Because the form is rare, the dataset functions as a near-complete precedent corpus for drafting and quality-checking a new submission before transmission.
Adjusting Reg CF cohort and attrition statistics. Market-data analysts use C-TR-W records to remove issuers from "terminated reporter" cohorts and add them back to active-issuer counts as of the withdrawal date, recomputing year-over-year attrition and survivorship curves so that non-linear reporting trajectories (terminate, then reinstate) are not double-counted as exits.
Regulatory and SRO surveillance of reporting-status consistency. Examiners pull C-TR-W records by CIK and verify that subsequent C-AR (or C-AR/A) filings actually appear on EDGAR within the expected window after the withdrawal signatureDate. Mismatches — a C-TR-W with no follow-on C-AR — become exam findings or follow-up items for the issuer and any associated intermediary.
The Form C-TR-W Files Dataset is available through three access methods: a metadata index endpoint, a full archive download, and per-container downloads. All filings since August 2018 are packaged in monthly ZIP containers.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-ctrw-files.json
This endpoint returns dataset-level metadata and the complete list of container files. The response includes the dataset name, description, last update timestamp, earliest sample date, total record count, total dataset size in bytes, form types covered, container format, included file types, and the full dataset download URL. Each entry in the containers array exposes a per-container downloadUrl, storage key, byte size, records count, and updatedAt timestamp, which lets you poll daily and pull only the containers that changed in the most recent refresh run. This endpoint does not require an API key.
1
curl https://api.sec-api.io/datasets/form-ctrw-files.json
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a56-9498-153fa5c92914",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-ctrw-files.zip",
4
"name": "Form C-TR-W Files Dataset",
5
"updatedAt": "2026-04-16T08:46:29.184Z",
6
"earliestSampleDate": "2018-08-01",
7
"totalRecords": 25,
8
"totalSize": 35358,
9
"formTypes": ["C-TR-W"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["XML", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-ctrw-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 4218,
17
"records": 3,
18
"updatedAt": "2026-04-16T08:46:29.184Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-ctrw-files.zip?token=YOUR_API_KEY
Downloads every container in a single archive containing all Form C-TR-W filings from August 2018 to the present. This endpoint requires an API key.
1
curl -o form-ctrw-files.zip "https://api.sec-api.io/datasets/form-ctrw-files.zip?token=YOUR_API_KEY"
Download Single Container: https://api.sec-api.io/datasets/form-ctrw-files/2026/2026-03.zip?token=YOUR_API_KEY
Use a per-container URL from the index response to fetch a single monthly archive instead of the full dataset. This is the recommended pattern for incremental updates. This endpoint requires an API key.
1
curl -o 2026-03.zip "https://api.sec-api.io/datasets/form-ctrw-files/2026/2026-03.zip?token=YOUR_API_KEY"
The dataset covers Form C-TR-W, the SEC filing that withdraws a previously filed Form C-TR "Termination of Reporting" notice under Regulation Crowdfunding (17 CFR Part 227). Filing it rescinds the prior termination and reinstates the issuer's ongoing duty to file annual reports on Form C-AR under Rule 202.
One record represents a single Form C-TR-W submission accepted by EDGAR, identified by an 18-digit accession number. Each record is a folder containing exactly two files — primary_doc.xml (the structured form body) and metadata.json (the EDGAR submission envelope) — for one issuer's act of withdrawing one prior Form C-TR.
Only the Reg CF issuer itself files C-TR-W, and only if it previously filed a Form C-TR. Funding portals, broker-dealer intermediaries, foreign issuers, investment companies, BDCs, blank check companies, and Exchange Act reporting companies do not file C-TR-W. The form is voluntary and event-driven; there is no statutory deadline.
The dataset's earliest sample is August 2018 and coverage continues to the present. Reg CF only took effect on May 16, 2016, and termination filings did not begin to accumulate until issuers had completed at least one annual reporting cycle, which is why the first C-TR-W records appear in mid-2018.
Records are delivered in monthly ZIP containers. Inside each container, every record is a folder named after the dash-stripped accession number containing two files: primary_doc.xml (XML conforming to the EDGAR formc namespace) and metadata.json (a flat JSON sidecar of the submission envelope). No HTML, PDF, image, or XBRL files are present.
Form C-TR ends a Reg CF issuer's Rule 202 annual reporting obligation; Form C-TR-W rescinds a prior C-TR and reinstates that obligation. The two datasets share the same filer population and metadata shape but produce opposite legal effects, and any C-TR-W is meaningful only when joined to the specific C-TR accession it reverses (a linkage the C-TR-W body does not carry, so it must be reconstructed by CIK and date).
The C-TR-W structured form does not carry a cross-reference accession number to the prior C-TR. To reconstruct the pair, look up every prior Form C-TR filed under the same CIK on EDGAR and select the most recent one preceding the C-TR-W's signatureDate. That pair represents one termination-and-reversal event.