The $114 million claim that almost went back out
A story about a number we removed, the tooling that nearly put it back, and why defensibility has to be a system, not a memory.
A senior product leader we worked with had a large number on their resume: a $114 million figure attached to a program they had genuinely worked on. The work was real. The number was real. The problem was the connection between them: under the kind of questioning a serious interviewer would bring, the client could not fully defend their claim to that specific figure. Not a lie. Just a claim that would wobble at the exact moment it needed to hold.
So we archived it. In our method, a claim that cannot be defended does not get softened or reworded; it comes out of active use, on the record, with the reason documented. The resume that went out was cleaner and stronger without it, because every claim that remained could stand questioning.
Here is the part most practices would not tell you.
Weeks later, that number nearly went back out the door. Like most modern practices, we generate documents from structured sources with scripts. The submitted resume had been cleaned, and the evidence records had been updated, but one generator script still carried the old content. One routine regeneration and the archived figure would have quietly reappeared in a client-facing document, with nobody deciding to put it there. We caught it before anything shipped.
The fix was not "be more careful." Careful is a memory, and memories fail. The fix was structural: we built an automated check that runs before any generated document can ship. It knows every claim that has been archived from active use, and if one of them appears in an output, the pipeline fails loudly and nothing goes out. The list of archived claims feeds the check automatically, so every future archival decision joins the safety net the moment it is made.
Why write this down in public? Because the near-miss is the honest version of the story every career-services provider tells about quality. Your materials drift. Everyone's do. Old numbers survive in old files, a verb gets changed in one place and not another, and the version of you that reaches a hiring manager stops matching the version you can defend in the room. Most people have no gate between that drift and the send button. We almost didn't either. Now we do, and it fires on every document, every time.
Defensibility is not a writing style. It is a system property: the claims you make, the evidence behind them, and the machinery that keeps the two from drifting apart. That is what we sell, and this is the incident that taught us it has to be enforced by something stronger than good intentions.
The Signal Audit applies this standard to your resume: which claims hold, which wobble, and what to do about it. Read about the Signal Audit.