The three places a WordPress publishing process skips approval (and the check that closes them)
You approved the draft on Tuesday. It went live on Thursday with two sentences that were never in what you approved. Nobody lied, nobody broke permissions, and no log records anything unusual.
This is the most common failure I see in client publishing workflows, and it is not a permissions problem. It is a record-keeping problem: the site stores the decision ("approved") but not the thing that was decided about .
Here is where it breaks, in order of how often it happens.
1. The approval lives in a different tool than the publish button
The client says "looks good" in an email. The copy is signed off in a Google Doc comment. The Figma shows final. Then the WordPress draft gets edited once more β a price, a date, a legal line β and published.
The CMS has no idea an approval ever happened, so nothing is violated from its point of view.β¦