Contractors: How to Make Your Microsoft Project Schedules Bulletproof

Microsoft Project (MSP) schedules are being used more and more on construction projects. However, commonly used settings, defaults and practices make MSP schedules far less bulletproof from a CPM perspective than Primavera P6.
The uncomfortable truth is that many Microsoft Project schedules only look like CPM schedules. The bars, links and dates are all there, but a quick review turns up problems that corrupt the underlying calculations. That matters well beyond project controls. When a job ends in a claim, the schedule becomes evidence, and disputes often turn on how well the schedules were maintained. A Microsoft Project schedule that does not calculate as a true CPM schedule loses its value as evidence and could cost a contractor millions of dollars in a claim.
The software is not the problem. Microsoft Project can produce a defensible schedule. The difference is that P6 enforces certain CPM disciplines by design, while Microsoft Project leaves them to the scheduler (often under advanced settings that most users are unaware of). Here are the five areas where I see Microsoft Project schedules go wrong most often, and my suggestions for what to do about each.
1. The status date is not a data date
In P6, the data date is the key date that drives the entire schedule calculation. When the schedule is calculated, everything to its left is actual progress and everything to its right is remaining work. The remaining duration of an in-progress activity starts at the data date, and an unstarted activity cannot be scheduled any earlier. Nothing incomplete can sit in the past.
Microsoft Project’s status date does not work that way. An activity that should have started last month can stay scheduled for last month, and the update will still report a finish date as if nothing were wrong. The forecast then shows uncompleted work being done in a past that no longer exists. Any later forensic analysis that relies on that update, such as a windows or half-step analysis, starts from planned dates that were already invalid on the day the schedule was published.
The fix takes two steps on every update:
1. Set the status date. Project > Project Information > Status Date. Left blank, Microsoft Project uses today’s date, which is not necessarily the date progress was measured.
2. Move unfinished work past it. Project > Update Project > “Reschedule uncompleted work to start after” the status date.
If you take nothing else from this article, take these two steps. One caution: the command places a Start No Earlier Than constraint on the unstarted activities it moves forward, so review them to make sure they are truly planned to start on the status date. Microsoft Project also has calculation options that do part of this job automatically as progress is entered. They are described in Note 1.
2. Do not type dates into Start and Finish
Schedulers enter durations and logic. The scheduling engine produces the dates. That is the whole idea of CPM, and the most common way I see it broken in Microsoft Project is a scheduler typing a date straight into the Start or Finish field.
Microsoft Project does not treat a manually entered date as information. It treats it as an instruction and quietly applies a constraint: Start No Earlier Than for a typed start date, Finish No Earlier Than for a typed finish date. From then on, the activity no longer moves with its predecessors the way the logic says it should. This causes major disruptions to the network logic, chopping up the schedule into many discontinuous paths of work.
Inexperienced schedulers do this most often when planning future work. An activity does not land where they expect, so they type in the date manually, unknowingly overriding the schedule logic. Apart from the rare genuine hard calendar constraint, the dates of future work should come from durations and logic, not from being typed into the Start or Finish column.
The same thing happens during updates, when progress is recorded by typing over Start and Finish. That is not how to properly record actual start and actual finish dates.
What to do:
· Record progress in Actual Start and Actual Finish. Add both as columns in your update view. Dates entered there do not create constraints.
· Status in-progress activities by remaining duration, not percent complete. Percent complete in Microsoft Project is duration-based, so the remaining duration should reflect the workdays actually left to complete.
· Audit the constraints before each submittal. Add the Constraint Type column and filter for anything other than As Soon As Possible. Every constraint that remains should be one you can explain (e.g., a hard calendar date for an equipment delivery).
· Keep the Indicators column visible. Its icons flag constraints and other oddities. Anything unusual there deserves a look. I usually set the Indicators column as the leftmost column in the schedule so it is always there as a check.
3. Give every activity an identity that does not change
Microsoft Project’s ID column is a row number. Insert an activity at row 40 and everything below it gets a new ID. In Primavera P6, the Activity ID stays with the activity for the life of the project, which is what lets a reviewer line up one update against the next.
Microsoft Project does have a permanent identifier, the Unique ID, and that is what I use to match activities from one update to the next. When it cannot be relied on, the comparison falls back to activity names, and every renamed activity becomes hard to track.
What to do:
· Give each activity a permanent ID of your own. Put an activity code in a text field such as Text1, show it as a column, and never reuse or change a code once it has been submitted. Set it as the second column from the left.
· Show the Unique ID column as a backup. As an alternative, right-click any column heading, choose Insert Column, and type “Unique ID.” Microsoft Project assigns it once and never renumbers it.
· Move activities by dragging, not by cut and paste. A pasted activity is a new activity with a new Unique ID.
· Save every update as a new file. Each update should start as a copy of the prior one, and the prior one should be left untouched as the historical record. Contractors overwrite the same file month after month far more often than you would believe. When that happens, the most important evidence for a delay claim, the native files of the intermediate schedule updates, is gone forever.
4. Clean up out-of-sequence progress
Work in the field does not always follow the logic in the schedule. A successor starts before its predecessor finishes, and the update now contains out-of-sequence progress.
P6 makes the scheduler choose how to handle this, with Retained Logic or Progress Override, and prints the choice in the schedule log. Microsoft Project has no retained-logic or progress-override setting. The closest it comes is the “Split in-progress tasks” option, which is not labeled as an out-of-sequence setting and is not reported anywhere in the schedule. The same logic and the same progress can therefore produce different dates in Microsoft Project than in P6, and a reviewer cannot tell from the file which treatment was applied.
The answer is to remove the ambiguity yourself:
· Find the out-of-sequence activities at each update. Look for any activity with an actual start earlier than the finish of a finish-to-start predecessor.
· Fix the logic instead of relying on the software. If the work really could proceed without the predecessor, the relationship is no longer valid. Revise it to reflect how the work is actually being built.
· Explain what you changed. List the logic revisions in the update narrative. Documenting your logic changes is a mark of top-tier scheduling practice. It shows the owner that you are being transparent and not playing games with the schedule.
5. Keep summary tasks and resources out of the way
Summary tasks in Microsoft Project play the role that WBS summaries play in P6: they roll up the activities beneath them. P6 does not let you tie logic to a WBS band. Microsoft Project lets you link a summary task, constrain it and assign resources to it. Don’t.
Reviewers concentrate on the detail activities, so logic, constraints or progress placed on a summary task are easy to miss. They are still driving dates in your file.
What to do:
· Put all logic on the detail activities. No predecessors or successors on summary tasks.
· Put no constraints, resources or manually entered progress on summary tasks. Let them roll up.
· Use Fixed Duration, non-effort-driven tasks. Otherwise a change to a resource assignment can change the activity’s duration, and with it the entire schedule and the critical path.
Note 2 has more for resource-loaded schedules.
Before you submit
A short check on every update catches most of the above:
☐ Status date is set to the date progress was measured
☐ No unfinished work is scheduled before the status date
☐ No actual dates fall after the status date
☐ Progress was entered in Actual Start and Actual Finish
☐ Every remaining constraint is intentional and explained
☐ Every activity has a permanent activity ID, unchanged from the prior update
☐ Out-of-sequence progress has been found and the logic corrected
☐ Logic changes are listed in the narrative
☐ Summary tasks carry no logic, constraints or resources
☐ The prior update is saved, untouched, as its own native MSP file
A schedule that passes this list will calculate the way a CPM schedule is supposed to, and it will hold up when someone other than its author opens it. That matters most on the day you need the schedule to prove a delay that was not yours
.
Notes
1. Status date calculation options. Microsoft Project can move work to the status date automatically as progress is entered. The options are under File > Options > Advanced > Calculation options for this project. Check “Move end of completed parts after status date back to status date” and “Move start of remaining parts before status date forward to status date,” along with the sub-option under each, and leave “Split in-progress tasks” checked under the Schedule options. Turn them on before entering progress: they act when progress is entered and do not go back and fix activities that were already updated. They only affect activities with progress, so unstarted work still has to be rescheduled as described in section 2. Resource-loaded schedules. Keep the assignments in step with the activity. An activity’s actual and remaining work should agree with the actual and remaining work on its resource assignments. Leave “Updating task status updates resource status” checked under File > Options > Schedule.
About the author
Don Carlow, CGC, EI, PSP, CFCC, is the owner and principal consultant of Florida Constructions and Scheduling Consultants LLC in central Florida. He is often hired to make sense of schedules that make no sense, usually after the project is over and the lawyers have arrived.
Over a 40-year career, Don has worked on hundreds of projects ranging from $500,000 to over $1.5 billion, including hospitals, highways, high-rises and theme parks. He has been appointed as a forensic scheduling or construction expert on well over 100 claims matters and has testified at deposition, arbitration and trial. He holds a civil engineering degree from the University of Central Florida, is a Florida Certified General Contractor, and holds AACE International’s Planning & Scheduling Professional and Certified Forensic Claims Consultant credentials.
He would much rather review your schedule before the claim than after it. Reach him at florida-consultants.com.




Comments