Insights
How to Find De-SPAC Closing Dates
Alphanume Team · May 15, 2026
Sourcing merger completion dates from proxies and 8-Ks — the anchor for every subsequent lock-up and warrant calendar.
The de-SPAC closing date is the anchor for everything downstream — lock-up expirations, warrant exercisability, redemption settlements, post-merger reporting cycles. Getting this date wrong, by even a few days, corrupts every event-window calculation that follows. Getting it right is straightforward if you know which filing to read.
The canonical source
The closing of a SPAC merger is disclosed in an 8-K filed within four business days under Item 2.01 ("Completion of Acquisition or Disposition of Assets"). The exact closing date is in the first paragraph of the body, typically in language like "On [Date], [Company] completed its previously announced business combination with [Target] pursuant to the Business Combination Agreement dated [Date]."
This 8-K is the canonical source. Every other reference — press releases, news coverage, third-party trackers — derives from it.
The preceding filings
Before the closing 8-K, several other filings reference projected or expected closing dates:
- DEFM14A (definitive proxy statement). Includes the merger agreement and discusses expected closing timing, but the actual date depends on the shareholder vote and other closing conditions.
- S-4 registration statement. Filed by the SPAC to register the securities issued in the merger. Often refers to expected closing windows.
- Pre-closing 8-Ks. May announce satisfaction of specific closing conditions (regulatory approvals, shareholder vote results) without announcing the closing itself.
The "shareholder vote" 8-K — typically filed under Item 5.07 ("Submission of Matters to a Vote of Security Holders") within four business days of the SPAC's special meeting — is often the most useful pre-close marker. The merger typically closes within days of a successful vote.
Distinguishing closing from announcement
SPAC mergers generate multiple announcement-style filings, and confusing them produces wrong dates:
| Event | Filing | Item |
|---|---|---|
| Merger agreement signed | 8-K | 1.01 |
| Proxy filed | PREM14A / DEFM14A | — |
| Vote held | 8-K | 5.07 |
| Merger closed | 8-K | 2.01 |
| Ticker change | 8-K | 5.03 |
The closing date for purposes of lock-up calculations is the Item 2.01 closing — not the announcement, not the vote, and not the ticker change (which often lags closing by one or two business days).
Edge cases
Several scenarios complicate the closing-date extraction:
- Two-step closings. Some mergers close in tranches — for example, a partial closing followed by a final closing weeks later. Read the agreement to determine which closing triggers lock-up periods.
- Reverse-merger structures with non-SPAC counterparties. A small-cap public company occasionally merges with a SPAC subsidiary in a structure that resembles a de-SPAC but is filed differently. Item 2.01 still applies.
- Cross-border mergers. Foreign private issuers file under different schedules (20-F, 6-K). The closing announcement is in a 6-K.
- Delisted SPACs. Some SPACs miss their deadline and liquidate, returning trust to shareholders. The relevant 8-K is filed under Item 8.01 or 1.02.
Programmatic approach
For systematic monitoring:
- Maintain a list of all currently-public SPACs (CIK-keyed).
- Subscribe to Item 2.01 8-Ks across that list.
- For each filing, extract the closing date from the body — the canonical phrasing is consistent enough that regex or LLM-based extraction works.
- Cross-check by reading the subsequent 10-Q or 10-K filed by the merged company, which typically references the closing date in its business description.
Why this matters
Every subsequent event calculation depends on the closing date:
- Lock-up expiration dates (typically expressed as "180 days after closing")
- Warrant exercisability dates (typically "30 days after closing")
- Earnings-restated S-1 / S-4 registration effectiveness windows
- PIPE resale registration deadlines (typically "30 days after closing")
Off-by-one or off-by-week errors in the closing date cascade through all of these.
Related reading
What is a de-SPAC; SPAC lock-up expiration; building a lock-up expiration calendar.
Where Alphanume fits
Alphanume's Dilution Events dataset tracks SPAC closings as a normalized event with the exact closing date sourced from the Item 2.01 8-K, and links each closing to the downstream lock-up and warrant calendar entries.