The Promises No One Signed: Why Your Real Obligations Live Outside the Contract
Photo: EU2017EE Estonian Presidency, CC BY 2.0, via Wikimedia Commons
Every company keeps two sets of books. The first is the one accountants reconcile: contracts, statements of work, employment agreements, the paper trail that lawyers review and courts enforce. The second is informal, unwritten, and far more consequential — the accumulating ledger of things someone at your company said would happen, and someone else reasonably believed would happen.
The signed obligations are the ones we manage. The unsigned ones are the ones that manage us.
Consider how work actually gets won and kept in American business. A mid-market manufacturer in Ohio doesn't retain its largest customer because of the master services agreement; it retains that customer because a vice president once said, in a hallway after a plant tour, "if you ever need a rush order, we'll figure it out." That sentence appears nowhere in the contract. It also, in the customer's mind, constitutes the relationship. When the rush order comes and the answer is no, the customer doesn't feel a contract has been broken. It feels a promise has. And in commercial life, the second feeling is far more corrosive than the first.
The Informal Balance Sheet
Implied obligations arise everywhere language travels. A reply-all email in which a founder writes "we'll take care of that" becomes, in the recipient's memory, a service commitment. A job interview in which a hiring manager describes a role as "a clear path to partner" becomes, eighteen months later, the basis for a departure and a grievance. A Slack message telling a team "no one's getting let go this quarter" becomes a covenant, however casually it was typed at eleven at night.
None of this is necessarily binding in a courtroom. Nearly all of it is binding in the court of reputation, which is the court where most businesses are actually judged. Small firms are especially exposed. A national company can absorb a disappointed counterparty; a ten-person consultancy cannot. Word moves through the same networks that generate referrals, and the networks have long memories for broken assurances.
The problem is not that leaders make informal commitments. They must — no deal of any complexity closes on the contract alone. The problem is that nobody keeps track of them.
Running the Handshake Audit
The remedy is an exercise I have come to call the handshake audit. It is deliberately simple, and it is best done annually, ideally in the same week the company reviews its insurance policies, because the two activities address the same category of exposure.
The audit has three steps.
First, collect the promises. Gather every channel through which commitments travel: email threads with clients, meeting notes, sales call recordings, exit interviews, performance reviews, all-hands recordings. Ask a dispassionate reader — outside counsel works, but so does a detail-oriented board member — to flag every statement that a reasonable person could interpret as a commitment. Not legal commitments. Human ones. "We'll get you there." "That won't be a problem." "You'll always have a direct line to me."
Second, sort by consequence. Most flagged statements turn out to be harmless or already fulfilled. The dangerous ones share three traits: they were specific, they were made by someone with authority, and they were made to someone who is still counting on them. A promise to a departed client matters less than a promise to your best engineer. A vague expression of goodwill matters less than a stated timeline. Rank the surviving items by what happens if the expectation is not met.
Third, reconcile or retire. Every informal obligation gets one of two treatments. Either the company formally adopts it — it goes into the next statement of work, the offer letter, the documented benefits policy — or someone with authority has a candid conversation that resets the expectation. What is forbidden is the default state: a promise that lives on in someone else's memory, unowned and unfunded.
What the Audit Usually Finds
Founders who run this exercise tend to discover the same pattern. The formal obligations are few and well managed. The informal ones cluster around three areas: service levels promised during the sales process and never priced, career trajectories described during recruiting and never structured, and flexibility promised to employees during periods of crisis — remote arrangements, modified hours, protected projects — that later collide with operational reality.
The last category deserves particular attention. The commitments made in the emergency become the baseline in the recovery. The company that said "do whatever you need to do to get through this spring" in April will be held to that standard in October, by people who heard it as policy rather than panic.
Candor Is Cheaper Than Breach
There is a school of thought that informal promises are best left unexamined — that ambiguity is a buffer, and a promise forgotten is a promise avoided. This is a founder's fallacy. The counterparty never forgets. Asymmetry of memory is itself a source of grievance: the employee recalls the exact sentence; the founder recalls the meeting only dimly. The audit's real function is not liability management. It is honesty at scale — making sure the company knows what it has told people, so it can decide deliberately whether to keep its word.
A signed contract protects the company from its counterparties. The handshake audit protects the company from itself. Between the two, most of a firm's reputation is made — and most of it is made in conversations no lawyer ever saw.