P6 Project ControlsWhy Your TIA Keeps Getting Rejected
Most Time Impact Analysis submissions fail because they don't follow the contract's scheduling specification, use the wrong insertion point, include activities that don't reflect the delay event accurately, or fail to demonstrate critical path impact. Some skip the fragnet entirely and just point to a calendar showing "we lost 30 days" — that's not analysis, it's assertion.
A properly prepared TIA is a prospective delay analysis technique that inserts a delay fragnet into the most recent approved schedule update, calculates the impact on the project completion date, and demonstrates whether the delay event affected the critical path. Done right, it gives owners and arbitrators the forensic evidence they need to make a fair time extension decision.
Our TIA Development Process
Delay Event Documentation
We review the delay event, isolate the cause, identify responsible parties, and establish the precise start date and duration based on project records, daily logs, and correspondence.
Schedule Insertion Point
We identify the correct schedule update (the last approved update before the delay event occurred) and validate that it accurately reflects project status at that point in time.
Fragnet Construction
We build a delay fragnet — a network of activities representing the delay event — with proper logic ties to existing schedule activities, accurate durations, and appropriate calendar assignments.
Impact Calculation & Report
We insert the fragnet, recalculate the schedule, measure the delta in project completion date, and produce a formal TIA report with before/after comparisons, critical path analysis, and time extension recommendation.
What Makes a TIA Defensible
The difference between a TIA that gets approved and one that gets rejected comes down to methodology, documentation, and presentation. Our approach addresses every element that owners, claims consultants, and arbitrators scrutinize.
- Correct insertion point — the fragnet must be inserted into the right schedule update, not the baseline or an arbitrary snapshot
- Accurate fragnet logic — activities must represent the actual delay event with realistic durations and proper relationship types to existing schedule activities
- Critical path demonstration — the TIA must clearly show whether the delay event affected the longest path through the network, with before-and-after critical path comparison
- Concurrent delay identification — if other delays were occurring simultaneously, they must be acknowledged and addressed
- Supporting documentation — daily logs, RFIs, submittals, weather records, correspondence, and photographs that corroborate the delay event timeline
- Contract compliance — the TIA must follow the methodology prescribed by the project's scheduling specification
Critical distinction: A TIA is a prospective analysis — it measures delay impact from the point the delay occurred forward, not retrospectively. This is different from retrospective methods like As-Planned vs. As-Built or Collapsed As-Built, which analyze delays after the fact. Using the wrong methodology is a common reason for rejection.
Types of Delay Events We Analyze
We prepare TIAs for every category of excusable delay recognized under federal and commercial construction contracts, including differing site conditions, design errors and omissions, owner-directed changes, permitting delays, utility relocation delays, unforeseen subsurface conditions, weather events exceeding baseline assumptions, force majeure events, and third-party interference.
Extension of Time (EOT) Support
Beyond the TIA itself, we prepare the complete Extension of Time request package including formal notification letters, delay event chronology, schedule analysis, cost impact summary (if applicable), and all supporting documentation organized for owner or arbitrator review. Our EOT packages follow the contract's notice and documentation requirements precisely — because procedural non-compliance is the fastest way to lose a valid time extension claim.
Litigation & Arbitration Support
When delay disputes escalate to formal proceedings, our TIAs are prepared to the standard required for expert testimony. We work with construction attorneys to ensure our analysis meets evidentiary requirements and can withstand cross-examination. Our team holds Planning & Scheduling Professional (PSP) certification from AACE International — the recognized credential for forensic schedule analysis.
Ready to Resolve Your Scheduling Challenges?
Book a free 15-minute consultation with our certified scheduling team.
Book Your Call →Frequently Asked Questions
A single-event TIA typically takes 1-2 weeks from receipt of project records and schedule files. Complex multi-event analyses or litigation-grade TIAs may take 3-4 weeks depending on the volume of documentation and the number of delay events.
At minimum, we need the project schedule files (XER or XML), the contract scheduling specification, daily logs covering the delay period, relevant correspondence (RFIs, change orders, letters), and any photos or reports documenting the delay event.
Yes. Our PSP-certified schedulers provide expert witness testimony for delay disputes in litigation, arbitration, and mediation proceedings. We prepare expert reports that meet the standards required by tribunals and courts.
TIA is prospective — it measures delay impact from the point of occurrence forward. Other methods like As-Planned vs. As-Built or Collapsed As-Built are retrospective. The appropriate method depends on your contract specifications and the stage of the dispute.