The work S-curve in Microsoft Project: the three fields nobody points you to

Project planned value in currency next to baseline cumulative work in hours at the same status date

This article is part of the guide The plan that holds: Microsoft Project best practices, symptom by symptom, nineteen things you can see in a plan and the move that reveals each one in thirty seconds.

On 30 November 2023, on Microsoft’s own support site, somebody asked a perfectly ordinary question: I want one chart with % planned work progress and % actual work progress together. I can produce the actual one. I cannot find the option for planned anywhere.

Three people answered. The first told him to select every task and hit Mark on Track. The second pasted a link to a video. The third, a Microsoft community moderator, said he would look into it. He tried the first suggestion, reported that everything came out as zeros, and since then that thread has sat there, open, unanswered.

What he was looking for exists. The work S-curve in Microsoft Project is built from three fields that are already inside his own plan — they are just not called what he expected.

Planned, in Project, means money

Anyone asking for «planned work» in Microsoft Project ends up in the same dead end, because the phrase everyone hands back is Earned Value. And Project’s earned value, the real one, is denominated in currency.

BCWS — planned value — has data type Currency, and Microsoft defines it like this: it «adds the timephased baseline costs of the task up to the status date». Costs. Not hours. Ask how much work should have been done by now, get an answer in euros, and you have been answered a different question.

The same project delay read as 5,400 in currency with BCWS and BCWP and as 116 hours with the cumulative work fields

It is the same delay, measured twice. But the number in currency depends on the rates: change them and the delay in money changes, without the real delay moving by one hour. For the steering committee, money is exactly right. For working out how much work is left, it is not.

There is a second reason he could not find the option: a «planned percent complete» field does not exist in Project. There is % Complete, % Work Complete and Physical % Complete, and all three describe what has already been done. The planned percentage is a ratio you work out, not a column you switch on.

The three fields that actually do it

They are already in the plan, Project calculates them, and you do not have to build anything with a formula.

The three timephased fields in Microsoft Project: Baseline Cumulative Work, Cumulative Work and Cumulative Actual Work

The first one, Baseline Cumulative Work, is the definition of the planned curve: «the amount of time scheduled for all resources assigned to tasks, accumulated over time, when the baseline was set». It also exists in the numbered flavours, Baseline1 through Baseline10, so you can draw the curve of the signed-off plan next to the curve of the latest replan.

The third, Cumulative Actual Work, is the actuals accumulated. Between the two sits Cumulative Work, which is today’s plan: work already performed plus remaining scheduled work. I come back to it in two sections, because that is the one that fools people.

They are not columns. They are rows

This is why people who go looking never find them. They do not show up in the list of columns, because they are not task data: they are timephased, one value per period. They live in the grid at the bottom of the Task Usage view, the one hardly anybody opens.

The timephased grid of the Task Usage view with three detail rows of cumulative work switched on

Four steps and they are in front of you. The third is the one that matters: in the Detail Styles dialog, Usage Details tab, you move fields from Available fields to Show these fields with the Show button. From then on they behave like the Work and Actual Work rows, and you can select them and paste them straight into Excel.

What comes out

I built a real plan to see it: ten weeks, seven tasks, five resources at €50 an hour, 680 hours in total, with the load concentrated in the middle weeks — the shape that gives the cumulative curve its S. Baseline saved on day one, status date at the end of week eight, and a realistic picture of progress: two tasks finished, three running late, one barely started.

Work S-curve in Microsoft Project: 600 hours planned against 484 actual at the status date

At the status date the plan called for 600 hours; 484 had been done. A hundred and sixteen hours of gap, which against the whole project is 88.2% planned versus 71.2% actual: seventeen points. That is exactly the chart the person on that thread was asking for, and it came out without writing a single formula.

One detail, for when the numbers have to reconcile: in the same plan BCWS reads €29,600, which is 592 hours rather than 600. A status date set at midnight leaves that day’s work outside the count. If you compare the curve in hours with the curve in money and a day seems to have gone missing, that is where it went.

The trap: two of the three curves match

In my plan Baseline Cumulative Work and Cumulative Work return identical numbers, week after week, all the way to the last one. That is not a bug: it is the normal case, and that is exactly what makes it dangerous.

Cumulative Work follows the plan as it stands right now. If tasks are running late but nobody has moved any dates, the plan still says the remaining work sits where it always sat, and its curve still finishes on time. Anyone comparing those two curves sees zero and relaxes, while the actuals are a hundred and sixteen hours short.

