General Contractors

CPM scheduling support without a full-time hire

For small and mid-sized GCs who owe the owner a P6 schedule but can't justify a salaried scheduler. Baseline, monthly updates and narratives, and TIAs when the job changes. Flat fee, scaled to the project.

PSP certified Primavera P6 Owner-compliant baseline Monthly updates & narratives DCMA 14-point AACE RP 91R-16
Who we work with

GCs who owe a schedule and have nobody to own it

$5M TO $150M

Small and mid-sized GCs

Commercial, multifamily, healthcare, education and municipal jobs where the owner wants real CPM and you have no scheduling department.

CM AT RISK / DESIGN-BUILD

CMAR and design-build teams

One schedule for design and construction, with GMP milestones, early packages and design deliverables tied to the dates they gate.

HEAVY CIVIL

Site, utility, roadway and heavy civil GCs

Weather calendars, phased MOT, utility relocations, DOT or municipal specs. Schedules that carry quantities and crews, not just bars.

FIRST FEDERAL JOB

GCs taking on VA, USACE or NAVFAC work

Major VA specs require an independent CPM consultant and a cost-loaded NAS baseline before the first pay request. Corps and Navy specs set their own rules. Our federal experience includes independent CPM consulting on a VA medical center and serving as lead scheduler on a USACE project. See federal scheduling.

OVERFLOW

GCs with one scheduler and too many jobs

Your scheduler is buried. We take the new baseline, updates on two jobs, or the TIA nobody has time for, in your P6 database.

IN A DISPUTE

GCs with a claim coming or going

Owner holding payment over the schedule, a sub claiming delay, or liquidated damages on the table. We tell you where you stand. See forensic delay analysis.

What we deliver

What a GC can hire us for

Fixed scope, fixed fee, quoted before we start. Pick one, or retain us as your schedule department.

Owner-compliant P6 baseline

Built to the owner's spec: WBS, coding, calendars, logic, crew and quantity based durations, contract milestones, and cost or resource loading if required. DCMA 14-point check before submittal. Typically 10 to 15 business days from kickoff.

Monthly update program

Field status, remaining durations, critical path and total float review, a three-week look-ahead, and the narrative the spec requires, delivered before the pay app so the two match. Month to month, no lock-in.

Subcontractor schedule integration

Each major sub's durations and sequence go into the master, signed off by the sub. When one slips, the schedule shows whose work moved the finish, your record for a back charge or claim.

Change orders and time impact analysis

A fragnet for each change that hits the critical path, run in the current update as a TIA under AACE RP 52R-06. Day count, exhibit and narrative in time for the notice deadline.

Recovery and acceleration schedules

We isolate what moved the finish and price each way back (resequencing, added crews, shift work, scope changes with the owner) so you can decide to accelerate, absorb or claim.

REAs, claims and claim defense

An REA built on the contemporaneous updates, or defense against a sub's delay claim or liquidated damages. Forensic analysis under AACE RP 29R-03, with expert report and testimony if needed. See REAs and claims.

Your schedule department

What a schedule department does each month

01

Build the owner-compliant baseline

Clean logic and realistic durations, built to the spec.

02

Run monthly updates and narratives

A narrative every period that keeps the owner paying and your position protected.

03

Hold the master schedule across trades

Clean handoffs, so a sub's slip doesn't become your delay.

04

Catch slippage and recover it

Slips flagged early, with a recovery plan and what it costs.

05

Model change orders and time impact

A TIA per AACE RP 52R-06 ties added time to the change, so you don't absorb the owner's scope creep.

06

Show up at the OAC

We attend progress and OAC meetings and carry the schedule position.

Where GCs get hurt

Where the schedule costs a GC money

We see these forensically, after they get expensive. On the scheduling side we go looking for them from the first baseline, while they are still cheap to fix.

01Nobody reads the spec. The baseline is rejected and the first pay app sits.
02The baseline goes in late, and the owner measures you against a schedule you never agreed to.
03Subs never bought into their durations, so the first slip is a fight, not a documented delay.
04Updates built from memory, not daily reports, so the record won't back you up.
05Boilerplate narratives, so the one month that mattered says nothing about what moved.
06A change order gets signed with no time because nobody built the fragnet before the deadline.
07Owner delay quietly absorbed with no notice letter, and float you might have claimed is gone.
08Constraints hold the finish on paper while the field slides, until the owner's scheduler finds it.
09The pay app and the update disagree on percent complete, and the owner uses the gap against you.
10Liquidated damages assessed, and the record is too thin for anything but a narrative defense.
Both directions

The schedule protects you toward the owner and the subs

UP

Toward the owner

Owner-caused delay documented as it happens: submittal turnaround, design changes, owner-furnished equipment, site access, decisions. Notice letters when the contract requires them, and extension requests built on the current update, not a year later.

DOWN

Toward the subs

Sub slips isolated in each update so the impact is attributable. Float ownership and schedule compliance language for your subcontracts keeps a sub's delay the sub's problem.

IN

Inside your own operation

