Write a monthly IT and security report for leadership
Turns ticket, uptime, and security metrics into a short report showing trends, risks, and decisions needed.
The prompt
Write a monthly IT and security report for leadership.
Reporting period: [MONTH]
Metrics this month and last: [PASTE - e.g. ticket volume, first-response and resolution times, SLA met %, satisfaction score, uptime per key service, patch compliance %, critical vulnerabilities open and overdue, MFA coverage, phishing report rate, backup success and restore tests, security incidents]
Notable events: [outages, incidents, projects completed, audits]
Projects in progress: [STATUS of each]
Risks or asks: [budget, headcount, decisions needed]
Audience: [CEO / leadership team / board risk committee]
Write:
1. Headline summary: 3 bullets on what leadership needs to know, good and bad.
2. Service health: support and uptime trends, with a short reason for any big change.
3. Security posture: the 4-6 metrics that matter, each with trend arrow (up / down / flat), target, and status (on track / watch / off track).
4. Incidents and outages: one line each, business impact, and status.
5. Projects: status table (Project | Status | Next milestone | Risk).
6. Top risks and decisions needed, each with a recommendation.
Rules:
- Use only numbers I gave. Calculate changes accurately; mark missing data [ADD].
- Explain metrics in business terms (e.g. "94% of laptops patched; the rest are mostly remote staff offline").
- No jargon without explanation. Under one page plus the tables.
Also suggest one chart worth including and which metrics I should start tracking if I am not already.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Data & Analysis prompts
What to fill in
- MONTH
- outages, incidents, projects completed, audits
- STATUS of each
- budget, headcount, decisions needed
- CEO / leadership team / board risk committee
- ADD
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Design a one-page company scorecard for my leadership teamA single page of leading and lagging metrics, with owners, targets, and thresholds, that the leadership team reviews every week.
- Analyze KPI performanceExplains movement in your KPIs: drivers, risks, and actions.
- Write commentary for a dashboard or KPI reportWrites the 'so what' narrative executives need alongside a dashboard — for sales, marketing, HR, finance, ops, or support.
- Write a SQL query from plain EnglishTurns a business question into SQL, with validation checks and an explanation.