01 / EBOOK
Connected context
Start with the relationships between opportunity demand, skills, assignments, projects and financial outcomes. An isolated data point rarely explains a services decision. The useful context is the chain showing how a change in one team’s plan affects the others.
- Linked records
- Shared definitions
- Business context
Related platform capability →02 / EBOOK
Risk signals
Use operational signals to focus attention on potential delivery, capacity and revenue issues. Distinguish observed facts from forecasts and make uncertainty visible. Teams need to understand why a warning matters before they can decide how to respond.
- Signal source
- Risk driver
- Forecast confidence
Related platform capability →03 / EBOOK
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.
- Skills required
- Demand confidence
- Start and end dates
Related platform capability →04 / EBOOK
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.
- Working calendar
- Leave
- Planned releases
Related platform capability →05 / EBOOK
Project context and ownership
Give every project a clear scope, accountable manager and delivery structure. Keep the team aligned on the work being delivered and the commitments behind it. Project context connects scheduling and execution decisions to the client outcome instead of leaving the plan as an isolated task list.
- Project owner
- Scope
- Delivery commitments
Related platform capability →06 / EBOOK
Risks, assumptions, issues and dependencies
Capture RAID items with an owner, impact and next review. Distinguish a potential risk from an issue already affecting delivery. Escalations should connect the operational cause to the milestone, capacity or commercial consequence, making the required decision clear.
- RAID owner
- Impact
- Mitigation action
Related platform capability →07 / EBOOK
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.
- Committed work
- Forecast assumptions
- Delivery dates
Related platform capability →08 / EBOOK
Confirmed leakage versus estimated exposure
Keep confirmed blocked revenue separate from modelled exposure. Confirmed amounts should be traceable to transactions; estimates depend on explicit assumptions. Adding both into one total can mislead decision-makers and obscure whether an intervention is resolving an existing blockage or preventing a possible one.
- Transaction evidence
- Model assumptions
- Separate totals
Related platform capability →