One schedule for field, office and pay app on the same data date, with look-aheads that match the master, so a dispute doesn't start inside the company.

OUT

In the room

The owner's scheduler or CM gets answers from the person who built the file, not a PM reading a bar chart.

Right-sized for you

You don't need a full-time scheduler. You need this done right

Scaled to the job, from a one-time baseline to a full monthly program.

01A one-time owner-compliant baseline when that is all the job needs
02Month-to-month updates and narratives with no lock-in
03Change orders, TIAs, recovery and meetings when you need them
The forensic edge

Scheduling informed by forensic delay experience

Why it is different

We spent years taking schedules apart. Now we build yours to survive scrutiny

Forensic work showed us how schedules get GCs in trouble: missing logic, soft constraints, a record that won't back you up. We build against that from the first activity, so your monthly schedule protects you if the job goes sideways.

Methodology grounded in AACE RP 91R-16 · 29R-03 · 52R-06
GC-side proof

Recent work for general contractors

A sample, not a full list. Names withheld, references available on request.

GC / Delay Claim Defense

Municipal sewer reconstruction, New Mexico

Default termination defense and delay claim for the general contractor. Period-by-period as-planned vs. as-built analysis (MIP 3.2) from PDF schedule prints and the as-built XER, isolating owner review delay and a disputed constructive change.

GC / Federal

VA medical center, Virginia

Independent CPM consultant for the GC under the VA Network Analysis Schedule spec. NAS-compliant baseline, cost loading and monthly updates tied to progress payments.

Design-Build

Mass burn waste-to-energy facility

Full plant scope: boiler, turbine generator, air cooled condenser, ash handling, and major mechanical, piping and electrical packages. Baseline and updates on the resource and quantity loaded P6 schedule.

EPC

Biosolids-to-fertilizer facility

Biosolids receiving and dryer system, granulation plant, and chemical and ammonia storage. Baseline and updates, with subcontractor schedules integrated into the CPM master.

How it works

Send the spec. We take it from there

1

Send the owner's spec and contract dates

Plus drawings or a scope summary, your sub list and any draft schedule.

2

Kickoff with your PM, super and major subs

One working session, on site or remote, to sequence the job with the people building it. The baseline comes from that session, not a template.

3

Baseline submitted, comments worked, accepted

DCMA 14-point and spec check first, then we work the owner's comments to acceptance. Every update and claim is measured against that file.

4

Monthly, in your P6 database or ours

Status call with the super, update, look-ahead, narrative, pay app support. TIAs when a change hits. OAC meetings if you want us there. Cancel any month.

Based in Florida. Scheduling, delay analysis, TIAs, REAs and claim defense for GCs nationwide, done remotely from your files.

General Contractor FAQ

Questions we get from GCs

I owe the owner a CPM schedule but can't justify a full-time scheduler. What do you do?
We act as your schedule department: baseline, monthly updates and narratives, TIAs and recovery, for a flat fee and no added headcount.
Can you build and hold the master schedule across all my subs?
Yes. We sequence the trades and flag a sub's slip in the update before it becomes your delay against the owner.
A change order or owner-caused delay hit. How do I protect my time and money?
We fragnet the change and run a TIA per AACE RP 52R-06 to measure the completion-date impact. Cost is documented separately. That beats a letter the owner can wave off.
We are behind. Can you build a recovery schedule?
Yes. We isolate what moved the finish and price each option (crashing, resequencing, added crews) against the time it buys back.
What does a baseline cost, and how long does it take?
Flat fee, quoted in writing up front, based on contract value, the spec and any cost or resource loading. A typical commercial baseline takes 10 to 15 business days from kickoff to submittal. Monthly programs carry a standing monthly fee.
The owner rejected our baseline. Can you fix it?
Yes, and fast. Send the file and the comments. Most rejections are missed spec items (coding, calendars, constraints, logic, cost loading, narrative). We fix the file, run the DCMA 14-point, and answer each comment in writing.
Our subs will not give us schedule input. What then?
We build their scope from production rates and the drawings, send each sub their activities, and document the reply or the silence. The record shows what each sub was asked and never disputed.
We already have a scheduler. Can you just take the overflow?
Yes, in your P6 database and templates: a new baseline, updates on a job or two, or the TIA due Friday. Your scheduler still owns the system.
The owner wants Microsoft Project, not P6. Can you do that?
Yes. We build in P6 and deliver what the spec requires, including Microsoft Project files and PDF layouts. If the spec is silent we recommend P6, since the native file carries the logic and float a claim needs.
A sub is claiming delay against us. Can you defend it?
Yes. We test their claim against the contemporaneous updates. Sub delay or concurrency in the record is your defense, and if the record points at you, you find out before mediation.
What do you hand the owner each month?
An updated schedule, look-ahead and a narrative on what moved and why, which keeps pay apps moving and your record straight.

Owe the owner a schedule and no one to build it?

Send the owner's spec or your draft baseline. On a 20 minute call we'll talk through the owner's requirements and price the baseline and a monthly program.

Back to top ↑