Campaigns are won before they launch — the anchor recruited, the seeds armed, the page polished, the rails tested — and lost in the same window, silently, by whatever wasn't ready when the link went out. The launch checklist exists because campaign-eve is the worst possible time to discover the missing piece: the goal nobody sanity-checked, the share image that renders as a gray box, the thank-you flow nobody wrote. This is the complete list, organized by the week it belongs to, ending in the launch-day run sheet — the difference between a campaign that opens with a bang and one that clears its throat for a week.
Two weeks out: the structural pieces
The load-bearing items with real lead time. The goal, sanity-checked: mapped to a real budget line, sized against the honest reach math (warm list × realistic average — the arithmetic in the copy guide done on paper), and shaped for the format (the wheel's tier per the wheel mechanics, the unit ladder for flat drives). The anchor and match, closed: the recruitment conversations finished, terms in writing, the announcement language agreed — a campaign launching without its anchor is launching at zero, which is a choice. The format decided: wheel, flat, auction, teams, or the layered combination — decided by genre per the placement rules, not by last year's habit. The date placed: clear of the community's calendar collisions (the other mosad's dinner, the three-day Yom Tov, the school play) — one conversation with the community's other organizers per the coordination courtesy prevents the season's classic fratricide. And the team layer, if running: captains recruited and teams seeded per the team guide — two weeks is captain-recruitment's minimum runway.
One week out: the surfaces
The visible campaign, assembled and tested. The page, through its edit passes: the full copy checklist run — headline tested, story in three blocks, tiers labeled, the trust furniture (fee line, organizer name, pledge-mode sentence, rules page where games ride) in place. The share layer, verified on a real phone: the link previewed in an actual chat (the preview card is the cascade's billboard — a broken image or a truncated title costs real percentage), the share texts drafted for the seeds, and the campaign's short link clean. The seed list, armed: fifteen to thirty placements mapped, each seed asked personally with their group named and their text ready — the cascade's entire first hour is prepared this week. The rails, test-fired: a real test pledge through the actual flow (the confirmation, the instant thank-you, the receipt — experienced as a donor, on a phone), the ledger checked, and the update-posting flow rehearsed once. And the launch communications drafted: the announcement for each channel (shul, email, chats — native to each), the rav's or rosh yeshiva's voice note recorded if using, and the first update's skeleton pre-written (you know the launch story before it happens; write it now, fill numbers later).
Launch readiness has a simple test: could a stranger give successfully, and could your busiest seed share successfully, at 8:01 — with nobody from the committee awake? If yes, you're ready. If it needs a human hovering, it isn't.
Launch day: the run sheet
The day itself, scripted hour by hour. Before the public hour: the inner circle gives — board, committee, staff, family — so the page opens with momentum, never zero (the first thirty gifts are social proof for the next three hundred, and they are manufactured, not hoped for). The anchor posts: the lead gift announced as the campaign's opening story ("R' ___ has opened our campaign"). The public hour (evening, per the cascade's clock): seeds fire in their staggered waves, the institutional channels post, and the organizer's job becomes watching and clearing — the first hour's only operational duty is unblocking (the seed who forgot, the link question, the payment hiccup escalated immediately). Hour three: the first micro-update where the launch went well ("$14,000 in three hours — thank you") — the same-night update converts the evening's watchers per the updates rhythm. And before sleep: the day-two plan confirmed — the held-back seeds, tomorrow's channel, the first full update's numbers slot — because launch is a two-day event wearing a one-day name.
The first 72 hours: protecting the open
The window that decides the campaign's slope. Watch the three numbers: total (obviously), participation count (the health metric — 90 gifts at $22,000 beats 30 at $24,000 for what week two will do), and share-driven arrivals (the cascade's pulse — if the second ring is dead, fix the message, not the cause). Keep the update drumbeat: day one's night note, day two's full update, day three's milestone or story — the campaign teaches the community its rhythm in the first three days, and silence teaches them to stop checking. Deploy nothing early: the match window, the reserve seeds, the team race's narration — the mid-campaign arsenal stays holstered while the launch's own energy runs; the classic error is spending week two's moves on day two's excitement. And log everything for the retro: what fired when, which seeds carried, where the friction was — the fifteen-minute post-campaign debrief is only as good as the notes taken while it happened, and next year's checklist is this year's annotated.
Frequently asked questions
How long should the full campaign run after launch?
Genre-dependent: wheel drives run hottest at seven to fourteen days, flat community campaigns at two to three weeks, auctions on their two-week arc — with the universal rule that the end must be real. Pick the window at checklist time and honor it; extensions teach the community that deadlines here are decoration.
What's the single most-skipped checklist item?
The real-phone test pledge — organizers polish the page for days and never once give through it on a phone. Half of all launch-day fire drills (the confusing confirmation, the broken preview, the missing thank-you) would have been caught by one $18 test the week before.
Should we soft-launch to a small group first?
The inner-circle giving hour IS the soft launch — it tests the rails with friendly traffic and banks the opening momentum in one move. A separate multi-day soft launch mostly leaks the campaign's news and spends its freshness; the compressed version gives you both benefits without the cost.
What if launch day lands flat despite the checklist?
Diagnose by the three numbers before touching anything: dead cascade with good conversion means a seeding problem (re-arm, re-ask, second wave tonight); traffic without gifts means a page problem (re-run the copy passes, check the flow); neither means the calendar or the cause's framing — and the honest move is the 48-hour regroup with the committee, not louder repetition of what didn't land.