The two only separate once you have rescheduled the uncompleted work past the status date. That command is what makes the «how it will end» curve honest. And if you have also genuinely replanned in the meantime, the baseline you are comparing against is no longer the signed-off one: that is a different question, and it wants the numbered baselines.

What about the advice he was given?

It was: select every task and press Mark on Track. The command sits on the Task tab, Schedule group, and it updates tasks to «the scheduled percent complete for the current date or a status date». Microsoft presents it for tasks that genuinely are on schedule: it saves you typing progress by hand into twenty tasks that are all going to plan.

Running it across the whole plan to manufacture the planned curve means writing fictional progress over real progress. You destroy the actuals in order to draw a chart, and actuals do not come back. Which is why, if you want to try anything of the sort, you try it on a copy of the file.

Why everything came out as zeros

Two causes, and they are the same two that catch everybody the first time they touch these fields.

No baseline saved. Every baseline field is born empty and stays empty until you set a baseline. There is no warning: there is a column of zeros.

No resources assigned. Work is calculated from the assignments. If you schedule in durations and assign nobody, the project’s work is zero, and so are all three cumulative rows. In that case the work curve simply cannot be drawn, and the only thing you have left to accumulate is cost — or you assign the resources, which is the right answer.

In short

  • Project’s planned value (BCWS) is Currency: it adds up baseline costs to the status date. It is not work.
  • A «planned percent complete» field does not exist: the planned percentage is a ratio you compute.
  • The work curve is made of three timephased fields that are already there: Baseline Cumulative Work, Cumulative Work, Cumulative Actual Work.
  • They are not columns: they are rows in the grid of the Task Usage view, switched on from Format → Add Details.
  • Baseline and scheduled match until you reschedule uncompleted work: comparing those two shows zero even when you are badly behind.
  • Mark on Track is not a way to fake the planned curve: it writes fictional progress over real progress.

If something does not add up

  • The baseline rows are all zero. There is no baseline. Set one, and from that moment the values exist — but they exist from the date you saved, not retroactively.
  • All three rows are zero. No resources are assigned, so there is no work. No cumulative field can invent it.
  • Actuals continue past the status date. Somebody entered progress with later dates. The status date does not prevent that: it only makes it visible to whoever is looking.
  • The actual curve is above the planned one. Not always good news: it can mean more work is being burned for the same result. Read it together with progress, never on its own.
  • The chart in hours and the chart in money disagree. They are not measuring the same quantity. Check which unit you are reading before you try to reconcile them.

Frequently asked questions

Does Microsoft Project have a planned percent complete field?

No. There is % Complete, % Work Complete and Physical % Complete, and all three describe what has been done. The planned percentage comes from dividing baseline cumulative work at the status date by total baseline work.

What is the difference between Cumulative Work and Baseline Cumulative Work?

The first is today’s plan, and it moves every time a date changes. The second is the snapshot taken when you saved the baseline, and it never moves again. Until you reschedule or replan, the two return the same numbers.

Can I compare more than one baseline on the same chart?

Yes: the cumulative fields also exist for the numbered baselines, Baseline1 through Baseline10. If you archived the signed-off plan in one of them, you can draw three curves together: the signed-off plan, the latest replan and the actuals.

Do I need Earned Value to draw the work S-curve?

No, and it gets in the way. Project’s earned value is denominated in currency and needs sensible rates on the resources. The work curve only needs a saved baseline, assigned resources and progress recorded.

Do these fields exist in every version of Project?

They are long-standing desktop fields; everything here was verified on Microsoft Project in Microsoft 365 by building the plan and reading the values out of it. Project for the Web is a different product and does not expose them the same way.

How do I get the curve out of Project?

Select the rows in the timephased grid and paste them into Excel: that is the most direct route, and the chart takes a minute from there. If it becomes a monthly job, automate it.


Disclosure: this is the blog of a company that makes project-control software, so take the paragraph below for what it is. Nothing above needs our tool: the three fields belong to Microsoft Project, and you have already paid for them.

If that curve has to be rebuilt at every status meeting, though, and every time it means reopening the plan and retyping a grid of weeks, MPP To Excel reads the .mpp file and lays its contents out in Excel, where the chart refreshes itself.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top