What a standalone Greenhouse or Workday export loses: one hire read before and after its offer context

Short answer

A single-system export keeps the facts its own system recorded and drops the reasons around them. A Greenhouse export shows how an offer was negotiated but not what pay the employee started on. A Workday export shows the hire and every later pay change but not what the candidate signed. Read alone, the correction of a keying error looks like an early raise. The missing context sits in the other systems: the offer versions, the signed letter and its completion time, and the payroll query that exposed the gap.

Visual briefFull-size diagram
A Workday hire record with four blank fields (what was offered, what was signed, what the day-38 change was, how it was found) that fill in as context tiles from Greenhouse, Docusign and a payroll query slide up into place.
Illustrative. The same fictional hire, first as an HR record on its own, then with the context from the other systems filled in.

This before-and-after reading is part of the offer-to-onboarding records guide. It follows one Illustrative hire through two readings. For the identifiers that join each step, see the record linkage page; to judge a whole archive, use the completeness checklist.

Before: the hire as the HR record tells it

Illustrative. A fictional 1,900-person healthcare provider hires a clinical manager. Someone exports its Workday history during a system review. Described at metadata level, the record for this one worker reads:

  • Hire event, effective March 17. Title: clinical manager. Base pay: $82,000.
  • Day 38. A compensation change to $86,000, entered by an HRIS analyst. Workday's auditing keeps the old value, the new value, who submitted the change and when, and that history can be viewed but not altered.
  • Day 90 and after. Still employed.

A reader with only this export draws a reasonable conclusion: a new manager earned a raise five weeks in and stayed. Nothing in the record contradicts it. Workday did its job. It stored exactly what was entered and when. It simply has no field for what was promised before the hire existed.

The Greenhouse export, read on its own, tells a different partial story. It shows offer version 1 at $82,000, a version 2 at $86,000 with fresh approvals, and the application marked hired. Greenhouse documents that a new version voids the original offer and its approvals, so the existence of version 2 is a durable fact, provided pay is one of the fields that creates a version in this company's setup. The export ends at the hire. It cannot say what payroll actually ran.

After: the same hire with its offer and signature restored

Now read the three systems side by side, joined on the application and envelope. The sequence below is the same Illustrative hire.

OrderSystemWhat the record shows
1GreenhouseOffer version 1 approved at $82,000, start date March 17
2GreenhouseCandidate counters; version 2 created and approved at $86,000
3DocusignLetter for version 2 sent, then completed by the candidate two days later
4WorkdayHire keyed by HR from the version 1 approval email at $82,000
5WorkdayEmployee starts March 17; payroll runs on $82,000
6Payroll ticketEmployee queries the first payslips against the signed letter
7WorkdayDay 38: pay changed to $86,000, the figure that was signed
8WorkdayStill employed after 90 days

The day-38 change is no longer a raise. It is a correction back to the signed $86,000 after five weeks of underpayment. The evidence that settles it is the Docusign Certificate of Completion, which lists the envelope ID, each recipient event with a timestamp, and summary events such as sent and completed; if the envelope had been corrected, an Envelope Updated event would show that too. Row 6 is worth noticing: the detection happened in a fourth place, a payroll query, which no export of the three core systems contains.

What goes missing, and where it lives

Each row is a question a reviewer, a model or an auditor would ask about this hire. The middle columns show what one export can answer; the last column shows where the missing piece is kept.

QuestionGreenhouse export aloneWorkday export aloneWhere the context lives
What was first offered?Version 1 at $82,000Not recordedGreenhouse offer versions
What changed in negotiation, and when?Version 2, if pay creates versionsNot recordedGreenhouse versions and approvals
What did the candidate sign?Only if letters were generated thereNot recordedDocusign envelope and certificate
What pay did the employee start on?Not recorded$82,000Workday hire event
Was the day-38 change a raise or a fix?Not recordedLooks like a raiseAll three compared
How was the mismatch found?Not recordedNot recordedPayroll query or HR ticket
Did the hire stay past 90 days?Rarely trackedYesWorkday, tied back to the offer

The pattern is general: structured fields survive an export, and the reasoning that connects them does not. The same gap appears in many record types, as what data is missing from AI training explains.

Why the misreading matters for training and evaluation

A model trained on the HR export alone would learn that new hires often get raises in their second month. That is wrong, and it is wrong in a way that matters for any system that drafts offers, audits payroll or answers employee pay questions. The connected history teaches the actual process, including the exception: an accepted offer that differs from the HR record, caught by the employee, fixed weeks later.

The same joined history makes evaluation possible. A question like "was this employee paid what they agreed to?" can only be graded when the signed letter sits next to the payroll record. A single export gives a confident wrong answer and no way to tell. That is why the onboarding context around a hire, covered in assessing original onboarding materials and onboarding and training records, adds weight to an otherwise ordinary HR archive.

Describing the gap without opening a record

You do not need to see this hire, or any hire, to tell SourceX whether the context exists. Four questions to the people who run the systems are enough:

  1. Where does the signed offer letter live, and since when? (Docusign, Greenhouse, a shared drive, or paper.)
  2. Does the Workday hire record carry a recruiting reference, and from which year?
  3. How are hires created in Workday: by integration, spreadsheet upload or hand entry?
  4. When a hire record is corrected, is the change labeled as a correction or entered as an ordinary pay change?

The owners are usually the talent acquisition operations lead, the HR coordinator who manages letter templates, and an HRIS analyst. None of them can authorize a licensing discussion about personnel records; that is the CEO, usually with the CHRO or head of people as internal sponsor and the CFO or general counsel advising. Partners never ask for or handle raw records: no names, salaries, letters or payslips.

Before introducing, check the baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, the right to license these 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. Candidate privacy notices and works council agreements can limit reuse; mention any you hear about. What stays unknown until SourceX reviews it: whether the records can be de-identified to a buyer's standard, which years matter, and what the company would be paid. For the Greenhouse side in more detail, see Greenhouse hiring 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 say where the offer versions, signed letters and hire corrections each live, and since when, register as a partner, confirm the company on who qualifies, and read the program terms before you introduce the sponsor.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

Is a Workday-only archive still worth mentioning to SourceX?

Yes. Years of hire events, pay history and tenure are a real record on their own. Say plainly that the offer and signature context is not joined, so the review starts from an accurate picture rather than an assumed one.

Can the missing context be rebuilt later?

Often, if Greenhouse still holds the offer versions and the Docusign envelopes still exist. The company would do that joining itself under an agreement. If candidate records were deleted under a retention rule, that part of the history may be gone.

Do I need to know how often hire records disagree with offers?

No. Ask whether it happens and how the company finds out. Counting cases needs the records, which stay with the company until an agreement is in place.

Sources

  1. doc.workday.com/admin-guide/en-us/manage-workday/tenant-conf…
  2. support.greenhouse.io/hc/en-us/articles/201093394-Create-a-new-off…
  3. support.docusign.com/s/document-item
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment