Split a six-hour commitment into realistic focus blocks

Define one finish line before creating sessions

Start with a statement someone could review: Produce a decision brief comparing three operating options, with a recommendation and its assumptions. That is more useful than Work on strategy because it defines the output and the judgement required. Keep a single owner accountable for the result even if other people provide inputs.

Next, list the work needed to reach that finish line. Gathering evidence, comparing options, and writing the recommendation are different activities. They may fit separate sessions without becoming unrelated commitments. A session should end with something stable enough to resume: a completed evidence table, a first comparison, or a draft ready for review.

Do not turn every paragraph into its own task merely to make the schedule look organized. Splitting is useful when it reduces ambiguity or exposes a dependency. If twenty small cards all share the same owner, deadline, and outcome, the tracking overhead may be greater than the benefit. A modest plan inside one task can preserve context while making progress visible.

Budget working effort, not elapsed calendar span

The fictional brief requires six hours of focused effort. That estimate excludes waiting two days for a colleague's response and excludes the transition between unrelated meetings. An allocation is a hypothesis about the work required, not a claim that you have already spent it or that it fits in the remaining week.

Three two-hour sessions total 360 minutes. If two sessions were placed on one otherwise empty day, a 15-minute gap would make their combined calendar span four hours and 15 minutes. The effort would still be four hours. When external meetings surround a session, the schedule must also accommodate their boundary gaps. Counting those gaps as productive effort would inflate the estimate without producing more output.

Keep separate notes for uncertainty. If the evidence may be incomplete, either allocate a small investigation first or retain contingency elsewhere in the week. Do not silently promise six hours of output from a day that contains only four usable hours. The unresolved difference should lead to a scope or deadline decision.

Worked example: evidence, comparison, recommendation

Assume a fictional owner has suitable availability on Monday, Tuesday, and Wednesday, with the brief due Thursday. The table shows a proposed plan in one timezone. It is a worked example, not a generated schedule or a guarantee that these times exist in your calendar. Each two-hour block has a defined output and a resumption note.

The owner schedules the final drafting session before the deadline day so that a review can expose a missing assumption without immediately becoming an emergency. The plan does not allocate review time to an imaginary colleague: that person's availability must be confirmed separately. A named reviewer and an agreed turnaround matter more than an attractive empty cell.

• Monday's preceding meeting must end by 09:00 and the next event begin no earlier than 11:30.
• Tuesday's preceding meeting must end by 09:45 and the next event begin no earlier than 12:15.
• Wednesday's preceding meeting must end by 13:00 and the next event begin no earlier than 15:30.

Represent the plan honestly in Critical Path

Create one action item with the deliverable, owner, due date, and six-hour allocation. Add concise plan steps for the evidence table, comparison, and recommendation. Keep the final acceptance condition in the description so the plan does not become a checklist disconnected from the result.

The current scheduling implementation caps an individual session at two hours and places at most one session for the same task on each working day. A six-hour allocation therefore needs at least three eligible working days with suitable availability. Its standard placement window is weekdays 09:00–17:00 in the workspace user's timezone, with 15-minute separation. It does not expand to evenings because weekly capacity was raised.

The scheduler seeks a complete placement for the allocation rather than presenting a partial plan as if everything fits. If the due date allows only two suitable days, investigate the shortage. Do not create artificial duplicate tasks solely to bypass the constraint. If the work really consists of independently useful deliverables, splitting into separately owned tasks may be legitimate, but retain their relationship to the same outcome.

Keep Plan 1/3 distinct from a session that elapsed

At the end of Monday, the fictional owner has completed the evidence table. Mark that plan step complete and record the unresolved source question. Plan 1/3 now means one of three checklist steps is checked. It does not prove exactly one-third of the intellectual work is done, because steps can vary in difficulty and effort.

A calendar block ending at 11:15 is not completion evidence. Perhaps interruptions consumed half the session, or the wrong problem was investigated. Review the output before changing task status. Likewise, do not infer that a later session should disappear simply because one early step completed. Reconcile the remaining work estimate deliberately.

The Critical Path task editor prevents selecting completion while plan steps remain open. That helps keep the visible workflow coherent, but it is not evidence that an external business outcome was achieved. Close the task only when its acceptance condition is met; an outcome track may still contain other work and broader measures that remain unresolved.

Replan interruptions without duplicating the commitment

Suppose Tuesday's session loses 45 minutes to an incident. First assess whether the comparison is unfinished, rather than automatically adding 45 minutes because that much time elapsed elsewhere. If it genuinely needs another 45 minutes, record the remaining requirement and inspect what can move before Thursday. The estimate is allowed to change when evidence changes.

Do not count the original two-hour reservation and a new two-hour task as four hours of new deliverable progress. Distinguish work already completed from work still required. Keep a short note stating what is finished, what remains, and why the plan changed; that is enough for a teammate to understand the adjustment without reconstructing your whole week.

If no safe slot remains, use a decision ladder: remove nonessential scope, seek an agreed contribution, move a lower-consequence commitment, or renegotiate the deadline. Taking the 15-minute gap away is not the first solution. A planner is useful when it exposes the tradeoff early, not when it compresses every shortage into the next available boundary.

1. Check the actual output from the disrupted session.
2. Revise the remaining work and acceptance condition where needed.
3. Inspect complete calendar availability and buffers before reserving replacement time.
4. Confirm the saved task and provider blocks agree.
5. Tell affected collaborators about a changed delivery commitment, not every internal scheduling detail.

Common questions