Capacity Upgrade Brief Report

Service or platform:

Use the name stakeholders already recognize in tickets, budgets, or change records.

Current peak utilization:

Enter the current measured peak as a percentage of usable capacity.

Monthly demand growth:

A positive value compounds the forecast; use 0 when the measured workload is flat.

% / month

Planning horizon:

The charts and required gain are evaluated at this future month.

months

Action threshold:

Typical briefs use this as the approval trigger, not as a hard outage limit.

Critical threshold:

The forecast chart draws this separately from the action threshold.

Implementation lead time:

The recommendation compares breach timing with this lead time.

months

Capacity strategy:

Choose the posture the brief should use when ranking options.

Target reserve after upgrade:

Required gain is calculated so the horizon forecast remains below action minus this reserve.

points

Bottleneck evidence:

Keep it brief enough for an approver, but concrete enough for engineering review.

Upgrade options:

One option per line. Disruption uses 1 for low impact and 5 for high impact.

Format: option, cost, gain %, lead months, disruption, note.

Check capacity brief inputs

{{ item }}

Forecast confidence:

Use low confidence when demand drivers are immature or historical data is thin.

Cost unit:

Examples: USD, MYR, capex, or project estimate.

Budget ceiling:

Options above this value are still listed but receive a budget-fit warning.

Maximum acceptable disruption:

Use 1 for very low impact and 5 for maximum acceptable change impact.

Include executive summary section

Keep enabled when the brief is meant for approval or budget review.

{{ model.briefMarkdown }}

Metric	Value	Brief note	Copy
{{ row.metric }}	{{ row.value }}	{{ row.note }}

Rank	Option	Cost	Gain	Horizon utilization	Decision note	Copy
{{ row.rank }}	{{ row.name }}	{{ row.costDisplay }}	{{ row.gainDisplay }}	{{ row.horizonDisplay }}	{{ row.decision }}

Export to PDF Fullscreen

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Capacity upgrade briefs turn rising service demand into an approval argument. They connect a measured utilization level with growth, delivery lead time, risk thresholds, bottleneck evidence, and candidate upgrade choices so reviewers can see why waiting may be risky or why a smaller change is enough.

A peak utilization number is rarely useful by itself. A firewall, storage pool, queue worker group, circuit, or cluster can look acceptable today and still run out of usable headroom before procurement, licensing, change approval, and validation finish. The planning question is how much runway remains before the service crosses the level where capacity work should begin.

Capacity runway diagram with forecast growth, action and critical thresholds, lead time, and upgrade relief.

Capacity risk rises when the forecast reaches the action threshold before the change can be implemented. The action threshold is not the failure point; it is the level where the team should already be moving. The critical threshold marks a stronger warning where latency, queueing, packet loss, storage exhaustion, failover margin, or user experience may become unacceptable.

A good brief still depends on honest inputs. A neat recommendation does not prove that a vendor upgrade will deliver its stated gain, that a migration will shift demand on time, or that the next business event will follow the historical trend. The result is strongest when measured peaks, growth assumptions, and option notes can be defended by telemetry, tickets, or change records.

Technical Details:

Capacity runway is modeled as a utilization forecast against two user-selected thresholds. Current peak utilization is treated as the starting point, monthly demand growth is compounded over the planning horizon, and the result is compared with the action and critical thresholds. This matches the way many infrastructure teams discuss capacity work: current measured pressure, expected demand, time to act, and minimum relief.

The arithmetic is deterministic from the entered values. Growth below zero is not accepted, the planning horizon is limited to 1 to 60 months, and the critical threshold must be greater than the action threshold. Option rows need a name and positive capacity gain before they can be ranked.

Formula Core

The forecast uses monthly compounding. Threshold timing uses logarithms when utilization is below the threshold and growth is positive; if utilization is already at or above a threshold, the breach time is now.

\begin{array}{lcl} Projected utilization & = & current utilization \times {(1 + monthly growth)}^{months} \\ Months to threshold & = & \frac{\ln (threshold / current utilization)}{\ln (1 + monthly growth)} \\ Required capacity gain & = & \max (0, (projected utilization / target utilization - 1) \times 100) \end{array}

For example, a service at 78% current peak utilization with 6% monthly growth reaches about 110.6% at a six-month horizon. With a 75% action threshold, 90% critical threshold, and 65% target horizon utilization, the required capacity gain is about 70.2%.

Capacity strategy effects on reserve and urgency
Strategy	Reserve effect	Urgency effect	Planning meaning
`Lead demand proactively`	Adds 5 extra percentage points of reserve pressure.	Treats the approval window as 1 month tighter.	Favors earlier approval and more headroom.
`Match demand incrementally`	Uses the entered reserve as-is.	Uses the entered implementation lead time as-is.	Balances lead time, cost, and incremental capacity.
`Lag until pressure is confirmed`	Relaxes reserve pressure by 4 percentage points.	Allows about 0.75 months more timing tolerance.	Accepts tighter runway and emphasizes cost restraint.

