Track-Record Forensics

In one search, years ago, we had two CFO candidates whose CVs were, at the line that matters, identical: Chief Financial Officer, industrial group, ~€400M. The first, when we audited the role, turned out to have owned treasury, tax, three refinancings, the board relationship, an M&A pipeline, and a function of sixty across four countries. The second had the same title, the same revenue figure, a group of comparable size, and had consolidated reporting spreadsheets for a parent company that kept treasury, banking, and every decision above €50,000 in another city. He was not lying. He had the title; the group had the revenue; every word on the page was true. The page was simply testimony, and testimony had been formatted to resemble record.

That distinction is this chapter. A CV is not a record of a career. It is the candidate's account of a career, assembled by an interested party, denominated in a currency of titles and revenue figures and team sizes whose exchange rate varies wildly across companies, countries, and eras. As Chapter 2's table showed, it is nearly worthless as prediction when taken at face value: years of experience, unverified, predicts performance at .07, a rounding error wearing a résumé. Yet the same table put verified track record at the foundation of the evidence hierarchy, the base layer everything else cross-checks against. The entire difference between .07 and foundational is one activity, forensics, and forensics is cheap, teachable, and almost never done. This chapter does it in four moves: scope the mandate, audit the perimeter, attribute the results, and verify the facts.

First move: know what you are looking for

Forensics without a target is tourism, so the work starts before any candidate exists, at the client's table, in the seat Chapter 4's chair map called chair one, where domain expert and assessor together translate the mandate into demands. Two disciplines, briefly, because they govern everything downstream.

Translate the title into a world. Chief Financial Officer names a genus, not a job. A CFO in a founder-led family group is a diplomat with a spreadsheet; the real work is the owner relationship, the boundary between family and firm, capital raised on trust. A CFO in a listed multinational is an institutional performer, working markets, auditors, quarterly theater, a machine of two hundred. Same title, different species. The failure mode of Chapter 1's opening vignette, the magnificent CFO who could not live with an owner who reversed decisions at Sunday lunch, was a species error, not a quality error. Write the role as a set of world conditions and demands: what this person must actually do, tolerate, and answer to, and what must be true in twenty-four months for the hire to have worked.

Type the situation honestly. Turnaround, realignment, scaling, stewardship: the mandate's real type, which Chapter 1 showed executives routinely misdiagnose and Chapter 13 showed boards romanticize. The kindest expensive sentence in this book, this mandate needs a steward, not a screenplay, is spoken here or never.

The output is a demands list. Now the candidate's history can be interrogated against it, rather than admired in general.

Second move: the scope audit

The scope audit asks one question of every role on the CV: what did this person actually own? Not the title's implication, but the operational truth, in six dimensions, each with a probe that sounds innocent and isn't:

Perimeter: What was inside your responsibility, and what was explicitly outside it? (The second half of the question does the work; real operators answer it instantly — they spent years negotiating that border.) P&L truth: Was the number you carried revenue you could influence, cost you controlled, or a consolidation you reported? Who set the targets? Decision rights: What could you decide alone — the largest hire, spend, price, exit you made without asking anyone? (This single probe separates our two CFOs in under a minute.) People: Direct reports by name and role; dotted lines honestly dotted; who hired and fired in your function — you, or elsewhere? Reporting reality: The org chart says you reported to the CEO; who did you actually clear things with? Inherited versus built: Of the function you're describing, what existed on your first day? — Chapter 10's archaeology, applied to structures instead of people.

Two supports make the audit sharp. The first is the title-to-scope map, the accumulated knowledge of what titles actually denote at specific companies in specific markets: that Managing Director at one Milanese group means a shareholder-adjacent principal and at its competitor means a senior salesman; that German Geschäftsführer carries statutory duties a British MD never sees; that Gulf conglomerate titles inflate a level against Northern European usage. This map is precisely the vertical recruitment experience Chapter 4 defined, calibration you cannot get from having held the jobs, only from having audited hundreds of them, and it is why the scope audit is faster and deadlier in a specialist's hands. The second support is paper: organograms the candidate can sketch, statutory filings, delegation-of-authority documents where they exist, artifacts requested casually ("could you draw me the structure as it was?") and compared quietly.

