Event 1
Time and money: an event passes one gate and fails the other
Type each event with the dates it moved completion on and the dates it held resources on, and say how much float stood in front of it. Two whole day counts come back that are usually different numbers, and every event lands in one of four boxes with the gate it did not pass named beside it. The two counts are never added, because they are read off different records. Nothing here decides entitlement or calls any day compensable.
Live result
The completion date gate returns 3 days, while the resource gate returns 3 days. They stay separate because they come from different typed records.
The completion date gate returns 3 days, while the resource gate returns 3 days. They stay separate because they come from different typed records.The two typed gates
Try a scenario
Same event scope and information cut
Both date lists need to describe the same event scope and the same information cut.
0 days
Zero absorbs no completion date. A positive whole count absorbs that many earliest typed completion dates.
Event inputs
Use YYYY-MM-DD in increasing order, separated by commas. Nothing is inferred between dates.
Event 2
day
Zero absorbs no completion date. A positive whole count absorbs that many earliest typed completion dates.
Event 3
days
Zero absorbs no completion date. A positive whole count absorbs that many earliest typed completion dates.
Event 4
days
Zero absorbs no completion date. A positive whole count absorbs that many earliest typed completion dates.
This page shows from 1 to 8 events so every event remains legible in the chart. The calculation accepts up to 50.
Typed float for the first event
daysdays
days
days
It does not check the values in between.
No other integer in the range leaves the two counts and the first event box at 3 / 3 / Completion dates only. Every admissible integer in this range was checked.
No other integer in the range leaves the two counts and the first event box at 3 / 3 / Completion dates only. Every admissible integer in this range was checked.| The answer | 3 / 3 / Completion dates only |
|---|---|
| Values sampled | 0 days to 4 days, 5 values, step 1 day |
| Holds from | 0 days, lowest sampled |
| Holds to | 0 days |
| Nearest value that changes it | 1 day |
| The answer there | 2 / 3 / Completion dates only |
What an unchanged region does and does not prove is set out in a short lesson.
Every admissible integer in this range was checked. Values outside the range remain unchecked.
- First checked change in a count or the target box
- At 1 days of typed float · Completion dates only
- First checked target box change
- At 2 days of typed float · Neither typed list passes
Two counts, kept apart
Distinct completion effect dates after float
3 days
Distinct resource effect dates
3 days
No combined total is produced.
Every event on the two gates
E1
Completion dates only
- earliest completion dates absorbed
- 0
- Gate not passed
- typed resource gate
E2
Resource dates only
- earliest completion dates absorbed
- 1
- Gate not passed
- completion date gate
E3
Both typed lists pass
- earliest completion dates absorbed
- 0
- Gate not passed
- Both gates passed
E4
Neither typed list passes
- earliest completion dates absorbed
- 0
- Gate not passed
- completion date gate and typed resource gate
- Shared completion dates
- none
- Shared resource dates
- none
Boundary
It counts the two typed date sets and places events on two declared gates, without deciding entitlement, classifying compensability, pricing delay, assigning cause, or reading a contract.
Here is the maths
The formula, in words
For each event, sort the typed completion effect dates and absorb the first whole number named by its float. Any remaining completion date passes the first gate. Any typed resource effect date passes the second. Count the union of dates separately for each gate, so a date shared by events appears once in that gate's total.
where is the extension day count, the event index, and completion dates remaining after float for that event.
where is the resource day count and typed resource dates for each event.
A worked example
Event E1 leaves 2 completion dates and no resource date. E2 has its 1 completion date absorbed and keeps 2 resource dates. E3 keeps 1 date in each list. E4 has neither. The first union contains 3 dates and the second union also contains 3 dates, but the two threes are never added.
What this does not model
The boxes only describe the typed lists. They do not classify a claim, price a delay, assign cause, interpret negative float, read a contract, or decide entitlement.
Source basis
The mechanism uses public set union and whole number arithmetic. It reproduces no definition, taxonomy or wording from sold guidance.
The whole record prints. Your browser can save it as a PDF instead of printing it.
The two gates do not decide entitlement or classify an event as compensable, and those requests are always refused.
Related
- Prolongation and disruption: delay costs money twiceStaying on site longer is one cost. Working less efficiently while you are there is a different one, proved with different records, and pricing either of them in the wrong month moves the figure further than the delay did.
- Total float: who owns it decides whether the finish date movesA supplier runs 20 days late into an activity with 25 days of float and the finish date does not move. The second time it does, and the reason is something that happened weeks earlier to somebody else.
Two gate event record
Time and money: an event passes one gate and fails the other
Accepted inputs
- Event 1
- E1
- Typed float
- 0 days
- Completion effect dates
- 2026-01-012026-01-02
- Resource effect dates
- none
- Event 2
- E2
- Typed float
- 1 day
- Completion effect dates
- 2026-01-03
- Resource effect dates
- 2026-01-032026-01-04
- Event 3
- E3
- Typed float
- 0 days
- Completion effect dates
- 2026-01-05
- Resource effect dates
- 2026-01-05
- Event 4
- E4
- Typed float
- 0 days
- Completion effect dates
- none
- Resource effect dates
- none
Separate results
- Distinct completion effect dates after float
- 3
- Distinct resource effect dates
- 3
- E1
- Completion dates only
- E2
- Resource dates only
- E3
- Both typed lists pass
- E4
- Neither typed list passes
Record fields
- Calculation version
- 1.0.0
- Boundary
- It counts the two typed date sets and places events on two declared gates, without deciding entitlement, classifying compensability, pricing delay, assigning cause, or reading a contract.
- Source basis
- The mechanism uses public set union and whole number arithmetic. It reproduces no definition, taxonomy or wording from sold guidance.