Cop Rules: A plain-English look at how real-world systems work—when the brochures and headlines aren’t telling the truth.
In the modern workplace, your memory doesn’t count. What’s written down counts.
Friday afternoon. Someone drops a “quick question” on you.
You answer. You do the work. You deliver.
Monday morning? “We never asked for that.”
Or my personal favorite: “That’s not what we agreed.”
Welcome to the part of adult life where amnesia becomes a management style.
Here’s the Cop Rule: Email is evidence.
Not because you’re paranoid. Because the workplace runs on plausible deniability, and evidence ruins that party.
Cop Rules: Email Is Evidence
Rule #1: If it isn’t written down, it didn’t happen.
Verbal agreements are like smoke. They vanish when the heat shows up.
What it looks like:
A manager gives you an assignment in the hallway, then later acts like it was your idea. Or the scope “evolves” after you’ve already shipped the work.
What you do:
Send the calm recap: who decided what, and by when.
Rule #2: Meetings are where accountability goes to hide.
A meeting with no record is a meeting that never happened.
What it looks like:
Ten people “align,” nobody owns anything, and you leave holding the bag.
What you do:
Send the recap with Owner + Deadline + Definition of Done.
Rule #3: The first version of the story is usually the most honest.
Later versions are “edited for optics.”
What it looks like:
The plan changes after failure. Suddenly you’re hearing, “We always intended…” (No. You didn’t.)
What you do:
Keep the early emails. Keep the screenshots. Keep the timeline.
Rule #4: Scope creep is just theft with a polite smile.
They keep adding “one more thing” until your job becomes three jobs.
What it looks like:
“Since you’re already in there…”
Translation: “We’d like more value for the same pay.”
What you do:
Ask the magic question: “What should I deprioritize to make room for this?”
Rule #5: Evidence beats emotion.
No speeches. No outrage. No “as you know.”
Just facts.
What you do:
Write like you’re explaining it to a neutral third party who just arrived on Earth.
What to Document (and what to stop trusting)
Document anything that could later be denied:
- Decisions: what was decided, by whom
- Scope: what’s included / excluded
- Deadlines: dates, time zones, dependencies
- Approvals: “Looks good / proceed”
- Constraints: budget, staffing, tools, access
- Hand-offs: who owns it next
- Changes: “Per today’s update, we’re now doing X instead of Y”
Stop trusting:
- “We’ll circle back”
- “Let’s keep it informal”
- “No need to put it in writing” (translation: I might deny it later)
The Toolbox: Copy/Paste Templates (use these forever)
1) The Meeting Recap (the accountability staple)
Subject: Recap: [Topic] — decisions + next steps
Hi all — quick recap from today:
- Decision: [What was decided]
- Owner: [Name]
- Due: [Date]
- Next steps:
- [Task] — [Owner] — [Due]
- [Task] — [Owner] — [Due]
If I missed anything, reply-all with corrections. Thanks.
2) The Scope Lock (prevents “But we thought you were also…”)
Subject: Confirming scope for [Project]
To confirm, I’m delivering:
- Included: [A, B, C]
- Not included: [D, E]
- Success looks like: [simple measurable outcome]
If scope changes, I’ll update timeline accordingly.
3) The “Which One Drops?” Boundary (for drive-by assignments)
Happy to take this on. To fit it in, which should I deprioritize: [Task A] or [Task B]?
4) The Deadline Reality Check (without sounding “difficult”)
Given current workload and dependencies, the earliest realistic delivery is [date].
If we need [earlier date], we’ll need to adjust scope or add support.
5) The “Per Our Conversation” Receipt (use sparingly, but use it)
Per our conversation, I’m proceeding with [X] by [date]. Please reply if anything differs.
6) The Approval Trap Blocker (so nobody can later say you “went rogue”)
Before I move forward, please confirm approval for [plan]. Once approved, I’ll proceed.
How to Write “Evidence Emails” Without Becoming a Pain in the Neck
This is where people mess up: they turn evidence into attitude.
Do:
- Keep it short
- Use bullets
- Use dates
- Assign owners
- Ask for corrections (“reply-all if I missed anything”)
Don’t:
- Accuse
- Snark
- Threaten
- Write angry (draft it, walk away, rewrite it)
Think of it like this: you’re not “building a case.”
You’re preventing a case.
When to Escalate (and how)
If someone repeatedly denies reality, stop debating and start documenting.
- Send a recap.
- Attach the prior thread if needed.
- Ask for a clear decision.
- If it affects deadlines, state impact plainly.
Example:
“Without confirmation by Tuesday 3 PM, delivery moves from Friday to next Wednesday.”
No drama. Just physics.
The Closer
The workplace has two currencies: results and narratives.
You’re already producing results. Now protect the narrative.
Because when things go sideways, nobody remembers your good intentions.
They remember what can be proven.
Cop Rule: Email is evidence.
And evidence beats excuses every time.
Exhibits
- Exhibit A — “The Cliché Playbook” (the official dodge language)
https://chatrodamus.com/2025/07/23/the-government-cliche-playbook-when-clear-means-anything-but/ - Exhibit B — “Transparency Theater” (when ‘clear’ means black ink)
https://chatrodamus.com/2025/07/24/transparency-theater-why-every-government-promise-comes-with-black-ink/ - Exhibit C — “Normal Is a Weapon” (how institutions police behavior with labels) https://chatrodamus.com/2026/01/09/normal-is-a-weapon/
- Exhibit D — “Those Pesky Phone Bots” (the never-ending scam machine) https://chatrodamus.com/2025/07/25/those-pesky-phone-bots-the-scam-that-wont-die/
- Exhibit E — “AI-Face Credibility Laundering” / online dating safety
https://chatrodamus.com/2026/01/11/love-lies-and-algorithms-online-dating-safety-in-2026/ - Exhibit F — “Sovereign Citizens” (how reality collapses without paperwork) https://chatrodamus.com/2025/07/26/sovereign-citizens-from-am-i-being-detained-to-call-my-lawyer-the-circus-never-ends/
Bunker Notice
If you made it this far, you’re bunker material. Join the Bunker Briefing—my unfiltered monthly dispatch from Bunker #69.