This is Week 12 of the AI Ops Playbook — Week 4 of Round 2 — and the whole drop lives in Internal Operations, specifically the part of running a business that almost nobody trains you for: managing people. Last week we built the sales motion, the system for turning conversations into customers. This week we move inside the company, to the documents a manager has to write about the people who work there. Here's the pattern we see in small businesses again and again. The owner or manager is great with people in person — they hire well by gut, they coach in the hallway, they celebrate wins out loud. But the moment a people situation requires a *written* document, everything stalls. An employee is underperforming and needs a formal plan, but the manager has been "meaning to write it up" for six weeks because a performance improvement plan feels legally terrifying to put on paper. A round of candidates is waiting to hear back, but the rejection emails feel so awkward that half of them never get sent and good applicants get ghosted. Someone clearly deserves a promotion, but no one ever builds the case, so they get promoted late, informally, or leave. Something goes badly wrong in the business, the fire gets put out — and then nobody writes down what happened, so the same incident quietly recurs three months later. None of these are people problems. They're *writing* problems — specifically, the kind of high-stakes, emotionally loaded writing that managers avoid because getting it wrong feels worse than not doing it at all. So it doesn't get done, and the cost is invisible: the underperformer drags on, the rejected candidate badmouths your hiring, the star employee walks, the incident repeats. This week's four templates take on exactly those four documents — the hardest ones a manager has to write — and turn each from a dreaded blank page into a careful, structured first draft. ## What's New This Week **Performance Improvement Plan Drafter** (Internal Ops, Advanced) — This is the document managers avoid most, because a PIP can become a legal record and the stakes feel enormous. Feed it your honest, dated notes about an underperforming employee — the standard, what's actually happening, specific examples — and it produces a complete, structured plan: behavior-based descriptions of each gap, a table of SMART expectations tied to those gaps, a concrete support plan (the part that separates a fair improvement plan from a paper trail for a firing), a 30/60/90-style check-in schedule, and plainly stated consequences. Crucially, it's built with guardrails: it refuses to reference protected characteristics, flags any expectation that looks unrealistic, and ends with a manager-only review section listing what you still need to substantiate. It produces a *careful draft, not a final document* — the template is explicit that every fact must be verified and HR or legal must review it before it's issued. What it removes is the paralysis of the blank page, which is the actual reason the plan never gets written. **Hiring Rejection Email Generator** (Internal Ops, Beginner) — The fix for the rejection emails that pile up unsent. List your candidates with the stage each one reached — application, phone screen, interview, or final round — and it writes a tailored email for each, scaling warmth and length to how far they got: a brief, kind note for early applicants, a genuinely personal message for a finalist who gave you a half-day. Every email delivers the "no" clearly, keeps the reason general and legally safe, and sounds like a real person at your company wrote it rather than a bulk-mail machine. You can do a whole hiring round in one prompt. The point isn't just efficiency — it's that a fast, gracious rejection protects your reputation as an employer (and, for a local business, as a neighbor), while a slow one or none at all quietly damages it. **Promotion Case Writer** (Internal Ops, Intermediate) — The document that should get written but rarely does, which is why good people get promoted late or leave. Give it an employee's accomplishments and it builds a structured, evidence-based case: demonstrated scope and impact tied to business outcomes, proof the person is already operating at the next level, an honest readiness table mapping them against the target role, and a grounded compensation recommendation that shows the real annual cost. It leads with impact rather than tenure, stays honest about any gaps (a case with one or two acknowledged open questions is more credible, not less), and reframes itself for whoever has to approve it — a co-owner, a board, or your own budget. You walk in able to defend the promotion in a five-minute conversation instead of fumbling through "they really deserve it." **Incident Postmortem Writer** (Internal Ops, Intermediate) — For when something goes wrong — an outage, a shipping fiasco, a botched launch, a client-facing mistake — and the fire gets put out but nobody writes down what happened. Brain-dump the messy story, the impact, and your best guess at why, and it produces a clean, *blameless* postmortem: a chronological timeline built from your chaos, a genuine root-cause analysis that pushes past the surface trigger to "why did our process allow this," a "what went well" section, and a table of specific, owned, dated action items split into quick fixes and systemic fixes. The blameless framing is the whole point — it describes systems and processes, never who's at fault, because a postmortem that makes people defensive prevents nothing and teaches the team to hide the next problem. It works for any incident, not just technical ones. ## Why These Four Together — The Manager's Hardest Writing These four documents look unrelated — a discipline plan, a rejection note, a promotion case, an incident review. But they're the same problem wearing four costumes, and that's why they belong in one drop. Every one of them is a piece of writing that a manager *knows* they should produce, that carries real consequences if done badly, and that is therefore avoided — and the avoidance is invisible until it isn't. The PIP that never gets written means the underperformer drags the whole team down for another quarter. The rejection emails that never get sent mean a dozen applicants conclude your business is rude. The promotion case that never gets made means your best person reads the silence as "they don't see me" and takes the next call from a recruiter. The postmortem that never gets written means you pay for the same incident a second time. Notice the shape: in each case the work *feels* optional in the moment — the fire is out, the candidate will understand, the employee isn't complaining yet — and so it loses to whatever's urgent. But the cost is real and it compounds. These are the documents where a small business quietly bleeds its best people and repeats its worst mistakes, precisely because they're hard to write and easy to defer. What an AI assistant changes here isn't the judgment — you still decide who gets the PIP, who gets promoted, what the real root cause was. What it changes is the activation energy. The reason these documents don't get written is almost never that the manager doesn't know what to say; it's that the blank page, the legal worry, and the emotional weight make starting feel impossible. A structured first draft in twenty minutes removes that barrier. The hard part becomes the human conversation — which is where a manager's time should go — instead of the staring-at-the-cursor part, which is where it currently gets lost. A business that handles these four documents *on purpose* — addresses underperformance early and fairly, treats rejected candidates with respect, makes the case for its rising people, and learns from what breaks — is simply a better place to work and a more durable company. Round 2 is about the systems that scale a business once the basics are in place, and the way you manage people is one of the most important of those systems. ## A Note on Cadence — Back on Schedule After two weeks of Friday slips, this drop is landing on its regular **Wednesday** — we're back on the normal rhythm. Thanks for bearing with the two late ones. As with the last few weeks, we kept all four templates together as a single coherent set — the people-management documents — rather than splitting them across categories, because they're most useful understood as one toolkit for the hardest part of managing a team. ## Get Started All four templates are available now for Pro members — they're the documents you'll reach for at exactly the moments they're hardest to write: - **Performance Improvement Plan Drafter** — [open the template →](/templates/performance-improvement-plan-drafter) - **Hiring Rejection Email Generator** — [open the template →](/templates/hiring-rejection-email-generator) - **Promotion Case Writer** — [open the template →](/templates/promotion-case-writer) - **Incident Postmortem Writer** — [open the template →](/templates/incident-postmortem-writer) Browse the full [Internal Operations](/category/internal-operations) category — it now holds the deepest set of people-management templates in the library. If you only build one thing this week, draft the PIP you've been putting off: not to issue it tomorrow, but to finally get the situation onto paper where you can see it clearly and decide what to do. If a template you need for your business isn't in the library yet, reply to this week's Quick Win email — member feedback is what shapes Round 3.

You are an experienced HR director and employment-practices advisor who specializes in performance management for small businesses. You write Performance Improvement Plans that ar