UNDOCUMENTED AGREEMENT
Someone says, “I thought we agreed to that.”
You remember the conversation. You don’t remember making the decision.
Now the customer expects it, the team thinks it’s part of the plan, or work has already started — but no one can point to where it was actually approved.
When people begin acting as though a decision has been made—even though it never was.
What is an Undocumented Agreement?
A decision is discussed.
It sounds reasonable.
No one objects.
But it’s never clearly documented or confirmed.
Later, it shows up as an expectation.
Signs a conversation has turned into a project expectation
“We talked about this already”
“I thought we agreed to include that”
“Wasn’t that part of the plan?”
Work gets added without a clear decision
No one can point to where it was approved
Why project conversations get mistaken for decisions
Conversations feel like alignment.
But without documentation, there is no shared reference point.
Each person walks away with their own version of what was decided.
What happens when no one can confirm what was agreed
Confusion about what was actually agreed
Work expanding without visibility
Tension between teams and stakeholders
Not because people are careless.
Because nothing made the agreement explicit.
What to do when an agreement was never documented
Separate conversation from commitment.
If something matters:
👉 write it down
👉 confirm it
👉 make it visible
If this feels familiar, you’re not the only one dealing with it.
I write about patterns like this every week in PM Clarity — how to spot them earlier and what to do before they turn into rework.