The target horizon utilization is the action threshold minus reserve and strategy adjustment, then clamped so it remains below the action threshold. That target is used to decide whether an option meets the desired reserve or only reduces pressure.

Capacity brief status rules and boundary conditions
Status	Boundary	Meaning
`Critical now`	Current utilization `>=` critical threshold.	The service is already in the critical band.
`Start now`	Forecast `>=` critical threshold, or action breach timing is within adjusted lead time.	The change path is too close to the forecast breach window.
`Approve in horizon`	Forecast `>=` action threshold and below the critical rule above.	The planning horizon crosses the action point.
`Watch current load`	Current utilization `>=` action threshold while the stronger rules do not apply.	The service is already above the action point.
`Monitor`	Current and forecast utilization remain below action under the selected settings.	No upgrade is indicated by the current forecast, but the inputs still need periodic review.

Option ranking combines relief, runway, cost, lead time, disruption, budget fit, and strategy posture. An option is strongest when its capacity gain brings the horizon utilization at or below the target, leaves action-threshold runway after implementation, stays within budget and disruption limits, and is not too slow for the breach timing.

Option ranking factors used in capacity upgrade briefs
Factor	How it affects ranking	Output implication
Relief fit	Capacity gain is compared with required gain and capped so one huge option cannot dominate every signal.	Drives whether the decision note says `Meets target reserve`, `Below action threshold`, or `Partial relief only`.
Runway	Post-upgrade months to the action threshold are compared with the planning horizon.	Rewards options that still leave action-threshold time after the chosen horizon.
Cost	Positive costs are compared with the cheapest positive option in the entered set.	Lower-cost valid options receive better cost fit, but weak relief can still lose.
Lead time	Option lead time is checked against the action breach timing.	Slow options are penalized when the service is already near or past the action point.
Disruption and budget warnings	Options above the budget ceiling or maximum acceptable disruption receive score penalties.	The option remains listed, but the decision note carries the warning.

Everyday Use & Decision Guide:

Use one recognizable service or platform label, then enter a sustained current peak rather than a one-sample spike. The monthly growth value should include normal demand and any known launch, migration, seasonal, or business-growth pressure. If growth is uncertain, keep the number conservative and set Forecast confidence to Low so the brief language does not sound more certain than the evidence.

Set the action threshold to the level where capacity work should begin. Set the critical threshold to the level where the service may experience unacceptable latency, queueing, packet loss, storage exhaustion, or failover-margin loss. Keep implementation lead time realistic by including procurement, licensing, delivery, approval, deployment, and validation.

Choose Match demand incrementally when the first pass should balance runway and cost.
Choose Lead demand proactively for services where slow procurement, strict availability, or business visibility makes extra reserve worth defending.
Choose Lag until pressure is confirmed only when cost restraint is more important than early headroom and the service can tolerate tighter timing.
Use Target reserve after upgrade to avoid landing exactly on the action threshold after the change.

Option rows work best when every line has option name, cost, gain percent, lead months, disruption from 1 to 5, and a short note. The old shorter form of option, cost, gain percent, and note still parses, but the ranking is more useful when lead time and disruption are present. Use Normalize rows after pasting rough rows so the option table reflects the parsed values you intend.

The best fit is a short approval brief for infrastructure capacity work: firewall throughput, VPN load, queue workers, storage pools, circuits, clusters, licenses, or similar platform limits. It is not a live telemetry reader, a vendor sizing guarantee, or a substitute for a change plan. Treat the output as a structured briefing draft that still needs measurement evidence and engineering review.

After the first pass, work from Capacity Ledger and Option Ranking. If the summary says Start now or Critical now, verify the current peak, growth driver, and option lead time before sending the Markdown brief to an approver.

Step-by-Step Guide:

Build the brief from demand signal to option evidence, then check the ranking before using the copied text.

Enter Service or platform. Use the same label that appears in tickets, budgets, change records, or stakeholder discussions.
Set Current peak utilization, Monthly demand growth, and Planning horizon. The summary primary value should update to the forecast utilization at the selected horizon.
Set Action threshold and Critical threshold. If the critical value is not greater than the action value, the validation area reports Critical threshold must be greater than the action threshold.
Enter Implementation lead time, choose Capacity strategy, and set Target reserve after upgrade. These values shape the required gain and urgency language.
Add Bottleneck evidence in one concise paragraph. It appears in the capacity ledger and in the generated brief, so include the measured component, symptom, and operational consequence.
Paste Upgrade options as CSV-style rows, use Load sample for a working example, or press Normalize rows after importing rough rows. A row without a name or positive gain produces a validation warning such as Option row 1 needs a name and positive capacity gain.
Read the badges under Capacity Upgrade Runway. Then open Capacity Ledger for forecast, breach timing, required gain, and recommended option values.
Open Option Ranking, Utilization Runway, and Option Relief Stack when the brief needs supporting evidence beyond the Markdown text. Use JSON when another workflow needs the structured inputs and result values.

