Linked Event Scenarios

Worked examples showing how anchor and dependent event pairs behave across different snap modes, gap settings, and rotation configurations.

Key — each cell in the day tables below represents one calendar day:

Symbol	Meaning
W	Work day
R	Mandatory rest (rotation)
—	Gap (calendar days, no work scheduled)
(empty)	Day outside this event's span

---

Scenario 1 — Snap to end, no rotation

Anchor: 7 work days, no rotation Dependent: 5 work days · snap=end · gap = 0 days

Oct	1	2	3	4	5	6	7	8	9	10	11	12
Anchor	W	W	W	W	W	W	W
Dependent								W	W	W	W	W

The dependent starts the calendar day after the anchor ends. If the anchor is dragged to Oct 5, the dependent automatically shifts to Oct 12–16 — no manual adjustment needed.

---

Scenario 2 — Snap to start (dependent precedes anchor)

Anchor: 6 work days · starts Oct 10 Dependent: 4 work days · snap=start · gap = 0 days

Oct	1	2	3	4	5	6	7	8	9	10	11	12	13	14	15
Dependent						W	W	W	W
Anchor										W	W	W	W	W	W

With snap=start, the dependent's end aligns to the anchor's start. The dependent works backward from Oct 9 for 4 work days, landing on Oct 6. If the anchor is pushed to Oct 14, the dependent automatically shifts to Oct 10–13.

Pre-mobilisation pattern

Use snap=start for activities that must complete before the main phase begins — procurement, site prep, permitting — so they stay locked to the anchor's start regardless of when it moves.

---

Scenario 3 — Rotation state carries across the junction (matching limits)

Anchor: 6 work days · 4 on / 2 off Dependent: 4 work days · 4 on / 2 off · snap=end · gap = 0 days

Oct	1	2	3	4	5	6	7	8	9	10	11	12	13	14
Anchor	W	W	W	W	R	R	W	W
Dependent									W	W	R	R	W	W

What happens at the junction:

The anchor ends Oct 8 with its crew having worked 2 consecutive days (days 7–8 of that segment). This state — daysOnCount = 2 — carries forward into the dependent.

The dependent starts Oct 9 counting from 2, not from 0:

• Oct 9–10: 2 more days worked → daysOnCount reaches 4 (the limit) → rest triggers
• Oct 11–12: mandatory rest (2 days)
• Oct 13–14: 2 more days worked → 4 total work days complete

The crew never works more than 4 consecutive days, even across the event boundary.

Without carry-forward

If the junction were ignored (daysOnCount reset to 0), the crew could work Oct 7–14 — up to 8 consecutive days — violating the 4-day limit. Carry-forward prevents this.

---

Scenario 4 — Different rotation limits at junction

Anchor: 4 work days · 4 on / 2 off Dependent: 6 work days · 6 on / 2 off · snap=end · gap = 0 days Warning: Linked Events have different rotation limits

Oct	1	2	3	4	5	6	7	8	9	10	11	12
Anchor	W	W	W	W
Dependent					R	R	W	W	W	W	W	W

What happens at the junction:

The anchor ends Oct 4 with daysOnCount = 4 (exactly at its 4-day limit). The effective limit at the junction is:

min(anchor.maxDaysOn, dependent.maxDaysOn) = min(4, 6) = 4

Since the crew arrives at the junction already at 4 consecutive days, rest fires immediately on Oct 5–6 before the dependent begins any work. The dependent's own 6-day internal limit then applies for its remaining segments — Oct 7–12 is 6 consecutive work days, which is within that limit.

Linked Events have different rotation limits

This warning appears on the dependent event whenever the two events have different Max Days On values. The schedule is valid — the stricter limit governs the boundary only. Each event applies its own limit for internal rotation scheduling.

Choosing the right limits

Goal	Approach
Crew rules are identical across both phases	Set the same Max Days On on both templates — no warning, seamless carry-forward
Phase 2 allows longer stretches than Phase 1	Dependent has higher Max Days On. Junction governed by Phase 1's (lower) limit; Phase 2 runs freely after the boundary rest