One Real Episode: How a Work Story Becomes Evidence

During the Iraq Surge, I was responsible for getting roughly 800 soldiers and their equipment onto aircraft — and the commercial scales we used to weigh the loads failed.

So we weighed pallets with bathroom scales.

I know how that sounds. But the aircraft had to be loaded correctly, the deployment timeline did not move, and improvisation was the only option that kept the mission on schedule. It worked. The loads went out, the weights were right, and the deployment held.

If you put that on a résumé, it becomes something like: “Managed aircraft load planning under high-tempo surge conditions.” True. And almost useless — to you, if you ever need to prove it, and to any employer trying to understand what you actually did.

That gap is what this issue is about. Not the résumé line. The episode underneath it — and how to capture it so it becomes something you can stand behind and an employer can examine.

In the first issue of The Guild, I gave you five questions: What was happening? What did you do? What constraints did you face? What changed? What evidence exists? Here is what answering them looks like with a real episode.

What was happening

A deployment surge. Roughly 800 soldiers moving with equipment. My responsibility: aircraft load planning — every pallet and piece of gear weighed and distributed so the aircraft were balanced and legal to fly. Context is the first thing a résumé drops and the first thing an employer needs. Without it, “managed load planning” could mean a warehouse anywhere.

What did you do

When the commercial scales failed, I made the call to improvise with bathroom scales — and owned the method: weighing in increments, cross-checking totals, building the load plans from those numbers. Notice the discipline here. The claim is not “I single-handedly deployed 800 soldiers.” Hundreds of people did that work. The claim is narrower and stronger: I identified the failure, chose the workaround, and stood behind the numbers it produced. A record that separates your contribution from the team’s is worth more than one that absorbs everyone else’s.

What constraints did you face

Broken equipment. A timeline that would not move. The reality that an aircraft loaded wrong is not an administrative problem. Constraints are what turn a story into evidence — they explain why the decisions were hard and what was at stake in them. An employer reading this learns how you think under pressure, not just that you were present for it.

What changed

The loads went out on schedule, with verified weights, and the deployment held. The outcome matters — but notice what the record does not claim. It does not claim zero risk, perfect accuracy, or sole credit. It claims what happened, as far as the evidence supports.

What evidence exists

This is the question most people skip, and it is the one employers care about most. What supports each part of the account? Load plans with dates. Unit movement records. The names of people who were there. And honesty about what is missing: I do not have the bathroom-scale readings in a file somewhere. Some of this lives in documents; some lives in memory and in the memories of others. A person’s account, a supporting document, and independent confirmation are different kinds of support — a record should say which is which.

That is the difference between a résumé line and a Living Professional Record entry. The line says something happened. The entry says what happened, who did what, under what constraints, with what result — and what supports each part.

For a hiring leader, that difference is the whole game. You cannot interview a bullet point. But you can interview an episode: “Walk me through how you verified the improvised weights.” “Who else was involved in the decision?” “What would you do differently with working equipment?” The record gives you something specific to examine — and it gives the candidate a fairer conversation, because they are being evaluated on work they actually did rather than on how well they compress it.

The sequence, again, because it matters: understand the work first, describe it second. Capture the episode before you write the résumé. One episode is enough to start — the record grows from there.

I built a free Manual Builder so you can work through exactly this process yourself, one episode at a time. There is also an automated path for the messy material many of us already have — documents, notes, screenshots — which organizes it into review drafts that you accept or correct before they become your record. Manual capture is always free; your first completed automated package is free too.

Start with one real episode of your own work. Answer the five questions. Notice what you can support, what needs more context, and what you had almost forgotten.

Speak your truth, and make it count!

Jeff Chamberlain