Fever Chart
Pattern: A named solution to a recurring problem.
The Critical Chain Project Management control chart that compares project-buffer consumption with critical-chain completion and ties each status zone to a management response.
The name is blunt because the reading is diagnostic. A fever chart does for a Critical Chain project what a temperature reading does for a patient. It doesn’t explain the whole condition, but it shows whether the system is within expected variation, needs closer watching, or needs action now. The chart replaces task-level percent-complete reporting with one system-level signal: project-buffer consumption relative to critical-chain completion.
Context
A critical-chain schedule has already compressed task estimates, resolved resource conflicts, placed a project buffer at the end of the chain, inserted feeding buffers at merge points, and added resource buffers as warning signals. The schedule is protected, but protection is not control. Once execution begins, the project manager has to know whether the protection is being consumed at an acceptable rate.
Critical Chain Project Management answers with buffer management for projects. At each reporting checkpoint, active task owners report remaining duration, not percent complete. Task overages debit the feeding buffer or project buffer according to where the task sits. The fever chart then plots the cumulative project-buffer consumption on the vertical axis and cumulative critical-chain completion on the horizontal axis. A single dot, updated each reporting period, gives the project’s status against the protected chain.
The TOCICO Dictionary defines the fever chart as a graph for the status of one project or multiple projects. Budd and Cerveny’s TOC Handbook primer gives the operational detail: green means expected variation, yellow means prepare recovery action, red means act. Newbold’s Project Management in the Fast Lane supplies the implementation-grade vocabulary for using the chart as a daily and weekly management control.
Problem
Traditional project control often asks the wrong question: “What percent complete is each task?” That question invites optimism, status bargaining, and reporting overhead. A task can be 90 percent complete for weeks. A team can report progress on many tasks while the project constraint sits starved. A project can look healthy on a Gantt chart until the moment the due date is already lost.
CCPM needs a different signal. The project manager needs to know whether the critical chain is advancing fast enough relative to the protection being consumed. If the chain is 40 percent complete and the project buffer is 20 percent consumed, the project is healthy. If the chain is 40 percent complete and the buffer is 80 percent consumed, the project is in trouble even if many task owners report local progress. The fever chart makes that comparison visible.
Forces
• Percent-complete reports are easy to game. Remaining-duration reports still require judgment, but they ask for the time needed from here rather than for a defensible story about work already done.
• Early intervention can damage the project. Acting in the green zone is tampering: it consumes management attention and can disrupt work that is still inside expected variation.
• Late intervention leaves few recovery options. Waiting for a formal task slip or missed milestone usually means the project buffer has already been consumed.
• The same chart must serve one project and a portfolio. A single-project manager needs a recovery signal; a program manager needs a way to compare projects competing for the same scarce resources.
• The zone boundaries are managerial choices. The Dictionary notes that the project manager determines the yellow-zone boundaries; the chart is an execution-control device, not a statistical proof.
Solution
Plot project-buffer consumption against critical-chain completion, then govern the response by zone. The fever chart’s x-axis is percent of critical chain completed. Its y-axis is percent of project buffer consumed. The project’s current status is the point where those two readings meet.
| Zone | Reading | Management response |
|---|---|---|
| Green | Buffer consumption is low relative to chain completion. | Leave the project alone; expected variation is being absorbed. |
| Yellow | Buffer consumption is near the project’s warning boundary. | Investigate causes and prepare a recovery plan, but hold the action. |
| Red | Buffer consumption has crossed the project’s action boundary. | Start the recovery plan; assign attention, resources, scope decisions, or escalation to the constraint. |
The fever chart’s zones slope across the graph. They are not the fixed thirds sometimes used to describe raw buffer penetration. The TOCICO Dictionary warns that the two color readings can differ and makes the project manager responsible for setting the yellow-zone boundaries.
The chart is cumulative. Each reporting period asks three questions. How much of the critical chain is complete? How much of the project buffer has been consumed? What has changed since the prior reading? The first two questions produce the chart point; the third points the project manager toward the task, resource, or dependency that moved the point.
The two calculations behind the chart are simple but easy to misuse. Buffer burn rate divides percent of project buffer consumed by percent of critical chain completed; a value near or below 1.0 usually means the project is consuming protection at an acceptable rate. Project buffer consumption rate (PBCR) divides the change in buffer consumption by the change in chain completion during the latest reporting period. PBCR catches a bad week that a cumulative burn-rate number would smooth away.
Task percent complete drops out of the control signal. A late task matters when it threatens the chain, and a red feeding buffer doesn’t carry the same response as a red project buffer. Every visible problem no longer competes for the project manager’s attention. One TOC question comes first: is the project constraint advancing fast enough for the protection that remains?
How It Plays Out
Budd and Cerveny’s worked project. Their TOC Handbook example begins with a 52-day critical chain and a 30-day project buffer. After 14 chain days are complete and 10 buffer days are consumed, chain completion is 27 percent, buffer consumption is 33 percent, and the burn rate is 1.22. The resized buffer still places the project in green, which shows why burn rate alone doesn’t determine the chart’s zone.
By the fourth reporting date, buffer consumption has jumped to about 80 percent while critical-chain completion has reached only 40 percent. The point is in red and requires immediate intervention. It recovers to yellow by the sixth period, where the project manager prepares further recovery plans rather than treating the improvement as proof that the risk has passed.
A multi-project engineering portfolio. A program office has 20 active projects competing for the same firmware specialists. Each project reports a fever-chart point weekly. Three projects are in yellow, one is in red, and the red project’s critical-chain task needs a specialist assigned to non-critical work elsewhere. The program manager doesn’t spread help evenly across all four projects. The red project gets the scarce resource first; the yellow projects get recovery plans and watch-list status.
This is where the chart becomes a portfolio tool rather than a project dashboard. It lets the program office subordinate local project preferences to the projects whose buffers are burning fastest against their chains. Without that common reading, every project manager argues from local urgency; with it, the portfolio has a shared priority signal.
Consequences
Benefits:
• Status becomes system-level. The chart reads the project constraint and the buffer protecting it, not a collection of local task reports.
• The project manager has a clear intervention rule. Green means leave it alone, yellow means prepare, red means act. The rule protects attention as well as schedule.
• The signal is harder to game than percent complete. A remaining-duration report can still be wrong, but it feeds a buffer calculation the whole system reads rather than a local claim about progress.
• Portfolio priority becomes visible. Multi-project fever charts show which projects most need scarce resources and which are merely loud.
• Improvement targets surface earlier. Repeated yellow and red movements trace to resources, dependencies, suppliers, or task definitions that need correction before the due date is lost.
Liabilities:
• The chart is only as good as the remaining-duration reports. If task owners protect themselves with padded remaining-time estimates, or understate trouble to avoid escalation, the chart inherits that distortion.
• Bad zone boundaries create bad behavior. A yellow zone set too tight produces constant intervention; one set too loose turns red into a late surprise.
• The chart can hide feeder-path detail. If feeding buffers are not tracked separately, the project buffer can become the first visible signal for a feeder-path problem that should have been caught earlier.
• Managers may treat the chart as an explanation. A red point says the project needs action; it doesn’t by itself say whether the cause is resource absence, unclear task definition, supplier delay, technical discovery, or bad multitasking.
• The chart requires subordination authority. A red signal has value only if someone can move resources, stop non-critical work, escalate dependencies, or change scope. If the surrounding organization refuses those moves, the chart becomes a warning with no control attached.
Related Articles
Complements: Resource Buffer — Resource buffers warn scarce resources before variation consumes time; the fever chart shows the buffer effect after variation has reached the project buffer.
Depends on: Critical Chain — The fever chart needs the critical chain as its progress axis; without an identified chain, the chart has no system-level completion measure to plot.
Detects: Bad Multitasking — A fever chart that keeps worsening while many tasks report partial progress often points to bad multitasking rather than to one isolated late task.
Detects: Multi-Tasking Cascade — In a multi-project environment, portfolio fever charts can expose cascading resource contention before every project reports a conventional schedule slip.
Detects: Student Syndrome — Repeated late starts and sudden buffer consumption near task due dates can reveal Student Syndrome consuming task-level safety before work begins.
Enforces: Subordination — A red fever-chart reading is a subordination signal: non-critical work, resource allocation, and escalation choices must yield to the critical chain's recovery need.
Informed by: Feeding Buffer — When a feeding buffer is fully consumed, remaining overage moves into the project buffer and therefore appears on the fever chart.
Measures: Project Buffer — The fever chart plots project-buffer consumption against critical-chain completion; the project buffer is the protection reserve the chart reads.
Specializes: Buffer Management — The fever chart is the CCPM specialization of Buffer Management's green-yellow-red reading.
Sources
• Cox, TOCICO Dictionary (2nd ed., 2012), entries “fever chart,” “buffer burn rate,” “critical chain completed (%),” “project buffer consumption rate (PBCR),” “buffer status,” and “project management measures.” The Dictionary supplies the certification-grade vocabulary and the single-project / multi-project distinction this entry cross-checks against. It is distributed through TOCICO membership and doesn’t carry an Open Library record.
• Goldratt, Critical Chain (1997), the originating treatment of CCPM. Introduces the project buffer, feeding buffers, resource buffers, remaining-duration reporting, and relay-runner execution behavior that the fever chart later turns into a visible management signal.
• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 3 (Budd and Cerveny, “A Critical Chain Project Management Primer”), the chapter-length operational specification. Gives the remaining-duration reporting rule, the green/yellow/red interpretation, buffer resizing, and the fever-chart reading across reporting periods.
• Newbold, Project Management in the Fast Lane (1998), the implementation-grade companion to Goldratt’s novel. Develops fever-chart use in single-project and multi-project settings, including the portfolio reading that lets a program office decide which project earns the scarce resource first.