Test the baseline before you accept it.
An independent review of the contractor’s baseline before approval. We test logic, float, calendars, constraints and the driving path, then tell you in writing what to accept, what to reject and why.
An accepted baseline becomes the yardstick.
Approval turns into evidence
Once accepted, the baseline measures every delay and time extension request. Flaws you approve are flaws you later defend.
Float banked in plain sight
Preferential logic and padded durations can hold float for one party. It surfaces months later inside a claim.
A short review window
Many contracts give the owner a few weeks to respond. Without a scheduler on your side, the clock runs out and silence reads as acceptance.
How we review a baseline.
- 01
Work from the native XER
Logic, codes, calendars and constraints only show in the P6 data. A PDF hides most of what matters.
- 02
Count the health metrics
Missing ties, leads, lags, start-to-finish links, hard constraints, high float, negative float and long durations, listed by activity.
- 03
Hold it against the contract
Milestones, access dates, phasing, work windows and the scheduling specification compared with what the file actually shows.
- 04
Trace each driving path
We follow the path to every milestone and confirm it runs through real work rather than a constraint or a lag.
- 05
Draft the comments you send
Numbered review comments in contract language with a recommended disposition, ready to issue.
What you walk away with.
Scoped to your project. Native files and plain-English outputs that stay yours when we leave.
Issues ranked by consequence, with the specific activities, ties and constraints behind each one.
Numbered comments with a recommendation: approve, approve as noted, or revise and resubmit.
Each scheduling requirement in the specification marked met or not met, with the evidence.
The driving path to each contract milestone described in plain words, with total float stated.
A second pass on the revised file to confirm every comment was actually closed.
When to call us.
The earlier we see the schedule, the more options you keep.
The baseline just arrived
The review window has started. Call on day one, not on the last day.
The resubmittal looks familiar
The contractor revised the file, and the same problems seem to be back.
Your team is light on P6
Your project managers are strong, but nobody on staff reads XER logic every week.
It was accepted without review
We can still document what the baseline contains before the first time extension request arrives.
Where this work has run.
Every project is confidential. Names describe the work, not the client.
Transportation · IllustrativeHighway Widening Owner Schedule ReviewThe agency needed someone to test a design-builder's monthly updates. We review each one before it is accepted.
Water & Wastewater · IllustrativeBiosolids Digester Upgrade RecoverySeven months behind with a regulatory deadline in view. A recovery schedule built from the remaining work brought the first digester back online on time.
Government & Civic · IllustrativeCounty Courts Building Baseline ReviewThe first baseline met the move-in date only on paper. Our review sent it back with fixes, and the accepted version held.Straight answers to fair questions.
Can you review from a PDF?
We can comment on one, but the useful findings live in the native file. Most specifications require the XER, so ask for it.
Will a detailed review damage the relationship?
Rarely. Specific, early comments cost far less goodwill than a dispute a year later.
Do contractors hire you for this too?
Yes. Contractors ask us to check their baseline before it goes to the owner, so fewer comments come back.
How fast is the turnaround?
We scope the review to fit your contract response period and confirm the turnaround before we start.
Related services.
Send the schedule. Act while you have options.
Share the project, the latest XER and the date you are protecting. We will tell you plainly what the schedule is telling you.