SOURCE OF TRUTH
The team is working toward one version of the project. The customer or stakeholder expects another.
You go back through the project history — requirements, decisions, approved changes, emails, contracts, or whatever defines the work — and something doesn’t match.
Somewhere along the way, what people believe the project should deliver separated from what was actually agreed.
When the versions don’t match, you need somewhere authoritative to go back to.
That’s your Source of Truth.
What is a project Source of Truth?
As a project evolves, conversations, requests, and assumptions start to shape the work.
But the original agreement doesn’t change unless it’s formally updated.
Over time, the project people are working on can drift away from what was actually committed.
Signs the work no longer matches what was agreed
“We’ve always done it this way”
“That’s just expected at this point”
“It’s not in the contract, but…”
Work continues based on verbal agreements
The contract is rarely referenced
No one is fully sure what is officially included
Why projects lose track of what was actually agreed
Day-to-day work is driven by conversations, not documents.
Teams focus on progress and responsiveness.
The contract starts to feel distant or irrelevant.
But it never stops being the actual source of commitment.
What happens when there’s no clear Source of Truth
Misalignment between expectations and obligations
Work being delivered without clear agreement
Difficult conversations when scope, cost, or timeline is questioned
Not because anyone is trying to create problems.
Because the reference point has shifted.
What to do when different versions of the project exist
Re-anchor the project to what was formally agreed.
Review:
what the contract actually includes
what has been added through conversation
where the gaps exist
Clarity comes from aligning the current work back to a shared, documented source of truth.
If you’ve inherited a project that feels harder than it should be, you’re probably seeing this already.
I write PM Clarity for project managers navigating the messy parts of the job — unclear expectations, shifting priorities, difficult decisions, and the things that don’t always show up in the project plan.
When the project starts moving but no one can point to what was actually agreed, decisions begin drifting without anyone realizing it.
→ See Undocumented Agreement
When updates feel consistent but don’t quite match what was originally approved, the project is no longer anchored to a single source of truth.
→ See Project Story Drift
When changes are discussed in meetings but never tied back to the contract, the real scope quietly shifts over time.
→ See Scope Drift
When you inherit a project and can’t clearly trace what was decided versus what was assumed, you’re working from a fragmented foundation.
→ See Inherited Project Story