Skip to content
Kairos OneBook a demo
Menu
Advanced · 2 min read

Fragnet

A small network fragment modeling one change or delay event, inserted into the schedule to measure its effect.

Working definition

A fragnet — fragmentary network — is a miniature schedule for a single event: the handful of activities, durations, and logic ties that represent a change order, a differing site condition, or a delay. Inserted into the current update and recalculated, it turns "this event hurt us" into a measured statement: "this event moved completion by N days." It is the working part inside every time impact analysis.

Key takeaways

  • A fragnet needs three honest components.
  • The number a fragnet produces is only as honest as its inputs, and each input can be inflated: durations padded beyond what records support, ties drawn to the critical path when the work actually intersected float, or the fragnet inserted into a conveniently pessimistic update.
01

Anatomy of a credible fragnet

A fragnet needs three honest components. Activities that describe the real added or disrupted work, at the same level of detail as the surrounding schedule. Durations supported by something — production rates, quotes, crew logic — rather than asserted. And ties into the existing network that reflect how the event actually intersected the work: which activities it stopped, which it displaced, which merely watched it happen.

02

Where fragnets get gamed

The number a fragnet produces is only as honest as its inputs, and each input can be inflated: durations padded beyond what records support, ties drawn to the critical path when the work actually intersected float, or the fragnet inserted into a conveniently pessimistic update. Reviewing a fragnet is therefore less about the arithmetic — the software does that — and more about interrogating each assumption against the contemporaneous record. A fragnet whose durations and ties can each be traced to a document is an argument; one that cannot is a request.

Sources and scope

Follow the reference trail.

This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.

10S-90: Cost Engineering TerminologyAACE International · checked 2026-08-01Recommended Practice 52R-06: Prospective Time Impact AnalysisAACE International · checked 2026-08-01UFGS 01 32 01.00 10: Project ScheduleWhole Building Design Guide / U.S. Department of Defense · checked 2026-08-01