Third move: attribution

The perimeter tells you what they owned. Attribution asks what, within it, they caused. Chapter 9 carries the interview-level machinery; here sit the two forensic tools that frame it.

The timeline overlay. Lay the claimed results against the tenure dates and ask the questions time answers for free. Did the inflection precede their arrival? (Then they surfed it.) Did it survive their departure? (Chapter 10's two-years-after test, in numbers.) Did the celebrated turnaround's hard decisions, the closures, the write-downs, happen under the predecessor, leaving the candidate the harvest? Public companies yield this to an afternoon with the filings; private ones yield it to the second ring.

The decomposition demand. For each headline result: how much was market, how much platform, how much team, how much predecessor's pipeline, and what, specifically, was yours? Chapter 9 established the tell: strong operators volunteer this decomposition, almost with relief, because they have done it privately for years; performers resist it, because the undecomposed number is the act. Either way, the components they claim become Layer-3 hooks for Chapter 7's references: she says the pricing architecture was hers — you were there; whose was it?

Fourth move: the chronological spine

The instrument that assembles the audit is the chronological career-history interview, walked in order, role by role, no skipping, adapted with credit from the Topgrading tradition and redesigned in two respects that matter. The classic method leans on what its authors call the threat of reference check: announcing that every claim will be verified, to frighten embellishment out of the room. This book keeps the verification and drops the menace. The same deterrent arrives with more dignity as transparency, our process checks what we discuss; I'll be asking who saw each of these chapters, which is simply Chapter 7 doing its job out loud. And where Topgrading's chronology serves a proprietary A-player taxonomy, ours serves the demands list from move one.

Per role, five questions, unchanging: How did you get the job? (Sought, recruited, inherited, rescued — the entry tells you how the market priced them at that moment.) What did you find? (The mandate archaeology: what the role actually was — launch, cleanup, stewardship — which is the fact that acquits or convicts half of Part III's flags: launches without landings are damning in a landing mandate and honorable in a launch one.) What did you actually do? (The scope audit and decomposition, executed here.) Why did you leave? (Singly, often rehearsed; in sequence, a career's reasons-for-leaving form a pattern no rehearsal anticipates — toward something or away from something, upward or sideways, their timing or someone else's.) And what happened after you left? (The question candidates least expect and time most honestly answers.)

Then read the assembled spine for shape. Does scope actually grow, or do titles inflate over constant perimeter? Do the same situations recur, the serial rescuer, the serial escapee? Do the gaps have stories, and do the stories have witnesses? A career's shape is testimony too, but testimony with dates, and dates can be checked.

Fifth move: verification — the layer beneath references

Everything above still travels through the candidate's mouth. The final move goes around it, and the base rate says you must: in recent screening-industry data, nine in ten organizations report finding discrepancies during candidate verification, employment history and education leading the list. Most are small. The habit of checking is what keeps them small.

The layers, run proportionate to the role and lawful in the jurisdiction: Credential and employment verification — degrees, dates, titles, against registries and issuing institutions, never against the CV alone. Public record — statutory filings, board registrations, the companies-house trail across borders (an afternoon that verifies directorships, tenures, and occasionally reveals the directorship the CV forgot). Press and archive — the celebrated transformation should have left footprints in trade press and archived company communications; its total absence is a question. Adverse media, litigation, and sanctions screening — for C-level, fiduciary, and regulated roles, at finalist stage, tightly scoped: role-relevant risk, not biography mining. The proportionality rules from Chapter 7 govern here with extra force — data minimization is law in most of this firm's jurisdictions and decency everywhere — and the sequencing rule likewise: deep verification is a finalist-stage activity, both because privacy demands it and because the audit's questions are sharpest when the interviews have supplied claims to check.

Red flags — with their innocent explanations

Title inflation against the map. Innocent surprisingly often: title conventions genuinely differ across markets and eras, and a candidate carries the title their company gave them. Charge the scope, not the word. The unverifiable private-company decade. Innocent: privacy is real, filings are thin, and NDAs exist; the remedy is the second ring, not suspicion. But a career engineered entirely below verification's waterline is itself a data point. Timeline gaps and overlaps. Innocent: garden leave, family care, a quiet interim mandate under confidentiality. Ask before inferring; the flag is the gap that changes explanation between tellings. "After I left, it collapsed." Sometimes true, and when true, diagnostic in the candidate's favor. But it is also the easiest unfalsifiable boast in the repertoire, so it earns belief only from witnesses and numbers, like everything else in this chapter.

Instrument: the scope-audit sequence

Printed for the interview file, hooks pre-wired to Chapter 7:

1. Draw me the organization as it was — you, your reports by role, your boss, the dotted lines. (Artifact request; compare later.)
2. What was explicitly outside your responsibility? (Perimeter, from the far side.)
3. The number on the CV — influenceable revenue, controlled cost, or reported consolidation? Who set your targets? (P&L truth.)
4. Largest decision of each kind — hire, spend, price, exit — you made without anyone's sign-off. (Decision rights.) → hook: confirm with then-chair/boss.
5. Of what you've described, what existed on day one? (Inherited vs. built.) → hook: predecessor or veteran witness.
6. For the headline result: decompose it — market, platform, team, you. (Attribution.) → hook: the component claimed as "you," to the second ring.
7. Why did you leave — and what happened there after you left? (Pattern data; time's testimony.) → hook: post-departure witness.
8. Verification layer, finalist stage: credentials, registries, filings, press, and — where the role warrants — adverse media and sanctions, tightly scoped, consented, logged.

Where the rules run out

The honesty paragraph. Forensics narrows the attribution problem and cannot close it. Chapter 9 said it and it stays said: even a diligent audit leaves residual uncertainty about how much of a verified result was the person, and the recommendation carries that uncertainty forward honestly. Private-company careers resist the public layers; cross-border verification is uneven in exactly the corridors this firm works (registry quality in the Gulf and Central Asia is not Companies House, and the chapter's method degrades gracefully there rather than pretending otherwise). The nine-in-ten discrepancy figure is industry survey data, credible and unaudited, graded [S] and used for the habit it justifies, not the decimal. And one boundary against zeal: forensics verifies the capability register and must not creep into biography mining. The perimeter of the audit is the demands list from move one, and curiosity beyond it is not diligence; it is a privacy violation with a spreadsheet. What the verified record still cannot tell you, whether this true, owned, decomposed career can be lived again, in your client's world, by choice, is Part IV's question, and no registry holds the answer.

Notes and sources

Evidence grades: [M] meta-analytic/systematic; [L] peer-reviewed primary; [S] credible practitioner/survey; [T] flagged synthesis.

• Years of experience at .07; verified-record logic: the post-2022 validity matrix (Sackett et al.), per Chapter 2. [M]
• Results embedded in platforms and teams; timeline logic: Groysberg (2010); Bidwell (2011). [L]
• Chronological career-history interviewing: Topgrading tradition (Smart), credited and redesigned; outcome-scorecard logic: ghSMART/Who tradition, credited. [S]
• Nine-in-ten discrepancy finding (employment history 64%, education 47% leading): screening-industry survey data (2025), practitioner-grade. [S]
• Verification layering, proportionality, finalist-stage timing, jurisdictional constraints: the reference-and-verification research underlying Chapter 7 (OPM/MSPB guidance; GDPR-family minimization principles). [S]
• Title-to-scope mapping as specialist calibration: Chapter 4's Kahneman–Klein framework applied; the map itself is practice knowledge. [T]
• Situation typing: transition literature (Watkins's STARS tradition). [S/L]
• The five-question spine, the after-you-left probe, the demands-list method: this book's synthesis from practice. [T]