Operating model
Under control, by design.
Governance, risk, schedule, cost, commercial controls, and reporting are connected through one control rhythm. In each reporting period, current evidence is reconciled at one data date, performance is measured against the baseline, and forecasts are prepared for leadership decisions.
The architecture maps eighteen processes and their dependencies, showing how a gap or weakness in one process can affect those that build on it. The ledger describes each process for use in a scoped review or implementation.
Scope and application
Proportionate depth. Explicit boundaries.
The project's stage, scale, contractual obligations, and reporting requirements determine the depth of control. Define the processes in scope, their owners, and the evidence required. Record exclusions and their implications for dependent processes and outputs.
Control rhythm
The rhythm is temporal.
Plan, Measure, Forecast, and Act repeat every reporting period. All disciplines use one data date and reconcile their evidence into a single reporting position.
Accepted updates and material exceptions can be assessed between reporting dates. The reporting cadence must support measurable progress, accruals, and comparable baseline measures.
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, assess 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
Current evidence. Controlled change.
Return to Plan with the latest forecast, updated risks, recorded decisions, and open actions. Each open action retains an owner and due date until closure is verified. Preserve the approved baseline and incorporate authorized changes through change management.
Control disciplines
No discipline decides alone.
Six connected disciplines contribute evidence to a single reporting position. Each participates throughout the control rhythm; their processes and dependencies 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 through appetite and tolerance, identification, qualitative and quantitative analysis, response, contingency, monitoring, and escalation.
- An enterprise risk management (ERM) framework with risk appetite and tolerance, 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 using one data date, with variances and forecasts assessed against the baseline 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
Assess the consequences across disciplines.
A schedule change can alter cost, cash flow, contractual exposure, and risk-adjusted forecasts. Reconcile those effects across disciplines before presenting a position for decision.
The combined purpose is informed program direction, board-level advice on risk exposure, and reporting designed to reduce manual effort and improve data accuracy.
Control architecture
A structure, not a checklist.
Eighteen processes across six disciplines are connected by their dependencies. Credible schedule is the keystone of this delivery-controls model, linking scope and resource planning to budgeting and forecasting.
Processes by phase
Open a phase and select a process to read its description and dependencies in the ledger.
Plan7 processes
Measure5 processes
Forecast5 processes
Act1 process
Full dependency map
Scroll the map sideways to compare discipline columns. The ledger below names every dependency.
Reading the map
Read the dependencies and the return loops.
Each column is a discipline; the phase bands read from Plan at the bottom to Act at the top. Lines show dependencies and return loops. Each core box pairs a schedule and cost process; risk and commercial lines returning into it show revisions to that pair. Hover to trace direct relationships; select a process to read its ledger entry.
Open a phase and follow a process link to the ledger. The full map shows the dependency structure by discipline and phase, from Plan at the bottom to Act at the top. Risk and commercial processes revise the schedule and cost processes they build on; the ledger includes both directions of these relationships.
Control ledger
Process by process.
The processes are grouped by discipline, in map order. Each entry describes its process; the “Builds on” links identify dependencies.
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 reflect current progress and cost; exposure is assessed against approved appetite and tolerance, 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, progress measurable at the reporting cadence, 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 Commercial reconciliation
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 Commercial reconciliation
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
Commercial reconciliation
Deliverable, invoice, payment, and claim status is reconciled with contract terms, acceptance evidence, and schedule and cost records; disputes are identified.
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 Commercial reconciliation, 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
A weakness in one process can compromise others.
Assess each process against its purpose, evidence requirements, and assigned responsibilities. Trace material gaps through the mapped dependencies to assess their effects on other processes and outputs. Prioritize corrective action, assign owners, and define how closure will be verified.
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
Strengthen your project controls.
Share the current position and the decision leadership faces next. The first conversation clarifies the processes to review, the evidence required, and the scope of any implementation.