An Approval That Is Easy to Edit Is Not an Approval

This week I locked a document so nobody could edit it. On purpose.

Not because I do not trust my team. Because I once trusted too quickly, and it burned me.

I used to think an approval was about getting an "okay" from people. Now I think an approval is about freezing that "okay", so it cannot quietly change afterwards.

A signature that still exists but means nothing

Think about signing a contract. Then someone changes one number inside it, silently, after you have signed.

Your signature is still on the page. It just no longer means anything.

Decision documents at work fail the same way all the time. The format looks official, the approver names are right there, everything looks legitimate. But the content is no longer the content people agreed to.

How decisions drift without anyone noticing

I have spent 20 years building digital products, and I have seen this pattern everywhere. Small startups, large companies, five-person teams, organizations with hundreds of people.

It always plays out the same. Everyone agrees in the meeting. The document gets stamped "final". Three days later the content has shifted, and nobody can tell you when it moved or who moved it.

Here is the uncomfortable part: this rarely happens because someone is acting in bad faith. It happens because everyone thinks they are helping. Someone cleans up a sentence. Someone updates a number to be more accurate. Then a new line of scope slips in because "we did discuss it last week".

Each edit looks tiny. Add them up and the document everyone approved last week has become a different document. And the approval is still sitting on it, exactly like that signature on the altered contract.

For me this is not a cosmetic problem. I currently run four product teams as Director of Product at a superapp in the MENA region, and almost every decision that matters cuts across teams. When a decision drifts silently, it is not one person who crashes. Every team executing against that decision crashes with it.

So I locked the document

This week one of our decision documents needed a finance sign-off. I locked the file. Genuinely uneditable, including by me.

There is exactly one rule attached to it: if the content changes after approval, the approval is void. Everyone re-approves from zero.

Annoying? Yes. But the annoyance is not a side effect. It is the whole point.

Change has to be expensive

Once editing the document costs something, people think twice before changing it quietly. The small "just tidying up" edits filter themselves out, because they are not worth dragging everyone back through re-approval.

And changes that genuinely matter? They still happen. They just walk through the front door now. Everyone sees them, everyone agrees again, and there is still exactly one version of the truth.

My working principle is simple:

An approval that can be quietly changed after sign-off is not a decision. It is meeting theater.

If an agreement can be undone without anyone knowing, then nobody ever really agreed. You just had people sitting in the same meeting.

How to apply this without the drama

You do not need expensive tooling. You need discipline at three points:

1. The moment a decision is approved, freeze the document. Lock the file, export a PDF, or snapshot the final version.
2. Write the rule into the document itself: any change after approval voids the approval, and everyone re-approves from zero.
3. Route future changes through a visible path. A separate amendment or a version history, never a silent edit to the same file.

It looks like added bureaucracy. What you are actually buying is one of the rarest things in any workplace: everyone holding the same version of the truth, and knowing exactly when that version changed.

What I thought would slow us down made us serious. What I thought was friction is what made our decisions mean something.

Open the most important decision document your team has right now. Is it still the same document everyone said "okay" to?