Skip to content

Task Deadline Auditor

Paste your tasks in the order you plan to do them, each with a duration and a deadline, and give the time you start. The durations are added up, so you see when every task ends, how much margin or delay it has, which one is the first to be late and how many are late. A second plan, sorted by deadline, shows whether a different order would save you.

Verdict

1 task is late

4 tasks, finishing at 7. First late: Review slides, 1 over its deadline of 5. Worst delay 1. Doing the tasks in deadline order removes every delay.
#TaskStartEndDeadlineMarginDeadline order
1Team call0198 to spare4
2Write report1440 to spare1
3Review slides465Late by 12
4Send invoices6781 to spare3

Doing the tasks in deadline order removes every delay.

How it works

  1. Write one task per line as “task ; duration ; deadline”, in the order you plan to do them.
  2. Enter the time you start, on the same scale as the deadlines (for example hours from now, or minutes from 9:00).
  3. Read the verdict, the first late task and the table of margins.
  4. Check the advice on deadline order, then copy the summary or the CSV.

What people use it for

  • A day of small jobs

    Check that the eight things you promised for today can all fit before their cut-off times.

  • Projects and handovers

    See which deliverable slips first when one task takes longer than planned.

  • Study and revision plans

    Order revision blocks against exam dates and spot the day you fall behind.

Questions

How are the end times computed?
The tasks run one after the other with no pause: the first starts at your start time, each next one starts when the previous ends, and a task ends at its start plus its duration. The margin is the deadline minus the end; a negative margin is a delay. A task that ends exactly on its deadline is on time.
What does the deadline order do?
It sorts the tasks by deadline, earliest first, keeping your order for equal deadlines, and recomputes the delays. This rule, known as earliest due date or Jackson's rule, gives the smallest possible worst delay for one person doing one task at a time. If that worst delay is still above zero, at least one task is late whatever the order; the rule does not promise the fewest late tasks, so a different order can sometimes leave fewer of them late.
Which unit do the numbers use?
Any, as long as it is the same for the start, the durations and the deadlines: hours, minutes, days. Values are read to six decimals and must be between -1,000,000 and 1,000,000, with at most 500 tasks. Dates and clock times are not read: turn them into numbers first.
What does it not take into account?
Several people working in parallel, breaks, tasks that cannot start before a given time, tasks that depend on each other and tasks you can split. It is a check on a single sequence, not a full scheduler, so treat the result as a first filter.