AI Prompts for IT Managers: 12 Copy-Ready Templates

You are the IT manager at [COMPANY], with [NUMBER] staff. Decisions we have made: approved tools [TOOLS AND PLANS], data that must never be pasted [DATA TYPES], required review [REVIEW RULES], how to request a new tool [PROCESS], what to do if someone makes a mistake [INCIDENT CONTACT].

Write a one-page acceptable use policy in plain language with those sections, plus five "do" and five "don't" examples drawn from our rules. Only include rules I listed.

Format: headed sections and two short lists.

Act as an IT and security reviewer. A team wants to use [TOOL] for [USE CASE]. Here is what I found on the vendor's own pages and in their documents:

[PASTE FACTS ABOUT DATA RETENTION, TRAINING ON CUSTOMER DATA, ADMIN CONTROLS, SSO, CERTIFICATIONS, DATA LOCATION]

Organize this into an evaluation: what the tool does with our data, admin controls available, gaps or unknowns to ask the vendor about and a list of conditions we would set if approved. Do not add facts I did not provide.

Format: a table with Area, What we know, Unknown or risk, then Conditions.

You are the IT manager. Write a short, friendly email for staff with practical tips for using [APPROVED AI TOOL] safely: what never to paste ([DATA TYPES]), how to check answers, how to spot suspicious instructions hidden in documents or emails, and who to contact: [CONTACT].

Format: a subject line, then a numbered list of six tips, under 220 words.

You are on the IT help desk at [COMPANY]. A user wrote: "[TICKET TEXT]". What I know: [DIAGNOSIS OR NEXT STEP]. Expected time: [TIME OR "UNKNOWN"].

Write a short, friendly reply that confirms what is happening, gives clear steps for the user if any (one action per line) and sets honest expectations. No jargon.

Format: under 120 words.

Act as an IT manager writing an internal knowledge base article. Here is how we solved a recurring issue:

[PASTE NOTES, WITH NO PASSWORDS, KEYS OR INTERNAL ADDRESSES]

Write an article for non-technical staff: a title phrased as the problem they would search for, a one-line fix, numbered steps with what they should see after each and when to contact IT instead.

Format: a title, then the article under 300 words.

You are the IT manager. New employees at [COMPANY] need: [ACCOUNTS, DEVICES, SOFTWARE, SECURITY SETUP SUCH AS MFA, TRAINING]. Owners: [WHO DOES WHAT].

Write a setup checklist split into before day one, day one and first week, with the owner for each item and a final security check.

Format: a checklist table with Item, When, Owner.

You are the IT manager. [SYSTEM] is [DOWN OR DEGRADED] since [TIME]. Confirmed impact: [IMPACT]. Workaround: [WORKAROUND OR "NONE"]. Next update: [TIME].

Write a short staff notice and a follow-up "resolved" template. State only confirmed facts and do not guess at the cause or the fix time.

Format: two labeled drafts, each under 100 words.

Act as an IT manager writing a blameless post-incident review. Timeline from our logs and notes (no credentials or sensitive data):

[PASTE TIMELINE]

Write: summary, impact, timeline, what went well, what did not, contributing factors (as supported by the timeline) and action items with owners. Mark anything uncertain as "To confirm".

Format: headed sections, with the timeline and actions as tables.

You are the IT manager. A staff member says they pasted [TYPE OF DATA, DESCRIBED GENERALLY] into [AI TOOL] on [DATE]. Our incident policy: [POLICY STEPS].

Write a calm, step-by-step response plan for the first hour: what to ask the employee, what to check in the tool's settings and history, who to notify under our policy and how to document it. Do not decide whether it is a reportable breach; flag that for [LEGAL OR PRIVACY CONTACT].

Format: a numbered plan, then a short note to the employee.

Act as the IT manager. On [DATE] we are changing [WHAT, SUCH AS MOVING TO A NEW PASSWORD MANAGER]. Why: [REASON]. What staff must do and by when: [ACTIONS]. Help available: [TRAINING, OFFICE HOURS, CONTACT].

Write the announcement with the actions as a short numbered list and a reminder email for the day before.

Format: two labeled drafts.

You are evaluating [CATEGORY OF SOFTWARE] for [TEAM]. Requirements: [MUST HAVES]. Options and facts from vendor pages: [PASTE OPTIONS, PRICES, FEATURES].

Build a comparison of how each option meets each must-have (Yes, Partly, No, Unknown), total annual cost for [NUMBER] users (show the math) and questions to ask each vendor. Do not recommend one.

Format: a comparison table, a cost table, then Questions.

Act as an IT manager requesting [AMOUNT] for [PROJECT, SUCH AS LAPTOP REFRESH OR BACKUP UPGRADE]. Current situation: [FACTS, SUCH AS DEVICE AGES OR RECENT ISSUES]. Risks of waiting: [RISKS]. Options with costs: [OPTIONS].

Write a short memo for [APPROVER]: the problem, options, recommendation, cost and timeline. Use only my facts.

Format: headed sections, under 280 words.