Controlling the Schedule and Cost

Two Numbers That Don't Tell You Enough

At some point in almost every project, someone looks at the schedule, sees that most tasks are green, and looks at the budget report, sees that spending is roughly where expected, and concludes the project is on track. That conclusion may be correct. It also may be completely wrong. A schedule that shows tasks as "in progress" without measuring actual completion against planned completion tells you what people are working on, not how far through the work they actually are. A budget that shows spending within forecast tells you how much money has gone out the door, not how much work that money produced. Controlling the schedule and cost means asking harder questions than whether the numbers look acceptable. It means measuring performance against the baselines that were built during planning and understanding what the gap between planned and actual actually signals.

The Schedule Baseline Is the Reference

The schedule baseline, the approved, time-phased version of the schedule that was formally agreed during planning, is the reference point against which all actual progress gets measured. In monitoring and controlling, you compare what is actually happening against that baseline to calculate schedule variance: the difference between where you planned to be and where you actually are. Ahead of baseline is positive. Behind is negative. The baseline is what makes "behind" meaningful, because without it you have nothing to compare against. A task that was planned to finish on Friday and finishes the following Wednesday is two working days late, and that is a meaningful number only because the baseline said Friday.

One of the practical complications in schedule control is the difference between a task being in progress and a task being on track. A task that is listed as in progress but has consumed 80 percent of its estimated effort with only 40 percent of the work complete is not on track. The task status says "in progress." The actual performance says "behind and getting worse." Schedule control means looking at both dimensions, completion status and effort consumption, rather than treating any active task as a green indicator.

Float as a Diagnostic

Float, the amount of time an activity can slip before it affects the project end date, looks like breathing room during planning. During monitoring and controlling, it serves a different function: it is a diagnostic tool that tells you where problems are developing before they reach the critical path. A task that slips but still has three weeks of float remaining is concerning but not yet critical. The slip is absorbing float, not threatening the end date. But if float is shrinking toward zero on a task that was not originally on the critical path, that task is becoming critical. Watching float burn down across the schedule tells you where the next pressure point will be, before it arrives, while there is still time to take preventive action.

This is why float should appear on the project status review, not just the critical path. A PM who only watches the critical path sees problems when they arrive at the end date. A PM who also monitors float consumption sees them approaching, which is an entirely different position to be in when deciding what to do about them.

Trend Analysis: One Delay or a Pattern

A single delay is a data point. Three delays in the same area of the project are a trend. Schedule control requires looking beyond individual variances and asking whether a pattern is emerging. Is the same team consistently running late? Are all tasks in a particular phase taking longer than estimated? Does the critical path slip by roughly the same amount each reporting period regardless of what actions are taken? Trend analysis is reading the direction of travel rather than just the current position. A project that is two weeks behind with no trend in any direction is a very different situation from one that is two weeks behind and falling further behind by roughly three days with each weekly review. Both have variance. Only the second one has a problem that will compound without a structural response.

Recovery Tools: Crashing and Fast-Tracking

When schedule variance is large enough to require correction, two techniques from planning come back into play. Crashing means adding resources to critical path activities to reduce their duration. More people, additional shifts, accelerated procurement for materials, whatever reduces elapsed time on the activities that determine the end date. Crashing can buy back schedule, but it costs money. There is no such thing as free crashing. The PM needs to know what the crashed schedule costs before presenting it as an option, because the sponsor's decision about whether to crash depends on whether the additional cost is preferable to the schedule slip.

Fast-tracking means starting activities in parallel that were planned in sequence, overlapping phases that were originally set up with a finish-to-start dependency. Fast-tracking can compress the schedule without adding cost, but it increases risk. Phases that were sequenced deliberately often had a reason for the sequence: a dependency, a review gate, a constraint that was assumed to be fixed. Overlapping them introduces the possibility that early-phase work will need to be redone when late-phase requirements are discovered. The PM's job is to analyze whether the dependency is truly fixed or could be managed under a parallel approach, and what risks that parallel approach introduces. Crashing increases cost. Fast-tracking increases risk. Both are real tradeoffs, not free schedule recovery options.

Resource Pooling: Where Crash Resources Come From

Crashing requires additional resources, and those resources have to come from somewhere. In many organizations, that somewhere is a shared resource pool: a centralized capability where specialists, technical leads, or functional experts are allocated across multiple active projects rather than dedicated to one. Understanding how your organization's resource pool works, who manages it, how requests are prioritized, and how availability is tracked, is practical knowledge that directly affects which schedule recovery options are actually available when you need them.

The appeal of resource pooling is efficiency: specialized skills are shared across projects without each project budgeting for dedicated headcount it only uses part-time. The risk is contention. When two projects need the same database architect or the same testing lead at the same time, the pool manager makes a prioritization call. One project gets the resource and its recovery plan works. The other doesn't and it doesn't. A PM who treats pool resources as reliably available without checking current utilization against the pool's other commitments is building a recovery plan against a baseline that may not exist. Confirm actual availability before presenting a crashing option to the sponsor as viable. A plan that depends on a resource who turns out to be unavailable is not a plan. The schedule will absorb the gap.

When to Update the Baseline

