# Offer-to-onboarding records: metadata packet | SourceX

Canonical: https://refer.sourcex.si/guides/chain-offer-to-onboarding
Last updated: 2026-11-04

A referral partner can describe a company's offer-to-onboarding history without opening a single offer letter. The useful facts are metadata: which system holds each offer version, where the signed letter lives, how the hire record is created, the date range and volume of each, which identifier carries an offer into the HR record, and who owns each step. The case to test before introducing is the one where the accepted offer and the HR record disagree.

## The business task the packet describes

Every hire passes through three decisions. Recruiting and the hiring manager negotiate terms, often through several drafts. The candidate accepts and signs. HR then turns the accepted terms into an employee record that drives payroll, benefits, probation and reporting. When those three agree, nobody looks twice. When they do not, someone has to spot it, decide which draft governs and repair the record.

Across thousands of hires, that sequence documents how a company negotiates, controls approvals and keeps its people data honest. The packet captures none of that content. Its job is narrower: to tell SourceX where each step is recorded, for how long, and how confidently the steps can be joined, so SourceX can judge whether a conversation is worth having.

## What each system can tell you without opening it

You can gather everything in the packet from a 30-minute call with a talent acquisition lead and an HRIS analyst, working from their admin screens and their memory.

- **The applicant tracking system (Greenhouse in this example).** Ask how many offers went through more than one draft, and since when. Greenhouse documents that only offer fields marked with the Refresh icon spawn a new version, that doing so voids the earlier offer and its approvals, and that older versions cannot be removed while the newest exists. Its Harvest API returns a new offer row with an incremented version number when the start date, opening or a version-triggering custom field changes. Version counts are therefore countable, not guessed.
- **The e-signature tool (Docusign here).** Ask whether letters go out from the ATS or from a separate template, and whether a resend creates a fresh envelope. The eSignature API returns audit events per envelope ID. What matters for the packet is whether that envelope ID, or the application ID, is written anywhere downstream.
- **The HRIS (Workday here).** Ask how a hire is created: through a recruiting integration, a spreadsheet upload, or manual entry. Workday keeps the old value, the new value, who submitted a user-made change and when, and auditors can view but not alter that history. A later repair to a hire record should therefore surface as a dated change, which is exactly what the failure case below depends on.

## Sample packet, filled in

Illustrative: a fictional 2,400-person regional logistics operator running depots in three states; every figure is invented to show the level of detail expected.

| Field | ATS (offer drafts) | E-signature (signed letter) | HRIS (hire record) |
|---|---|---|---|
| Object types | Applications, offers with versions, offer approvals | Envelopes, completed documents, certificates of completion | Hire events, job and position history, worker records |
| Date range | 2020 to today | 2020 to today | 2014 to today |
| Approximate volume | 4,700 hires; about 1,600 offers redrafted at least once | About 5,200 offer envelopes | About 9,800 hire events, heavy seasonal rehiring |
| Version marker | Offer version number | One envelope per sent letter; resends create new envelopes | Effective-dated job and hire-date changes |
| Link to next step | Application ID written to the envelope? Yes, as a custom field | Envelope ID stored in the HRIS? No | Recruiting reference on the hire? From 2022 only |
| Step owner | Recruiting operations manager | Talent coordinator who maintains letter templates | HRIS analyst |
| Retention rule | Non-hired candidate data purged after 18 months | None known | Seven-year employment records policy |
| Planned change | Replacing the ATS within a year | None | None |

The "No" and "From 2022 only" answers are what make this packet credible. An introducer who records a missing join is easier for SourceX to work with than one who assumes an integration exists. If the client names a planned system change, write it down; for the HRIS side, [exporting Workday history after a migration](/systems/workday-data-export-after-migration) explains why that kind of decision often carries a deadline. Per-system detail is in [Greenhouse hiring records](/systems/greenhouse-export-candidate-data) and [Docusign agreement archives](/systems/docusign-bulk-download-envelopes).

## How the packet flags an offer the HR record contradicts

Illustrative, same fictional operator. A night-shift depot supervisor is offered $61,000 with a May 5 start. Before signing, the candidate asks for two more weeks to serve notice, so recruiting issues offer version 3 with a May 19 start, same pay and title. The signed letter carries May 19. The HRIS hire record, keyed from the version 2 approval, says May 5.

Nothing looks wrong on payday, because pay and title match. The damage is in everything dated from the hire: the 90-day probation review lands two weeks early, the benefits waiting period starts before the person was employed, and the seniority date used for shift bidding is off. The probation form, sent a week before the review falls due, reaches the supervisor's manager for someone who has worked only ten weeks. The manager flags it, and the hire date is corrected on day 71 of actual employment.

The partner never sees any of this. The packet makes the pattern findable through three answers: many offers are redrafted, start dates are among the fields that trigger a new version, and the envelope ID never reaches the HRIS. Together they tell SourceX that date mismatches are likely, that some were repaired, and that the repairs are logged. Ask the HRIS analyst one question: "When a start date moves after approval, how does the new date reach the hire record?" If the answer is "someone retypes it," the packet should say so.

## Who can authorize a licensing discussion, and what stays unknown?

Offer letters and hire records are personnel data, so the sponsor sits high: typically the chief people officer alongside the CFO or general counsel. A recruiting operations manager can describe the systems but seldom holds the authority to discuss licensing them.

Before you introduce, confirm:

- The company has 50+ full-time employees at peak, contractors excluded, and a documented operating history.
- It holds the right to license these records. Candidate privacy notices, works council agreements and vendor contracts can all restrict reuse; note any you hear about without ruling on them.
- A named decision-maker will take a first call.
- 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.

Partners never ask for or handle raw records; discovery stays at the level of what, how much, how long, which system and who owns it. Open until SourceX reviews the opportunity: whether the records can be de-identified to a buyer's standard, which years and fields a buyer would want, what consent limits apply, and what the company would be paid. Extensive records do not guarantee a fit, for reasons covered in [why a documented company can still be declined](/questions/why-can-a-company-with-extensive-documentation-still-be-declined). For why people records draw interest at all, see [why HR data is valuable](/proof/why-hr-data-is-valuable); other record locations are on the [systems hub](/systems).

## Go deeper on offer-to-onboarding records

- [Offer-to-onboarding record linkage](/guides/offer-to-onboarding-record-linkage): the record chain, step by step, with the identifier that joins each hop and where it breaks.
- [Offer-to-onboarding completeness checklist](/resources/offer-to-onboarding-completeness-checklist): a pass, partial or fail scorecard for judging whether the hiring trail is complete enough to discuss.
- [What a single-system offer export loses](/guides/offer-to-onboarding-missing-context): a before-and-after reading of one hire, with and without its surrounding records.

## 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 your client can name the owner of each step and roughly when the offer-to-hire link starts, that is enough to [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and introduce the sponsor under the [program terms](/terms).

## Sources

- https://refer.sourcex.si/terms
- https://support.greenhouse.io/hc/en-us/articles/201093394-Create-a-new-offer-and-re-trigger-offer-approval
- https://harvestdocs.greenhouse.io/reference/get_v3-offers
- https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/listauditevents/
- https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/auditing/dan1370797846272.html
