Offer-to-onboarding records across Greenhouse, DocuSign and Workday: a metadata packet for introducers

Short answer

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.

Visual briefFull-size diagram
A three-column field check compares the accepted offer version 3, the signed letter and the HRIS hire record; pay and title match at $61,000 and depot supervisor, while the start date reads May 19, May 19 and May 5.
Illustrative. One fictional depot hire, three systems, and the start date the HR record got wrong.

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.

FieldATS (offer drafts)E-signature (signed letter)HRIS (hire record)
Object typesApplications, offers with versions, offer approvalsEnvelopes, completed documents, certificates of completionHire events, job and position history, worker records
Date range2020 to today2020 to today2014 to today
Approximate volume4,700 hires; about 1,600 offers redrafted at least onceAbout 5,200 offer envelopesAbout 9,800 hire events, heavy seasonal rehiring
Version markerOffer version numberOne envelope per sent letter; resends create new envelopesEffective-dated job and hire-date changes
Link to next stepApplication ID written to the envelope? Yes, as a custom fieldEnvelope ID stored in the HRIS? NoRecruiting reference on the hire? From 2022 only
Step ownerRecruiting operations managerTalent coordinator who maintains letter templatesHRIS analyst
Retention ruleNon-hired candidate data purged after 18 monthsNone knownSeven-year employment records policy
Planned changeReplacing the ATS within a yearNoneNone

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 explains why that kind of decision often carries a deadline. Per-system detail is in Greenhouse hiring records and Docusign agreement archives.

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. For why people records draw interest at all, see why HR data is valuable; other record locations are on the systems hub.

Go deeper on offer-to-onboarding 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, confirm the company against who qualifies, and introduce the sponsor under the program terms.

  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

Do I need to see offer letters or salaries to describe this chain?

No. Version counts, date ranges, which system holds the signed letter, which identifier links an offer to a hire, and who owns each step are enough. Salaries, names and letters stay inside the company; the figures on this page are fictional.

Does SourceX connect to Greenhouse, Docusign or Workday?

This page names the tools only to show where records usually sit. It does not describe a SourceX connector or vendor relationship. If the company proceeds, it decides what to share under a signed agreement, and SourceX handles rights review and preparation from there.

Is a company that only uses Greenhouse still worth introducing?

It can be. A long hiring history with offer versions and outcomes has value on its own, but the offer-to-hire link is what makes this chain distinctive. Describe what exists, mark what does not, and let SourceX's review decide scope.

Sources

  1. refer.sourcex.si/terms
  2. support.greenhouse.io/hc/en-us/articles/201093394-Create-a-new-off…
  3. harvestdocs.greenhouse.io/reference/get_v3-offers
  4. developers.docusign.com/docs/esign-rest-api/reference/envelopes/enve…
  5. doc.workday.com/admin-guide/en-us/manage-workday/tenant-conf…

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