# The Company Trigger-Event Reference: Anchor Date, Proof, and Window

*For a raise, deal, debt, restructuring, cyber, or WARN event, set the legal anchor date, cite the earliest record, and date a window another rep would match.*

- Canonical URL: https://www.refolk.ai/guides/company-trigger-event-reference-3
- Pillar: Sales and go-to-market
- Format: Reference
- Published: 2026-11-19
- Last reviewed: 2026-11-19
- Reading time: 20 min
- Keywords: sales trigger events list with timing, how long after funding round to reach out, when to contact a company after an acquisition, trigger event outreach window, company buying signals what they mean, signal decay outbound by trigger type

## Key takeaways

- A Form D is due 15 calendar days after the first sale, which is the date the first investor is irrevocably committed, so the first-sale date is the anchor for a private raise, not the press release.
- In one vendor sample, 186 of 197 raises of $5m or more had no news coverage, so a funding window counted from the announcement cannot be calculated for roughly 94% of them.
- Published averages from deal announcement to close run from about 53 days to 264 days, so only the close date gives an acquisition window two reps can reproduce.
- Between signing and close the parties remain independent competitors, so nothing about the target's vendor choices opens until the Item 2.01 close filing exists.
- A WARN notice must come at least 60 calendar days before the event, so the anchor is the separation date stated in the notice, not the date the notice was posted.
- In Refolk's index, 937 people in the US and 353 in the UK hold integration-lead titles, so the UK post-close buyer pool is 2.65x smaller and more concentrated.

This reference is for founders, account executives, SDR leads, and partnerships teams who spot a company event in their feed and have to decide whether to reach out now, wait, or drop it. For each company-level trigger, it gives you the legal anchor date behind the headline, the earliest public record that shows it, what the event proves and how it can mislead, and an outreach window with a dated open, peak, and close. It covers company events only. Person moves, hiring, and renewals each have their own reference, listed at the end.

## Why do published trigger windows contradict each other?

Published windows contradict each other because each one starts the clock on a different date, and most never say which date that is. A funding window of "14 days from the signal" and one of "0 to 180 days from the close" are not competing advice. They measure from different starting points.

Here is how the funding windows line up once you write down the anchor each source uses:

| Source | Window | Anchor |
|---|---|---|
| Lusha | 14 days | Signal fired |
| Spear | Within 5 days | Trigger |
| salestarget.ai | Weeks 1 to 3 | Announcement |
| Origami | 45 to 90 days | Announcement |
| SalesOne | 0 to 180 days | Close date |

Acquisitions are worse. The usual advice counts from the announcement, but published averages from announcement to close vary too much for that to work:

| Source | Sample | Announcement to close |
|---|---|---|
| KPMG | 682 deals, 2012 to 2024 | 187 days |
| Wall Street Horizon | Coverage universe, 2016 to 2019 | ~53 days |
| Wall Street Horizon | Coverage universe, 2020 to 2024 | ~150 days |
| Ideals | Virtual data room deals, single year | 264 days |
| DAMITT | Significant US investigations, single year | 12.3 months |

The longest average is roughly 7x the shortest. A window counted from the announcement therefore depends on which year and which dataset you trust. Two reps reading the same deal would set different dates.

The announcement anchor fails for raises too, because most raises are never announced.

**186 of 197 - Raises of $5m or more with no news coverage, in one vendor sample**

That is about 94% of first filings sampled between 1 September and 21 October, so an announcement-based window cannot be calculated for most raises.

So this reference sets the anchor first, then the window. The anchor tells you what actually happened. The window is a fixed offset from it.

## Which date starts the clock?

The clock starts on the legal anchor, and it is almost never the date of the headline. A **legal anchor** is the date when a legal commitment or obligation took effect, as recorded in a public filing.

There are five anchors you will use:

