Protocol

Compare work estimates and delivery dates separately

An hour of work and two days of waiting are different planning problems.

About 2 min read

Before you use it

Use when
  • The same work always takes longer than planned.

Keep this limit in mind

  • Completed-task records leave out still-blocked work. Small or selected samples do not establish a reliable forecast; a past average is not a guaranteed delivery date.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

For similar completed tasks, compare estimated working hours with actual working hours, and expected delivery date with actual delivery date. Use the same meaning of finished, such as approved rather than drafted. Note waiting, review and rework to explain a miss. Record start and finish when comparing elapsed time; overlapping activities cannot simply be added together.

Steps

  1. Save both estimates before starting, then record the actual hours and delivery date. Keep the units and completion condition consistent.
  2. Use the records to revise the next assumption: the work needed more effort, approval arrived later, or the task changed. Mark an unknown cause as unknown.

An example

Illustrative: a change takes the estimated one hour to write, but approval moves delivery from Monday to Wednesday. The work-hour estimate held; the delivery-date estimate did not.

Check your result

You can show each estimate beside its matching result and explain which assumption needs revision, without calling waiting time extra working hours.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingCompare work estimates and delivery dates separately

Evidence and sources
Supports

UK government delivery guidance suggests regular explicit prioritization based on evidence, user research and available resources.

Claim limit: General public-service prioritisation guidance. It does not prescribe the card-specific effort/date comparison or establish forecasting accuracy. Commitment substitution and estimate review are editorial adaptations, not demonstrated productivity effects. Source reading history: selected_passages; 2026-10-10; Regular priority review using user research, delivery performance and stakeholders. The cited official page was retrieved on 2026-10-10 and the named passages were inspected. Card-specific adaptations are independent editorial reasoning, not validated improvements. Introductory prioritisation and capacity passages reread on 2026-10-12; they do not specify the card-specific forecasting procedure. Agent release review: Atlassian calendar guidance and the UK Government Service Manual supply context for calendar and prioritization practices. The precise estimate comparison and scheduling methods are editorial adaptations; the original data and emergency limits remain attached.

Deciding on priorities · Regular priority review using user research, delivery performance and stakeholders

All sources (1)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details