Skip to content

Articles

Why due-date dashboards mislead, and how to plan by do dates

Updated 5 min read By Operators team

A due date is when work must be finished. A do date is when you have to start so it finishes on time. Most dashboards only know due dates, so they stay green until the day before and then turn red. Across several companies, where big deadlines arrive from different directions, planning by do dates is what keeps the red away.

The key points

  • Due dates say when work must be done. Do dates say when work must begin.
  • For short tasks they are the same day. For big ones they are weeks apart.
  • Dashboards built on due dates are calm until it is too late.
  • Invented dates make every dashboard worse.
  • Give big work a start item with its own date.

Two dates, two questions

Due date Do date
Question it answers When must this be finished? When must I start?
Who sets it Usually someone else: a client, a regulator, a board You, from how long the work takes
What it protects The promise The quality of the work
What happens if you ignore it You miss the deadline You hit the deadline badly, late at night

A board pack due on the 3rd of December has a due date of the 3rd. If it takes two days of work plus a day for the finance lead to send numbers, its do date is around the 26th of November. The dashboard, though, only lights up on the 2nd.

Why dashboards lie

They only see the finish line

A list sorted by due date shows you what is due soon. It does not show you what should have started already. A large job and a small job due the same day look identical. You learn the difference the evening before.

They fill with invented dates

When a tool asks for a date on every task, people make one up. End of the week. End of the month. These dates are not commitments, so people learn to ignore them. Then the real deadlines are buried among the invented ones, and the whole dashboard is treated as noise.

They mix urgency with importance

Due-date views put the trivial thing due today above the critical thing due next month. Over time, the urgent trivia wins every morning.

They hide what is blocked on you

A due date says nothing about whether someone is waiting for you to act. A review that blocks a team may have no due date at all. It still matters more than most dated tasks.

How to plan with both

Keep due dates honest

Only give an item a due date when there is a real deadline or commitment. If a client said Friday, the due date is Friday. If nobody said anything, leave it blank. A board that never invents dates is a board you can trust at a glance. Operators follows this rule for items from your tools: no date in the tool means no date on the board.

Give big work a start item

For anything that takes more than a day, add a second item for the start, with its own date:

  • “Start Halden board pack, ask finance for numbers” on the 26th.
  • “Send Halden board pack” on the 3rd.

The first one is the date that matters to you. The second is the promise. Both appear in their own time.

Work back from fixed deadlines

For filings, tax returns and renewals, work back from the deadline with whoever does the work. If your accountant needs your year-end numbers six weeks before the filing, the do date is six weeks earlier, and it should be in your calendar as such. The fixed dates guide shows how to set up both the start and the deadline as repeating dates.

Look ahead every week

Do dates fail when nobody looks ahead. In a weekly review, scan the next four weeks of due dates and ask, for each large one, whether the work has started. The weekly review guide includes this step.

Separate blocked-on-you from dated work

Keep a separate view of what is waiting on you, whatever its date. Most dashboards blend this into “due soon”, which loses it.

Across several companies

When you run one company, its big deadlines are in your head. When you run four, they collide. The 3rd of December board pack for one company lands in the same week as another company’s tax filing and a third company’s insurance renewal. Each due date looks fine on its own. Together they make an impossible week.

Two habits help:

  • One calendar of fixed deadlines for every company, so collisions show up early. The article on the annual calendar lists what belongs in it.
  • Do dates staggered on purpose, so you start one company’s big job early to make room for another’s.

A short test of your own dashboard

Open the view you use most and ask:

  1. How many dates on it are real commitments?
  2. Which large items due in the next month have not started?
  3. What is blocked on me that has no date at all?

If any answer surprises you, your dashboard answers ‘what is due soon’, not ‘what should I start’.

What to do next

Questions people ask

What is a do date?
A do date is the day you need to start a piece of work so it is finished by its due date. For a one-hour task it may be the same day. For a filing that needs weeks of preparation, it is weeks earlier.
Why do dashboards built on due dates mislead?
They show work only when it is close to due, so a big job looks fine until it is too late to do well. They also fill with invented dates, which teaches people to ignore them.
Should every task have a due date?
No. Give a date only when there is a real deadline or commitment. A task with no real date should stay undated, and be reviewed in a weekly look at open work.
How do I track do dates in a tool that only has due dates?
Add a second, earlier item for the start of the work, with its own date, such as starting the year-end pack eight weeks before the filing.

See every company you run on one screen.

Try the demo first: no sign-up, and every screen works on made-up data. You can't connect your own tools to it.

Join the list