This checklist belongs to the recruiting firm acquisition guide. The 30-minute meeting agenda is where the questions are first asked; this page keeps the answers current as the deal moves.
Setting the three dates first
A countdown is only honest if the clock is real. Before marking any item, write down the dates the company has actually documented and where each came from.
| Milestone | Where the date usually comes from | If no date exists yet |
|---|---|---|
| Announcement | The signed purchase agreement or the communications plan | Work milestone one quietly with the owner only |
| Cutover | The integration plan's system consolidation date | Record who owns the decision; revisit when it is set |
| Switch-off | The old ATS license end, a transition services agreement or a decommissioning ticket | Leave it open; the item becomes "find out who decides" |
Use three states for every item: confirmed (a person with authority said so), unknown (with a name for who will find out) and at risk (the current plan loses it). A confirmed item needs a person, not a field you spotted in a report. Keep the sheet short, share it only with the people who answered, and never record candidate names, client fees or contract text in it.
If the deal is still confidential, the first milestone may be all you can do. That is fine. Confidentiality is a reason to keep the circle small, not a reason to skip the questions.
Where the checklist lives in the project. Integration programs already run on weekly steering calls and status trackers. Ask the integration lead for one standing line in that tracker, "closed history items," instead of a separate workstream. It costs the team a minute a week and keeps the open items visible to people with the authority to close them.
How to ask. Ask what exists and who decides, and nothing more. "Where is that kept, and who would know?" is the right shape. If someone offers to pull a report or forward a document, thank them and say a description is enough. Partners never take copies.
When to escalate. An item that stays unknown for two steering cycles usually has no owner. Raise it with the decision-maker directly, briefly, and without inventing a deadline to make it feel urgent.
Milestone one: before the acquisition is announced
The owner still controls the records and can answer freely. Ask now, while nothing has been decided about the old history.
| Confirm | Owner | What happens if it is skipped |
|---|---|---|
| Which entity owns placement, agreement and credit records, and whether they transfer with the deal | Seller's owner, with counsel | Nobody can authorize a discussion after closing |
| Who can authorize a licensing discussion before closing and who after | Seller's owner | An interested company stalls on a question of authority |
| Roughly how many placements and closed cases, over how many years | Operations lead | The history has no shape and cannot be described |
| Whether client agreements are linked to placements or filed separately | Operations or finance lead | The link between terms and decisions is assumed rather than known |
Milestone two: before cutover to the acquirer's ATS
Migration scope decides what survives in usable form. Closed cases look finished, so they are the first thing a mapping exercise trims.
| Confirm | Owner | What happens if it is skipped |
|---|---|---|
| Whether guarantee period and prorated-day fields migrate | ATS admin and integration lead | Placements arrive without the terms that governed them |
| Whether notes, attachments and custom objects migrate or stay behind | Integration lead | Reasons for leaving and exception approvals are stranded |
| Where credit notes and refund approvals live and whether they keep a placement reference | Finance lead | Outcomes can no longer be matched to cases |
| Which client or MSP programs restrict reuse of their records | Owner or account directors | Restricted data is mixed with unrestricted data |
Systems capture part of this already. Bullhorn's permanent placement billing summary report, for example, includes placement guarantee columns, Days Guaranteed and Days Pro-Rated, for each placement. Whether those fields, and the documents around them, reach the new system is a decision someone is making right now. The Bullhorn data export page describes what a standard export carries.
Milestone three: before the old ATS is switched off
Switch-off is final. Anything still open here is usually gone afterward.
| Confirm | Owner | What happens if it is skipped |
|---|---|---|
| Whether the old instance goes read-only, is exported to an archive, or is shut down | Integration lead | The history disappears with the license |
| Who holds the archive and who can grant access to it | Acquirer's IT or operations lead | The records exist but nobody can open them |
| Which fields identify candidates and would need de-identification | Owner, with counsel | Any later discussion starts with an unknown privacy scope |
| That legal retention minimums are not mistaken for the archive plan | Owner or HR lead | History beyond the minimum is deleted by default |
The last row matters. Federal EEOC rules require private employers to keep personnel and employment records for one year from the record or the action, whichever is later. That is a minimum for one category of record, not a plan for the guarantee history. The system decommissioning guide describes what usually happens to old instances.
From a finished checklist to an introduction
Illustrative. A 230-person light industrial staffing firm, acquired by a national group, finished the checklist across all three milestones. Its summary for the owner read:
| Area | State | Note |
|---|---|---|
| Ownership after closing | Confirmed | Records transfer with the acquired entity |
| Placements and closed cases | Confirmed | Six years of permanent placements |
| Terms linked to placements | Partial | Agreements attached from year three onward |
| Credit notes with placement reference | Confirmed | Kept in the finance system |
| Notes and attachments after cutover | At risk | Planned to stay in the old instance |
| Client program restrictions | Partial | Three MSP programs excluded |
That is a sound metadata-level description. If the owner wants to explore licensing:
Disclose. You are a SourceX referral partner. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward that is funded separately and never deducted from the company's payout. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout.
Check fit. 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Demand, the rights review result and any offer stay unknown until SourceX reviews an application. For why records like these can matter, see why HR data is valuable.
Introduce. Use the annotated introduction email. Sign the Channel Partner Agreement first. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. The rewards page lists every condition; the staffing screening worksheet and staffing and recruiting page cover the sector.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the checklist shows the terms still link to decisions before switch-off and the owner wants to talk, register as a partner, check who qualifies, and read the program terms first.