P6 scheduling errors, like missing logic links, hard constraints, and poor WBS structure, often lead to approval rejections and subsequent delays. Know how to run DCMA health checks to eliminate logic flaws, clear negative float, and ensure your baseline schedule earns first-pass approval every time.
Key Takeaways:
- Address Logic Errors Early: Eliminating dangling activities, hard constraints, and calendar mismatches prevents immediate schedule rejections by reviewers
- Adopt Resource-Driven Durations: Relying on productivity rates and crew sizes rather than static durations builds a defensible, realistic critical path
- Audit Before Submission: Pre-submission DCMA-style health checks eliminate float issues and ensure seamless first-pass project baseline approvals
If you are unaware of what Primavera P6 is, it is an Enterprise Project Portfolio Management (EPPM) that is a robust and easy-to-use solution. Used for prioritizing, planning, managing, and executing global projects, programs, and portfolios.
However, most project teams that use it may make mistakes, leading to scheduling errors that further delay project approvals. Some common errors include missing logic links, overuse of hard constraints, static durations, manual date overrides, and poor WBS structure.
This blog will address these common errors to help you improve your P6 scheduling capabilities.
Why a Technically Correct Schedule Still Gets Rejected
P6 errors are actually an approval-cycle problem, not just a technical one. Owners, contract managers, and lenders reject schedules that look fine on a Gantt chart but fail logic, float, or constraint checks during review.
| Reviewer Check | What It Looks For | Typical Pass Threshold |
| Logic completeness | Activities with no predecessor and/or successor (excluding start/finish milestones) | 0% missing logic |
| Leads (negative lag) | Overlapping logic that assumes partial predecessor completion | 0% of relationships using leads |
| Lags | Waiting time inserted between predecessor and successor | Under 5% of relationships |
| Hard constraints | Must-Finish-By/Mandatory dates overriding calculated logic | Under 5% of total activities |
| High float | Activities with total float above a set ceiling, often 44 working days | Under 5% of activities |
| Negative float | Any activity where the schedule cannot meet an imposed date | 0% of activities |
| High duration | Activities exceeding roughly 44 working days without breakdown | Under 5% of activities |
Table 1: What Reviewers Actually Check Before They Approve a P6 Schedule
7 Common P6 Scheduling Errors That Trigger Rejections
The following are some of the common P6 errors that cause delays in approval for complex projects.
Dangling Activities and Missing Logic Links
Open-ended/dangling activities have no predecessor or successor, which breaks the driving logic path. Furthermore, P6’s schedule calculation still runs without flagging it.
Because its engine automatically defaults unlinked starts to the Data Date and unlinked finishes to the Project Finish. DCMA’s Missing Logic check instantly flags any activity lacking both relationships.
| Keystone Tip: A schedule with 5%+ dangling activities almost always fails first-pass owner review. Run a logic-gap filter in P6 before every submission, not just at baseline. |
Overuse of Hard Constraints
Hard constraints (Must-Finish-By and Mandatory dates) override calculated network logic and lock schedule dates, hiding true float. Reviewers treat >5% hard-constrained activities as a red flag on baseline and update submissions alike.
This is because artificially fixed dates mask real delays and prevent dynamic critical path calculations.
Calendar Mismanagement
Assigning continuous 7-day tasks like concrete curing or inspection activities placed on 5-day admin calendars forces artificial weekend pauses. These mismatched calendars silently distort durations and finish dates across the whole network.
| Real-World Use Case: A hospital GC submitted a P6 baseline with MEP inspections on a 5-day calendar instead of the authority’s 7-day cycle. The mismatch pushed real dates 12 days past the approved milestone. |
Static Durations Instead of Resource-Driven Logic
Fixed-duration activities that ignore crew size or productivity rates create schedules that look achievable on paper but can’t survive a resource-loading review. Here’s what you should know:
| Method | How It Calculates | Approval Risk |
| Fixed duration | Duration is entered manually and stays constant regardless of crew size or output rate | High; reviewers flag durations that don’t scale with resource loading |
| Resource-driven duration | Duration is calculated from assigned crew size, productivity rate, and quantity of work | Low; defensible under an owner’s resource-loading review and easier to justify in a delay claim |
Table 2: Fixed Duration vs. Resource-Driven Duration
Resource Over-allocation & Unrealistic Crew Peak Traps
Resource-loading a schedule is essential for defensibility, but simply assigning labor and equipment without verifying site capacity creates a major approval bottleneck. Owners and Construction Managers routinely run resource profile checks during baseline audits; when they see demand spikes that exceed realistic site limits, the schedule gets rejected immediately.
Unmanaged resource allocations trigger approval rejections through three specific mechanisms:
- Theoretical Crew Peaks: A schedule might require 45 certified pipefitters on a single working day when the subcontractor’s master agreement caps local availability at 18.
- Spatial Stacking: Assigning multiple trade crews to the same WBS work area simultaneously creates physical trade interference that invalidates planned production rates.
- Blind Automatic Levelling: Relying on P6’s automatic resource levelling tool without reviewing driving paths often delays critical-path activities behind non-critical tasks, introducing unapproved project completion shifts.
| 📝 Real-World Example: A water treatment facility baseline showed a massive spike requiring four specialized crane rigs on-site during a 3-day window. The reviewer rejected the submission because the site footprint could physically accommodate only two cranes, forcing a 2-week baseline resubmission cycle. |
Manual Overrides to Actual Dates and Out-of-Sequence Progress
Manually forcing actual dates bypasses data-date status updating. Furthermore, out-of-sequence progress breaks network continuity. Overriding driving logic then
- changes the actual remaining durations,
- corrupts critical path forecasting, and
- generates unreliable, misleading total float across the entire project schedule.
This makes it nearly impossible to understand how to perform schedule time impact analysis in Primavera P6 accurately during delay claims.
| Keystone Tip: Never hand-edit actual dates to “fix” a schedule’s look. Reviewers cross-check actual dates against the data date; manual overrides are one of the fastest ways to lose approval credibility. |
Poor WBS Structure That Hides the Critical Path
When learning how to create a schedule in Primavera P6, structuring your WBS correctly is crucial; a flat or inconsistent WBS makes it impossible for a reviewer to trace how the critical path rolls up to milestones. A schedule where you cannot see the critical path gets rejected, and thus approval gets delayed.
| Real-World Use Case: An airport-expansion scheduler used 400+ unstructured activities under one WBS node. Reviewers couldn’t trace the critical path to substantial completion, adding three weeks to approval. |
In most cases, these errors, when unchecked, might also introduce certain risks. Know the importance of schedule risk analysis in projects.
Deep-Dive: Automating the Full DCMA 14-Point Health Check
While manual spot-checks catch basic errors, major project owners and government agencies utilize automated diagnostic software (such as Deltek Acumen Fuse or Primavera Risk Analysis) to evaluate your .xer file against the official DCMA 14-Point Assessment. Understanding how these 14 metrics are calculated ensures your schedule passes automated screening on the first attempt.
Passing the automated audit requires meeting strict statistical thresholds across the core health metrics:
- Relationship Integrity: Over 90% of all activity links should be standard Finish-to-Start ($FS$). Start-to-Start ($SS$) and Finish-to-Finish ($FF$) ties must be minimized, while Lead times (negative lag) must be exactly 0%.
- Float Health: High float (typically $>44$ working days) must not exceed 5% of uncompleted activities, while Negative float must be strictly 0%.
- Critical Path Test: The critical path must be unbroken from the Data Date to the primary milestone. The Critical Path Test verifies that delaying the start of the primary critical activity extends the project finish date by the exact same duration.
- Resource and Cost Integrity: All non-milestone activities must have resource or cost assignments, ensuring zero “orphan” tasks exist within the cost model.
Pre-Submission Checklist Before You Send Your P6 Schedule for Approval
DCMA 14-point criteria is a self-audit that project managers can run before submission. At Keystone Scheduling, our team runs this check on every client engagement. Before sending the schedule for approval, we:
- Run a logic-gap and dangling-activity filter before every submission.
- Cap hard constraints at under 5% of total activities.
- Confirm activity calendars match real inspection, curing, and regulatory cycles.
- Convert fixed-duration activities to resource- or productivity-driven logic where feasible.
- Never manually override actual dates; we let the data date drive status.
- Audit WBS structure so the critical path is traceable to every milestone.
Then we check the following as instructed and take the necessary actions suggested.
| Check | Quick Test in P6 | Action if Failed |
| Dangling activities | Filter for activities with no successor (excluding project finish milestone) | Add a driving logic relationship or justify in the schedule narrative |
| Hard constraints | Group by constraint type; count Must-Finish-By and Mandatory dates | Convert to soft constraints unless contractually required |
| Calendar mismatch | Compare activity calendars against inspection/curing/regulatory requirements | Reassign to the correct calendar before recalculating |
| Negative float | Sort activities by total float ascending | Re-sequence or resource-load until float clears to zero or positive |
| Out-of-sequence progress | Run the out-of-sequence report against the data date | Correct actual dates and re-validate logic before recalculating |
* The full DCMA framework covers 14 specific metrics (e.g., Relationship Types, Lags, Leads, Invalid Dates, Cost/Resource Loading); the checklist focuses on the most frequent rejection triggers.
Table 3: Quick DCMA-Style Pre-Submission Checklist
Conclusion
P6 scheduling mistakes can happen. What’s more important is solving them before you send it for approval. Conducting reviews and proper checks of the schedule allows you to mark the errors before the higher-ups find them during approval.
Get Your Schedule Approved on the First Pass with Us!
Keystone Scheduling runs a full DCMA 14-point health check on every baseline and update before it reaches an owner or CM. We can help you turn rejection risk into a first-pass approval.
Contact us for Primavera P6 scheduling and delay analysis to make sure that your P6 scheduling is error-free!
Frequently Asked Questions
- What Software Tools Can Automate a DCMA 14-Point Schedule Assessment?
Tools like Deltek Acumen Fuse, Oracle Primavera Risk Analysis, and Schedule Inspector automatically run complete DCMA health checks.
- How Does Using Retained Logic Versus Progress Override Affect P6 Schedule Calculations?
Retained Logic respects original logic paths during delays, whereas Progress Override ignores uncompleted predecessors, often skewing critical path results.
- What is the Impact of Excessive Total Float on Project Claims?
Excessive float can lead owners to consume schedule contingency without compensation, complicating future delay and acceleration dispute claims.
- How Frequently Should a P6 Baseline Schedule Be Updated During Construction?
Schedules are typically updated monthly to reflect progress, though complex projects often require weekly or bi-weekly status updates.
- Why Should Activity Steps Be Used Instead of Creating Multiple Short Activities?
Activity steps simplify complex WBS structures while tracking granular progress without cluttering the schedule or inflating relationship counts.
