INSIGHT ·
From Pipeline to Capacity: Building a Connected Demand Forecast
Translate likely opportunities into dated skill requirements without treating every possible deal as a confirmed assignment.
Read article →Operating playbook · CLOUSYS OPERATIONS LIBRARY
From Resource Planning to Revenue
Turn the staffing plan into a reliable delivery and revenue plan.
For resource managers, delivery leaders and finance teams who need to connect capacity decisions to billable work.
WHY THIS MATTERS
Turn the staffing plan into a reliable delivery and revenue plan.
A resource plan is more than an allocation calendar. Each assignment has a start date, effort expectation, skill requirement and commercial context. When those details are separated from delivery and finance, teams can appear fully staffed while milestones remain exposed or completed work cannot be invoiced. This playbook follows the same engagement from demand through assignment and delivery into billing readiness.
CHAPTER 1
Demand before the project starts
Translate upcoming work into dated resource requirements. Capture the skill, effort, duration and confidence of each need. A likely opportunity and a signed project should remain distinguishable so planners can model scenarios without double-booking people against uncertain demand.
CHAPTER 2
Capacity with real constraints
Available capacity is not simply headcount. Subtract existing assignments, leave, working patterns and internal commitments from the planning horizon. Compare supply with dated demand by skill and role, and inspect upcoming releases before deciding that a gap requires a new hire.
CHAPTER 3
Allocation on one timeline
See project assignments alongside the people doing the work. Weekly and monthly views reveal overlaps, unassigned demand and timing conflicts that a list of names cannot. Review assignment percentages with the underlying working hours so a part-time colleague is not treated as a full-time resource.
CHAPTER 4
Bench and redeployment
Identify people approaching the end of an assignment and connect them to upcoming work. Review bench exposure against demand timing and skill fit rather than pushing every available person into the first open slot. Earlier visibility creates room for redeployment, targeted development or a revised staffing plan.
CHAPTER 5
Backlog and work boards
Organize epics, use cases and backlog items into a delivery workflow. Track work through agreed states so the team can distinguish work waiting to start from work actively in progress. Keep the board connected to project priorities and use it to resolve constraints, not only to report activity.
CHAPTER 6
Forecast against actual effort
Compare expected effort with recorded work throughout delivery. Review the remaining effort as well as the variance already incurred. A project can be busy and still be moving away from its commercial plan; early variance reviews give delivery and finance time to discuss scope, staffing or estimates.
CHAPTER 7
Revenue with an operational basis
Build the forecast from work that can realistically be staffed and delivered. Keep opportunity assumptions, committed work and billing expectations distinguishable. When a date or allocation changes, review the downstream revenue effect instead of updating the finance forecast independently of delivery.
CHAPTER 8
Commercial exceptions
Review billing exceptions against the engagement’s agreed terms. Rate discrepancies, purchase-order constraints and missing approvals require different resolution paths. Keep the reason and accountable owner visible; a single unbilled total does not explain which decisions will release the value.
TEAM WORKSHOP
Apply the framework to one real engagement.
Take a project due to start within the next month. List the requested roles, confirmed assignments, remaining gaps and expected billing model. Then test a change: one specialist becomes unavailable for a week. Identify the delivery commitment affected, the replacement options and the impact on planned effort and billing. Preserve the assumptions so the next review can compare plan with actuals.
Agree the review cadence before expanding the scope. Use the same definitions each time and note changes to assumptions. Progress should be visible in the evidence behind the decision, not only in the appearance of a new dashboard.
TAKE THE GUIDE WITH YOU
Use it in your next operating review.
The PDF contains the framework, chapter notes and working-session prompts shown here. Share it with the teams who own the handoffs so everyone can prepare using the same questions.
Your details are not submitted to a mailing list by this download form.
A practical example
An IT services team has a senior backend engineer available in two weeks and an urgent role beginning next Monday. A second engineer can cover part of the work but lacks one required skill. Hiring immediately may be unnecessary if discovery can start with the available team and the senior engineer joins before implementation. The planning review must compare dated work, not merely match a job title to a person.
The measurement behind the decision
A specialist has 40 contracted hours, 8 hours of approved leave and 4 hours reserved for internal work. The remaining assignable capacity is 28 hours. A proposed 24-hour assignment leaves 4 hours of headroom. Adding a separate 12-hour request would exceed that planning capacity by 8 hours. Do not describe the specialist as 90% allocated without specifying which denominator the percentage uses.
Weekly: refresh supply and demand
Review opportunity changes, confirmed project dates, leave and assignments ending in the next four weeks. Every gap should have a skill, effort and date range. Keep uncertain opportunities in a separate scenario so the committed schedule remains executable.
At assignment: confirm the economics
Validate skill fit and availability with the person and delivery owner. Check the expected rate, staffing cost and scope assumptions with finance when material. Confirm who can approve a substitution and record the reasons for any exception.
At period close: reconcile intent and actuals
Compare planned hours, recorded time, approved billable work and invoice-ready value. Investigate the gap stage by stage. A low realized utilization figure may arise from missing time, non-billable scope or an allocation assumption; each requires a different response.
Download the complete field guide
Includes the operating model, worked example, decision tables, implementation cadence and a reusable workshop worksheet.
