
The Data You Need Before Firing Anyone: An Owner's Pre-Termination Checklist
TL;DR
- •Review 30 days of plan vs fact data before any termination conversation.
- •Separate individual output from team and system constraints.
- •Document the gap, the coaching, and the owner's decision criteria in writing.
I sat across from a founder who had just fired his head of operations. He was confident in the decision until I asked for the data behind it. He had none — only a Friday feeling that things weren't moving fast enough.
That moment is common. Owners of 30-500 person companies often make termination calls based on vibes, recent incidents, or a single bad month. When the conversation turns to severance, references, or wrongful termination claims, the owner realizes there is no paper trail — just memory.
This article is about the data you need to collect before you fire someone, not after. If you run a company of 30 to 500 employees, you need an objective baseline that separates performance problems from process problems, and personal issues from systemic ones.
Definition: Plan vs Fact
Plan vs Fact is a visibility method where you compare what was committed (plan) against what was actually delivered (fact) over a set period. The gap between them shows where work breaks down — and whether the person or the process is responsible.
Definition: Pre-Termination Data
Pre-termination data is the objective record of performance, feedback, and context that an owner assembles before making a termination decision. It protects the company legally and keeps the decision honest.
What Most Owners Get Wrong
Owners usually fire based on the most recent mistake. A missed deadline, a client complaint, or a tense meeting becomes the justification. But that single event rarely tells the full story.
What you actually need is a pattern. Did this person consistently miss commitments? Was the work unclear to begin with? Did other teams block them? Without 30 days of daily or weekly updates, you cannot tell the difference between a performance problem and a management problem.
The Five Data Points to Review Before Firing
1. Plan vs Fact Over the Last 30 Days
Look at what this person committed to deliver and what they actually delivered. Not what you remember from meetings — what is written down.
If the plan was vague, the fact will be vague too. That is a management failure, not necessarily an employee failure. If the plan was specific and the fact shows repeated misses, you have a performance signal worth acting on.
2. Blocker History
Check what this person raised as blocked, and when. A performer who surfaces blockers early is doing their job. A performer who stays silent until the deadline passes is not.
Blockers also reveal whether the person is stuck because of missing access, unclear requirements, or dependencies on other teams. Firing someone for a system constraint punishes the wrong person.
3. Coaching and Feedback Trail
Before termination, there should be a written record of what was discussed, when, and what changed after. Not a formal HR dossier — just dated notes from 1-on-1s or status updates.
If there is no coaching trail, the termination will look arbitrary to the rest of the team. That damages trust more than the firing itself.
4. Team and System Context
Compare this person's output to their peers in the same role. If everyone in sales is missing targets, the problem is the product, the market, or the sales process — not one rep.
Also check whether the person was hired into a broken workflow. A great employee cannot succeed in a process that requires three manual handoffs and no documentation.
5. The Decision Criteria You Will Use
Write down what would have to happen for you to keep this person instead of firing them. If you cannot name it, you are not ready to terminate.
This prevents post-hoc rationalization. It also gives you a clear bar for the next hire in that seat.
Manager Scan: Pre-Termination Review Example
Here is what a 2-minute owner scan looks like before a termination conversation:
- Role: Head of Customer Success
- Plan vs Fact (30 days): 6 of 10 committed renewals delivered
- Blockers raised: 2 (both resolved by engineering)
- Coaching conversations: 3 (weeks 1, 2, and 3)
- Peer comparison: other CSMs hit 8 of 10 renewals
- System context: renewal process requires manual data entry from three sources
- Decision: terminate for performance, with severance and documented rationale
This scan takes minutes if you already collect daily updates. Without them, it takes weeks of reconstruction.
Micro-Case: What Changes After 14 Days of Visibility
A founder of a 60-person logistics company wanted to fire an operations manager who kept missing dispatch deadlines. Before the conversation, I asked him to pull 14 days of plan vs fact data.
The data showed the manager hit 11 of 14 daily targets. The three misses coincided with carrier delays and warehouse staffing gaps — issues outside the manager's control. The founder did not fire him. Instead, he fixed the carrier escalation process.
Two weeks later, dispatch times improved without any personnel change. The owner kept a good employee and solved a real operational problem.
Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.
Tool Tip: Making the Data Visible Daily
If you do not have plan vs fact data ready, you are flying blind. The fastest way to build it is a lightweight daily update that asks each person what they planned, what happened, and what is blocked. That creates the record you need before any difficult HR decision.
Tool tip (AiAdvisoryBoard.me): Start with the free org chart tool: enter your website and headcount, and it maps departments, tasks, and routine work that can be handed to AI agents — plus the visibility layer owners need to see Plan → Fact → Gap across the company. https://aiadvisoryboard.me/?lang=en
FAQ
How much data is enough before firing?
At minimum, 30 days of written plan vs fact updates, plus any coaching conversations. Less than that, and you are deciding on memory, not evidence.
What if the employee committed a serious violation?
Immediate termination for cause still requires documentation of the incident, witnesses, and any policy breached. The pre-termination data review runs in parallel, not instead of, that record.
Do I need to show the employee their data before firing?
You do not have to share the full owner scan, but you should be able to cite specific missed commitments and prior feedback. Vague references to "performance issues" invite disputes.
What if my team does not write daily updates?
Start now. Two weeks of updates is better than zero when the next difficult conversation comes.
Can AI help me collect this data?
AI can summarize daily updates and surface plan vs fact gaps, but it cannot replace your judgment. The owner still decides what the data means.
Conclusion
Firing someone is one of the heaviest decisions an owner makes. Make it on data, not on a bad afternoon. Review plan vs fact, blockers, coaching history, peer context, and your own decision criteria before you schedule the termination meeting.
If you want to see the Plan → Fact → Gap across your company before your next personnel decision, run the 7-day diagnostic.
Tool tip (AiAdvisoryBoard.me): The 7-day diagnostic builds a map of your real processes and shows where work actually stops — so you can see performance problems before they become termination problems. https://aiadvisoryboard.me/?lang.en
If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works.
https://aiadvisoryboard.me/?lang=en
Frequently Asked Questions
Read with AI
Open this article in your assistant — it will summarize it and help apply it to your company.
Show the prompt
Read the article https://aiadvisoryboard.me/blog/owner-data-before-firing-pre-termination-checklist.md and summarize the key points. Then ask me about my company (industry, team size, what takes the most time) and explain which ideas from the article apply to us and where to start.
The pillar guide for "Owner Visibility Before AI" linking every article in this cluster.

Implements AI agents in companies and teaches founders and their teams to work with them — through courses and corporate programs.
This article was prepared with AI assistance, based on Yaroslav Maxymovych's methodology and materials. Spotted an inaccuracy — let us know via the form below.
Your company's first 3 AI automations — in 2 weeks
A corporate AI-transition program: 4 live sessions with your team plus a video course for every employee. Up to 20 people for one fixed price. If it doesn't work — money back.
AI adoption resources — one email
Leave your email to receive a welcome email with blog resources. There is no regular newsletter at present
No spam. Unsubscribe anytime.
Related Articles

Milestone Burn-Up Chart for Non-Software Projects: A Founder's Visibility Tool
A milestone burn-up chart helps owners track real progress in construction, retail, logistics, and operations projects without relying on subjective percent-complete estimates.
Read more
Security Guard Incident Logs: Auditable Reports for Owners
Learn how to create security guard incident logs that owners can actually audit, ensuring accountability and operational clarity. Discover the key components, digital tools, and reporting culture…
Read more
Hiring Without Blind Spots: What Data Should Drive Role Decisions
Founders often hire because something feels broken, without data showing where the break is. Learn what operational signals — backlog age, cycle time, reactive work, and decision wait time — should…
Read more