Doitify
Pricing Enterprise Download Contact Us
Doitify › Project Management Questions

“What Is An S Curve In Project Management?”

Updated on November 12, 2026 https://doitify.com/project-management-questions/what-is-an-s-curve-in-project-management/
Share
Summary

What an S curve shows, why it bends, how to read the gaps between planned, earned and actual value, and how to build one with S curve project management.

An S curve plots cumulative value against time. The vertical axis is cost, hours, quantity or percent complete; the horizontal axis is calendar time. It looks like an S because projects start slowly, accelerate, then taper. Mobilisation, peak delivery and closeout are three different rates of production.

What is an S curve, exactly?

S curve project management is a key topic in modern project management and teamwork. An S curve is a line chart of cumulative progress against time. Because the values accumulate rather than reset each period, the line only rises, and it rises slowly at first, steeply in the middle, then flattens as the remaining work shrinks.

The formal definition in project controls literature is a graphical display of cumulative costs, labour hours, progress or other quantities plotted against time. The American Association of Cost Engineering treats S curve analysis as a recommended practice, which tells you how embedded it is in serious project controls.

The distinction that matters operationally: an S curve is not earned value management. EVM is a management method with formulas, baselines and variance rules. The S curve is the standard way to display EVM’s three core metrics. You can draw an S curve without doing EVM at all, using man-hours or installed quantities instead of money.

Why does the curve have an S shape?

The shape is not stylistic. It reflects how production actually behaves on almost any project.

At the start, the team is mobilising. Permits, procurement, design, onboarding and site setup consume time without producing much measurable output. Cumulative progress crawls.

In the middle, work fronts open in parallel. Crews, developers and suppliers all produce simultaneously, and cumulative progress climbs steeply.

At the end, the remaining work is the awkward remainder: snagging, testing, documentation, commissioning, acceptance. Each item takes longer per unit of value than the peak-phase work did.

The practical consequence is a rule worth memorising. Neal Whitten’s widely cited 50/70 rule, published through PMI, states that when 50 percent of an activity’s time has elapsed, roughly 70 percent of the work should be complete. Linear 50/50 reporting systematically overstates progress, because the tail is where plans die.

> Practical tip: If a team reports 50 percent complete at the halfway point of a task, assume the task is late. The curve predicts it, and the curve is usually right.

Join Doitify Today

Move projects forward without the chaos: all your tasks, progress, and team reports in one unified workspace. Built for companies, startups, and remote teams — with a quick setup and a free trial.

What are the three S curves you actually plot?

Three curves, drawn from the same baseline, tell the whole story. Each answers a different question.

Curve What it measures How it is calculated Typical distortion
Planned Value (PV) Budgeted value of work scheduled by the data date Time-phased baseline budget Baseline never updated after approved scope change
Earned Value (EV) Budgeted value of work actually completed Sum of percent complete × budget by work package Optimistic percent-complete judgments
Actual Cost (AC) Money actually spent for the work performed Invoices, timesheets, purchase orders Costs recorded late or gross of accruals

The data date is the single most important label on the chart. A curve without a data date is a decoration. All three lines must be cut at the same moment, using the same scope, or the comparison is meaningless.

How do you read the gaps between the curves?

Read the vertical distance between lines at the data date, then convert it into a variance and an index. Direction tells you the problem; magnitude tells you whether to act.

What you see Plain meaning First thing to check
EV below PV Behind schedule Critical path, not the total float
EV above PV Ahead of schedule Whether EV rules are inflating progress
AC above EV Over budget for value earned Labour rates, rework, unapproved scope
AC above PV but EV tracking AC Spending fast because work is fast Genuinely ahead, not necessarily a problem
EV flat while AC climbs Paying for work that is not progressing Blocked work fronts, waiting on approvals
All three flat late in the project Stalled closeout Snagging lists, acceptance sign-offs

Three formulas turn the visual into a number you can trend:

  • Schedule variance: SV = EV − PV. Negative means behind.
  • Cost variance: CV = EV − AC. Negative means over budget.
  • Indices: SPI = EV ÷ PV and CPI = EV ÷ AC. Below 1.00 is adverse.

What does an S curve look like with real numbers?

Here is a twelve-month, £1,200,000 programme at the end of month six. Because of a slow mobilisation, the baseline expects only 35 percent of the budget to be earned by the halfway mark.