- **First sale (private raises).** This is the date the first investor is irrevocably contractually committed to invest. The Form D is due 15 calendar days after it. If day 15 falls on a weekend or holiday, the deadline moves to the next business day. The anchor can therefore be up to 15 days earlier than the filing date, and weeks earlier than any press story.
- **Signing and close (acquisitions).** Signing is when the agreement is executed. Close is when ownership actually changes. The target's window depends on close.
- **Agreement date (debt facilities and major contracts).** This is the date of the material agreement reported under 8-K Item 1.01, which is due within 4 business days.
- **Materiality determination (cyber incidents).** This is the date management concludes an incident is material. It is not the date the incident was discovered. Item 1.05 is due within four business days after this determination.
- **Separation date (WARN layoffs and site closures).** This is the date stated in the notice. The notice itself must be given at least 60 calendar days before it.

Acquisitions have the most stages, and the stage you are in decides whether anything is open at all:

#### Acquisition stages and where the target's window opens

1. **Signing** - Agreement executed; 8-K Item 1.01 or a Rule 425 filing makes it public
2. **HSR filing** - Both parties file their premerger notification reports
3. **Waiting period** - Usually 30 calendar days, or 15 for all-cash tender offers; a second request extends it to 30 days after substantial compliance
4. **Close** - 8-K Item 2.01 confirms it; integration begins and the target's window opens

*Between signing and close the parties remain independent competitors, so the target's window opens at close and not at the announcement.*

> **Rule:** Write the anchor before the window
>
> Set no window until one anchor date is written down, along with the filing it came from. If you cannot name the filing, you are acting on a rumour, not a trigger.

## How is the outreach window set from the anchor?

Every window in this reference is a fixed offset from the anchor, set by stage. Two reps holding the same filing will therefore set the same three dates. **Open** is the first day outreach is allowed. **Peak** is the stretch where it should be concentrated. **Close** is the day the event stops justifying a message.

The research on timing is thin, and you should know that before you trust any offset. No independent measurement of reply rates by days since a trigger has been published. The figures that exist come from vendors. One vendor reports 4.8% conversion within 48 hours of LinkedIn activity and 1.5% after two weeks. It also gives a funding "half-life" of 3 to 7 days, with no published method. On the other side, practitioners describe a crowding effect: "Right after a funding round, every SDR alive is emailing that company. So sometimes I wait 60 to 90 days." One source says to respond within 48 hours of discovering a trigger. Another says not to prospect immediately after funding announcements.

Both pieces of advice are right in different situations, and the difference is whether there is a crowd. An unannounced raise has no crowd, so speed pays. An announced raise has one, so waiting pays. That is how the table below resolves the disagreement.

| Stage | Open | Peak | Close |
|---|---|---|---|
| Raise, unannounced | Day you find the Form D | Within 48 hours, until any announcement | First sale + 180 days |
| Raise, announced | First sale + 60 days | First sale + 60 to 90 days | First sale + 180 days |
| Deal signed, target | Not open | Not open | Re-check at close |
| Deal closed, target | Close date | Close + 0 to 90 days | Close + 180 days |
| 8-K event (1.01, 2.05, 1.05) | 8-K filing date | Anchor + 0 to 90 days | Anchor + 180 days |
| WARN notice | Notice posting date | Posting to separation date | Separation date |

> **Note:** These offsets are a convention, not a measurement
>
> The 60, 90, and 180 day offsets come from published practitioner ranges, not from measured reply data, because no such data has been published. Their value is that everyone applies them the same way. If your own replies by days since the anchor disagree, change the offsets for the whole team at once.

Two questions decide which row of the table you are in. The first is whether you hold a legal record. The second is whether the event has been widely reported.

#### Act now, wait, or verify

Horizontal axis runs from Headline only to Legal record in hand. Vertical axis runs from Quiet, unreported to Crowded, widely reported.

| Quadrant | What it means |
| --- | --- |
| Crowded, unverified | Find the filing before anything else; do not join the pile on a headline |
| Crowded, verified | Wait for the peak, 60 to 90 days after the anchor |
| Quiet, unverified | Hold; check the press, state notices, and investor posts |
| Quiet, verified | Reach out within 48 hours of discovery |

