Commercial intent to delivery reality.
How the Deal Model becomes the Project Plan, how staffing changes show in the outlook as they happen, and how additional scope is captured before margin is lost.
How do you track project profitability as delivery changes?
By starting delivery from the deal model rather than a blank plan. The Deal Model converts into the Project Plan, and the outlook reads from that plan as staffing, phasing and scope move. Delivery-led scope is captured as a priced change rather than quietly absorbed, so a project's current margin position stays visible while there is still time to act.
The delivery layer downstream of Pipeline.
Projects is the delivery layer downstream of Pipeline. It is not a project-management database. It is where the deal model behind a won deal becomes the Project Plan, and where staffing changes, phase shifts and additional scope stay visible as financial decisions rather than after-the-fact explanations.
Five surfaces work together, anchored by one operational principle: the Project Plan is the canonical editing surface for project assumptions. Convert to Project promotes the Deal Model into the Project Plan without re-entry. From that moment, delivery reality is managed by updating plan assumptions, not spreadsheets.
What delivery does, and what the system carries forward.
Manage the Project Plan as the canonical editing surface.
Scan project health and portfolio performance at a glance.
Capture delivery-led scope changes, and link them back to Sales.
- Mark signed only: phase becomes firm, revenue moves into Contracted, no Pipeline event.
- Record sale now: creates a Won opportunity in Pipeline in the same action, named "Extension: [Project] / [Phase]," traceable back to the project.
See the financial impact of all projects across time horizons.
This area does not stand alone.
Pipeline and deal pricing
Convert to Project carries the Deal Model through to project delivery intact: same roles, people, phases and commercial modes. The Project Plan is what the outlook is built from, so the margin you see in delivery is on the same rows the deal was priced on.
People cost and capacity
Adding a person to a plan triggers capacity and availability checks. Open roles are modelled financially using grade cost. The same cost resolution that drives the Project Plan governs bench cost and firm-level P&L.
Timecards and delivered cost
With Timecards on, Exceptions compare planned days from the Project Plan with delivered days per person and project, month by month, and accepted time lands on the project as delivered days and delivered cost. Time is evidence of delivery against the plan. It does not author revenue and it does not move the outlook.
Forward P&L
Project margin and cost roll into the firm's monthly P&L Outlook, filterable by scenario. Signing an extension with Record sale now creates a Won opportunity in Pipeline that feeds firm-level Contracted revenue. The continuity closes the loop.
Management cockpit
Projects surfaces, including list health, portfolio financials, and open roles, feed the Dashboard's Outlook and Drivers panels. Projects ending soon and extension opportunities appear as drivers, ranked by revenue impact. Open roles flow into the Open Demand headline.
The discipline behind it
Extensions and change requests are margin decisions, not administration. Commercial Discipline is the principle behind capturing delivery-led scope and pricing it before it erodes the margin the Project Plan carries into the outlook.
See how delivery teams execute against commercial intent, and how changes are captured without losing the original plan.