Operating model
Under control, by design.
Capital projects seldom slip for want of data. They slip when schedule, cost, risk, and contract information sit in separate systems, reconciled late and read optimistically, so leadership learns of a deviation after the time to act has passed. The operating model closes that gap: one control rhythm, run every reporting period on one data date, through six disciplines that bring their evidence to the same decision.
The disciplines across and the rhythm up form a matrix, and eighteen processes sit where they cross. Each builds on the ones beneath it, so a weakness low in the matrix shows in every forecast above it and can be traced to its source. What leadership gets is a position it can act on each reporting period: one reconciled set of numbers, forecasts adjusted for risk, and decisions recorded and tracked to closure.
At a glance
- Rhythm
- Plan to act, every reporting period.
- Disciplines
- Connected disciplines that run the whole rhythm.
- Architecture
- The dependency map of the processes.
- Ledger
- A card for every process.
Control rhythm
The rhythm is temporal.
Plan, measure, forecast, and act, repeated every reporting period on one data date, with every discipline taking part.
Plan
Frame and baseline
Set governance and decision rights, then approve the scope, the credible schedule, the mapped budget, the risk approach, and the performance measurement baseline.
Measure
Record and measure
Delivery teams run the approved work while project controls records physical progress, accruals, deliverables, and exposure at one data date and measures performance against the baseline.
Forecast
Forecast and adjust
Turn the actuals into forecast dates and estimates at completion, adjust them for risk, test emerging claims and exposure, and compare the results with the variance thresholds.
Act
Prevent and correct
Escalate threshold breaches, authorize change and preventive or corrective action, record the decision, and track actions to closure.
Next reporting period
Back to Plan, with current evidence.
Carry forward the latest forecast, approved changes, updated risks, and open actions, and confirm what the next reporting period must control.
Control disciplines
No discipline decides alone.
Six connected disciplines, not a handoff sequence: each contributes its evidence to the same reporting-period decision. The processes they are made of follow in the architecture.
Governance
PMO governance
First, the frame: decision rights, baselines, reporting thresholds, and escalation routes, agreed before delivery starts.
- A PMO governance framework with performance baselines, reporting structures, and escalation pathways
- To equip executive leadership with oversight of program performance
Risk
Risk management
Risk governed from appetite and identification through qualitative and quantitative analysis, response, contingency, monitoring, and escalation.
- An enterprise risk management (ERM) framework with appetite and tolerance thresholds, and quantitative risk analysis (QRA) using Monte Carlo simulation
- To deliver risk-adjusted baselines, P-level forecasts, and evidence-based contingency allocation
Schedule
Integrated planning
One integrated plan across contractors and work packages, with interfaces resolved before they become conflicts.
- Interdependent schedules synchronized across contractors and work packages
- To resolve interface conflicts and maintain schedule integrity
Cost
Budgeting and cost control
Budgets mapped to the performance measurement baseline, and schedule-driven forecasts that reconcile cost to date, commitments, and remaining exposure.
- Five-year and annual financial plans with schedule-driven rolling forecasts
- To drive capital allocation and cash flow management
Commercial
Commercial controls
Commitments and claims tested against contract, budget, schedule, and approved change before money moves.
- Invoice verification, change order evaluation, and extension-of-time (EOT) assessment
- To safeguard budgets against unsubstantiated claims and support dispute resolution
Reporting
Performance reporting
Schedule and cost evidence reconciled to one baseline and one data date, with variances and forecasts prepared each reporting period and their assembly automated.
- A performance measurement baseline, enterprise project portfolio management (EPPM) software linked to enterprise systems, and reporting automation
- To produce executive dashboards tracking schedule performance index (SPI), cost performance index (CPI), estimate at completion (EAC), and variance trends
What the disciplines serve
Six disciplines, one decision.
Together they give leadership a program it can steer, risk exposure ready for board-level advice, and reporting built to reduce manual effort and improve data accuracy.
Control architecture
A structure, not a checklist.
Eighteen processes across the six disciplines. Each builds on the processes beneath it, none can be skipped, and Credible schedule is the keystone.
Scroll the map sideways
Reading the map
Columns, bands, and lines.
Each column is a discipline and the bands are the control rhythm, plan to act, bottom to top. A straight line up a column is the discipline's own chain; the risk and commercial processes build on the schedule and cost processes beside them and revise them in return, the line returning into the box. Hover a process to light what it builds on and what builds on it; the ledger that follows names every dependency.
Control ledger
Process by process.
The processes by discipline, in map order. Each entry names what it builds on, and a process clicked on the map lands on its entry.
GovernancePMO governance
1.1
Strategic alignment
Project targets map to enterprise objectives; control gates, priorities, timing, and resources are decided against strategic value.
1.2
Governed delivery
Decision rights, processes, procedures, and the work, cost, and organization breakdown structures (WBS, CBS, OBS) are defined and applied in line with strategy.
Builds on 1.1 Strategic alignment
1.3
Evidence-led decisions
Reported estimates and forecasts produce timely decisions, clear dispositions, accountable actions, and verified outcomes.
Builds on 1.2 Governed delivery, 6.3 Forecast and escalation
RiskRisk management
2.1
Risk-based approach
Uncertainty, triggers, owners, and responses are recorded, and the responses are built into the schedule and budget before exposure becomes an issue.
Builds on 3.1 Credible schedule, 4.1 Mapped budget
2.2
Monitored exposure
Risks, triggers, and issues are updated against current progress and cost; exposure is tested against approved appetite, and threshold breaches escalate.
Builds on 2.1 Risk-based approach, 3.2 Evidence-based updates, 4.2 Progress-based accruals
2.3
Risk-adjusted forecasts
Quantitative risk analysis and what-if scenarios turn current forecasts into risk-adjusted dates and costs at a stated confidence level, and size the contingency.
Builds on 2.2 Monitored exposure, 3.3 Reliable forecast, 4.3 Schedule-driven forecasts
ScheduleIntegrated planning
3.1
Credible schedule
Complete scope, valid logic, measurable work within one reporting period, loaded critical resources, and work packages linked through interface milestones.
Builds on 1.2 Governed delivery, 2.1 Risk-based approach, 5.1 Change management
3.2
Evidence-based updates
Actual dates, physical progress, and remaining durations are supported by current records at each data date.
Builds on 3.1 Credible schedule, 2.2 Monitored exposure, 5.2 Deliverable tracking
3.3
Reliable forecast
Remaining work, logic, and resource loading drive the forecast dates, so a slip in one package shows its effect on every other and on completion.
Builds on 3.2 Evidence-based updates, 2.3 Risk-adjusted forecasts, 5.3 Defensible position
CostBudgeting and cost control
4.1
Mapped budget
Budget is mapped to control accounts, allocated to work packages, and time-phased into the performance measurement baseline, with contingency held in its own account.
Builds on 1.2 Governed delivery, 3.1 Credible schedule, 2.1 Risk-based approach, 5.1 Change management
4.2
Progress-based accruals
Accruals reflect verified progress for work completed but not yet invoiced at the data date.
Builds on 3.2 Evidence-based updates, 4.1 Mapped budget, 2.2 Monitored exposure, 5.2 Deliverable tracking
4.3
Schedule-driven forecasts
Project, annual, and cash forecasts follow current schedule dates, and the estimate at completion reconciles cost to date, commitments, and remaining exposure.
Builds on 3.3 Reliable forecast, 4.2 Progress-based accruals, 2.3 Risk-adjusted forecasts, 5.3 Defensible position
CommercialCommercial controls
5.1
Change management
Trends, change instructions, and notices are logged with response dates and stay traceable through assessment, approval, schedule, cost, and contract modification.
Builds on 3.1 Credible schedule, 4.1 Mapped budget
5.2
Deliverable tracking
Contract obligations, deliverables, and acceptance criteria are assigned and tracked against the schedule.
Builds on 5.1 Change management, 3.2 Evidence-based updates, 4.2 Progress-based accruals
5.3
Defensible position
Contemporaneous records and early tests of entitlement, causation, and quantum keep the position defensible against unsubstantiated claims and disputes.
Builds on 5.2 Deliverable tracking, 3.3 Reliable forecast, 4.3 Schedule-driven forecasts
ReportingPerformance reporting
6.1
Performance measurement baseline
Scope, schedule, and cost integrated into one baseline, with reporting structures, variance thresholds, and the reporting period set before performance is judged.
Builds on 1.1 Strategic alignment, 3.1 Credible schedule, 4.1 Mapped budget
6.2
KPIs and variance analysis
Performance data share one data date and reconcile to the baselines and source records; earned value, indices, and variances are analyzed for cause and trend.
Builds on 3.2 Evidence-based updates, 4.2 Progress-based accruals, 6.1 Performance measurement baseline
6.3
Forecast and escalation
Estimates at completion and forecast dates are reported against the baselines and compared with the variance thresholds; breaches escalate for decision.
Builds on 3.3 Reliable forecast, 4.3 Schedule-driven forecasts, 6.2 KPIs and variance analysis
What the architecture serves
No process stands alone.
A forecast is only as reliable as the actuals beneath it, and the actuals only as reliable as the baseline. The map reads the maturity of a project's processes the same way: which are in place, which build on processes that are not, and where to strengthen first.
Use and attribution
Free to use, with credit.
The operating model on this page, its text, map, and ledger, is © 2026 Shahyn Management Consultancy L.L.C-FZ. It may be used and adapted, in whole or in part, with credit to Shahyn Management Consultancy and a link to this page, shahynmc.com/operating-model. It is published as a method, not as advice on any specific project. The Shahyn name, wordmark, and logo are not licensed.
Contact
Where to strengthen first.
Share the current position and the decision leadership faces next. The first conversation names the discipline to start with and the evidence it needs.