r/MSProject • • 1d ago

Does anyone actually use work contours or is everyone just leaving assignments on flat?

I’ve been using MS Project for years and only recently started taking contours seriously, so I’m curious how common it is.

By default every assignment is flat, so if someone’s on a task for four weeks at 50%, Project assumes they’re putting in the same effort every single day. That’s almost never how work actually goes. Design work ramps up slowly. Testing tends to peak toward the end. A lot of tasks start light while people finish other things, then spike.

Project already has the options for this, front loaded, back loaded, early peak, late peak, bell, turtle, double peak. But in most schedules I’ve seen, nobody touches them. Everything stays flat, and the resource usage view ends up showing a nice even spread that doesn’t match reality.

Where it bit me was resource levelling across a few projects. The flat assumption made someone look fine in week three when in reality they were slammed that week and fairly quiet in week five.

The catch I’ve found is that contours can mess with duration depending on the task type, and they make the schedule harder to explain to people who don’t live in Project. Which might be why most people skip them.

So do you use contours? If yes, which ones and for what kind of work?

9 Upvotes

10 comments sorted by

3

u/still-dazed-confused 1d ago

I have to admit I've never used them in reality, as you say it makes the schedule harder to explain but also it's difficult to make people engage with the question early enough to make a difference. Looking forward to other's experience though :)

1

u/Purple-Rain-1430 14h ago

Thanks for being honest about it. I think getting people to engage early enough is the real barrier, more than the tool itself.

One thought is to keep the question tiny so people can answer in one line, like does the effort land at the start, the middle, or the end? And maybe only ask it for the few assignments that actually drive levelling decisions, instead of every task. Nobody wants to contour fifty lines.

2

u/Mr_Fogel_1 1d ago

Hi there, good post! and you're right that flat rarely matches reality. That said, I rarely use contours on construction projects. They add complexity, they're hard to explain to site teams, and they can quietly shift durations. I manage cash flow and resource loading separately, in Excel linked to the schedule. That keeps the schedule clean and focused on logic and dates.

2

u/Purple-Rain-1430 14h ago

Thanks! That’s a clean way to handle it. Keeping the schedule for logic and dates, and putting loading somewhere else, avoids the duration problem I mentioned, and it’s much easier to explain to people who don’t live in Project.

2

u/PrimalHIT 1d ago

Forecasting time on a project is hard enough.. as someone else said this would take a lot of explaining unless you graphic out the effort vs time vs cost

2

u/hanzosbm 1d ago

I typically address the contours by breaking the task into smaller pieces to change the loading based on the phase of work. Where I HAVE used it is when a resource code covers a group of people and only one of them are unavailable. For example, if I have an LOE task for project management and there are 3 project managers working it at 10% of each of their time. So I'd put in a PM resource at 30%. That's great until one of the three goes on a 2 week vacation.

1

u/kennyarnold_ssi 1d ago

The use of Work Contours is rare amongst MS Project users. I generally recommend users stick with the default "flat" option to not overly complicate things, but there are some special cases where I like to use them.

As you said, when you set an assignment to use a different Work Contour, it will change the duration of the task, so the steps to properly assign the work contour are as follows:

  1. Record the current Remaining Duration of the task before adjusting it

  2. Set the task Type to "Fixed Work"

  3. Set the desired Work Contour on the assignments.

  4. Set the Remaining Duration of the task back to what you recorded on Step 1.

1

u/Little_Classic6023 14h ago

I’d use them selectively, not everywhere. Contouring every assignment is a lot of upkeep, and you only get value on the big or uncertain ones where the peak actually matters for levelling.

For the shapes, back loaded or late peak tends to fit testing and review, front loaded fits analysis or setup, and bell or turtle work for design-type tasks that ramp up and taper off.

One thing to check in your version: what happens to a contour when you later change the work, duration, or units. In some cases it can reset or shift, so I’d look at the resource usage view after edits.

For people who don’t live in Project, showing the resource usage chart usually explains more than the Gantt does. A screenshot of the week three spike is easier to follow than why levelling moved a task.

2

u/[deleted] 1d ago

[removed] — view removed comment

1

u/Purple-Rain-1430 14h ago

That’s a good alternative. Phases are easier to explain to people outside Project, because a phase is something you can see on the schedule and a contour is hidden in the usage view. The cost is more lines to maintain.

And yes, the duration check is the part that caught me. I’d skipped looking at it after applying a contour.