A turnaround schedule that looks perfect on paper but collapses in the field is worse than useless. It creates false expectations, strains contractors, and damages leadership credibility. One of the most common causes of this disconnect is the failure to use Primavera’s resource-leveling engine. Many so-called “schedulers” skip it because they don’t know how, think it takes too much time, or, most dangerously, avoid it because leveling reveals hard truths: the work cannot be done in the time promised. Ignoring those truths doesn’t make them go away; it simply hides them until execution, when the costs are far higher.
A disciplined turnaround organization treats P6’s leveling engine as non-negotiable. If a schedule has not been leveled, it is not a real schedule. It is a wish list dressed up in logic ties.
Schedulers who avoid real leveling present schedules that appear aligned with milestones and duration targets, but the underlying resource assignments tell another story. On paper, hundreds of tasks are stacked into the same timeframe, requiring far more crews than are available. The critical path might look achievable, but in reality it depends on resources that do not exist.
Even worse, many engage in fake leveling. A scheduler sits with a construction lead and says, “Okay, we’ll do this exchanger, then this one, then this one.” Instead of letting Primavera level, they hard-tie the end of one job to the start of another. The result is a chain of artificial dependencies that looks like leveling but isn’t. All they’ve done is force jobs into a false sequence to mimic a leveled schedule.
Fake leveling is more common than true avoidance because it gives leadership a tidy story. Paths converge neatly around the true longest path. But it voids the purpose of leveling. Instead of using actual resource limits, availability dates, and priorities, the scheduler imposes artificial ties. The outcome is not an optimized schedule; it’s a disguised one.
There are also schedulers who neither level nor fake-level. They don’t rely on the schedule for manpower at all, leaning on execution teams’ intuition or contractor guesses. This underutilizes Primavera, reducing the schedule to a bad sequencing diagram with no resource credibility.
The danger of fake leveling is that it convinces leadership and contractors that the schedule has been structured correctly when it hasn’t. Execution teams prepare for sequences that were never resource-driven. Contractors line up to dates that are misleading. The result is a cascade of failure:
Stacked Work: Tasks may appear spread out, but in reality, artificial logic ties create bottlenecks that distort the flow of work.
Hidden Resource Conflicts: Because leveling wasn’t used, the schedule never validated crew demand against availability. Resource histograms are useless if the inputs are fake.
False Confidence: Leadership assumes the schedule is reliable when, in truth, it has been manually massaged to meet dates.
Lost Opportunity for Transparency: Fake leveling hides the reality that scope, resources, or duration must change. Avoiding that truth in planning only makes it more painful in execution.
For schedulers who skip leveling entirely, the risks are different: they avoid false confidence but waste Primavera’s power and disconnect leadership from accurate resource planning.
Resource leveling in Primavera is a key component of the planning phase and is considered a best practice in developing accurate turnaround schedules. Primavera’s resource leveling engine is not optional; it is the core of credible schedule development. When used correctly, it forces planners and leaders to confront the real constraints of manpower, equipment, and access.
Schedules must include real crafts, crew sizes, and quantities that reflect how work will actually be performed. Without this, leveling has nothing to act on.
Schedulers must set priorities on activities, with particular attention to critical jobs, and define resource limits with availability dates. This combination allows Primavera’s engine to allocate resources intelligently. Instead of manually forcing jobs into sequences, the software uses float and priority to balance work across available crews.
With resource assignments, priorities, and limits in place, the leveling engine adjusts activity start dates to ensure that demand does not exceed availability. This often stretches durations or shifts critical path dates, but these shifts are reality. They reveal what can actually be achieved with the given resources.
Primavera provides histograms that display resource demand versus availability. Reviewing these graphs is essential to spot peaks, valleys, and chronic overloads. A credible schedule shows realistic loading, not vertical spikes of demand that can never be met.
When leveling reveals the plan won’t meet targets, leaders choose: add resources, cut scope, or extend duration. They cannot ignore the data or cover it with fake leveling.
A leveled schedule is a non-negotiable requirement. If it has not been leveled with real resources and priorities, it is not approved. This prevents “fantasy” schedules and forces discipline.
Making Primavera’s leveling engine mandatory is a cultural statement. Leaders who demand leveled schedules say: realism matters more than appearance. Discipline in planning protects execution, even when it means uncomfortable conversations upfront.
Schedulers resist because it makes their jobs harder—forcing accurate data entry, conflict confrontation, and delay explanations. But difficulty is not an excuse. The harder it is to level, the more important it becomes.
Leadership’s job is simple: do not accept unleveled schedules. Ask for the histograms. Ask for the resource profiles. If the plan needs more boilermakers or pipefitters than exist in the region, it is not a real plan.
A schedule without real leveling is a fantasy. Fake leveling, hard-tying activities to mimic sequencing, is the most common deception. It creates false confidence, sets contractors up for failure, and erodes leadership credibility. Avoiding leveling altogether underutilizes Primavera and reduces the schedule to a sequencing tool without resource discipline.
Turnarounds are too complex and costly to gamble on fake schedules. Leaders must enforce P6’s leveling engine as a non-negotiable requirement. Do so, and the schedule becomes a roadmap, not a wish list.
When contractors fail during a turnaround, it is rarely due to lack of effort in the field. Poor job plans, missing materials, weak logistics, and unclear inspections are upstream failures that leadership must own. Turnaround groups create the conditions for contractor success—or for failure.