TAP TAP GO
Describe the capacity unit
Explain what capacity means in the proposed service: projects, users, orders, support cases or another relevant unit. State the conditions under which the estimate applies. Avoid multiplying a small successful demonstration into a large delivery claim without examining the work involved. Identify staffing, supplier, training and process dependencies that may change as demand increases.
Separate current and planned capacity
Show what is available now and what would need to be added. Keep management targets distinct from demonstrated throughput. Describe the evidence available for review, such as operating records or a bounded pilot, without exposing confidential customer information. Use the discussion to identify the next validation step. A credible capacity story can include constraints; those constraints help a prospective partner understand how expansion would actually be managed.
Put the guide to work
Ask which constraint would become visible first if demand doubled in the proposed scenario. Treat the answer as a planning question, not a forecast. It can help the team identify a practical test or resource decision before making a larger delivery commitment.
Hypothetical example
A supplier successfully supports one event and claims readiness for a large multi-city programme. Its capacity review identifies training and support coverage as the main constraints. The proposal then describes staged expansion and the evidence needed before each additional deployment.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
