Capacity Watch
Review utilization trends before storage, compute, licensing, or staff capacity becomes urgent.
Purpose
Capacity work should look for trend, threshold, business context, and lead time. Capacity risk becomes expensive when detected only after users experience service limits.
Operating record
| Cadence | Set a normal review interval and event-driven trigger. |
|---|---|
| Owner | Identify the role accountable for keeping capacity watch current. |
| Source data | List the systems, logs, reports, tickets, or records used during review. |
| Findings | Record exceptions, decisions, blockers, risk changes, and follow-up actions. |
| Evidence | Keep the smallest durable proof that the review occurred and produced a result. |
When to use
- When the work repeats often enough that memory is no longer reliable.
- When more than one person may request, perform, review, or inherit the work.
- When risk, approval, evidence, or handoff needs to be visible later.
Common failure modes
- Utilization thresholds ignore growth trend.
- Procurement lead time is missing from planning.
- Capacity ownership is split across teams.
Review guidance
Review this page after a material incident, after a role or system change, and on a normal cadence appropriate to its risk. During review, check whether the owner is still correct, whether inputs are still complete, whether the output is still useful, and whether related pages need updates.
External guidance
These resources are references for terminology, control thinking, or review design. DailyWF adapts the ideas into lightweight operating pages rather than reproducing full standards.
- ISO quality management principlesProcess approach, evidence-based decisions, improvement, and relationship management.
- NIST Cybersecurity Framework 2.0General cybersecurity risk management structure: govern, identify, protect, detect, respond, recover.