Monthly Updates & Narratives

Every monthly update is your record. We make it the one that holds up

An independent Primavera P6 or Microsoft Project update: field progress against the approved baseline, critical path and float tracked, each delay and change flagged as it happens, and a written narrative that becomes your contemporaneous record. Built to support forensic analysis under AACE RP 29R-03 and prospective TIAs under RP 52R-06.

Flat monthly fee. Updates back within two business days of verified field data. Revisions within the agreed scope are included through owner review.

PROJECT SCHEDULE · DEMO DATADATA DATE 4/27/26IDACTIVITYODTFMARAPRMAYJUNJULA1000Notice to proceed00Start milestone, 0 daysA1010Mobilization50A1020Foundations210A1030Structure350A1040Envelope and dry-in280A1050MEP rough-in309TF 9A1060Interior finishes350A1070Site and paving2023TF 23A1080Commissioning and TAB140A1090Substantial completion00Finish milestone, 0 daysCritical (TF 0)Non-criticalMilestone (0 days)Data dateOD and TF in calendar days

Swipe to see the full schedule

PSP certified Primavera P6 & MS Project Contemporaneous record AACE RP 29R-03 DCMA 14-point Built to your schedule spec Flat monthly fee
Why the update matters

A monthly update is evidence, not paperwork

The real value of the monthly update is the record. When a delay or change hits, the contemporaneous update and narrative support your extension and cost, not a story rebuilt a year later. An update that misses the field or lets float bleed off helps the other side.

01In a dispute, every accepted update and narrative is dated evidence. It beats memory
02Critical path movement and float erosion show up early, while you can still act
03An update that doesn't match the field gets you caught in the progress meeting
What is in each update

A full monthly update, not a percent-complete guess

Status checked against field reports and PM input, a real baseline comparison and a narrative, every period.

Progress Checked Against Field Records Status

Actual starts, finishes and remaining durations from daily reports and super and PM input, checked against site conditions.

Variance vs Baseline Variance

Planned versus actual against the approved baseline, so you track real variance and trend.

Critical Path & Float Tracking

Critical path and total float by update, so erosion shows up the month it starts.

Delay & Change Flagging Protection

Delays, out-of-sequence work and change order impacts logged as they happen.

EVM Metrics Performance

Earned value (SPI, CPI, cost variance, EAC) where planned value, earned value and actual cost data exist.

Written Narrative Record

What moved, why, what drives the critical path, and what it means for completion.

How we run the update

Built to match the field and survive a review

We spent years reading other people's updates in delay disputes. We run yours so the record is clean.

01

Pull and verify the field data

Daily reports, super and PM input and inspection records, reconciled before status goes in. Anything we can't verify gets flagged.

02

Status the schedule at the data date

Actuals and remaining durations at the data date, with out-of-sequence work resolved, not buried.

03

Compare to the baseline

Real variance, critical path movement and float change against the approved baseline.

04

Flag delays and changes

Delays, disruption and change impacts logged, with a prospective TIA per AACE RP 52R-06 where a change drives the critical path.

05

Run the health check

DCMA 14-point checks each period so logic, constraints and float stay clean.

06

Write the narrative and deliver

Updated native file (P6 .xer and .xml, or Microsoft Project .mpp), review PDF, narrative, and a NAS compliant export with a clean SDEF where the spec requires it.

Owner & federal compliant

Updates that pass the same review every month

On VA, USACE and NAVFAC work, each update follows the contract's submittal requirements, including the narrative, native schedule files and SDEF export to RMS where required. We build it to the agency and owner spec and run DCMA 14-point checks every period, so payment and the record stay on track.

NAS progress update, narrative, SDEF export to RMS where required, every period

See federal and agency scheduling →

Update FAQ

Monthly update questions

How often do you update, and how fast is the turnaround?
Usually monthly, on your cycle, for a flat fee. Schedule and narrative come back within two business days of verified field data.
What is in the narrative?
A plain-language write-up of what moved, what drives the critical path, how float changed, and what any delays or change impacts mean for completion. It's the record that protects your time later.
How do you keep the update matching the field?
We check reported progress against daily reports, super and PM input, and site conditions before statusing, so the update doesn't show "not started" on work already poured.
Can you submit NAS updates and SDEF to RMS each period?
Yes. We run the progress update to your scheduling section, write the narrative to the spec, and export a clean SDEF to RMS where the contract requires it.
Do you flag delays and change order impacts during the update?
Yes, as they happen, with a prospective TIA per AACE RP 52R-06 where a change hits the critical path. The time impact gets documented while the record is fresh, cost separately.
We are behind. Can a monthly update help us recover?
Yes. It shows what moved the finish and where the float went, the basis for a recovery or look-ahead plan and any extension you are owed.

Tired of defending updates that don't match the field?

Send your baseline and latest field reports. We quote a flat monthly fee within one business day.

Back to top ↑