A Time Impact Analysis is only as strong as the schedule logic it's built on and the fragnet insertion methodology behind it. HADVEN LLC prepares prospective and retrospective TIAs that isolate a single change event, insert it into the accepted CPM logic at the correct point of impact, and demonstrate the resulting effect on project completion — in the format USACE, VA, Caltrans, and Port Authority reviewers expect on first submission.
A TIA lives or dies on the fragnet — the logic-tied sub-network inserted into the schedule to represent the delay event. Insert it at the wrong point in the network, base it on a schedule update that wasn't current, or fail to tie resource and cost data to the same activities, and an owner's reviewer or opposing expert has an easy basis to reject the whole analysis before engaging with the substance.
HADVEN LLC builds every TIA from the contemporaneous schedule record — the update actually in effect when the event occurred — and ties the fragnet to real logic, not an assumption of how the event "probably" affected the critical path. That is what makes the difference between a TIA an agency accepts on first read and one that comes back with rejection comments.
Fragnet built from the schedule update in effect at the point of impact — not reconstructed after the fact when avoidable
Delay quantified against the accepted critical path, with float impact shown at every affected activity
Prepared in formats accepted by USACE, VA, Caltrans, Port Authority, and state DOT reviewers
Supporting narrative that ties the fragnet to daily reports, RFIs, and correspondence — not a bare schedule export
Built to feed directly into an EOT claim if the delay ultimately requires a formal time extension request
Every TIA HADVEN LLC prepares is built to hold up under the exact review process it's headed for, whether that's an owner's project engineer or opposing counsel.
A Time Impact Analysis prepared at or near the time the change event occurs, using the schedule status in effect at that point to demonstrate the projected delay before it fully plays out in the field.
Reconstruction of the schedule status as it existed at the time of a past delay event, built from daily reports, RFIs, submittals, and correspondence where the contemporaneous update record is incomplete.
Logic-tied fragnet networks representing the impacting event, inserted at the correct point in the accepted schedule to isolate the delay's effect on the critical path without distorting unrelated activities.
Sequential TIAs across a series of related change events on the same project, maintaining consistent methodology and a running record of cumulative schedule impact through the life of the contract.
Independent review of a TIA prepared by another party — owner, contractor, or opposing expert — evaluating fragnet placement, logic integrity, and whether the quantification methodology holds up.
TIA output structured so it feeds directly into a formal Extension of Time claim without rework, when a quantified event needs to become a contractual time-extension request.
Whether the event happened last week or two years ago, the same sequence keeps the analysis defensible.
The change event, RFI, or disruption is reviewed against contract documents, correspondence, and the schedule update in effect at the time it occurred.
A logic-tied fragnet representing the event is built and inserted at the correct point in the accepted schedule network.
The schedule is recalculated with the fragnet in place, isolating the resulting shift to the critical path and project completion date.
Findings are documented in a written narrative and exhibit package formatted for the owner, agency, or legal reviewer the TIA is headed for.
A HADVEN LLC TIA arrives as a complete exhibit package, not a schedule file that needs interpretation.
Native P6 / MS Project files showing the fragnet insertion and resulting schedule recalculation.
A written narrative explaining the event, the fragnet logic, and the resulting delay in plain language.
Supporting exhibits tying the fragnet to daily reports, RFIs, submittals, and correspondence.
Agency-ready formatting matching USACE, VA, Caltrans, or DOT submission conventions.
A structure ready for EOT — output formatted to feed directly into a formal time-extension claim.
A single point of contact throughout the engagement, available to walk the analysis through owner or agency questions.
A Time Impact Analysis quantifies the schedule effect of a single change event, RFI delay, or owner-caused disruption by inserting that event into the accepted CPM schedule at the point of impact and measuring the resulting delay to project completion.
A TIA quantifies the schedule effect of one specific event, usually prepared close to when it happens. An Extension of Time claim is the broader contractual submission, often built on one or more TIAs, that formally requests additional contract time and establishes entitlement.
A prospective TIA is prepared at or near the time the delay event occurs, using the schedule status in effect at that point. A retrospective TIA is prepared after the fact, reconstructing the schedule status as it existed when the event occurred, which requires more supporting documentation to establish credibly.
USACE, VA, Caltrans, Port Authorities, and most state DOTs recognize Time Impact Analysis as a standard, accepted method of quantifying schedule delay, provided the fragnet insertion and supporting logic follow the specification's methodology requirements.
A single-event TIA is typically prepared within one to two weeks once the schedule update and supporting documentation for the event are available, though this depends on the complexity of the event and how well-maintained the underlying schedule record is.
Contact HADVEN LLC to scope a Time Impact Analysis. We respond to all inquiries within one business day.