Metric Value Calculation
Budget at completion (BAC) £1,200,000 Approved baseline
Planned value (PV) at month 6 £420,000 35% of BAC
Earned value (EV) at month 6 £360,000 30% of BAC
Actual cost (AC) at month 6 £405,000 Ledger to data date
Schedule variance −£60,000 360,000 − 420,000
Cost variance −£45,000 360,000 − 405,000
SPI 0.86 360,000 ÷ 420,000
CPI 0.89 360,000 ÷ 405,000

Two conclusions follow immediately. First, at 50 percent of the schedule the programme has earned 30 percent of its budget, which is well below the 50/70 benchmark and consistent with the early warning the S curve was designed to give. Second, every pound spent has bought 89 pence of planned value.

Forecast the finish: EAC = BAC ÷ CPI = 1,200,000 ÷ 0.89 = £1,350,000, a £150,000 overrun. Forecast the date: 12 months ÷ 0.86 = roughly 14 months. The S curve has produced a cost and a date from two divisions.

How do you use the curve to spot a late finish early?

The most useful application is not the snapshot but the projection. Scheduling tools can generate two baselines — one using early start dates, one using late start dates — and the envelope between them is the banana curve.

Take a project with an early-date finish in week 40 and a late-date finish in week 48. At week 32, actual completion is 62 percent, against 68 percent on the early curve and 60 percent on the late curve. The project is technically inside the banana, which means it can still finish on time. But its trajectory is tracking the late-date curve, and extrapolating the last four weeks puts the finish at week 46.

Six weeks of slip on a site with £18,000 per week of standing overhead costs £108,000. That number, produced eighteen weeks before the deadline, is the difference between a recoverable problem and a post-mortem.

What does it mean when the curve is not an S?

A curve that deviates from the classic shape is telling you something about the plan itself, before any work has gone wrong.

A front-loaded curve climbs steeply from week one and flattens early. That is normal for procurement-heavy or licence-heavy work, where most of the money leaves before delivery starts. It is also what an over-mobilised project looks like: too many people on site before there is work for them.

A back-loaded curve stays flat for months and then turns almost vertical. This is common when design or discovery dominates the first half. The risk is a cliff: 68 percent of the budget landing in the final 30 percent of the schedule means the organisation must absorb a spending and staffing spike it has never tested.

A stepped or terraced curve shows distinct plateaus followed by jumps. That usually signals stage-gated delivery with formal acceptance between phases, which is legitimate but makes month-to-month comparisons misleading.

A plateau in the middle is the one to worry about. Cumulative progress that stops rising while costs keep climbing is the clearest visual signal of a stalled work front, and it is the pattern most often missed in a status report built from percentages.

A double-S curve — two separate rises — is what a programme with two delivery waves against one baseline looks like. If the baseline was never re-drawn to reflect the waves, every variance calculation will be wrong in the gap between them.

Which other S curve types are worth knowing?

Different questions need different vertical axes. The shape is the same; the unit changes.

Type Vertical axis Best used for
Baseline cost Cumulative budget Cash flow and funding requests
Actual cost Cumulative spend Comparing burn rate to plan
Earned value Budgeted value of completed work Performance measurement
Labour hours Cumulative man-hours Resource and productivity control
Progress percentage Cumulative percent complete Stakeholder communication
Quantity installed Units placed, e.g. cubic metres of concrete Physical progress verification

Percentage curves are the easiest to communicate and the easiest to fake. Quantity curves are the hardest to fake, which is why construction and manufacturing rely on them. If you can measure something physical — metres installed, modules tested, tickets resolved — plot that instead of a subjective percentage.

Why is an S curve sometimes misleading?

It is a good chart with sharp edges. Four of them matter most.

Progress measurement can be optimistic. If the same person reports percent complete and signs off the invoice, the incentive points one way. Curve accuracy is a governance question, not a charting question.

The curve inherits the schedule’s flaws. The S curve takes its dates from the underlying programme. A badly sequenced plan produces a curve that looks orderly and is wrong. A smooth line is not evidence of a sound plan.

Front-loaded costs distort early reading. Mobilisation, licences, deposits and equipment purchases often land before any earned value appears. A project can show a healthy gap in month one that has nothing to do with performance.

Roll-ups hide the distribution. A programme-level curve can look acceptable while one work package is in serious trouble. Always check the top three variance contributors, not just the aggregate.

> Common mistake: Presenting the curve without the data date, the baseline version and a one-line explanation of what changed this period. The chart then becomes a Rorschach test in which each stakeholder sees what they expected to see.

How do you build one without a scheduling team?

