IT management is half technical decisions and half organizational politics. You're translating business requirements into infrastructure roadmaps, justifying budget asks to executives who don't understand the stack, managing vendors who miss SLAs, and keeping a team productive while handling incidents that were never in the plan.
ChatGPT doesn't replace your judgment about architecture or risk. It won't know your organization's legacy debt or your CTO's risk tolerance. But it eliminates the documentation overhead, accelerates the first drafts of policies and communications that eat your evenings, and helps you think through decisions before you're in the room.
These 35 prompts are fill-in-the-bracket templates. Replace the bracketed sections with your environment's specifics and get a working first draft in under 60 seconds.
1. Project Planning and Resource Allocation
IT projects fail on planning more often than on technology. These prompts help you scope, resource, and communicate technical initiatives before the work starts.
Prompt 1 — Project scope document:
You are an experienced IT project manager. Write a project scope document for [PROJECT NAME]. Business objective: [DESCRIBE]. In scope: [LIST KEY DELIVERABLES]. Out of scope (explicitly): [LIST EXCLUSIONS]. Assumptions: [LIST KEY ASSUMPTIONS]. Dependencies: [INTERNAL AND EXTERNAL]. Stakeholders: [LIST WITH ROLES]. Success criteria: [HOW WILL WE KNOW IT'S DONE AND DONE WELL]. High-risk areas: [WHAT COULD GO WRONG]. Format as a structured document under 500 words.
Prompt 2 — Resource request justification for leadership:
Write a resource request justification for [HEADCOUNT / BUDGET / TOOL] for [PURPOSE]. Audience: [EXECUTIVE/DIRECTOR/CFO — someone who will ask "why do we need this?"]. Include: the specific gap or problem this resource addresses, the business impact of not addressing it (risk, lost productivity, missed opportunity), how we determined the resource amount requested, alternatives we considered and why they don't work, and the expected ROI or risk reduction. Under 300 words. No technical jargon.
Prompt 3 — IT project prioritization framework:
We have [NUMBER] IT projects or requests competing for the same [QUARTER/YEAR] roadmap. Create a prioritization framework I can use to score and rank them. Criteria to include: business impact, strategic alignment, technical risk, resource requirement, regulatory/compliance urgency, and dependencies on other work. Provide a weighted scoring rubric (1–5 scale per criterion) and a sample scoring table I can populate with our projects. Explain how to facilitate a leadership discussion around the results.
Prompt 4 — Sprint/iteration planning for IT team:
Help me plan the [SPRINT NUMBER / WEEK OF DATE] for our IT team. Team capacity: [NUMBER] engineers/analysts, each with approximately [HOURS] available after meetings and overhead. Backlog items to consider: [LIST TICKETS/TASKS WITH ROUGH ESTIMATES]. Priorities from leadership this cycle: [LIST]. Known constraints: [PTO, INCIDENTS, CHANGE FREEZE, ETC.]. Produce: a recommended sprint commitment with rationale, items to defer and why, and a capacity warning if we're overcommitted.
Prompt 5 — Project kickoff agenda and pre-read:
Create a project kickoff meeting agenda for [PROJECT NAME] (estimated duration: [TIME]). Attendees: [LIST ROLES — e.g., project sponsor, business owner, IT lead, security, legal]. The kickoff should cover: project overview and business case, scope and out-of-scope confirmation, roles and responsibilities (RACI), timeline and milestones, communication plan and meeting cadence, risk discussion, and Q&A. Also draft a one-page pre-read stakeholders should review before the meeting.
2. Vendor Management and Procurement
Vendor relationships determine a lot of your operational stability. These prompts handle the documentation and communication layer.
Prompt 6 — RFP evaluation scorecard:
We are evaluating vendors for [PRODUCT/SERVICE TYPE]. Create an RFP evaluation scorecard with the following requirement categories: [LIST — e.g., security and compliance, integration capabilities, total cost of ownership, support SLAs, implementation approach, vendor stability]. For each category: define 3–4 specific evaluation criteria, a 1–5 scoring rubric with descriptors for each score, and a weighting factor based on our priorities (I'll adjust weights — start with equal weighting). Include a column for notes and a total score formula.
Prompt 7 — Vendor escalation email:
Write a vendor escalation email to [VENDOR NAME] regarding [ISSUE — e.g., missed SLA, unresolved support ticket, implementation delay, billing discrepancy]. Issue details: [DESCRIBE: what happened, when, impact to our operations, what we've tried, what we were promised]. This email goes to [ACCOUNT MANAGER / ESCALATION CONTACT / EXECUTIVE SPONSOR]. Tone: firm and professional, not hostile. Include: clear description of the issue and business impact, specific resolution requested, deadline for response, and statement of next steps if not resolved.
Prompt 8 — Contract review checklist:
Generate a checklist for reviewing a vendor contract for a [TYPE OF SERVICE — e.g., cloud infrastructure, SaaS platform, managed services, software development]. Focus areas: data processing and security obligations, SLA definitions and remedies, termination and exit rights (data portability, notice periods), intellectual property, liability limitations and indemnification, price escalation provisions, and audit rights. For each area, list the specific clauses I should locate and questions to ask our legal team if something is missing or unclear.
Prompt 9 — SLA performance review summary:
Write a vendor SLA performance review summary for [VENDOR NAME], service: [SERVICE], review period: [QUARTER/DATES]. Performance data:
- Uptime: [X%] vs. [SLA%] committed
- Incident response time: [AVERAGE] vs. [SLA]
- Open tickets older than SLA: [NUMBER]
- Notable incidents: [LIST]
Write: a performance summary paragraph, whether SLA remedies apply, what we need from the vendor in the next quarter, and whether we recommend contract renewal or renegotiation at the next cycle.
Prompt 10 — Offboarding a vendor and data migration plan:
We are ending our contract with [VENDOR NAME] for [SERVICE]. Contract end date: [DATE]. Data we need to recover: [LIST — e.g., transaction records, configuration data, user accounts, attachments]. Create an offboarding checklist covering: data export and verification (formats, completeness checks), access credential revocation, contractual obligations for data deletion, communication to internal stakeholders and end users, knowledge transfer documentation, and go-live requirements for the replacement solution.
3. Team Management and Performance
IT teams need technical growth paths and clear expectations. These prompts handle the management layer.
Prompt 11 — Performance review template for IT staff:
Write a performance review template for an IT [ROLE — e.g., systems administrator, software engineer, IT support analyst, network engineer]. The review covers: technical skill areas relevant to the role [LIST], delivery and project execution, collaboration and communication, initiative and continuous learning, adherence to security and process standards. For each area: include 3 rating anchors (exceeds / meets / below expectations with behavioral descriptors) and a notes field. Add a development goals section at the end.
Prompt 12 — Technical skills gap analysis:
Our IT team needs to expand capabilities in [TECHNOLOGY AREA — e.g., cloud infrastructure, DevSecOps, data engineering, cybersecurity]. Current team: [LIST ROLES AND ROUGH CURRENT SKILL LEVELS]. Target state needed in [TIME PERIOD]: [DESCRIBE]. Produce a skills gap analysis that identifies: what we need vs. what we have, which gaps can be closed with training vs. hiring, recommended training paths for current staff, and a hire-vs-train recommendation with rationale for each gap.
Prompt 13 — 1:1 agenda and coaching framework:
Create a standing 1:1 agenda template for weekly check-ins with an IT team member. Include sections for: top of mind items from them, project status updates (brief), blockers I should help remove, career development and learning check-in, feedback exchange (two-way), and action items with owners. Also write 5 coaching questions I can rotate through to keep the conversation from becoming a status report. Ideal time: 30 minutes.
Prompt 14 — Job description for technical hire:
Write a job description for a [ROLE TITLE] at a [COMPANY SIZE — e.g., 200-person, mid-market] company. Team context: [DESCRIBE TEAM — size, what they do]. Primary responsibilities: [LIST 5–7]. Required qualifications: [LIST — be specific about technologies and years]. Preferred qualifications: [LIST]. What we offer: [LIST]. Important: write requirements that are genuinely necessary (don't pad with wish-list items), use inclusive language, and avoid years-of-experience requirements that screen out non-traditional candidates unfairly. Under 400 words.
Prompt 15 — Difficult conversation preparation with a technical employee:
Help me prepare for a difficult conversation with a team member who [DESCRIBE ISSUE — e.g., is resistant to following security protocols, consistently misses deadlines, has interpersonal friction with colleagues, has performance that's declining]. The specific behavior: [DESCRIBE WITH EXAMPLES]. My goal: [OUTCOME I WANT — e.g., clear agreement on behavior change, escalation warning, understanding the root cause]. Write: an opening that doesn't trigger defensiveness, 3 questions to understand their perspective, the key message I need to land, and a specific agreement to close with.
4. Incident Response and Change Management
When systems break, communication matters as much as the fix. These prompts help you manage incidents and changes cleanly.
Prompt 16 — Incident response runbook template:
Create an incident response runbook template for [INCIDENT TYPE — e.g., service outage, data breach, ransomware, network failure, cloud provider disruption]. Include sections for: incident detection and triage, severity classification criteria (P1–P4 with examples), notification and escalation tree, immediate containment steps, investigation and root cause approach, stakeholder communication protocol (internal and external), resolution and verification steps, post-incident review requirements, and documentation checklist. Make it executable under pressure — short sentences, numbered steps, no paragraphs.
Prompt 17 — Incident status update to non-technical stakeholders:
Write an incident status update email for [INCIDENT NAME/DATE] to be sent to [AUDIENCE — e.g., executive team, affected business unit, all staff]. Current status: [DESCRIBE — what's down, since when, what we know]. What we're doing: [LIST KEY ACTIONS IN PROGRESS]. Impact: [DESCRIBE — who is affected, what they can't do]. Expected resolution: [TIME OR "still investigating"]. Write it plainly. No technical details executives don't need. Lead with impact and current status, not root cause theory.
Prompt 18 — Post-incident review (PIR) template:
Create a post-incident review template for [INCIDENT NAME — e.g., "March 14 database outage"]. Include sections for: incident summary (what happened, when, duration, impact), timeline of events (detection through resolution), root cause analysis (5-why or fishbone framework), contributing factors, what went well in our response, what we could improve, action items with owners and due dates, and process changes we're committing to. Format for a 60-minute retrospective meeting. Start with the principle that PIRs are blameless.
Prompt 19 — Change request documentation:
Write a change request for the following IT change: [DESCRIBE CHANGE — what, why, when]. Change type: [STANDARD / NORMAL / EMERGENCY]. Include: change description (technical and business impact), risk assessment (probability and severity of each risk), rollback plan (step-by-step, time to execute), testing approach, communication plan (who needs to know, when), approval requirements, and maintenance window details. Reviewers: [CHANGE ADVISORY BOARD / MANAGER / PEER]. Flag any risks that should prompt a go/no-go discussion.
Prompt 20 — Maintenance window communication:
Write a maintenance window notification for [SYSTEM/SERVICE] scheduled for [DATE AND TIME — include time zone]. Duration: [ESTIMATED]. What will be unavailable: [DESCRIBE]. Who is affected: [LIST TEAMS/SYSTEMS/USERS]. Action required from users (if any): [DESCRIBE OR "none"]. Contacts for emergencies during the window: [NAME/CHANNEL]. Write: a pre-maintenance notification (sent [X] days before), a "maintenance starting" message (sent at start), and a "maintenance complete" message (sent when done). Each under 100 words.
5. Security Policies and Risk Management
Security is everyone's responsibility but the IT manager's problem. These prompts help you write policies, communicate risks, and manage access.
Prompt 21 — Security policy draft:
Write a [POLICY NAME — e.g., Acceptable Use Policy, Password Policy, Remote Work Security Policy, Data Classification Policy] for a [COMPANY SIZE/TYPE] organization. The policy should cover: purpose and scope, specific requirements and rules, employee responsibilities, IT team responsibilities, enforcement and exceptions process, and review cycle. Language should be clear enough for non-technical employees to follow without legal training. Include an acknowledgment section employees sign. Under 600 words.
Prompt 22 — Security risk assessment summary:
Write a security risk assessment summary for [SYSTEM/PROJECT/INITIATIVE — e.g., a new SaaS tool deployment, migrating to cloud infrastructure, allowing BYOD]. Assets at risk: [LIST DATA/SYSTEMS]. Threats to consider: [LIST — e.g., unauthorized access, data exfiltration, credential theft, misconfiguration]. For each threat: assess likelihood (high/medium/low), business impact (high/medium/low), current controls in place, residual risk level, and recommended mitigation. Format as a risk register table with a summary paragraph for leadership.
Prompt 23 — Access review communication:
Write a communication to [AUDIENCE — e.g., department heads, system administrators, HR] explaining our upcoming access review process for [SYSTEM — e.g., Active Directory, production database, cloud admin console, SaaS apps]. The communication should explain: what an access review is and why we do it, what they need to do (with a specific action and deadline), what happens after they respond, and consequences of not completing the review. Make it clear that this is a compliance requirement, not optional. Under 200 words.
Prompt 24 — Security incident communication to affected users:
Write a user notification for a security incident where [DESCRIBE INCIDENT — e.g., a third-party vendor had a breach that may have exposed employee email addresses, a phishing campaign targeted our staff, a misconfiguration exposed a database temporarily]. What happened: [BRIEF DESCRIPTION]. Data potentially affected: [LIST]. What we've done: [REMEDIATION STEPS]. What users should do: [SPECIFIC STEPS — password reset, MFA enrollment, watch for phishing, etc.]. Tone: transparent and responsible, not alarming. Do not admit to regulatory violations.
Prompt 25 — Vendor security questionnaire response:
Help me draft responses to a vendor security questionnaire that is asking about our [SPECIFIC SECURITY DOMAIN — e.g., data encryption practices, access control, incident response, backup and recovery, employee security training]. Questions asked: [PASTE QUESTIONS]. Our actual practices: [DESCRIBE WHAT WE DO]. Write accurate, professional responses that: answer the question truthfully, present our practices in the best accurate light, don't over-claim capabilities we don't have, and flag any areas where I should consult our security team before answering.
6. Budgeting and Cost Optimization
IT budget conversations happen in every direction — justifying spend upward and finding savings downward. These prompts help with both.
Prompt 26 — IT budget request narrative:
Write the narrative section of an IT budget request for [FISCAL YEAR]. Total IT budget request: $[AMOUNT]. Key investment areas: [LIST WITH AMOUNTS — e.g., cloud infrastructure $X, security tools $Y, headcount $Z, hardware refresh $W]. For the narrative: explain the strategic rationale behind the largest line items, connect each investment to a business objective or risk, address the "why now" question for new investments, and explain what we're cutting or deferring to fund these priorities. Audience: CFO/executive team. Under 500 words.
Prompt 27 — SaaS audit and cost reduction analysis:
I need to conduct a SaaS spend audit for our organization. We have [NUMBER] active SaaS subscriptions totaling approximately $[AMOUNT]/year. Help me create: a data collection template (what to capture for each tool), evaluation criteria for each tool (business value, utilization, overlap with other tools, contract renewal date), a decision framework (keep/cancel/consolidate/renegotiate), and a tracking sheet for negotiation targets. I want to identify at least [TARGET %] in potential savings.
Prompt 28 — Cloud cost optimization plan:
Our cloud spend on [AWS / Azure / GCP] is $[AMOUNT/MONTH] and trending [UP/FLAT]. We want to reduce costs by [TARGET %] without impacting performance. Current environment: [DESCRIBE — e.g., 50 EC2 instances, mix of on-demand and reserved, several idle resources identified]. Create a cost optimization plan that covers: right-sizing recommendations, reserved instance / savings plan opportunities, storage optimization, network egress reduction, and any architectural changes worth evaluating. Prioritize by estimated savings impact.
Prompt 29 — Total cost of ownership comparison:
Help me build a total cost of ownership comparison for [OPTION A] vs. [OPTION B] for [TECHNOLOGY DECISION — e.g., build vs. buy, on-prem vs. cloud, current vendor vs. replacement]. Cost categories to include over a [3/5-YEAR] horizon: licensing and subscription fees, implementation and migration, staff time (setup + ongoing management), training, integration, security and compliance overhead, downside risk (breach, downtime), and exit costs. Structure as a comparison table I can present to leadership.
Prompt 30 — IT cost allocation justification to business units:
Our organization is implementing IT chargeback/showback for [COST CATEGORIES — e.g., cloud compute, SaaS seats, helpdesk hours]. Write a communication to [AUDIENCE — business unit leaders, department heads] explaining: what IT chargeback is and why we're implementing it, how their costs are calculated, what they can do to manage and reduce their IT costs, and who to contact with questions. Goal: help business partners see IT costs as something they can influence, not just a tax. Clear, non-defensive tone.
7. Stakeholder Communication and Reporting
IT managers bridge technical teams and business leadership. These prompts handle the translation layer.
Prompt 31 — IT monthly/quarterly status report:
Write an IT status report for [MONTH/QUARTER] for [AUDIENCE — executive team, board, business leadership]. Include: key accomplishments (bullet list with business impact, not technical details), ongoing initiatives status (name, % complete, key milestone next period), service reliability metrics (uptime, incident count, mean time to resolution), open risks and issues requiring leadership attention, and looking ahead to next period priorities. Under 400 words. Assume the reader wants to know if IT is under control, not how it works.
Prompt 32 — Technology roadmap presentation narrative:
Write the narrative for a [YEAR/3-YEAR] IT technology roadmap presentation. Audience: executive team and board. Roadmap themes: [LIST 3–5 STRATEGIC THEMES — e.g., cloud migration, security hardening, digital employee experience, data platform modernization]. For each theme: the current state, target state, key initiatives, timeline, investment required, and expected business outcome. Frame everything in terms of business risk reduction and capability enablement, not technology for its own sake. Under 600 words.
Prompt 33 — Business case for a technology investment:
Write a business case for [TECHNOLOGY INVESTMENT — e.g., implementing an ITSM platform, upgrading network infrastructure, deploying endpoint detection and response]. Investment required: $[AMOUNT]. For the business case: describe the problem being solved, quantify the current cost of the problem (productivity loss, risk exposure, manual labor hours, etc.), describe the solution and how it addresses the problem, estimate financial benefits (hard and soft), calculate ROI or payback period, and address likely objections. Audience: CFO and CEO. Under 500 words.
Prompt 34 — Communicating IT strategy to non-technical executives:
I need to explain [TECHNICAL CONCEPT OR STRATEGY — e.g., zero-trust security model, microservices migration, moving to a data mesh architecture] to our executive team in a [20-MINUTE / BOARD PRESENTATION / MEMO] format. They understand business outcomes but not technology. Write an explanation that: uses one business analogy to make the concept intuitive, explains why this matters to the company in terms of risk and opportunity, names the key decisions they need to make or approve, and avoids any technical jargon not defined in the explanation.
Prompt 35 — Executive escalation memo:
Write an executive escalation memo for [ISSUE — e.g., a critical security vulnerability we've discovered, a vendor about to fail, a compliance gap, a key technical risk we can't fund]. Audience: [C-SUITE / BOARD]. Include: the issue in one sentence, the business risk if not addressed (with specificity — cost, regulatory exposure, operational impact), options for response (at least 2, with trade-offs), our recommended course of action, what we need from them (decision, funding, authority), and the decision deadline. Under 300 words. Decision-oriented, not informational.
Get 35 More Prompts — Advanced IT Leadership Scenarios
These 35 prompts cover core IT management workflows. The full pack adds 35 more for advanced scenarios: digital transformation leadership, enterprise architecture decisions, compliance and audit management, multi-site and international IT operations, and CISO-level security strategy.
Get the full 70-prompt IT Manager ChatGPT Pack →
Use LAUNCH30 for 30% off — limited uses remaining.
Every prompt is editable. Works with ChatGPT-4, Claude, and Gemini.
Top comments (0)