Blog · Territory, capacity and quota planning
Connect accepted commercial scope to delivery readiness, customer expectations and unresolved dependencies. Keep signed sales, delivered scope and recognized revenue distinct.
A newly signed expansion can create problems when the delivery team receives a product code and an amount but not the promises made during the sale. The customer expects a particular site, specification and date; operations plans something else. A reviewed handover connects the accepted commitment to the work needed to fulfill it.
The bookings, billings and revenue guide preserves the financial distinctions. This article owns operational readiness between the accepted sale and delivery, not an accounting recognition rule.
Identify the order or agreement, version, customer decision unit, delivery sites, specifications, quantities and accepted dates. Use the agreed record rather than a salesperson's earlier draft. Attach any approved changes and show unresolved interpretation questions.
Keep commercial and operational terms together. A service commitment, required installation or promised support arrangement can be as material as the product itself. If the delivery team cannot find the evidence, mark the handover incomplete.
Use the account hierarchy and sold-to, bill-to and ship-to guide to prevent the purchasing account from being confused with the delivery location.
Review availability, required configuration, delivery capacity, customer preparation and any technical acceptance. Name an owner and an evidence source for each applicable dependency. Avoid adding checks that do not matter to the proposed scope.
A customer may need to provide access or complete a prerequisite before delivery. Record that dependency and the confirmed date; do not assign it to the supplier's queue without explanation. Conversely, an unresolved supplier capacity problem should not be labeled as a customer delay.
Use separate readiness states: confirmed ready, confirmed blocked and unknown. Unknown means the evidence is missing; it is not a green status or proof that delivery will fail.
The DEMO-901 portfolio below is invented. Its values are signed order amounts on one declared commercial basis, not recognized revenue. Twelve orders total $450,000.
| Readiness state | Orders | Signed value | Next review |
|---|---|---|---|
| Confirmed ready | 8 | $300,000 | Confirm release and customer date |
| Confirmed blocked | 3 | $100,000 | Resolve named delivery dependencies |
| Unknown evidence | 1 | $50,000 | Obtain missing readiness confirmation |
| Total | 12 | $450,000 | States reconcile to signed population |
Ready value is $300,000 / $450,000 = 66.7%. Blocked value is 22.2% and unknown value is 11.1%, rounded. Ready orders are also 8 / 12 = 66.7%; that equality is incidental to this example, not a relationship between count and value rates.
Removing the unknown order would raise the apparent ready count rate to 8 / 11 = 72.7%. The report would become more flattering by omitting an unresolved commitment. Keep the unknown state visible instead.
For a blocked order, describe the dependency, impact, available alternatives and decision owner. If a different item or date is proposed, record customer approval through the agreed route before changing the commitment view.
Preserve the original date and revised date. That makes a later performance review interpretable rather than allowing internal edits to erase a delay. Use the order-to-activation guide for the duration measure after the relevant events exist.
The UK government's contract-management principles provide context on clear roles and controlled change. The readiness states here are an original operating design, not a mandated private-sector process.
Agree who communicates the status, confirms any changed expectations and records the response. An account manager and delivery team sending different dates can make a manageable dependency into a relationship problem.
The specialist handoff guide addresses earlier cross-team qualification. A delivery handover follows an accepted commitment and therefore needs the agreement version and fulfillment evidence, not just a promising customer question.
Record delivery, customer acceptance and remaining obligations under the applicable terms. Keep finance's reporting basis separate. Where ongoing purchases matter, the repeat-demand guide follows the new category after its first order.
Bring this readiness view beside the completed customer-growth review. Share an authorized order sample through Covirage contact to agree the evidence required and review scope.
No. Availability, specifications, customer prerequisites and delivery ownership may still be unresolved. Review those separately against the accepted scope.
No. Operational readiness and revenue recognition are different views. Finance must apply the appropriate accounting policy and evidence.
Use the agreed commercial and customer approval route. Record the revised commitment and customer confirmation rather than silently changing an internal planning date.