This page is part of the offer-to-onboarding guide, which covers the metadata a partner can collect. Here the job is to name each hand-off, its key, and where it snaps.
One hire, four hand-offs (Illustrative)
A fictional 520-person regional logistics company hires a warehouse operations supervisor. The offer is approved with an April 7 start. The candidate needs two more weeks to leave a current job, so the recruiter moves the start date to April 21. Every name, date and value below is invented.
| Step | Record | Key carried forward | System |
|---|---|---|---|
| 1. Candidate reaches offer stage | Application on the supervisor opening | Application ID | Greenhouse |
| 2. Offer drafted and approved | Offer version 1, start April 7 | Offer ID and version number | Greenhouse |
| 3. Start date moved | Offer version 2, start April 21; version 1 voided with its approvals | Same application ID, version number goes up | Greenhouse |
| 4. Version 2 re-approved | Approval on version 2 | Offer version | Greenhouse |
| 5. Offer letter sent and signed | Signing package with sent, opened and signed events | Package ID; application ID in a custom field, if configured | Docusign |
| 6. Hire record created | New starter record with start date and position | Employee ID; recruiting reference only if the integration writes one | Workday |
| 7. Start date corrected | Change from April 7 to April 21 | Old value, new value, who, when | Workday |
Illustrative. The keys describe how each join would be made, not a tested export.
The identifiers and what each one proves
Application ID. Created when the candidate applies and constant through every offer version. It is the one key that can, in principle, travel the whole chain.
Offer ID and version number. The applicant tracking system treats certain field edits as a new version: per its help center, the earlier offer and its approvals become void, and prior versions stay on file while a later one exists. Its developer reference lists a start-date change among the edits that add a fresh offer row with a higher version number. So the trail in steps 2 to 4 usually survives, and it proves which terms were approved last.
Envelope ID. The e-signature platform's API returns a signing package's audit events by its ID, which proves when the letter went out, was opened and was signed. It proves nothing about which HR record the letter belongs to unless someone wrote the application ID onto it.
Employee ID. Created in the HR system at hire. Its auditing logs the prior value, the replacement value, the person behind a user-made change and a timestamp, in a history reviewers can read but not edit. That makes step 7 provable: the correction is a dated change, not a silent overwrite.
Where the hire chain snaps
| Hand-off | How it breaks | What the record shows afterward |
|---|---|---|
| Version to version | Rarely; Greenhouse keeps the trail | Clean, unless offers were made outside the system |
| Offer to signed letter | Letter generated from a template with no application ID | A signed letter that matches a candidate only by name |
| Signed letter to HR record | Record keyed by hand from the wrong offer version | The HR record disagrees with what the candidate signed |
| Hire to correction | Change made by deleting and re-creating the worker | The correction is invisible |
In the Illustrative company, the hand-off from signed letter to HR record is the weak link. A coordinator keyed the new starter from an approval email for version 1, so the record began with April 7. The signed letter said April 21. Nothing tied the two, because neither carried the other's key.
Repairing the letter-to-HR-record link
- From a known date: an exact key. Once the company switched on its recruiting integration, new starters arrived in the HR system with the application ID in a reference field. From that year, offer and HR record join exactly, and the signed letter joins too if the same ID was written to a custom field on it.
- Before that date: an inferred join. Earlier hires can often be matched inside the company on candidate name, opening and start month. That is an inference built on personal data, done by the company, and it should be described as inferred.
The answer a partner needs is usually one sentence from the HRIS analyst, such as "exact from 2022, when the integration went live." That year becomes the start of the joined history.
When the hire record disagrees with the signed offer
The unresolved case is the one the weak link produces: an accepted offer that differs from the HR record. In the Illustrative hire, payroll and benefits enrollment were set up for April 7, and the error surfaced when the first payroll run treated the supervisor as already working. Workday's change history records the correction from April 7 to April 21, with who made it and when.
That correction is valuable precisely because it is recorded. A history of mismatches and fixes shows how a company's HR data drifts from what candidates were promised, and how quickly it notices. The missing-context comparison reads a case like this from one system and then from three, and the completeness checklist scores whether the keys were kept.
Owners, sponsor and unknowns
The talent acquisition operations lead owns the Greenhouse keys, whoever manages Docusign templates owns the envelope field, and the HRIS analyst owns the Workday side and the integration. Offer and hire records are personnel data, so the sponsor is senior: the CHRO or head of people with the CFO or general counsel. The CEO is the person who can authorize a licensing discussion and sign.
The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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.
Unknown until SourceX reviews it: whether candidate notices and employee agreements allow licensing, how records would be de-identified, and how many hires join exactly. Partners never ask for or handle raw records and sign the Channel Partner Agreement first. For each system, see Greenhouse hiring records, Docusign envelope archives and Workday history after a migration; for onboarding material itself, see onboarding and training records and assessing original onboarding materials.
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 a client can say which year its application ID started reaching Workday, register as a partner, check the company against who qualifies and read the terms before introducing its sponsor.