Event Countdown Planner

What this generator does

Takes a date and a list of jobs and computes, for each one, the day it has to be finished and the day it has to start. The finish date is the event minus that job's lead time; the start date is the finish minus its duration. The earliest start across every job is when the whole plan has to begin. If any start date is in the past, it says so and by how many days, rather than presenting a compressed timeline that looks achievable and is not.

How to use this tool

1. Choose the date of the event.
2. List what has to happen, one per line: the job, how many days before the day it must be done, and how long it takes.
3. Turn weekends off if the work only happens on weekdays.
4. Press Work backwards, and read when each job has to start.

Understanding the controls

The date itself

The fixed point everything is measured back from. It can be in the past, which is occasionally useful for working out what a plan should have looked like.

What has to happen

One job per line: the name, the number of days before the date by which it must be done, and optionally how long it takes. The lead time is when it must be finished, not when it should start — 'book the venue, 90' means booked and confirmed 90 days out. Duration defaults to a day, which is what most checklist items really are.

Skip weekends

Off by default here, because party and family planning genuinely happens at weekends. Turn it on and durations are counted in working days and nothing is scheduled on a Saturday or Sunday — which typically stretches a five-day job across a full week.

Worked examples

Book the venue, 90, 2

Finished 90 days before the day; starts two days before that.

Send invitations, 45

One day's work, done 45 days out.

A plan that fits

'Everything fits. The first thing has to start on Monday 16 February.'

A plan that does not

'This plan does not fit. 2 tasks would have had to start already.'

Common use cases

• Planning a wedding, a party or a big birthday without discovering the venue lead time too late
• Working out the last sensible day to order something that has to arrive
• Turning a checklist into dates instead of a list of intentions
• Finding out whether a plan is actually deliverable in the time left
• Printing a timeline that other people can follow

How this generator works

It is a backward pass. Each job's finish date is the event date minus its lead time, and its start date is that finish minus its duration, counting the finish day itself so a one-day job starts and finishes together. When weekends are skipped, both steps count working days rather than calendar days and the result is nudged off a weekend — which matters more than it sounds, because five working days back from a Monday is the previous Monday rather than the previous Wednesday, and a plan with a dozen jobs in it accumulates that error until the timeline is a week out. Jobs are then sorted by start date, the earliest of which is when the plan has to begin. Any start date before today marks that job overdue, and the largest overshoot is reported as the shortfall.

Randomness and fairness

Nothing here is random. The same date and the same jobs always produce the same plan, which is what makes it something to print and hand round rather than reroll.

For how randomness is produced across the whole site, see how Generate Random works.

Assumptions this tool makes

• A lead time means the job must be finished that many days before the event, not started then.
• A duration includes the finish day, so a one-day job occupies a single date.

Limitations and good to know

• Jobs are independent. It does not know that the invitations cannot go out before the venue is booked, so it will happily schedule them in the wrong order if the lead times say so — read the finish dates and check the sequence makes sense.
• There is no notion of who does the work. Three jobs scheduled for the same week may be impossible for one person and trivial for five, and nothing here can tell the difference.
• Lead times are your estimates. The arithmetic is exact and the inputs are guesses, which is where the uncertainty in any plan actually lives.
• Public holidays are not skipped, only weekends. A plan spanning Christmas or a bank holiday weekend needs its durations padded by hand.
• It plans; it does not track. Nothing is stored, so it will not remember what you have already done.

Common mistakes

Entering the lead time as when to start

It is when the job must be done. 'Book the venue, 90' means the booking is confirmed 90 days before the day; the duration is what covers the phoning around beforehand.

Leaving weekends on for work-week jobs

Anything involving suppliers, printers or offices runs on weekdays. With weekends counted, a five-day job looks like it fits into a week that contains a Saturday, and it does not.

Ignoring an overdue warning because the event is months away

The warning is about lead times, not about the event. A job needing four months' notice is already late for an event in three, however far away that feels.

Practical tips

• Put the longest lead time in first. It usually decides when the whole plan has to start, and it is the one people forget.
• Pad the lead times of anything that depends on somebody else replying. The arithmetic is exact; suppliers are not.
• Print the plan once it fits. A timeline in a shared place gets followed; one in a browser tab does not.

Troubleshooting

Everything is marked overdue

The date is too close for the lead times given. Either the date has to move or the lead times are longer than they need to be — the shortfall figure tells you exactly how many days you are trying to find.

Two jobs are scheduled in an impossible order

Their lead times say so. The tool places each job independently, so a dependency between them has to be expressed as lead times that respect it — give the later job a shorter lead than the one it depends on.

Privacy and your data

Your dates and task names never leave the browser. Nothing is uploaded, nothing is stored, and nothing is written into the page address — which matters when the plan is for something private. Analytics records only that the tool ran and how many jobs were in the list, never the jobs themselves or the date.

Frequently asked questions

Why plan backwards rather than forwards?

Because the date is the fixed thing and the effort is not. Planning forwards from today produces a list that runs out of road at the end, and you find out last. Planning backwards puts the constraint first: each job lands where it has to land, and if the plan does not fit you know on day one rather than in the final fortnight.

What does 'the plan does not fit' actually mean?

That at least one job's start date is in the past. Given the lead times you entered, it should already have been under way. The shortfall shown is how many days late the earliest of those is, which is the amount of time you need to find — by cutting something, shortening a lead time, or moving the date.

Does it handle dependencies between jobs?

No, and that is a deliberate limit rather than an oversight. Full dependency scheduling needs a task graph and turns a five-minute tool into project management software. Lead times express sequence well enough for a plan of this size: give the dependent job a shorter lead than the one it waits on.

Why does skipping weekends change the dates so much?

Because working days and calendar days diverge quickly. Five working days back from a Monday is the previous Monday — seven calendar days, not five. Over a plan with a dozen jobs that difference compounds into a week or more, which is exactly the kind of error that makes a hand-drawn timeline undeliverable.