Capacity
Due date vs time allocation vs calendar block: what each means
A due date says when a result is needed. Time allocation says how much effort you intend to invest. A calendar block says when you intend to do that work. Keeping them separate makes planning and rescheduling more honest.
By QuadrantWorksUpdated 8 min read
The short version
- A deadline is not an execution appointment, and an estimate is not a reservation.
- A six-hour allocation can become three two-hour sessions without creating three separate deliverables.
- Buffers consume calendar space but are not automatically part of productive task effort.
- When the plan changes, edit the field that changed instead of moving the deadline to hide a missed session.
In this article
Three fields answer three different questions
Task tools often place a due date, duration, and start time close together. That proximity makes them easy to treat as interchangeable. They are not. You can have a well-defined deadline with no effort estimate, a reasonable estimate with no available time, or a calendar full of blocks that do not add up to enough effort.
A believable commitment needs all three questions answered when the work requires protected time: when is the result needed, how much effort is expected, and which real windows will hold that effort? Some small or delegated actions need a lighter treatment, but the distinctions still help you decide what is missing.
The following fictional example follows a six-hour proposal from estimate to completion. It illustrates planning choices rather than claiming that any particular number of sessions guarantees a finished result.
| Field | Question it answers | Example | What it does not prove |
|---|---|---|---|
| Due date | By which day is the result needed? | Friday | That any work time is reserved |
| Time allocation | How much effort do we intend to invest? | 6 hours | That six suitable hours are available |
| Calendar block | When will a work session happen? | Tuesday, 09:00–11:00 | That the entire task is complete |
| Plan step | Which observable part needs completion? | Validate assumptions with the owner | A calendar reservation or an effort measurement |
A due date should not silently become a morning appointment
Suppose a proposal is due Friday. Placing a six-hour block at 08:00 on Friday would introduce assumptions you did not make: that the morning is free, that the entire task can be done in one sitting, and that no review is needed before submission. A date-only deadline communicates none of those things.
Critical Path presents task due dates as dates and does not use a universal 08:00 deadline anchor to place work. Calendar placement is a separate scheduling decision. If the commitment actually has a precise external cutoff, make that cutoff explicit in the task context and coordinate the review accordingly; do not infer it from a date-only field.
This separation is especially useful when several tasks share a deadline. They can all be due Friday without all competing for Friday morning. The execution plan should spread feasible work earlier, leaving enough opportunity to handle a missing input or a decision that needs another person.
Estimate the work you control, including necessary preparation
For the fictional proposal, the owner estimates two hours to assemble evidence, two to develop the recommendation, and two to revise and prepare the final handoff. That is six hours of expected effort. Waiting overnight for a colleague's answer is elapsed time, not six additional hours of the owner's work.
An estimate should include the preparation required to produce the result. Excluding document gathering because it is not the main task makes the estimate look smaller without reducing the work. Conversely, avoid counting a preparation activity both inside the task and as a separate allocated action.
Critical Path task allocations use fifteen-minute increments. The increment is a convenient planning unit, not a precision claim. A forty-five-minute estimate can still be wrong. When the scope is uncertain, write down the uncertainty and choose a review point instead of treating a more detailed number as more reliable.
Worked example: six hours across three feasible sessions
Critical Path divides larger allocations into calendar sessions no longer than two hours. Here is one possible plan for the proposal, due Friday. Each listed window is fictional and assumes it has been checked against the owner's existing calendar. The exact placement depends on real availability and current authorization.
On Tuesday a meeting begins at 11:15, so the first session ends at 11:00. Wednesday's previous meeting finishes at 12:45, allowing the second session to start at 13:00. Thursday's preceding meeting finishes at 09:45, allowing a 10:00 start. Each example preserves at least fifteen minutes at the adjacent meeting boundary.
| Session | Reserved time | Intended result | Effort |
|---|---|---|---|
| Tuesday | 09:00–11:00 | Evidence assembled; missing inputs identified | 2 h |
| Wednesday | 13:00–15:00 | Recommendation drafted for review | 2 h |
| Thursday | 10:00–12:00 | Feedback incorporated; final handoff prepared | 2 h |
| Total | Three distinct sessions | One proposal, due Friday | 6 h |
Keep buffers separate from work and check the actual reservation
The fifteen-minute gap after Tuesday's session is not a seventh slice of proposal work. It is space for transition before the next meeting. Include such gaps when deciding whether a session fits, but do not automatically add them to the effort estimate. The same principle applies to lunch, travel, and unavailable time.
Google Calendar represents timed reservations with start and end values and a timezone or offset. That differs from an all-day date. Check the timezone shown by your calendar when interpreting a block, particularly when traveling or coordinating across offices.
In Critical Path, a task allocation and a suggested placement are not equivalent to a confirmed external event. Review the connected calendar and its synchronization state. If authorization needs attention or no safe window is found, keep the shortage visible. Do not assume the plan is protected because the task still appears in List or Matrix.
When something changes, edit the right promise
If Tuesday's work is displaced by an essential meeting, the proposal deadline has not necessarily changed. First look for another feasible execution window. If no such window exists before Friday, raise the capacity problem and decide whether to reduce scope, obtain help, or renegotiate the deadline.
If the evidence reveals two additional hours of analysis, the allocation has changed even when the deadline remains Friday. Update the estimate and review placement again. A plan that still reserves only six hours should not be described as covering an eight-hour commitment.
If the recipient agrees to accept the proposal Monday, the deadline has changed. That may create options, but it does not by itself move existing reservations or prove they remain appropriate. Inspect the resulting plan rather than assuming the date edit repaired every dependency.
| What happened | Revisit first | Also check |
|---|---|---|
| A meeting displaced one session | Calendar placement | Can remaining effort still finish before the deadline? |
| The required scope grew | Time allocation and plan steps | Is there capacity for the additional work? |
| The recipient changed the delivery date | Due date | Are existing sessions and review dependencies still sensible? |
| A required input has not arrived | Dependency and task status | What can proceed, and who owns the follow-up? |
| The result is no longer needed | Commitment and task status | Does the calendar still reserve unnecessary future time? |
Plan progress is evidence of steps, not elapsed time
Completing one of three plan steps does not necessarily mean one third of the effort is complete. Evidence gathering might consume half the work, while the final handoff takes fifteen minutes. Treat step progress as a record of defined results rather than a hidden time tracker.
Likewise, reaching the end of a reserved session does not automatically finish the task. Record what changed: a completed step, a revised estimate, or a blocker. The Critical Path task editor keeps plan-step progress visible and disables completion while steps remain open. Review those steps when the scope changes so the completion rule reflects real work.
A five-question check before calling work committed
Use this check during capture for a small task, or during planning for a larger one. An unanswered question is useful information. It tells you what needs a decision before the commitment becomes credible.
- Is the result and its accountable owner clear?
- Does the due date reflect a real requirement rather than a placeholder?
- Does the estimate include the work needed to produce that result?
- Do the actual reservations cover the effort, with gaps around neighboring obligations?
- If the current plan cannot fit, is the required scope, capacity, or deadline decision explicit?
Common questions
Is a due date the same as a scheduled date?
No. The due date describes when the result is needed. A scheduled date and time identify an execution session, which may occur days earlier. A single task can have several sessions before one due date.
Does a six-hour allocation create a single six-hour event?
In Critical Path, calendar sessions are capped at two hours, so a six-hour allocation requires multiple blocks. Successful placement still depends on availability and the calendar connection; an estimate alone is not confirmation.
Should I move the due date whenever I miss a work session?
Not automatically. First assess remaining effort and available time. Change the deadline only when the underlying delivery commitment changes, rather than to conceal a scheduling problem.
Are buffers counted as part of time allocation?
Treat allocation as intended task effort. A transition buffer occupies additional calendar space around that effort. Include it when checking whether the work fits, and avoid counting the same time twice.