The Talent-Availability Signal Reference for Target Companies

You watch a set of target companies. This reference tells you which public events mean their people just became reachable, which employees each event actually moves, how long the window stays open, where to detect the event in public sources, and the specific way each signal lies. It is a lookup document: jump to the row you need and leave.

Most company-signal guides answer a different question. They read events as reasons a company is hiring, or they score a company as a source of talent. This one flips the lens. Each event here is a row with a receptivity window, a detection method, and a failure mode, and the events are sorted into two piles that behave nothing alike: signals that a company is growing, and signals that a company is shedding people. Growth tells you who they will hire. Shedding tells you who of theirs you can now reach.

What "talent availability" actually measures

Talent availability is the state where a company's own employees have just become reachable and receptive because of a public event, not because they were casually browsing. It is a property of the event, not the person.

Two things follow from that definition, and both matter for how you use this document.

First, availability is time-bounded. Every event opens a window and closes it. A laid-off engineer is most reachable in the weeks after the notice and much less reachable once re-employed. An employee whose IPO lockup is still running is cash-motivated but not yet liquid, so reaching them pre-expiry wastes the window. The window is the whole point.

Second, availability splits cleanly into two mechanisms. Growth signals are budget-backed and predict net new demand: a company hires for a market before it enters it, for a product before it ships it, for a function before it admits it needs one. Shedding signals are attrition-linked and predict that existing people are becoming reachable. The observable test is the headcount trend around the event. Growth shows postings and headcount rising. Shedding shows a triggering event plus flat or falling headcount. Confuse the two and you send a growth playbook into a company that is quietly cutting.

The two piles: growth versus shedding

A company event is either a growth signal (net new demand, existing people staying put) or a shedding signal (a trigger event with existing people becoming movable). Sort every event into a pile before you do anything else, because the pile decides the playbook.

Growth signals tell you the company is about to compete with you for talent. They rarely make the company's current people reachable; a well-funded team is usually a happier one. Their value to a poacher is indirect: they tell you where the market is heating and where you will soon be outbid. Shedding signals are the ones that make people movable, and they are what most of this reference is about.

The dangerous quadrant is the top-left: a company shedding people while its headline says growth. A down round or bridge round dressed as a funding announcement lives here. So does an RTO mandate at a company still posting jobs. The correction is always the same: read the headcount trend, not the headline.

The signal reference: what each event proves

This is the core table. Each row is a company-level event, what it proves about which employees just became reachable, the receptivity window, and where to detect it. The precise per-employee windows are set by the mechanism in each row, not by a single vendor number.

A few of these deserve a note on strength.

The acquisition row is the highest-yield shedding signal in this table, and the mechanism explains why. Non-founding employees do not get to choose who buys them, and that lack of choice creates an organizational mismatch that leaves acquired employees looking toward the door. The result is 33% of acquired workers leaving in the first year against 12% of regular hires. That is a large, documented effect size, not a survey of feelings.

The RTO row is the one people misread most, so read the window carefully: it opens at the enforcement date. Intent-to-leave is stated when the mandate is announced, but people actually move as the in-office deadline arrives. Watching the effective date beats reacting to the press release.

Who moves under each event: the numbers

Different events push out different people, and the size of the movable group is documented for the events that matter most. This table is your denominator: it tells you how many of the affected group you can realistically expect to be reachable.

Read the RTO row as intent, not exits - it is the one number in this table that measures what people say rather than what they did. The merger and acquisition rows measure actual departures. Layered onto the raw rates, the RTO research adds a segment signal worth keeping: high performers' intent to stay is 16% lower under strict RTO requirements, double the 8% seen among average employees, and among women and millennials intent to stay drops 11% and 10%. RTO does not just shed people; it shed the people you most want.

There is also a company-level tell you can use to confirm an RTO mandate bit: Unispace found that 42% of companies mandating office returns experienced higher-than-anticipated attrition, and RTO firms took 23% longer to fill roles. If a target with a fresh mandate is suddenly slow to fill and leaking people, the mandate is doing its work.

Growth signals tell you who a company will hire. Shedding signals tell you who of theirs you can reach right now. </pull> ## Where to detect each event, and the timing that comes with it Detection has to be repeatable from public sources, or the watchlist rots. This table pairs each event with a source you can subscribe to and the timing baked into that source. | Event | Public source | Documented timing | |---|---|---| | Mass layoff | WARN filing / tracker | 60-day advance notice | | Funding | Funding feed / founder post | Need peaks 2-4 wks post-close | | IPO liquidity | S-1 / lockup calendar | 90-180 day lockup | | Vesting cliff | Equity norms | 1-year cliff, 4-yr vest | Two mechanisms are worth knowing in detail because they set the window precisely. **WARN filings.** Employers must notify the government at least 60 calendar days before a plant closing or mass layoff, with thresholds around 50 or more workers at a single site (where 50 is at least a third of the workforce) or any layoff of 500 or more. The notices usually coincide with employees being told, though they can be filed ahead of a companywide announcement. That advance-notice mechanism is exactly why a WARN feed gives you a head start over a press cycle. **IPO lockup and vesting.** The common practice is a 180-day lockup, ranging from 90 to 180 days, though some companies let employees sell a portion earlier. Standard equity is four-year vesting with a one-year cliff in venture-backed startups. Both dates are mechanical: locked-up employees are cash-motivated but not liquid, so the expiry date, read from the S-1 and a lockup calendar, is the reach-out date, not a day before. For posting clusters, the read is simpler and weaker: posting multiple roles in the same department within a short window indicates real headcount commitment, read off ATS pages. But treat clusters as a hypothesis, not a conclusion (see the failure modes).

