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.
Translate a sales scenario into a staffing scenario
Two opportunities each have a 50% probability and each needs one full-time architect for the same month. A weighted model suggests demand for one architect. In reality, the business may win neither, one or both. If both close, the requirement is two architects at the same time. The weighted average does not describe the staffing commitment you would need to make.
Use weighted demand to discuss portfolio exposure, then examine discrete scenarios for scarce skills. Show the earliest start, likely duration and practical notice needed for each staffing option. This makes the handoff from CRM opportunity to resource demand concrete without confusing a sales estimate with a confirmed project booking.
Illustrative operating example; this is not a reported customer result or a product performance claim.
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.
Translate one opportunity before modelling the whole pipeline
Take an illustrative implementation opportunity with a proposed start next month. Sales records the expected fee and close date. Resource planning adds a discovery lead for two weeks, an architect for six weeks and a delivery team that ramps up after design approval. Those staffing dates may differ from both the contract date and the invoice schedule.
Link every requirement back to the opportunity, but do not make the opportunity stage its only source of confidence. A customer may be likely to sign while still being uncertain about procurement or access. Capture that timing uncertainty so the staffing plan can show a realistic window rather than a falsely precise Monday start.
Agree what a tentative reservation actually means
A tentative allocation should say who requested it, which opportunity it supports, when it expires and who can confirm it. Without these rules, a soft reservation can quietly prevent a consultant from being assigned to signed work. Conversely, deleting it without discussion can leave sales promising a team that no longer exists.
Use the review to compare competing opportunities and the cost of holding capacity. Some requirements justify early specialist recruitment; others need a backup plan until commercial confidence improves. Make the trade-off visible rather than allowing whichever spreadsheet was updated last to determine the outcome.
Review forecast quality after the start date
Compare the roles and dates originally forecast with what actually began. Separate lost opportunities from delayed opportunities and inaccurate role estimates. Each points to a different improvement: qualification, date discipline or better collaboration with delivery during scoping.
Keep both the original forecast and the revised plan. Overwriting yesterday’s assumptions makes today’s plan look tidy but prevents you from learning why shortages occurred. The goal is a more useful conversation about future capacity, not a pipeline number that appears exact.
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.
A practical checklist for your team
Capture the shape of work
Describe roles, effort and date ranges rather than only opportunity value. Two deals with similar value can require very different skills and delivery patterns.
Review confidence jointly
Sales should explain commercial confidence; delivery should explain schedule feasibility. Preserve both views rather than hiding them inside one probability field.
Protect confirmed work
When turning demand into bookings, show which existing commitments would be affected. Escalate conflicts before confirming an assignment or customer start date.
What happens when the opportunity slips?
Update the dated demand and review tentative bookings, hiring requests and partner reservations linked to it. Keep the reason and previous dates so teams can understand the change instead of discovering it through conflicting spreadsheets.
Put these ideas into your operating model.
Explore a focused Clousys walkthrough built around your current systems, handoffs and leadership priorities.









