The scorecard is part of the offer-to-onboarding records guide. To see what one break looks like inside a single hire, read the before-and-after reading of one hire first.
Scoring rules: pass, partial, fail
Mark every check from what you hear, not from what you hope the answer is.
- Pass: the fact is recorded by a system, for most of the years the company wants to describe.
- Partial: it is recorded for some years only, or it depends on a person's habit or memory.
- Fail: it is not recorded, or nobody in the room can say. Unknown counts as fail until someone confirms otherwise.
Do not add the marks into a single number. Report a profile instead, such as "five pass, two partial, one fail", and name which checks failed. A profile tells SourceX where to look first. It predicts nothing about acceptance, scope or what the company might be paid.
The eight checks for a hiring trail
| # | Check | Ask this | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1 | Coverage | Since which year can offers, signed letters and hires each be retrieved? | All three overlap for five or more years | Overlap is shorter, or split by a migration | Only one system, or unknown |
| 2 | Offer-to-letter link | Is the application or offer ID written onto the signing envelope? | Yes, written by an integration | Typed into a letter name by hand | No link |
| 3 | Offer-to-hire link | Does the Workday hire carry a recruiting reference? | Yes, for all years | Only from a given year | Matched by name and start date |
| 4 | Version trail | Which offer fields create a new version in your Greenhouse setup? | Pay, start date and title all do | Some do | Edits overwrite with no version |
| 5 | Event order | Can approval, send, signature and hire be put in order from timestamps? | All four timestamped in systems | Paper or emailed letters for some years | Order unknown |
| 6 | Value agreement | Who keys pay into the hire record, and from what? | An integration from the accepted version | Rekeyed from the latest approved offer | Rekeyed from emails or memory |
| 7 | Correction labels | How is a fix to a hire record told apart from a raise? | A correction reason is recorded | Comments, sometimes | Not distinguishable |
| 8 | Outcomes | Where would I see an accepted offer that never started, or a hire who left within 90 days? | Recorded against the offer | Recorded on one side only | Not recorded |
Check 4 depends on configuration, not on the product name. In the recruiting tool, only certain fields start a fresh offer version when edited; changes to other fields simply overwrite. A recruiter can usually tell which fields behave which way by looking at the offer form, and that answer decides the mark.
Checks 5 and 7 lean on system history. E-signature platforms keep a per-envelope event log, so signature timing usually passes when letters are signed electronically. The HR system keeps a read-only trail of old value, new value, who changed it and when; check 7 asks whether the record also says why.
The test that matters: an accepted offer the HR record contradicts
Check 6 deserves its own question: "If an offer changes after approval, how does the new figure reach Workday?" The answers fall into three groups.
- Integration (pass). The accepted version flows into the hire record. A mismatch can still happen, but it would need a manual override, which Workday's audit history would show.
- Rekeyed from the approved offer (partial). An HR coordinator types the figures from the latest approved offer. Usually right; wrong when a version is approved after the hire is started.
- Rekeyed from email (fail). Pay comes from an approval email or a spreadsheet. In an Illustrative case, this is how a hire signed at $86,000 ends up in Workday at $82,000, the version 1 figure, until the employee queries a payslip.
Then ask: "How do you find out when that happens?" "Payroll catches it" is a real answer. It means the evidence sits in a payroll query or HR ticket, a fourth system worth naming in your notes. A company that says "yes, it happens, and here is how we catch it" is describing a known, labeled exception, which is more useful to a reviewer than a trail that looks perfect because nobody checked.
A scored example (Illustrative)
A fictional 760-person logistics company, scored in one call with its talent acquisition operations lead and an HRIS analyst. Every answer is invented.
| # | Check | Answer heard | Mark |
|---|---|---|---|
| 1 | Coverage | Greenhouse since 2019, Docusign since 2019, Workday since 2017 | Pass |
| 2 | Offer-to-letter link | Letters sent from Greenhouse through the integration | Pass |
| 3 | Offer-to-hire link | Recruiting reference on hires only since 2022 | Partial |
| 4 | Version trail | Pay, start date and title all create versions | Pass |
| 5 | Event order | All steps timestamped since 2019 | Pass |
| 6 | Value agreement | HR coordinator rekeys from the approved offer | Partial |
| 7 | Correction labels | Corrections entered as ordinary pay changes | Fail |
| 8 | Outcomes | Reneges and early leavers recorded against the application | Pass |
How a partner would summarize it: "Offers, signed letters and hires since 2019; offer-to-hire link only from 2022; pay rekeyed by hand; corrections not labeled." That sentence is the kind of description SourceX can use, and it contains no personal data.
Who answers each check, and who authorizes the conversation
The checks name the owners for you: talent acquisition operations for checks 1, 4 and 8; the HR coordinator who manages templates for checks 2 and 5; the HRIS analyst for checks 3, 6 and 7. None of them is usually the person who can authorize a licensing discussion about personnel records. That is the CEO, normally with the CHRO or head of people and general counsel involved.
Confirm the company baseline before you introduce: 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. The company fit checker covers the same basics.
What stays unknown until SourceX reviews it: what candidate privacy notices and works council agreements allow, how personal data would be removed, which years a buyer would want, and what the company would be paid. Partners never ask for or handle raw records. For the wider value of onboarding material, see onboarding and training records; for a client-intake style of questioning, the MSP client onboarding questionnaire uses a similar approach. The record linkage page covers the identifiers behind checks 2 and 3.
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.
Once the scorecard lets you describe the hiring trail in one honest sentence, register as a partner, check the company against who qualifies, and read the program terms before introducing the CEO.