A countdown won't keep your deadline. Checkpoints will

A countdown is very good at one thing. It tells you, without rounding and without mercy, how many days are left. "30 days" is harder to argue with than "about a month".

What it cannot tell you is whether 30 days is enough. The number goes down by one every day whether you did the work or not. A countdown measures time, and time passes at the same rate for the person who is ahead and the person who has not started.

That gap is where deadlines get missed. This post is about closing it with checkpoints.

Time left is not pace

Take a thesis due in 120 days. On day 60 the countdown says "60 days left". That is true, and useless. The useful questions are different: is the literature review done, is the data collected, is there a draft of chapter two?

With only a countdown, you answer those questions in your head, whenever you feel like it, and you grade yourself kindly. The usual pattern follows:

• For the first two thirds, the number looks large and nothing feels urgent.
• Somewhere in the last third, the number looks small and the remaining work looks large.
• You find out you are behind at the point where there is the least room to do anything about it.

The countdown did its job the whole time. It was never asked the right question.

What a checkpoint is

A checkpoint is a date before the deadline with a concrete result attached. "Draft done by 1 December." "Three practice tests done by the end of February." "Mock exam sat by week six."

On that date, you answer one question: are you on track? There are three possible answers.

Answer	What it means	What to do
Ahead	The result was done before the date.	Nothing. Don't spend the slack yet.
On track	The result is done, or will be today.	Nothing. Carry on.
Behind	The result is not done.	Change something today.

That is the whole method. It works because it replaces a vague, continuous worry ("am I doing enough?") with a small number of dated yes-or-no moments. Between checkpoints you can stop asking and do the work.

Note what it leaves out. There is no percentage complete, no daily streak and no score. Percentages invite false precision ("I'm 70% done" usually means "I've done the easy 70%"). Daily check-ins turn into a chore you click through. Three honest answers across three months tell you more.

How many checkpoints to set

Fewer than you think.

• Under two weeks: one, around the middle, or none.
• One to three months: two to four.
• Longer than that: roughly one a month.

Every checkpoint is an interruption. Set ten and you will start answering "On track" on reflex to make them go away. Set three and each one carries weight.

Where to put them

Spacing them evenly is a fine default. Two adjustments make it better.

Put the first one early. The first checkpoint should come sooner than feels necessary, about a fifth of the way in. Its job is to prove that you have started. If you are behind at the first checkpoint, you have lost a fifth of the time and still have four fifths to recover. If your first checkpoint is at the halfway mark, the same discovery costs you half.

Put the last one before the end, not at it. Leave real room between the final checkpoint and the deadline. Things go wrong late: a reviewer is slow, a file is corrupted, you get a cold. A last checkpoint that sits a few days before the deadline is a rehearsal for the deadline itself.

Name each one after a result. "Checkpoint 2" tells you nothing on the day. "Chapters 1 to 3 drafted" can be answered in two seconds, and you cannot fool yourself about it. If you cannot say what should be finished by a date, that date is not a checkpoint yet.

What to do after a "Behind"

A Behind answer is information. It is not a verdict on you. Its entire value is that it arrives while there is still time to act.

So act that day. You have three levers:

1. Cut scope. Decide what the deadline can survive without. This is usually the right lever and the one people reach for last.
2. Add time before the next checkpoint. Block specific hours in the calendar. "Work harder" does not count.
3. Move the date. If the first two will not close the gap, the deadline is wrong. Change it now. (More on this below.)

The one response that never works is answering Behind and changing nothing. If you were behind at this pace, you will be further behind at the next checkpoint at the same pace.

It helps if the Behind answer stays where you can see it until the next checkpoint. Ahead and On track are the normal state and need no marker. Behind should follow you around a little.

Moving the date versus making it

When the countdown reaches zero, there are only two honest outcomes: you made it, or the date moves.

Many countdown apps handle zero badly. Some start counting up ("3 days ago"), which turns a deadline into a growing number you learn to ignore. Others stop silently. Neither asks what happened.

Moving a deadline is not failure, with two conditions.

• Move it on purpose. Pick a new date you believe, and say it out loud to whoever is waiting for the work. A date that drifts is different from a date that was moved.
• Keep the record. Write down the old date and the new one. One move is a correction. Three moves on one project is a pattern, and it tells you something about how you estimate.

The best time to move a date is at a checkpoint, when the evidence first appears. The worst time is the day after the deadline.

A worked example in Doom Count

Doom Count for iPhone is a countdown app built around this method. Here is how the ideas above map onto it.

Setting checkpoints. When you create a countdown, you choose how many checkpoints you want: none, one to five, or monthly for longer countdowns. The app spaces them evenly and shows the gap (for example "2 checkpoints · every 23 days"). You can then rename each one and change its date, which is how you move the first one earlier.

Being asked. On a checkpoint day the app asks "Are you on track?" with three answers: Ahead, On track and Behind. The question arrives as a notification you can answer from the banner, on the medium and large Home Screen widgets, and inside the app. There is one notification per checkpoint day. You can also answer on any other day from the countdown's screen if something changes.

Living with a Behind. A Behind answer stays visible on your widgets and on the daily wallpaper until the next checkpoint asks again. It is shown in amber, never red. Ahead and On track show for the rest of that day and then clear.

Reaching zero. On the deadline day the number stops at 0 and the app asks "Did you make it?" with two buttons: Made it and Move the date. Moving the date keeps a record on the countdown (how many times it moved, and by how many days), and the checkpoints you have not reached yet shift to fit the new deadline. A countdown you made stays on your home list as a record.

Checkpoints and check-ins are in the free version, which allows two active countdowns.

Start with one deadline

Pick the deadline that worries you most. Give it three checkpoints: one early, one in the middle, one a little before the end. Name each after a result you could show someone.

Then put the countdown somewhere you cannot avoid it. A Home Screen or Lock Screen widget takes a minute to add. When the first checkpoint arrives, answer honestly. That answer is worth more than the number.

Questions