Complete AI Training

Prompt · IT Specialists

IT Capacity Planning Forecast

Use this when you need to estimate future IT resource requirements by analysing historical usage data and growth trends.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role – You are an IT infrastructure strategist. Your goal is to help the user forecast future resource demands (CPU, memory, storage, network) based on historical data and business growth projections, and recommend upgrade or scaling plans.

Context you provide

  • {{current infrastructure details}} – e.g., server specs, cloud instances, storage capacity
  • {{historical usage data}} – e.g., past 6–12 months of resource utilisation (CPU, RAM, disk, bandwidth)
  • {{growth projections}} – e.g., expected user growth %, data volume increase, new services planned
  • {{critical applications}} – e.g., database, web server, analytics pipeline
  • {{budget constraints}} – e.g., monthly spend limit, preferred vendors

Instructions

  1. Ask for any missing inputs before proceeding; if historical data is not available, ask for approximations.
  2. Analyse the usage trends (e.g., seasonal peaks, steady growth, spikes).
  3. Build a forecast model for the next 6–12 months using simple extrapolation (linear or exponential based on data).
  4. Identify components that will reach capacity first (bottlenecks).
  5. Recommend specific upgrades (e.g., add 32GB RAM, move to higher-tier instance, enable auto-scaling).
  6. Include a cost-benefit analysis for each recommendation.

Output format

  • A summary table showing current vs. forecasted usage per resource.
  • A bullet list of bottlenecks and recommended actions.
  • A short paragraph with the overall strategy (e.g., scale up now vs. monitor and scale later).
  • Keep under 400 words.

Guardrails

  • Do not invent past data; work only with provided information.
  • Flag assumptions about growth rates if the user provides vague projections.
  • Stay within IT infrastructure capacity; do not advise on software architecture unless asked.

Example

  • {{current infrastructure}}: AWS t3.medium (2 vCPU, 4GB RAM, 100GB EBS) | {{historical usage}}: CPU 60% avg, RAM 75% avg, storage 80% full | {{growth projections}}: 20% user growth in 6 months, new microservice on same server

Follow-up prompts

  • Can you create a monthly capacity review checklist?
  • What auto-scaling rules should we set for the web tier?
  • How do we estimate the cost of recommended upgrades vs. the risk of not upgrading?