*A verified trigger that nobody has reported is the only quadrant where moving within 48 hours clearly pays.*

## Capital and contract events: anchor, proof, window

For capital and contract events, the anchor is either the first sale on a Form D or the agreement date on an 8-K Item 1.01. In both cases the filing shows a commitment and nothing about how the money will be spent.

| Event | Anchor | Earliest record | Proves |
|---|---|---|---|
| Private raise, Form D filed | First sale | Form D, up to 15 days after | Money committed |
| Announced raise, no Form D | Stated close (proxy) | Press, blue-sky notice, investor posts | A claimed raise |
| Debt facility | Agreement date | 8-K Item 1.01, 4 business days | Borrowing capacity |
| Major contract or licence | Agreement date | 8-K Item 1.01, 4 business days | A material agreement |
| Grant | None for this cadence | Varies | Not a round |

### Private raise with a Form D

- **Proves:** at least one investor was irrevocably committed on the first-sale date, for the amount sold.
- **Does not prove:** the stage, the investors, or that the round is finished. A Form D never states a stage or names an investor.
- **How it lies:** an amendment, a pooled fund, or a Form D filed before any sale can all look like a new raise. All three are covered in the failure section.
- **Coverage bias:** Form Ds skew toward larger raises. Firms that cannot "fly under the radar" are more likely to file, so early-stage biotech and tech raises are under-represented. If you find no filing for a small early-stage company, that tells you very little.

### Announced raise with no Form D

Non-filing is common, and it does not mean the raise is false. Filing is not a condition of the exemption, and some issuers are casual about it. One academic paper found that 31.5% of VC-backed firms never file a Form D, and that Form Ds are filed for only 75% of rounds on average. If the announcement gives a close date, use it as a proxy anchor and label the record "proxy". If it does not, use the announcement date. One vendor says press coverage typically appears 4 to 6 weeks after a round closes, but it publishes no method, so do not use that to back-calculate a first sale.

### Debt facility or major contract (Item 1.01)

- **Proves:** the company entered a material agreement, such as a credit facility, an acquisition agreement, or a major licensing deal.
- **Does not prove:** that the facility has been drawn, or that the money has a spending plan you can sell into.
- **How it lies:** an Item 1.01 that is actually an acquisition agreement belongs in the acquisition rows. Reclassify it, or you will contact a target that is frozen.

### Grant

A grant is not a round. At least one ranking page puts "Funding round or grant" in a single row, which mixes non-dilutive money with equity. Check the security type and the issuer before a grant enters your funding cadence.

## Acquisition events: anchor, proof, window

For the company being acquired, the anchor is the close, not the signing. Between signing and close the parties remain independent competitors under gun-jumping law, which bars the merging parties from acting as one before close. The target's vendor decisions are effectively frozen until then.

The companies say so in their own filings. In an employee FAQ filed under Rule 425, Equity Residential wrote that it does "not expect any prospective changes resulting from the merger to take place until after the closing of the transaction." RXO told staff: "until the close of the acquisition... we are still separate companies... Once that happens, we will begin integrating."

| Event | Anchor | Earliest record | Window on the target |
|---|---|---|---|
| Deal signed | Signing | 8-K Item 1.01 or Rule 425 | Not open |
| Deal closed | Close | 8-K Item 2.01 | Close to close + 180 days |
| No close filing | None | Absence of Item 2.01 | None; re-check |

- **Signed deal proves:** the parties have agreed terms. **It does not prove** the deal will complete. In one semiconductor study, many firms failed to complete their announced deals.
- **Second request:** if regulators issue one, the waiting period runs until 30 days after both parties substantially comply. Nothing in the public record tells you that date in advance. Re-check every month instead of guessing.
- **Closed deal proves:** integration is now legally allowed and usually starts. That is the buying condition: systems, vendors, and teams get rationalised.
- **Closed deal does not prove** that a specific contract is up for review. Use the renewal reference listed at the end to date individual contracts.