A recurring question in schedule control is when to update the baseline versus when to keep the original and show the variance. The answer matters for the integrity of the monitoring process. The schedule baseline should only be changed through formal change control, not to correct for delay or make the schedule look better than it is. If the project absorbs a two-week slip and the baseline is updated to reflect the new dates, the variance disappears. The project now shows zero schedule variance against a baseline that has already captured the overrun. That is not a project in control. That is a project where the measurement system has been adjusted to confirm the desired outcome.

Keep the original baseline. Show the variance. Update the baseline only when a formally approved scope change justifies a new baseline, or when the organization has made a deliberate replanning decision with sponsor authorization. A project that always shows zero variance isn't being controlled. It is being managed to look controlled. The honest picture of where performance diverged from the plan is exactly what the sponsor and steering committee need to make informed decisions about recovery options and expectations.

• Do not rebaseline to correct for ordinary delay or cost overrun.
• Do rebaseline after a formally approved scope change that alters schedule or budget.
• Do rebaseline after sponsor-authorized replanning — document the decision and the date.
• Preserve the original baseline in the project record regardless of what the new baseline shows.

Cost Control: The Baseline and What It Measures

Controlling cost begins with the cost baseline, the approved, time-phased budget that specifies not just how much money the project has in total, but how much should be spent at each point in time. This time-phased structure is what separates a meaningful cost comparison from a misleading one. A project at the halfway point of its timeline with half the budget spent might be perfectly on track, or significantly off track, depending on whether the work completed at this point is worth half the budget. The cost baseline tells you what the planned expenditure should be at this moment in the project. The comparison of actual spending to that planned figure produces cost variance: positive when you've spent less than planned, negative when you've spent more.

Three Layers of Cost

One thing that confuses people new to cost control is that actual costs on a project don't always equal what has been invoiced or paid. Three layers of cost are relevant to the full picture. Actual costs are what has been paid, the money that has left the project budget. Committed costs are what has been approved and incurred but not yet invoiced, a vendor who has done the work, an invoice that was signed off but hasn't cleared. Accrued costs are what has been incurred but not yet formally approved, a contractor who has been working for three weeks but bills monthly. The budget report that shows only actual payments captures only one of the three. Cost control requires tracking all three, because the real cost picture at any moment in the project is the combination of what has been paid, what is owed, and what is being earned by contractors currently working.

Direct and Indirect Costs

Project costs fall into two categories, and understanding which category a variance is coming from changes what you do about it. Direct costs are traceable to the project: materials purchased specifically for the work, contractor fees, travel expenses, equipment the project is renting or buying. Indirect costs are overhead allocated to the project as part of doing business: shared office space, IT infrastructure, administrative support charged at a rate against the project. Both count against the budget. The split matters for analysis and for response. If direct costs are within baseline but indirect cost allocations have increased unexpectedly, the cause and the corrective response are different from a situation where direct labor is running over. Know which category the variance is coming from before deciding what to do about it.

Corrective Action and Forecasting: Two Different Jobs

When cost variance appears, the PM has two distinct jobs that should not be confused. Corrective action addresses the current problem: understanding why costs are running over in a specific area and deciding whether to reduce scope, find efficiencies, or raise a change request for additional budget. Forecasting looks forward: based on current spending performance and the work remaining, where will this project finish? A cost forecast answers that question by projecting current trends to estimate the total cost at completion. It does not assume that variance will self-correct. It models where the project is heading if current performance continues.

The sponsor always wants the forecast, not because they enjoy bad news, but because a problem flagged in week eight is still manageable. A problem revealed at the final invoice is not. Presenting a forecast when the variance is still small gives the sponsor time to make decisions: tighten scope, release contingency, have a conversation with the client about expectations. Waiting for the variance to become undeniable before raising it removes all of those options. The PM who provides an honest forecast early is protecting the sponsor's ability to respond. The PM who softens or delays it is taking that ability away.

Cost Control Is a Discipline, Not a Report

The most common failure mode in cost control is treating it as a monthly reporting exercise rather than an ongoing discipline. By the time a monthly budget report shows a significant overrun, the decisions that caused it were made weeks earlier. Cost control works when it is continuous: tracking actuals weekly, watching for trends before they become large variances, and talking to team members and vendors about anything that is running differently from the plan. The PM who waits for the budget report to learn the project is overspending is always behind the problem. The PM who monitors costs as part of the regular project rhythm is almost always ahead of it and still has options when variance appears.

What's Next

The next chapter, Earned Value Management, goes deeper into the cost and schedule measurement framework that connects spending to accomplishment rather than treating them as separate measures. EVM is the methodology that answers the question that standard budget reports cannot: given what we've spent, are we actually on track?

Reflect

• On a recent project, did the schedule status tracking distinguish between "task in progress" and "task on track"? What would you need to see in the tracking tool to catch a task that is consuming effort without completing at the expected rate?
• Have you seen float used as a diagnostic tool, watching it burn toward zero to identify emerging critical path candidates before they arrive? What changed in your monitoring approach when you started watching it that way?
• Think about a cost variance you encountered on a recent project. Was it in direct costs, indirect allocations, or accrued but not yet invoiced? Did identifying the category change what you did about it?
• How far in advance did you raise cost variance with your sponsor on your most recent project? What options were available at that point that would not have been available if you had waited another four weeks?