IT managers are some of the most time-pressed writers in any company. Runbooks, post-mortems, change request summaries, incident status updates, escalation emails, vendor justifications, budget cases — it's a constant stream of documentation and communication that doesn't feel like “real IT work” but easily eats half the week.
These 10 prompts cover the three core writing jobs IT leaders do every week: building and maintaining documentation, managing incidents and escalations, and handling vendor and stakeholder communications. Fill in the brackets, and the draft is done.
IT Documentation & Knowledge Base
Good documentation prevents incidents, reduces onboarding time, and keeps your team from answering the same questions twice. These four prompts give you repeatable starting points for the documents every IT team needs but rarely has time to write properly.
1. Runbook Generator
The Prompt
Write a runbook for [system/process] that covers the following sections: (1) prerequisites — tools, access, and knowledge required before starting, (2) step-by-step instructions — numbered, specific, and reproducible, (3) rollback steps — how to undo each major action if something goes wrong, (4) common failure points — what typically breaks and how to diagnose it. Audience: an experienced IT technician unfamiliar with this specific system.
Why it works: A runbook that covers prerequisites, rollback steps, and failure modes is the difference between a doc that gets used and one that gets ignored. This prompt enforces the structure that makes runbooks actually valuable under pressure.
2. Incident Post-Mortem Draft
The Prompt
Write a post-mortem for an incident where [describe what happened]. Structure the document as follows: (1) incident timeline — key events with approximate timestamps, (2) root cause — the technical and process factors that caused the incident, (3) impact — systems affected, users impacted, duration, and any business consequences, (4) action items — specific, assigned, and time-bound steps to prevent recurrence. Tone: factual and blameless.
Why it works: Blameless post-mortems require a clear structure to be useful rather than defensive. This prompt produces a document organized around root causes and action items — the two things that actually prevent the next incident.
3. Change Request Summary
The Prompt
Summarize this change request in plain English for a non-technical stakeholder. Focus on: (1) what is changing and why, (2) what systems or users will be affected, (3) when the change will happen and how long it will take, (4) what the rollback plan is if something goes wrong, (5) what approvals are required before proceeding. Avoid technical jargon. Change request details: [paste change request details]
Why it works: Stakeholders approve change requests faster when they understand what they're approving. This prompt translates technical change specs into a readable five-point summary — without losing the details that matter for the approval decision.
4. Knowledge Base Article
The Prompt
Write a knowledge base article explaining how to [task] for end users. Format: (1) a one-sentence summary of what this article covers, (2) numbered step-by-step instructions with clear, non-technical language, (3) a troubleshooting section listing the 3 most common issues and their fixes, (4) a note on who to contact if the steps don't resolve the issue. Avoid jargon. Assume the reader has no technical background.
Why it works: Knowledge base articles written for technical audiences don't reduce helpdesk volume. This prompt structures the output for end users — plain language, numbered steps, troubleshooting built in — so people can actually self-serve.
Incident & Escalation Communications
How you communicate during and after an incident is as important as how you resolve it. These three prompts help you write the updates, escalations, and executive summaries that keep stakeholders informed and trust intact when things go wrong.
5. Incident Status Update
The Prompt
Write a clear, calm incident status update for [affected users/stakeholders]. Include: (1) current status — what is happening right now in one sentence, (2) impact — which systems, services, or users are affected, (3) what we are doing — specific actions already underway, (4) ETA to resolution — [timeframe] or "under investigation" if unknown, (5) next update time — when you will communicate again. Tone: calm, transparent, and action-oriented. Current status: [brief status]. Impact: [describe impact]. ETA to resolution: [timeframe]
Why it works: During an incident, stakeholders need a single source of truth. This prompt produces a structured update that answers the four questions everyone is asking — what happened, who's affected, what's being done, and when it will be fixed — without the panic.
6. Escalation Email
The Prompt
Draft an escalation email to [vendor/team] for a critical issue with [system/service] that has been unresolved for [timeframe]. Include: (1) a clear subject line that flags urgency, (2) a brief description of the issue and when it started, (3) a summary of steps already taken to resolve it, (4) the business impact if this is not resolved — quantify where possible, (5) a specific ask: what we need, and by when. Tone: firm, professional, and factual. No emotional language.
Why it works: A weak escalation email gets triaged like a support ticket. This prompt structures the email around business impact and a specific, time-bound ask — which is what moves a vendor from queue to priority.
7. Post-Incident Executive Summary
The Prompt
Write a 1-paragraph executive summary of [incident name] suitable for a VP or C-suite audience. Cover: (1) what happened — a plain-English description of the incident, (2) impact — duration, systems affected, and any business or customer impact, (3) resolution — how it was resolved and when, (4) prevention — the specific steps being taken to prevent recurrence. Limit to 150 words. No technical jargon.
Why it works: Executives don't read post-mortems. They need a 150-word summary that tells them what happened, what it cost, and what you're doing about it. This prompt is calibrated for that exact audience and format.
Stop writing from scratch
The Flux Prompt Pack gives you 100+ ready-to-use prompts for documentation, communications, and stakeholder updates — built for professionals who run on tight timelines.
Get the Prompt Pack — $19 →Vendor & Stakeholder Management
Vendor evaluations, budget justifications, and weekly status reports are some of the most high-stakes documents IT managers produce — and the ones most likely to sit in drafts until the deadline hits. These three prompts give you solid first drafts in minutes.
8. Vendor Evaluation Scorecard Narrative
The Prompt
Write a vendor comparison narrative for [vendor A] vs [vendor B] covering the following evaluation criteria: price, support SLA, integrations, and scalability. For each criterion, summarize how each vendor performs and note the key trade-offs. End with a clear recommendation — which vendor to select and why — in two to three sentences. Audience: IT leadership and procurement. Tone: objective and decisive.
Why it works: A comparison narrative that ends with a clear recommendation is what actually moves the decision forward. This prompt structures the evaluation by criterion and forces a definitive conclusion — so the document does its job.
9. IT Budget Justification
The Prompt
Write a business case for investing in [tool/upgrade/headcount]. Structure it as: (1) the current pain — what problem exists today, with specifics on time lost, risk, or cost, (2) the proposed solution — what we are requesting and what it does, (3) estimated cost — one-time and ongoing, (4) expected ROI — time saved, risk reduced, or revenue protected, with numbers where possible, (5) recommendation — approve by [date] to achieve [outcome]. Audience: finance and executive leadership. Length: one page or less.
Why it works: Budget requests get approved when they speak in business terms, not technical ones. This prompt frames the ask around pain, cost, and ROI — the language finance teams respond to — while keeping the document to one page.
10. Team Update / Status Report
The Prompt
Write a concise weekly IT status update for my manager covering the following: completed this week: [list what was finished], in progress: [list active work], blockers: [list anything stalled or at risk], upcoming: [list what's planned for next week]. Format as short bullet points under each heading. Tone: direct and factual. Keep the total length under 300 words.
Why it works: Weekly status reports get skimmed. This prompt keeps the output tight and structured — four sections, bullets only, under 300 words — which means it actually gets read and acted on rather than filed.
IT managers don't get to choose whether they write — the runbooks, post-mortems, and budget cases are part of the job. ChatGPT doesn't change that. It just means you spend five minutes on the draft instead of an hour. Start with the prompt that matches what's sitting unfinished on your desk right now.
Ultimate ChatGPT Prompt Pack
$19
100+ prompts for every business function
No-Code Automation Starter Kit
$27
Automate the repetitive IT workflows that eat your week