When a change order or a delay hits, we measure what it did to your completion date
When a change order or owner-caused delay hits, we fragnet it into your Primavera P6 or Microsoft Project schedule and measure the float loss and critical path shift. Time is documented, cost supported separately. Prospective TIA per AACE RP 52R-06, backed by years of forensic delay work.
Flat fee per analysis. Draft TIA within a few business days of your records. Owner-facing narrative and exhibits included.
Swipe to see the full schedule
Sign a change order without checking the time impact and the time is usually gone
Owners and agencies don't pay for delay you can't prove, and a stack of emails doesn't prove it. Entitlement starts with what the event did to the critical path and float, backed by the contract, notice and records. Model it when the change hits. Reconstruct it a year later and you're negotiating from memory.
A TIA is only as strong as the baseline and monthly record behind it. We build both: P6 baseline development and monthly updates and narratives.
A defensible analysis, not a letter saying you're late
Everything the submission needs.
Fragnet Modeling Network
The fragnet for the change or delay, inserted into your P6 or MS Project schedule at the right point and data date.
Critical Path Impact Entitlement
We measure how the event moves the critical path and the completion date.
Float Loss & Delay Windows Analysis
Float consumption and delay windows quantified against the schedule, not estimated after the fact.
Concurrent Delay Causation
Your delay separated from the owner's and from concurrent causes, so you claim the time you can support.
Owner-Facing Narrative Record
Each delay tied to its cause, date and contractual basis, ready to submit.
Exhibits Proof
Gantt fragnets, delay diagrams and float-loss exhibits a reviewer can follow.
Modeled the way it would be defended
Same work we do in disputes, done early so the claim is built right the first time.
Pull the records
Baseline, updates, RFIs, change orders, field reports and correspondence: what happened and when.
Build the fragnet
We find the delay driver and build the fragnet for the event.
Model the impact
We validate the update just before the event, insert the fragnet and measure the shift in milestone dates and float, per AACE RP 52R-06.
Establish causation and entitlement
Each delay tied to its cause, date and the contract, concurrent delay separated, and classified as excusable, compensable or neither.
Write the narrative and exhibits
Owner-facing narrative and exhibits a reviewer can follow.
Deliver and stand behind it
Native file (P6 .xer and .xml, or Microsoft Project .mpp), review PDF, narrative and exhibits. The same record is ready if the change becomes a dispute.
A TIA built to the agency spec and the contract
On VA, USACE and NAVFAC work, the TIA and REA must follow the contract and the spec. We model the fragnet, quantify entitlement, write the narrative to agency requirements, and keep the schedule NAS compliant with a clean SDEF where required.
Fragnet TIA, entitlement, owner-facing narrative, formatted to the agency specChange order and TIA questions
Got a change order or a delay sitting unresolved?
Send the change and your schedule. We quote a flat fee within one business day, then deliver a TIA that measures the time impact, with cost documented separately.