Delay Notices, Fragnets, and Time Impact Analysis

When something outside your control delays the job, you need to show its effect on the critical path. The Claims view keeps the record and does the math.

Open Claims

More views… → Claims. Writing to it needs Owner or Editor access. Anyone can view and download.

Log a delay notice

Fill in:

• Activity: the activity affected
• Reason: weather, predecessor, materials, manpower, design change, access, or other
• Impact (days)
• Narrative: what happened, when, and who was notified

Click Add notice. Then Apply duration adds the impact to the activity's duration and recalculates. Each notice can be applied once.

Insert a fragnet

A fragnet is a small piece of new schedule, such as the work added by a change, inserted into the network to measure its impact.

1. Under Fragnet insert, choose the Predecessor, the Successor, and the Duration (d).
2. Click Preview fragnet impact. You'll see the finish before and after, the impact, and whether it's critical. Nothing has changed yet.
3. Confirm onto live inserts the delay activity, or Discard preview.

See the blog on writing a fragnet and time impact analysis.

The TIA report

The TIA report totals attributable days by simple sum and with a concurrency model, and lists each notice with its activity, reason, whether it's applied, the cumulative impact, and the finish without it. Download TIA markdown saves it for your claim file.

Draft an owner notice

Share & reports ▾ → Owner notice drafts a delay notice letter from the baseline comparison. It needs an active baseline. Switch between Preview and Edit, then Download .md or Email to me. Review it before it goes out. It's a starting draft, not legal advice.

Delay report

Share & reports ▾ → Delay report downloads a narrative of slip against the baseline.