A pipeline value tells resource teams little about who will be needed and when. To plan capacity, they need roles, skills, effort, start dates and confidence. That translation is where a commercial forecast becomes a usable demand plan.
The commitment starts before the contract
Sales may describe a promising opportunity as one deal. Delivery needs a different description: which roles, what skills, how much time and which start date. Capture those requirements while the opportunity is still being shaped. A revenue total cannot tell a resource manager whether two specialist roles will be available together.
Turn an opportunity into a staffing requirement
Separate confirmed work from tentative demand. Record both the probability of winning and the confidence in the proposed start date. Two opportunities with similar value can create very different capacity requirements because their timing, skills and staffing patterns differ.
- Requirement: role, proficiency, location and working arrangement.
- Timing: earliest start, expected duration and scheduling flexibility.
- Demand state: tentative, approved or confirmed.
- Supply: availability after leave, existing commitments and planned releases.
Use scenarios rather than a false average
Suppose two possible projects each need the same architect for a full month. A probability-weighted view might suggest one architect is sufficient, yet winning both requires two. Keep the weighted planning view, but also inspect the simultaneous-win scenario and the consequences of a delayed start.
Review what changed before confirming the date
Run a short review around new opportunities, changed dates and imminent release dates. Assign an owner to each unresolved role. Before a delivery date is promised, make the trade-off visible: tentative reservation, internal redeployment, external sourcing or a revised start.
Explore the relevant Clousys workflow: Resource Management. Bring a current requirement to the walkthrough so the discussion can cover your records, responsibilities and configuration needs.
Put these ideas into your operating model.
Explore a focused Clousys walkthrough built around your current systems, handoffs and leadership priorities.