figure kind: flow title: From event to scheduled outreach caption: Every event runs the same pipeline; only the classification step changes the downstream playbook. step: Detect :: A public source fires: WARN filing, funding feed, policy post, deal news step: Classify :: Sort into growth or shedding using the headcount trend step: Confirm :: Corroborate with an independent second source step: Segment :: Name the specific employees the event pushes out step: Time :: Schedule outreach against the event's window

Assembling a named shortlist from a fired event is where most of the manual work lives, and it is the friction I built [Refolk](/) to remove: you describe the movable segment in plain English and get the people back, rather than reconstructing them by hand from a filing plus a dozen profile checks.

## The procedure: from watchlist to scheduled outreach

The workflow is the same for every event; the classification step swaps the playbook. Build the watchlist once, then run each incoming event through detect, classify, confirm, segment, time, and reach.

On step six, the reply economics justify the discipline. Single-channel outreach converts at 1 to 3%, while multi-channel sequences deliver up to 287% more responses, and a $168,000 per recruiter annual revenue gap separates the top quartile of firms from the rest across a 2,100+ firm benchmark. Both effects come from acting on a signal within 24 to 48 hours rather than sending more cold messages. Timing beats volume.

How this goes wrong: failure modes and false positives

Every signal in this reference has a way of lying, and the lies are more useful to know than the signals. This is the section to read twice. Each row below is a documented false positive and the check that catches it.

Funding read as pure growth

A funding announcement can be a down round or bridge round covering a cut, not an expansion. The failure is reading the headline as growth when headcount is flat or falling. Check the headcount trend, not the announcement. And even on a genuine round, the day-of window is the trap: teams treat funding as content to read, so by the time your outreach goes out the account has already heard from recruiters, agencies, software reps, and every SDR running the same congratulation email. Move on the early signal, not the press cycle.

Posting clusters that are ghosts

Postings are a weaker signal than they used to be. In a 2024 survey, 40% of hiring managers said their company had posted a fake job in the past year, and US job openings have exceeded actual hires by over 2.2 million per month since early 2024. A posting-only read produces false growth signals at scale. Check that postings convert to filled headcount over the next quarter before you trust a cluster.

RTO intent mistaken for exits

The 19% and 33% intent-to-leave figures measure stated intent, not actual departures, and the announcement date is not when people move; the enforcement date is. Reacting to the press release over-counts the movable group and mistimes it. Confirm with profile updates around the effective date.

Acquisition segment assumed to be all-star

The 33% first-year departure figure does not caveat who leaves. Assuming all of them are top talent is wrong; a share of the departures are simply people who were not a good fit. Segment by role, seniority, and signals like patents before treating the whole acquired team as a target list.

IPO lockup reached too early

A locked-up employee is cash-motivated but not yet liquid. Reaching them before expiry wastes the window, because the retention lever is still on. Verify the actual expiry date from the S-1 and a lockup calendar, not a rumor, and reach on that date.

Senior-leader exit with no ripple

A leader's departure only shakes loose their team when the exit is abrupt and the leader was respected. An amicable, well-planned succession triggers no ripple at all. Check for a backfill announcement - a named successor already in place usually means the team is staying.

WARN filing treated as a roster

A WARN filing lists the affected site and the number of workers, not names, and not which of them are the good ones. Timing also varies by state, and filings can precede the public announcement. Corroborate with individual profile changes to turn a filing into a named shortlist.

A ready check before you send

Run this before you schedule outreach on any fired event. It encodes the failure modes as pass/fail gates.

Keeping the reference current

Signals decay, and the mechanisms behind them shift, so treat this reference as something you re-check rather than memorize. Two habits keep it honest.

First, re-verify the mechanical dates, not the vendor numbers. WARN thresholds, the 90-to-180-day lockup range, and the one-year cliff are the load-bearing facts, and they change slowly through policy and market norms. When a target's event fires, pull the specific date from the primary source: the S-1 for a lockup, the state filing for a WARN notice, the policy post for an RTO effective date. A calendar entry beats a rule of thumb every time.

Second, watch the posting-versus-hires gap as a running correction. As long as openings run millions above actual hires, any posting-based growth read carries a discount, and you should lean harder on headcount confirmation. If that gap closes, postings regain some signal value. The point is not to trust the current number forever but to track the mechanism and re-check where it stands before you rely on a posting cluster.

The steady state is a watchlist wired to repeatable public sources, an events log tagged growth or shedding, and a shortlist that names people rather than companies. The events will keep firing. What decides whether you or a competitor reaches the movable person first is how fast you move from a fired event to a timed, named, corroborated shortlist - and that is a workflow, not a lucky guess.