A PDF Gantt chart can look spotless in a slide deck while the underlying Primavera P6 or Microsoft Project file is structurally broken. Hard constraints can pin milestone dates in place, missing successors can leave thirty activities dangling with fake float, and a single wrong calendar assignment can shift substantial completion by six weeks the moment actuals are entered.
Picture what happens when a general contractor submits an unvetted baseline or monthly update to a federal, municipal, or institutional owner. The owner's project controls reviewer imports your `.xer` file, runs an automated diagnostic screen in five minutes, and issues a formal rejection notice listing open-ended logic, excessive lags, and negative float. Now your pay application is on hold and your team loses two weeks arguing over software mechanics instead of building the job.
We built our **$750 48-Hour Schedule Health Check** so contractors, subcontractors, and project owners can catch and fix those exact structural flaws before the file ever leaves the trailer. Here is the exact 10-point checklist we run on every Primavera P6 and MS Project file, and how it compares to our $600 Compliance Check and $897 Schedule Working Review.
The 10-Point 48-Hour Schedule Health Check Matrix
Every 48-Hour Schedule Health Check inspects your native schedule file against both DCMA 14-Point assessment thresholds and practical field-constructability rules. On mobile phones, each row below stacks into a readable audit card.
| Check Area | Target Threshold | Why Submittals Get Rejected or Fail in the Field | What Our Readout Gives You |
|---|---|---|---|
| 1. Open-Ended Activities (Missing Logic) | 0 open ends (only Project Start has no predecessor; only Finish has no successor) | Activities without a successor float to the end of the project and hide real critical-path risk | Exact Activity ID list of every open start, open finish, and dangling start-to-start link |
| 2. Excessive Leads (Negative Lags) | 0% negative lags | Negative lags obscure true predecessor-successor relationships and violate almost all owner specs | Replacement logic pairs converting negative lags into explicit intermediate milestones or split tasks |
| 3. High Lags | Less than 5% of relationships with lag > 0 | Using a 30-day lag instead of a procurement or cure activity hides progress tracking | List of high-lag links that should be converted into trackable submittal, fab, or cure activities |
| 4. Relationship Types (FS Dominance) | At least 90% Finish-to-Start (FS) ties | Overuse of Start-to-Start (SS) and Finish-to-Finish (FF) chains creates detached parallel ladders | Audit of non-FS chains where missing finish ties allow activities to remain open indefinitely |
| 5. Hard Constraints | 0 mandatory/hard constraints without contractual justification | Mandatory Start/Finish constraints override network logic and manufacture artificial negative float | Every constrained activity flagged with the exact logic tie needed to remove the hard pin |
| 6. High Total Float | Less than 5% of activities with Total Float > 44 working days | Usually proves a trade or area was never tied back into its downstream inspection or turnover milestone | Pinpoints the disconnected work packages so they can be tied into the proper area completion milestone |
| 7. Negative Float | 0 unexplained negative float in a baseline; full recovery narrative in updates | Submitting an update with unexplained negative float signals an unmitigated late completion | Traces the exact driving path causing the negative float and identifies candidate resequence points |
| 8. High Durations | Less than 5% of incomplete tasks with duration > 20 working days (1 month) | 60-day single-line activities make monthly percent-complete entries subjective guesswork | Identifies long-duration bars that should be broken down by floor, area, or phase |
| 9. Invalid Dates & Out-of-Sequence Progress | 0 forecast dates before Data Date; 0 actual dates after Data Date; 0 unresolved out-of-sequence ties | Causes P6 retained-logic vs. progress-override calculations to produce wildly different end dates | Exact list of broken actuals and out-of-sequence activities corrupting the critical path calculation |
| 10. Critical Path Continuity & Calendar Hygiene | Unbroken critical path from Data Date to Completion; consistent workweek/holiday calendars | Mixing 5-day and 7-day calendars on linked tasks creates phantom float traps across weekends | Verification that the longest path traces through real controlling field work from start to finish |
Which Scheduling Review Fits Your Timeline and Budget?
We offer three distinct review entry points before you commit to a monthly update retainer or a full baseline rebuild. Choose the tier that matches what is sitting on your desk today:
| Review Option | Flat Price | Turnaround | Best Use Case | Direct Link |
|---|---|---|---|---|
| Schedule Review / Spec Compliance Check | $600 per review | 2 to 3 business days | You have a completed schedule and want a fast pre-submittal check against the contract spec section | Book a $600 Compliance Check |
| 48-Hour Schedule Health Check | $750 flat | 48 business hours | You inherited a contractor or trade XER/MPP file and need a rapid 10-point structural and DCMA readout | Request a $750 48-Hour Health Check |
| Schedule Working Review (Paid Brief) | $897 flat | 3 to 5 business days | You need a principal-reviewed written brief covering structural health, critical-path realism, phasing risk, and a corrective action plan | Order the Schedule Working Review ($897) |
What Happens After the 48-Hour Health Check?
You are never locked into a follow-on contract. Many project managers hand our 48-hour readout to their internal scheduler or trade subcontractor so they can clean up the flagged Activity IDs themselves. When your team wants CDM Suite to execute the fix, our published follow-on rates are straightforward:
- Monthly schedule update cycle: $950 per update (Net 15)
- Time Impact Analysis (TIA): $1,800 to $3,500, see Time Impact Analysis Cost and Process in 2026
- Recovery or resequence planning: $2,500 to $5,000
- Full CPM baseline schedule in Primavera P6 or MS Project: $3,800 per project, see Primavera P6 Scheduling Cost in 2026
Have a Primavera P6 or Microsoft Project file that needs a hard look before your next owner meeting? Order the $897 Schedule Working Review online or book a consultation to start a $750 48-Hour Schedule Health Check.
Start with a principal-reviewed Schedule Working Review ($897) on our Briefs page, or book a call to kick off a $750 48-Hour Schedule Health Check.
Frequently Asked Questions
What is included in CDM Suite's $750 48-Hour Schedule Health Check?
For $750 flat (50 percent to start, balance on delivery), an Oracle Primavera certified principal audits your native Primavera P6 (.xer) or Microsoft Project (.mpp) file across 10 core logic, float, constraint, duration, and DCMA 14-point metrics and returns a prioritized fix readout within 48 business hours of receiving the file.
How is the $750 48-Hour Health Check different from the $600 Compliance Check and the $897 Schedule Working Review?
The $600 Schedule Review checks whether a file meets a specific contract submittal checklist before upload. The $750 48-Hour Health Check runs a rapid 10-point structural and DCMA audit with a prioritized fix list in two business days. The $897 Schedule Working Review goes deeper into critical path realism, phasing risk, and recovery strategy with a full written brief.
Can you fix the issues found in the health check for us?
Yes. After reviewing the health check readout, your team can either apply the fixes internally or hire CDM Suite for a $950 schedule update cycle, a $2,500 to $5,000 recovery/resequence plan, or a $3,800 full CPM baseline rebuild.
What files do we need to send to start a 48-Hour Schedule Health Check?
Send the native Primavera P6 (.xer) or Microsoft Project (.mpp) file along with your contract scheduling specification section (if applicable). A PDF Gantt chart alone hides underlying logic links, lag values, and calendar settings.
