# CAL1: the complete day-planning input

This is original fiction. Rowan is the fictional planner and sole worker; every task below belongs to Rowan. The tasks are already clarified. The durations are estimates Rowan explicitly accepts for this exercise, not measured completion times or promises. No work has started and no task is reported complete.

## Day and fixed commitments

- Plan date: **14 May 2030**. Every time in this packet is **UTC**.
- Work window: **14 May 2030, 09:00–17:00 UTC**, with no overtime.
- Both V1 and the later V2 are prepared **before work starts**. V1 is prepared at 08:30 UTC; the one change arrives at 08:45 UTC. These are fictional scenario times, not actual execution timestamps.
- One person can do only one activity at a time. Start is inclusive and end exclusive: adjacent blocks may share an endpoint.
- All starting source materials are available at 09:00. T02 still requires the exception list produced by T01; the only task dependency is T01 → T02. No travel, setup or waiting time is required beyond the estimates and fixed blocks explicitly supplied here. This simplified assumption belongs to the example; add those costs when they apply to your day.
- Do not move, shorten or use fixed meetings or breaks for tasks. Preserve every task and every estimate in both versions. Do not infer completion from a block's clock time.

| Fixed ID | Start (UTC) | End (UTC) | Minutes | Commitment |
| --- | --- | --- | ---: | --- |
| F01 | 10:00 | 10:30 | 30 | Team coordination meeting |
| F02 | 12:00 | 12:45 | 45 | Lunch, unavailable for work |
| F03 | 14:30 | 15:00 | 30 | Project review meeting |
| F04 | 15:00 | 15:15 | 15 | Break, unavailable for work |

## Every task and its accepted estimate

Every deadline is an inclusive latest finish, not an intended start. T07's next-day deadline does not authorize working outside today's window or invent a booking for tomorrow.

| Task ID | Defined work | Estimate (min) | Latest finish (UTC) | Splitting | Dependency | Priority |
| --- | --- | ---: | --- | --- | --- | ---: |
| T01 | Inspect the supplied sample dataset and note exceptions | 45 | 2030-05-14 11:00 | No: one continuous block | None | 1 |
| T02 | Draft the review note using T01's exception list | 75 | 2030-05-14 14:30 | No: one continuous block | T01 must finish first | 1 |
| T03 | Draft the handoff checklist | 90 | 2030-05-14 17:00 | Yes: one or two blocks, each at least 30 min | None | 2 |
| T04 | Reconcile the project tracker | 60 | 2030-05-14 17:00 | No: one continuous block | None | 2 |
| T05 | Prepare the FAQ draft | 90 | 2030-05-14 17:00 | No: one continuous block | None | 3 |
| T06 | Archive the reference snippets | 30 | 2030-05-14 17:00 | No: one continuous block | None | 3 |
| T07 | Sketch next week's workshop outline | 60 | 2030-05-15 12:00 | No: one continuous block | None | 4 |

## Rowan's explicit selection rule

Rowan accepts the priority order 1, 2, 3, 4, with 1 highest. Within a priority, use the earlier deadline; if deadlines tie, use the lower numeric task ID. The resulting order is **T01, T02, T03, T04, T05, T06, T07**.

Reserve fixed commitments first. Consider tasks in that order, retaining earlier reservations. Place the whole task at the earliest legal time that fits its duration, dependency and deadline. For T03, use the earliest legal allocation of all 90 minutes in one or two blocks, with each block at least 30 minutes. Never place only part of a task and call it scheduled. If the task cannot fit, leave it unscheduled with its full estimate and continue to the next task; a lower-priority task may use a gap that cannot hold the higher-priority one. Do not move earlier reservations merely to fit a later task. This is Rowan's chosen planning rule, not a claim of globally optimal scheduling.

Report the whole day, including unallocated time. For each of the seven IDs, report scheduled and unscheduled minutes and a reason. Unscheduled means **not allocated in this plan**, not canceled, completed or booked for another day. Only Rowan may change estimates, priorities or deadlines, permit a different split, or agree to a new commitment. Make those changes explicit before replanning.