The week before a church event is always the same. Someone asks who is bringing tables. Someone else realizes the sign-up sheet stopped getting checked two weeks ago. The coordinator, who has been carrying the whole thing in her head, starts making calls at nine at night. None of this is because the team did not care. It is because the planning had no shape — no list of what had to be true, and by when.
A timeline fixes that, and it is not complicated. You start at the event date and work backward, naming what has to happen at each interval so it stops piling up in the final week. Eight weeks out is a good starting point for most events bigger than a Sunday gathering — long enough to reserve a room, order anything that has a lead time, and recruit help before people's calendars fill up.
Why backward planning works better than a to-do list
A to-do list answers “what do we need to do?” A timeline answers “what do we need to do, and by when, so it does not become an emergency?” The difference sounds small. It is not. A flat list lets every task feel equally urgent, so people default to whatever is loudest that week — usually food and setup — while the things with a real lead time, like reserving a van or confirming a guest speaker, sit untouched until they are suddenly overdue.
Working backward from the event date forces you to ask, for every task, “how long before the event does this actually need to happen?” A task with a two-week lead time gets scheduled two weeks out, not left until the week of because nobody thought about it until then. That is the whole method. It is not software; it is a habit of asking the lead-time question before you start assigning work.
It also changes how the team talks about the event. Instead of a running worry — “did we ever figure out the food?” — everyone can look at the same dated list and see exactly what is settled and what is not. That single change, from ambient anxiety to a specific answer, is most of what a timeline is actually for. The tasks do not get easier. They just stop competing with each other for attention in the same panicked week.
Eight weeks out: decide what this event is
Before anyone reserves anything, settle the basics in one sitting: date, time, location, expected size, and the one sentence that describes what the event is for. That last part is easy to skip and expensive to skip. An event with no stated purpose accumulates scope all the way to the week before, as everyone adds their own idea of what it should include.
This is also the point to name who owns the whole thing. Not a committee — one person. A timeline with two owners quietly becomes a timeline with none, because each person assumes the other is tracking the dates.
Write the budget down here too, even if it is rough. “We have roughly three hundred dollars” is enough to prevent the awkward conversation in week six where two people have each ordered decorations because neither knew the other was handling it. A number, even an approximate one, keeps everyone working from the same plan instead of their own private version of it.
Six weeks out: reserve, recruit, announce
This is the week for anything with a lead time. Reserve the room or the outdoor space if it is not already yours. Put in the order for anything that takes a while to arrive — printed materials, rented equipment, catering that requires notice. Start recruiting volunteers now, while calendars are still open, rather than the week before when everyone already has plans.
If you are announcing the event to the congregation, this is a reasonable week to start. Early enough that people can plan around it, late enough that it is not forgotten by the time it happens. If you are running a headcount through registration, open it now so you have real numbers to plan food and space around instead of a guess.
Recruiting deserves its own moment here. A general announcement — “we need volunteers” — from the front rarely produces enough hands, because it asks nobody in particular. A direct ask to specific people, for a specific role, with a specific time commitment, works far better and costs almost nothing extra. If you already know who tends to show up for this kind of thing, start with them by name before the general announcement ever goes out.
Four weeks out: name every task and its owner
By the halfway point, the vague sense of what needs doing should become a specific list, and every item on it needs a name attached and a date it is due. “Someone needs to handle food” is not a plan; it is a hope. The same discipline that protects a serving team from burnout applies here — clear, bounded ownership is what lets people actually help, and what lets the coordinator see at a glance what is still unclaimed instead of guessing.
This is also a good week to check the registration or RSVP numbers against your plan. If forty people signed up and you planned for twenty-five, better to know now than the morning of.
Four weeks out is also when gaps become visible if you look for them. Walk the list and ask, out loud, what is missing rather than only checking off what is already assigned. A missing setup crew or a missing person to run the sound board is much easier to solve with a month of runway than with four days of it.
Two weeks out: confirm, do not assume
Two weeks out is for confirming, not starting. Every vendor, every volunteer, every reserved space gets a check-in: are we still on? Anything that was supposed to happen by now and has not is a problem to solve today, while there is still time to solve it, not a surprise to discover on setup day.
This is also the week to finalize the actual headcount. Food, seating, and materials all get ordered against a real number now, not a guess from six weeks ago.
If something has slipped — the confirmed volunteer went quiet, the vendor has not responded — two weeks out is still enough time to find a backup without it feeling like an emergency. That is the entire point of building in the buffer this early: a problem discovered now is a phone call; the same problem discovered three days out is a crisis.
The week of: setup, run sheet, and one shared list
The week of the event should be quiet by design — everything with a lead time was handled weeks ago, so this week is setup, a run sheet for the day itself, and a last check that every volunteer knows where and when to show up. If this week feels like a scramble, that is a sign the timeline started too late, not that the team did not work hard enough.
Keep the day-of details — who is coming, who is helping, what still is not handled — in one place the whole team can see. When those three things live together, “are we ready?” is a glance instead of a round of texts to five different people.
The week after: the part most timelines skip
Most event plans end at the event. That is the mistake. A well-run event fills a room with people, some of them new, and what happens in the days after decides whether any of that turns into something lasting. Put follow-up on the timeline before the event happens, not after — who calls the first-time guests, who sends the thank-you note to the volunteers, and by when.
The full approach to that week is worth its own read: closing the loop after a big Sunday. The short version is that a name and a date attached to each follow-up task work exactly the same way they do for the event itself — without them, good intentions quietly expire.
What to do if you are starting late
Sometimes eight weeks is not eight weeks — it is three, because the event got approved late or the calendar slipped. The method still holds; it just compresses. Cut straight to naming the non-negotiables: the room, the headcount, and the volunteers you genuinely cannot run the event without. Everything else — decorations, extras, nice-to-haves — gets triaged or cut. A short timeline done honestly beats a long one that was never actually followed.
SundayBridge keeps a gathering, the people registered for it, and the team assigned to it in one view, so checking “are we ready” is a matter of looking rather than reconciling a spreadsheet, a group text, and a clipboard. It will not send your volunteers a reminder text or manage a public registration page — it is a place to organize the event and the people connected to it, not a messaging or ticketing tool.
If your events currently live across a clipboard, an inbox, and someone's memory, the deeper fix is the same one behind moving off spreadsheets generally: one home for the record, so the timeline has something real to point at instead of a folder no one opens.