Describe the system, team, or facility you need to plan. Makeform turns it into a capacity planning checklist for usage, forecasts, thresholds, bottlenecks, owners, and decisions.
Route completed reviews to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, adapt the assumptions, and send the prompt into the builder. Samples preview useful fields, not a live forecast.
Audience
Platform and infrastructure teams
Format
Quarterly checklist with threshold-driven actions
Prompt size
404 chars
Example checklist structure
Quarterly checklist with threshold-driven actions
Baseline period and planning horizon
Current average and peak utilization
Forecast demand and confidence
Does demand cross an operating threshold?
Selected action, owner, and due date
Suggested routing tags
Within threshold
Action required
Assumptions to validate
Ask for both a baseline period and a planning horizon. Utilization without dates cannot support a defensible capacity decision.
Step 1
Baseline
measure current demand and usable capacity
Step 2
Forecast
state horizon, drivers, scenarios, and confidence
Step 3
Compare
find headroom, thresholds, and constraints
Step 4
Act
record the decision, owner, trigger, and review date
Planning evidence
Capture where the numbers came from, what may change, and who owns the response before approving more capacity.
Require a metric, unit, source, time window, average, peak, and usable limit.
Record demand scenarios, drivers, confidence, and the assumption that changes the decision.
Finish each gap with an action, owner, trigger, dependency, and review date.
Flexible planning scope
Change the units and constraints while keeping a consistent baseline-to-action review path.
Track compute, storage, databases, network, licenses, queues, response-time thresholds, and scaling lead times.
Compare forecast workload with available hours by role, allowing for leave, support duties, onboarding, and scarce expertise.
Review floor space, workstations, docks, machines, maintenance windows, shift throughput, and procurement lead times.
Expose competing work, shared dependencies, service demand, sequencing choices, and work that can be deferred.
Checklist workflow
Start with the decision, then request the measurements and assumptions needed to reach it.
Name the resource, baseline period, forecast end date, and decision to support.
Use your units and thresholds. Show remediation fields only for a projected gap.
Collect source links and assumptions, then route reviews to decision owners.
Keep triggers, owners, dates, and outcomes together for the next cycle.
Choosing a format
Use the checklist as the review record while dashboards monitor and spreadsheets model scenarios.
Field guide
These six sections create a traceable line from observed demand to an owned capacity action. Adapt the measures to the resource being planned.
Scope and purpose
Name the resource, decision, baseline, and planning horizon so every reviewer uses the same scope.
Demand and baseline
Capture typical and peak demand with a source and observation window. Averages alone can hide the binding constraint.
Usable capacity
Account for reserves, maintenance, unavailable shifts, redundancy, and licensed limits before calculating headroom.
Forecast and scenarios
Record base, high, and low cases when uncertainty could change the action. Name the driver, source, and confidence.
Constraints and risks
Name the binding constraint, trigger, warning time, and consequence so the team can respond before the threshold.
Decision and follow-through
Choose whether to add, optimize, reallocate, defer, or monitor capacity, then record who follows through.
Related tools
Use these live Makeform tools to document inventory, continuity risks, service demand, and changes around the planning review.
Inventory assets that establish installed and available capacity.
Open toolDocument continuity resources, dependencies, fallbacks, and responsibilities.
Open toolEvaluate constraints that could interrupt operations.
Open toolCapture the scope, impact, owner, and review path for a capacity change.
Open toolCollect service demand for workload and support planning.
Open toolRecord project changes when capacity forces a trade-off.
Open toolFAQ
Practical answers for operations, IT, service, and portfolio managers building a repeatable review.
It is a structured review of current demand, usable capacity, forecasts, thresholds, constraints, options, and actions. It connects measurements and assumptions to a decision, owner, and review date.
Include scope, baseline, horizon, demand units and sources, average and peak demand, usable capacity, thresholds, forecast scenarios, confidence, bottlenecks, lead times, action, owner, due date, and next review.
Review more frequently than the time needed to respond to a gap. Also set event triggers such as a threshold breach, launch, staffing change, migration, or demand shift.
Define usable capacity after reserves, maintenance, and redundancy, then compare forecast peak demand with it. Always record the unit, time window, and operating threshold.
Yes. Infrastructure can use throughput, storage, connections, or seats. Staffing can use available hours, workload, handling time, leave, and skill. Link dependencies between the plans.
Record base and high-demand scenarios, their method, source, drivers, assumptions, and confidence. Pair each important scenario with a trigger for review or contingency action.
Yes. Makeform supports unlimited free forms and responses, so you can generate, edit, publish, and reuse capacity review checklists without a submission cap. The paid tier removes Makeform branding.
No. Keep telemetry in monitoring systems and calculations in models. Use the checklist to link sources and record assumptions, constraints, decisions, owners, and review dates.
Make the next capacity review actionable.