If the summary says Capacity brief needs input, clear the validation list before reading the ledger, ranking, charts, or brief text.

Interpreting Results:

The headline value is the forecast utilization at the planning horizon. Read it with the status badge and Action threshold breach. A service already above the action threshold can still show different urgency depending on growth, implementation lead time, and the selected strategy.

The recommended option is the top-ranked row, not an automatic purchasing decision. A row can rank first because it is the best available option while still saying Partial relief only or carrying a budget or disruption warning. Confirm vendor sizing, deployment constraints, and rollback planning before using the brief for approval.

How to read capacity upgrade brief outputs
Output	Trust this for	Do not overread
`Required capacity gain`	The minimum gain needed to put the horizon forecast at or below the target utilization.	It does not include vendor sizing error, architecture changes, or workload mix shifts.
`Action threshold breach`	The time until current trend reaches the action threshold.	It is not an outage forecast; it is an approval-timing warning.
`Recommended horizon utilization`	The modeled horizon utilization after the top-ranked option gain is applied.	It assumes the entered gain percent is real and delivered at the option lead month.
`Utilization Runway`	How the no-upgrade path compares with the recommended option across the horizon.	It does not account for unexpected launches, incidents, or one-off traffic changes unless they are included in growth.
`Option Relief Stack`	Which entered options reduce horizon utilization below action or target levels.	It does not prove the change is operationally safe.

A calm Monitor result should still be reviewed when the input confidence is low or the bottleneck evidence points to user-visible symptoms. A severe badge should be checked against recent telemetry before escalation, especially when the monthly growth estimate came from a short sample.

Worked Examples:

Firewall capacity approval

An internet edge firewall starts at 78% current peak utilization with 6% monthly growth over 6 months. The action threshold is 75%, the critical threshold is 90%, implementation lead time is 2 months, and the target reserve is 10 points under the match strategy. Capacity Upgrade Runway reports about 110.6% at month 6 and moves to Start now. In the sample options, Add HA pair ranks first because its 90% gain lowers Recommended horizon utilization to about 58.2% and meets target reserve.

Lead-time edge case

A worker pool at 70% utilization grows 2% per month over a 6-month horizon with a 75% action threshold and 90% critical threshold. The action threshold is about 3.5 months away. If implementation lead time is 4 months, the status becomes Start now even though critical breach is farther away. An option with 10% gain lowers the horizon to about 71.7%, so its decision note can read Below action threshold while still missing the stricter target reserve.

Invalid option rows before review

A user pastes License expansion,15000,0,Needs vendor quote and leaves every other option blank. The validation list reports that the row needs a name and positive capacity gain, and the summary stays at Capacity brief needs input. Changing the row to include a positive gain, such as License expansion,15000,30,2,2,Needs vendor quote, lets Option Ranking, Capacity Ledger, and the brief text populate.

FAQ:

What should I use for current peak utilization?

Use a recent sustained peak as a percentage of usable capacity. A one-sample spike can exaggerate urgency unless that spike is the exact service-level risk the brief needs to defend.

Why does the brief say start now before the horizon ends?

The status compares action breach timing with implementation lead time and strategy urgency. If the action threshold is too close for the change path, the badge can show Start now even before the planning horizon reaches the critical threshold.

What format do upgrade option rows use?

Use one row per option in the order option, cost, gain percent, lead months, disruption from 1 to 5, and note. Shorter legacy rows with option, cost, gain percent, and note still parse, but ranking has less evidence.

Why is an option listed if it is over budget?

The budget ceiling is a ranking penalty and warning, not a filter. Over-budget options remain visible so reviewers can see whether the stronger capacity result is worth escalation or should be ruled out.

Does forecast confidence change the math?

No. Forecast confidence changes the wording in the capacity ledger and brief context. The projected utilization, threshold timing, required gain, ranking, and charts still use the numeric inputs.

Does it connect to monitoring systems?

No. The analysis uses the values and option rows you enter in the browser session. It does not query telemetry, procurement, vendor, or change-management systems.

Glossary:

Action threshold: The utilization level where capacity work should begin before service quality, resilience, or delivery lead time is at risk.
Critical threshold: The utilization level where unacceptable latency, queueing, packet loss, exhaustion, or failover-margin loss may occur.
Planning horizon: The future month used to evaluate forecast utilization, required gain, and option relief.
Implementation lead time: The time needed for procurement, licensing, approval, deployment, and validation before capacity relief is available.
Target reserve: The intended gap below the action threshold after the upgrade has been applied.
Required capacity gain: The minimum percent gain needed to bring the horizon forecast down to target utilization.
Horizon utilization: The forecast utilization at the planning horizon, either without an upgrade or after an option's gain is applied.

References:

Site Reliability Engineering: Introduction, Google SRE, 2017.
Production Services: Best Practices, Google SRE, 2017.
Reliability Pillar, AWS Well-Architected Framework, 2020.
What is capacity planning?, IBM Think.