The Sentence That Should Have Said More

Followed exactly as written, and still a lawsuit

A company's expense policy says: "Employees will be reimbursed for reasonable business travel expenses." Eighteen months and one lawsuit later, that nine-word sentence is Exhibit A in a wrongful termination claim — not because it was violated, but because it was followed exactly as written.

What actually happened

An employee submitted a $40 daily meal expense while traveling for a client meeting. Her manager approved it without comment. Over the next year, she kept submitting $40 a day for every trip, reasoning that since the first submission was approved, $40 was now the established "reasonable" amount.

Her manager never objected — he simply never noticed the pattern, because nothing in the policy defined a number or required re-justifying each submission.

A new finance director took over expense review, flagged eleven months of $40 meal claims as excessive against the company's actual travel norms, and terminated her for "policy violation" — submitting expenses that weren't reasonable. She sued, arguing every single claim had been approved and she had never been told $40 wasn't reasonable.

Where the actual gap sits

The clause says "reasonable business travel expenses." It never says reasonable by what standard — a fixed dollar cap, a percentage of typical local costs, a per-city rate — and it never says whether one approval sets a precedent for every future claim or has to be judged fresh each time.

Every party in this dispute was reading the same nine words honestly. The employee read "reasonable" as whatever had already been approved once. Her original manager read it the same way, which is exactly why he never flagged the pattern.

The finance director read "reasonable" as a standard that has to hold up against actual market rates regardless of prior approvals — and by that reading, eleven months of $40 claims were never actually reasonable at all.

Why this dispute was entirely preventable, and where

The failure didn't happen at the moment of termination, or even at the moment the pattern started repeating. It happened the moment the clause was drafted, well over a year earlier.

Three things were left completely unspecified: what "reasonable" actually means in dollar terms, whether an approved claim sets a standard for future claims or has to be re-justified each time, and who has authority to revise that standard once it's been established in practice.

None of those three gaps were visible while things were going fine. All three became load-bearing the instant a new reviewer looked at the exact same facts through a different lens.

What the sentence needed to say instead

"Employees will be reimbursed for business travel meal expenses up to $30 per day, subject to review regardless of prior approvals." Nine more words. Every one of them closes a specific gap the original left open: a number, not a feeling — so "reasonable" can't quietly drift upward through repetition. An explicit statement that prior approval doesn't set precedent — so one manager's oversight doesn't become an entitlement.

None of these additions are exotic legal language. They're just the specific facts the original sentence assumed everyone would agree on without anyone actually writing them down.

What this reveals about policy language generally

A policy clause doesn't fail the moment it gets misread. It fails the moment it was drafted, if it left a genuinely important fact unspecified — what standard applies, whether precedent counts, who can revise it.

That gap can sit completely invisible for months or years, doing no damage at all, right up until circumstances change enough that two honest readers land on opposite sides of it. By then, the actual problem isn't the dispute. It's a sentence that was always missing something, discovered only once it mattered.