How to Write a Capacity Planning Doc in English

A capacity planning doc that just says “we’ll need more servers eventually” doesn’t give anyone a decision to make — this guide covers the structure that turns capacity planning into concrete numbers a team can actually budget and plan around.

Key Vocabulary

Current utilization — the baseline measurement of how much of existing capacity is being used right now, such as CPU, memory, or storage percentage, stated with enough precision to serve as a credible starting point for projections. “Start with current utilization stated plainly: our primary database is at 65% CPU utilization at peak traffic, and storage is at 70% of provisioned capacity. Everything else in this document builds from these two numbers.”

Growth projection — an explicit, justified estimate of how demand will increase over a defined period, based on historical trend data or known upcoming events, rather than an unexplained guess. “The growth projection here isn’t a guess — it’s based on our last twelve months of user growth, which has been roughly 8% month over month, extrapolated forward with a note that this assumes no major product launch accelerating it further.”

Headroom target — the buffer above projected peak demand that capacity should be provisioned for, chosen deliberately based on how much risk the team is willing to accept versus how much idle capacity costs. “We’re setting a headroom target of 40% above projected peak, not just 10%, because this service has historically seen sudden traffic spikes around product launches, and a thin buffer has caused outages for us before.”

Trigger threshold — the specific utilization percentage that should prompt provisioning more capacity, defined in advance so the decision to scale up isn’t made reactively during an incident. “We’re setting a trigger threshold at 75% sustained utilization — once we cross that consistently, it should automatically trigger a capacity review, rather than us waiting until we’re at 95% and scrambling under pressure.”

Common Phrases

• “What’s our current utilization at peak, not just average?”
• “Is this growth projection based on historical data, or is it a rough estimate?”
• “What headroom target are we comfortable with, given the cost of extra capacity?”
• “At what trigger threshold should we actually provision more capacity?”
• “Does this projection account for known upcoming events, like a planned launch?”

Example Sentences

Stating current utilization precisely: “Current utilization: the checkout service runs at 55% CPU on average, but peaks at 82% during our daily traffic spike between 6 and 8 PM. Any capacity plan needs to be built around that peak number, not the average.”

Justifying a growth projection: “Our growth projection assumes 10% month-over-month user growth, consistent with the past two quarters, plus an additional 25% one-time bump around the planned mobile app launch in September, based on comparable launches we’ve seen before.”

Setting a trigger threshold: “We’re proposing a trigger threshold of 70% sustained utilization over a rolling week — crossing that should automatically open a capacity review ticket, so we’re provisioning ahead of the crunch instead of reacting to it during an incident.”

Professional Tips

• Report current utilization at peak, not average — average utilization can look comfortable while peak periods are already close to capacity limits.
• Base every growth projection on actual historical data and known upcoming events, and state those assumptions explicitly — an unexplained number invites skepticism and is hard to revisit later.
• Choose a headroom target deliberately based on the cost of an outage versus the cost of idle capacity, not an arbitrary round number — different services warrant different levels of buffer.
• Define a concrete trigger threshold in advance, so the decision to provision more capacity is made calmly ahead of time, not reactively during a traffic spike or incident.

Practice Exercise

1. Write a current utilization statement that includes both average and peak figures.
2. Draft a growth projection sentence that states its underlying assumption explicitly.
3. Write a trigger threshold clause specifying the exact percentage and resulting action.