Five steps, and the first four are data work rather than charting.

  1. Fix the baseline. Approved scope, approved budget, approved dates. Note the version.
  2. Time-phase the budget. Spread cost, hours or quantity across the periods when the work is scheduled. This produces PV.
  3. Set a progress rule. Use 0/100 for short tasks, 50/50 for tasks under two weeks, and physical measurement where it exists. Write the rule down; changing it mid-project invalidates the trend.
  4. Collect actuals against the same work packages. Costs must cover the same period and scope as the earned value.
  5. Plot and annotate. Three lines, one data date, one sentence explaining the gap.

The arithmetic is trivial. The failure mode is organisational: when the budget lives in finance, the schedule lives in a Gantt tool and time is tracked in a third system, producing the monthly curve becomes a reconciliation project nobody trusts.

That is the problem Doitify addresses — tasks, owners, dependencies, budgets and progress reporting in one workspace, so planned and actual draw from the same data instead of three exports. Doitify is our product, so read that as a statement of fit; a team of twenty tracking a single programme will benefit more than an enterprise that already runs a dedicated project controls function.

For the cost side of the same picture, the guide to the cost performance index explains how to turn these curves into a forecast you can defend.

S curve vs Gantt chart vs burndown: which do you need?

They answer different questions, and mature teams use more than one.

Tool Shows Best for Weakness
S curve Cumulative value against time Cost and schedule performance against baseline Hides task-level detail
Gantt chart Tasks, durations and dependencies Sequencing and critical path Hard to read at portfolio level
Burndown Work remaining per iteration Sprint-level flow Resets each sprint; no cumulative view
Burn-up Work completed against scope Scope creep visibility Needs disciplined scope baseline

A practical split: the Gantt chart runs the work, the S curve reports it, and the burndown manages the next two weeks. Asking one chart to do all three jobs is how reporting becomes a second full-time role.

Where does the S curve help, and where does it not?

It helps when you need a defensible answer to “how are we doing” that a non-specialist can read in ten seconds. It also helps in cash flow planning, because the PV curve is effectively a funding requirement schedule.

It struggles when the baseline is unstable. If scope changes weekly and the baseline is never re-approved, the curve compares new work to an old plan. The output is arithmetically correct and operationally useless.

It cannot prove causation. A curve can show that cumulative output fell behind. It cannot tell you whether that was a supplier failure, a design change, weather, or a resourcing decision — and it cannot support a delay claim on its own.

It rewards honesty less than it should. Teams learn quickly that a flat EV curve invites questions. The countermeasure is not a better chart; it is an independent check on progress, such as physical inspection or milestone verification.

FAQ

An S curve is a cumulative graph of a project variable — usually cost, labour hours or percent complete — plotted against time. It starts slowly, rises steeply during peak delivery, and flattens near completion.

Because the plotted line resembles the letter S. The shape comes from three distinct rates of production: slow mobilisation, fast execution, and a slow, awkward closeout.

No. Earned value management is a method with formulas and baselines. The S curve is the standard chart used to display EVM's three metrics: Planned Value, Earned Value and Actual Cost.

PV is the budgeted value of work scheduled by a date. EV is the budgeted value of work actually completed. AC is the money actually spent. Comparing them produces schedule and cost variance.

A banana curve is the envelope formed by two S curves built from early start dates and late start dates. If actual progress stays inside the envelope, the project can still finish on time; if it drifts outside, the finish date is at risk.

Match the reporting cadence: weekly for fast-moving delivery, monthly for construction and enterprise programmes. Consistency matters more than frequency, because an irregular cadence distorts the trend line.

Yes. Enter periods in one column and cumulative PV, EV and AC in the next three, then insert a line chart. The difficulty is not the chart, it is keeping the three inputs aligned to the same scope and data date.

Conclusion

An S curve is the cheapest honest answer to the question every sponsor asks. Three cumulative lines, one data date, and two divisions give you a cost forecast, a schedule forecast and an early warning that is hard to fake for long.

Use it with discipline: fix the baseline, apply one progress rule consistently, annotate every movement, and look at the trend rather than the snapshot. Then keep the underlying detail in a place where the people doing the work can update it, because a curve is only ever as current as the data behind it.

If this post on S curve project management was helpful, you might also enjoy How Project Management Relates To Other Discipline? and Does Project Management Certification Expire?.

Join Doitify Today

Move projects forward without the chaos: all your tasks, progress, and team reports in one unified workspace. Built for companies, startups, and remote teams — with a quick setup and a free trial.

0 0 votes
Article Rating
Share
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Table of Contents

Ready to do more with Doitify?

Bring your projects, team, and goals together in one AI-powered workspace.

Get Started
Table of Contents