Integration leads are the people who own that work once the deal closes. The pool is small and easy to count.

**937 - People in the US holding integration-lead titles, in Refolk's index**

Titles counted: Integration Manager, Integration Director, Head of Integration, and Post-Merger Integration; the same titles return 353 people in the UK.

| Market | Integration-lead total | "Integration Manager" share of a 25-profile sample |
|---|---|---|
| United States | 937 | 44% |
| United Kingdom | 353 | 52% |

In Refolk's index of professional profiles, the UK pool is 37.7% the size of the US pool, so the US pool is 2.65x larger. The UK pool is also more concentrated. HSBC (4) and Fujitsu (3) account for 7 of the 25 UK profiles sampled, while no US employer appeared more than once. I have not verified why the UK pool is concentrated, so do not build a theory on it. There is also a caveat about precision. "Integration" also matches technical roles, and the samples included off-target titles such as Principal Software Engineer. Read every profile before it enters a sequence.

Matching closed deals to the people who run integration means joining two data sources: filing dates and current titles. [Refolk](/) does that join from one plain-English request, so you do not have to cross-reference an 8-K list against title searches by hand.

I ran this search: `Integration managers at US companies that closed an acquisition in the last 90 days` - [see the full result list](https://www.refolk.ai/s/q25t6rc5t1).

*Returns named integration leads at recently closed acquirers, with profile links to check for off-target technical "integration" titles before outreach.*

If you are recruiting the acquired startup's people rather than selling to the company, the Acquired-Startup Talent Window covers that job from deal close.

## Restructuring, cyber, and layoff filings: anchor, proof, window

For these three events, the anchor is a date the company sets itself or announces in advance. A restructuring's costs can arrive later by amendment, a cyber clock starts when management decides the incident is material, and a WARN notice comes before the layoff it announces.

| Event | Anchor | Earliest record | Proves |
|---|---|---|---|
| Restructuring | Event date in the filing | 8-K Item 2.05, 4 business days | A committed restructuring |
| Restructuring cost update | Date costs are determined | 8-K/A, 4 business days after | The cost estimate |
| Cyber, voluntary | None | Item 8.01 or 7.01 | An incident, not materiality |
| Cyber, material | Materiality determination | Item 1.05, 4 business days after | Management judged it material |
| WARN notice | Separation date in notice | State WARN list | A planned site-level reduction |

### Restructuring (Item 2.05)

The first filing can be released before the costs are known. Filers may amend the cost estimates within 4 business days of determining them, and ManTech did exactly that. Treat the original filing as the anchor, and treat the amendment as the point where the size of the restructuring becomes known. Do not size the opportunity from the first filing.

### Cyber incident (Item 1.05 vs 8.01)

- **Proves (1.05):** management has decided the incident is material.
- **Does not prove:** when the incident happened, what was affected, or that a purchase is coming.
- **How it lies:** the company sets the anchor itself, because management makes the materiality call. A voluntary filing under Item 7.01 or 8.01 can come first and is not a claim of materiality. Treat an 8.01 as a watch item and open the window only if an Item 1.05 follows.

### WARN notice

WARN applies to employers with 100 or more employees. It requires 60 calendar days' notice for events affecting 50 or more employees at a single site. The notice is a leading indicator, so the anchor is the separation date it states, not the posting date. The window for HR, outplacement, and transition offers runs from the posting up to that separation date. Statutory exceptions allow shorter notice, so always read the date in the notice itself. Do not assume 60 days.

If you sell into workforce transitions, [Refolk](/) can return the HR leaders at companies on a state's WARN list in one request. Try "HR directors at companies with WARN notices filed in California this quarter". To break one notice down into named teams, use the Layoff-Filing Teardown.

## How to read a trigger event, step by step

Every event goes through the same seven steps, in this order, and the output is one record per event. The effort estimates for reps are my own and unmeasured. The statutory lags are sourced.

#### From feed item to dated window

1. **Classify the event** - Label it as a raise, M&A, debt or contract, restructuring, cyber, or WARN. Anything else, such as an IPO filing or a new site, goes to the unverified pile.
2. **Pull the earliest public record** - Find the Form D, 8-K, Rule 425 filing, or state WARN listing, not the press story. You are done when you have a URL and a filing date; I estimate 10 to 20 minutes.
3. **Set the legal anchor** - Write one date: first sale, signing (Item 1.01), close (Item 2.01), materiality determination (Item 1.05), or the separation date in the WARN notice.
4. **Rule out a false positive** - Confirm it is an original filing from an operating company, the amount sold is above zero, and the item number matches the event type.
5. **State what it proves and what it does not** - Write one line for each. A Form D proves money was committed; it never states a stage or names an investor.
6. **Assign open, peak, and close** - Apply the stage's offsets from the window table to the anchor. For an acquisition, nothing about the target opens before close.
7. **Re-check at stage transitions** - Set a dated reminder for the close 8-K, an Item 2.05 cost amendment, or an Item 1.05 that follows an Item 8.01.

Use the same record format on every account so that any rep can audit any other rep's window:

**Trigger record, one per event**

```
Account:
Event type: raise / M&A / debt or contract / restructuring / cyber / WARN
Earliest record: form and item / URL / filed on
Anchor type: first sale / signing / close / materiality determination / separation date
Anchor date:
Anchor quality: legal / proxy (announcement only)
Checks: original filing Y/N / operating company Y/N / amount sold above zero Y/N / item number matches Y/N
Proves:
Does not prove:
Window: open on / peak from and to / close on
Re-check: which filing would change this, and by when
Decision: reach out now / wait until (date) / drop
```

*Paste into the CRM note or a shared sheet; write "none" or "unverified" rather than leaving a field blank.*

## How trigger reads go wrong

Most bad trigger reads start with a feed of raw filings counted as events. The eight failure modes below account for the errors I see. Each comes with the specific check that catches it.

1. **An amendment counted as a new raise.** Counting filings without filtering roughly triples your apparent "new raises". In one sampled week, 383 filings were amendments. *Check:* the original-versus-amendment flag on the Form D.
2. **A pooled fund mistaken for a company.** About two thirds of Form D filings come from investment funds. In one sampled week, 587 of 913 new filings came from pooled funds. *Check:* the issuer's industry group.
3. **A pre-filed Form D.** An issuer may file before any securities are sold, so the filing exists but no money has been committed. *Check:* the amount sold is above zero and the first-sale date is filled in.
4. **A missing Form D read as "no raise".** About one in four rounds has no filing. *Check:* the press, the state blue-sky notice, and investor posts before you drop the account.
5. **An announced deal treated as done.** Deals fail to complete, and the target stays frozen while they are pending. *Check:* an 8-K under Item 2.01 confirming the close.
6. **A cyber filing read as material.** An Item 8.01 filing is voluntary and makes no claim of materiality. *Check:* the item number. Only Item 1.05 opens a window.
7. **The WARN posting date read as the layoff date.** The notice comes at least 60 days before the event, and exceptions allow shorter notice. *Check:* the separation date stated in the notice.
8. **A grant read as a round.** Some signal lists merge the two. *Check:* the security type and the issuer.

> **Watch out:** Never count raw filings
>
> An unfiltered Form D feed mostly lists funds and amendments, not companies that just raised. Filter on both the original-filing flag and the issuer's industry group before a single account reaches a rep.

There is one more check I would like to recommend but cannot support. People talk about a "relabelled office", where a new site turns out to be an existing office under a new name. I found no primary source for how to detect it, so it is not in the list. If you rely on site-opening triggers, test for it yourself with the company's own location pages over time.

> A trigger without a filing is a rumour with a date attached, and rumours do not get windows.

## What this reference leaves out, and how to keep it current

This reference covers six event types whose anchors I could tie to a statute or a filing rule. Everything else is either not yet verified or covered by another reference.

**Not verified, so no lags are given:** IPO registration (a public S-1 or a confidential submission), new site or market entry, and government contract awards. If you need one of these, find the earliest public record yourself, write down its filing date next to the date of the event it reports, and do this for several examples before you trust any lag. Do not borrow a window from a row above.

**Out of scope, with their own references:**

- Executive and leadership moves: the Leadership-Move Alert Reference.
- Open roles and hiring plans: the Account Hiring-Signal Read.
- Contract renewal timing: the Incumbent Renewal-Window Read.
- Team-level layoff detail: the Layoff-Filing Teardown.
- Which initiative a raise or earnings call actually funds: the Funded-Initiative Teardown.

Web visits and public meetings are also excluded here.

**Keeping a read current.** A window is only valid until the next stage transition. A close 8-K opens the target. An Item 2.05 amendment resizes a restructuring. An Item 1.05 turns a watch item into an open window. A deal with no close filing should be re-checked monthly, not assumed dead or done. When a reminder fires, update the record in place and keep the old anchor in the note, so the history of the window stays visible.

#### Before you send or schedule anything

- [ ] The record names one anchor date and the filing it came from.
- [ ] The filing is an original Form D or 8-K, not an amendment.
- [ ] The issuer is an operating company, not a pooled investment fund.
- [ ] For a Form D, the amount sold is above zero and the first-sale date is filled in.
- [ ] For an acquisition target, an Item 2.01 close filing exists.
- [ ] For a cyber event, the filing is under Item 1.05, not 8.01 or 7.01.
- [ ] For a WARN notice, the window is dated from the separation date in the notice.
- [ ] Open, peak, and close are written as calendar dates, not durations.
- [ ] Any proxy anchor taken from an announcement is labelled as a proxy.
- [ ] A re-check date is set for the next stage transition.

## Frequently asked questions

### How long after a funding round should I reach out?

It depends on whether the round was announced. Count from the first-sale date on the Form D, not from the press story. If you find a Form D and there is no press coverage, there is no crowd yet, so reach out within 48 hours of finding it. If the round was announced, every other seller has seen it too, so wait until 60 days after the first sale. In both cases, the window closes 180 days after the first sale.

### When should I contact a company after an acquisition?

Reach out to the acquired company after the deal closes, not when it is announced. Between signing and close the two companies stay independent competitors, and their own employee FAQs say nothing changes until close. Wait for the 8-K under Item 2.01 that confirms the close. The window opens on that date, peaks over the next 90 days, and closes 180 days after close. If no close filing ever appears, assume the deal may have failed.

### Does a Form D tell me what stage the round was?

No. A Form D never states a stage or names an investor. It proves that at least one investor was irrevocably committed on the first-sale date, and it reports the amount sold. To learn the stage, check the press, investor posts, or the company's own announcement. Also check the security type and the issuer, because a grant or a fund can look like a round in a raw feed.

### A company announced a raise but I cannot find a Form D. Is the announcement wrong?

Probably not. Filing a Form D is not a condition of the exemption, and one academic study found Form Ds are filed for only 75% of rounds on average. Use the close date from the announcement as a proxy anchor, mark it as a proxy, and handle it as an announced raise. Before you drop the account, check the state blue-sky notice and investor posts.

### Is an 8-K cybersecurity filing a buying signal?

Only if it is filed under Item 1.05. That filing means management has decided the incident is material, and it is due within four business days of that decision. A filing under Item 8.01 or 7.01 is voluntary and does not claim materiality. Treat it as a watch item, not an opening. Keep in mind that the company itself chooses when to make the materiality decision.

### Why do sales trigger windows differ so much between sources?

Each source starts the clock on a different date, and most do not say which. Published funding windows run from 'within 5 days' of a trigger to '0 to 180 days' from the close date. Acquisition averages from announcement to close run from about 53 to 264 days. If you fix the anchor first, using the first sale, the close, or the separation date, the windows stop contradicting each other.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/company-trigger-event-reference-3*
