Skip to content
Search

Scope Schedule and Budget Management

Every project operates within three interdependent constraints:

Scope
/ \
Schedule ── Cost

Change one, the others are affected. If scope increases, schedule or cost (or both) must increase to compensate. If timeline compresses, either scope must decrease or cost must increase (more resources). The project sponsor chooses which constraints are fixed and which flex — the consultant’s job is to make that trade-off explicit.

Common client assumption to challenge: “We need the same scope, same timeline, and the budget is fixed.” This is the triple constraint in violation — it requires scope reduction or will result in budget overrun.


The WBS decomposes the project into deliverable-based work packages — not activities, but outputs. A deliverable-based WBS makes scope boundaries visible.

Engagement
├── Phase 1: Discovery
│ ├── 1.1 Current-State Assessment Report
│ ├── 1.2 Data Collection Package
│ └── 1.3 Stakeholder Interview Findings
├── Phase 2: Analysis
│ ├── 2.1 Network Flow Model
│ ├── 2.2 Process Gap Analysis
│ └── 2.3 Benchmarking Report
└── Phase 3: Recommendations
├── 3.1 Solution Options Brief
├── 3.2 Implementation Roadmap
└── 3.3 Business Case / ROI Model

Each lowest-level work package should be assignable to a single owner and estimable in effort (hours) and duration.


CPM identifies the longest-duration path through the project — the critical path. Any delay on the critical path delays the project end date.

Key terms:

  • Float (slack): How long a task can slip before it affects the project end date. Critical path tasks have zero float.
  • Dependency types: Finish-to-Start (most common), Start-to-Start, Finish-to-Finish
  • Fast-tracking: Running critical-path tasks in parallel to compress schedule (increases risk)
  • Crashing: Adding resources to critical-path tasks to shorten duration (increases cost)

Practical use in consulting: Full CPM networks are overkill for most consulting engagements. Use CPM to identify 3–5 tasks whose slippage would blow the delivery date, then actively manage only those.


EVM provides objective performance measurement by comparing planned value, earned value, and actual cost at any point in the project.

TermAbbreviationDefinition
Budget at CompletionBACTotal planned budget
Planned ValuePVBudgeted cost of work scheduled to be done by today
Earned ValueEVBudgeted cost of work actually completed by today
Actual CostACActual cost incurred by today
IndexFormulaInterpretation
Schedule Performance IndexSPI = EV / PV<1.0 = behind schedule; >1.0 = ahead
Cost Performance IndexCPI = EV / AC<1.0 = over budget; >1.0 = under budget
Schedule VarianceSV = EV – PVNegative = behind
Cost VarianceCV = EV – ACNegative = over budget
ForecastFormulaUse
Estimate at CompletionEAC = BAC / CPIProjected final cost at current CPI
Estimate to CompleteETC = EAC – ACRemaining budget needed
Variance at CompletionVAC = BAC – EACProjected final over/underrun

EVM in consulting: Full EVM is typically used in large fixed-fee engagements or government contracts. For standard consulting, use a simplified version: track planned vs actual hours by work stream weekly; compute a burn rate vs percent complete.


Fee TypeDescriptionBudget RiskBest For
Fixed fee (lump sum)Agreed price regardless of hours; consultant bears overrun riskHigh for consultant if scope driftsWell-defined deliverables with clear scope
Time and Materials (T&M)Bill actual hours + expenses at agreed rates; client bears overrun riskHigh for clientExploratory work, dynamic scope
Not-to-Exceed (NTE)T&M with a cap; shares riskModerate for bothDefined outcomes but uncertain effort
RetainerMonthly fee for defined access/outputLow if scope is well-definedOngoing advisory relationships

Define escalation thresholds in the charter:

TriggerDefault ThresholdAction
Budget burn vs plan15% varianceInform engagement manager
Forecast overrun10% of total feeSteering committee discussion
Out-of-scope requestAnyFormal change order required
Schedule slip (critical path)1 weekCommunicate to client sponsor; agree recovery plan

Never let a budget variance accumulate in silence. Surface it early — at 10–15% overage — when there are still options. Surprises at 90% budget consumed with work incomplete are unrecoverable.

Standard content

Continue reading with Standard

This article is part of our Standard library — written from real projects, not generic explainers.

  • Full Standard tier vault — automation, intralogistics, supply chain, more
  • Practitioner-level guidance from real projects
  • Unlimited AI questions across the Standard corpus

$19/mo Standard · $25/mo Pro · cancel anytime