We didn’t discover the problem during an HR review.
We discovered it when someone asked a simple question.
The answer should have taken thirty seconds.
Instead, one manager pulled up a document from a shared folder.
Another manager forwarded a newer version from an email.
Then someone found a handbook containing different language altogether.
We had three versions of what appeared to be the same workplace policy.
And nobody could immediately tell me which one actually represented our current practice.
None of the Documents Looked Obviously Wrong
That’s what made the situation dangerous.
If one document had been clearly outdated, the problem would have been easy.
But all three looked legitimate.
They had company branding.
They used professional language.
They had been distributed internally at some point.
A manager could reasonably open any one of them and believe it was current.
The problem wasn’t that we lacked documentation.
We had too much documentation without enough control over it.
I Wanted to Know How We Got There
Nobody intentionally created three competing policies.
It happened gradually.
The original handbook contained Version A.
Later, management changed part of the process.
Instead of replacing the original document everywhere, someone created a separate instruction.
That became Version B.
Months later, a location encountered a practical problem and adjusted how managers handled the situation locally.
That became Version C.
Each individual decision seemed reasonable at the time.
Together, they created a mess.
Shared Folders Can Become Document Graveyards
We used to think:
“It’s in the shared drive, so everyone can find it.”
That wasn’t the same as having a controlled source.
The folder contained:
Policy.pdf
Policy-New.pdf
Policy-Final.pdf
Policy-Final-Updated.pdf
Policy-2025.pdf
Which one would a manager choose?
Probably whichever appeared first in search results.
That isn’t a policy-management process.
It’s document roulette.
Email Made the Problem Worse
Managers frequently saved important instructions from email.
That created another hidden version of company policy.
Someone might have received updated guidance six months ago and continued following it correctly.
Another manager who never saw that message would continue using the older handbook.
Both believed they were following company rules.
That’s how inconsistent treatment can develop without anyone deliberately deciding to treat people differently.
I Stopped Asking “Do We Have a Policy?”
That question was too easy to answer.
Of course we had one.
We had three.
I started asking better questions:
Where is the current version?
Who owns it?
When was it last reviewed?
Who approves changes?
How are managers told that something changed?
What happens to the old version?
Those questions revealed whether we had a real process behind the document.
Local Practices Were the Hardest Part
Written documents weren’t our only source of inconsistency.
Some managers had developed their own interpretations over time.
One location handled a situation one way.
Another location handled it differently.
Neither variation necessarily existed in a formal document.
It was simply:
“That’s how we’ve always done it here.”
Those unwritten versions were harder to find because they didn’t appear in any folder.
I Asked Managers to Explain the Process Without Looking It Up
This became an unexpectedly useful test.
I picked a policy and asked several managers:
“How does this work?”
I wasn’t testing them.
I was testing the company.
If five managers gave five substantially different answers, that told me our documentation or communication wasn’t working.
A policy only creates consistency if the people applying it understand the same thing.
I Created One Authoritative Source
The biggest improvement wasn’t writing more policies.
It was deciding where the current policy lives.
One controlled location.
One current version.
Clear ownership.
If someone downloads a copy for reference, fine.
But that copy isn’t automatically the permanent source of truth.
When there’s uncertainty, everyone knows where to check.
I Added Version Information
I wanted to be able to answer:
“When did this change?”
That meant keeping basic revision information.
Nothing complicated.
For important documents, I wanted:
- Current version
- Effective date
- Review date
- Responsible owner
- Record of significant revisions
Now “I think this is the newest one” wasn’t good enough.
Old Versions Weren’t Simply Left Beside the New Ones
Historical records can be useful.
But historical and current documents shouldn’t be indistinguishable.
We separated archived versions from active material.
That allowed us to preserve history without inviting managers to accidentally use an obsolete instruction.
Changes Needed a Communication Process
Updating the document wasn’t enough.
If a manager had memorized the old rule, changing a PDF somewhere wouldn’t magically update their behavior.
So every meaningful policy change needed a second question:
“Who needs to know?”
Depending on the change, that could mean:
- Managers
- A specific location
- A particular team
- The broader workforce
Document maintenance and communication became part of the same process.
I Became Careful With Exceptions
Exceptions are where policies often start multiplying.
A manager encounters an unusual situation.
They create a workaround.
The workaround happens again.
Eventually, everyone at that location treats it as a permanent rule.
I don’t assume exceptions are always wrong.
But I want them identified as exceptions instead of quietly becoming another version of company policy.
State Differences Can Be Legitimate
Not every variation should be eliminated.
A company operating across different states may need different practices because applicable requirements can vary.
That’s different from two managers inventing conflicting rules.
The goal isn’t:
“Every document must say exactly the same thing everywhere.”
The goal is:
“Every difference should exist for a reason.”
That’s a much more useful standard.
Where Trion Solutions Can Become Relevant
Policy administration becomes harder as a company grows.
More managers create more interpretation.
More locations create more communication paths.
Additional states can introduce different requirements.
A PEO relationship with Trion Solutions can provide HR guidance and support around workplace administration while the company establishes clearer processes.
But outside support doesn’t remove the company’s responsibility to know which rules it has actually adopted.
Someone inside the organization still needs ownership.
My Policy-Control Checklist
For an important workplace policy, I now want to know:
✅ Where is the current version?
✅ Who owns the document?
✅ When did it become effective?
✅ Are older versions clearly archived?
✅ Have affected managers been informed?
✅ Are local differences intentional?
✅ Are exceptions being tracked?
✅ Can managers explain the rule consistently?
✅ Is there a process for future changes?
The Real Problem Wasn’t Three PDFs
The PDFs were just evidence.
The actual problem was that we didn’t have a reliable method for turning a management decision into one consistent company practice.
A policy can be beautifully written and still fail if half the organization follows an older version.
That’s why I no longer measure policy quality by asking:
“Do we have this documented?”
I ask:
“If I asked five managers today, would they all know which version actually applies?”
If the answer is no, the company doesn’t really have one policy.
It just has several documents competing to become one.