Most campaigns communicate twice: the launch announcement and — weeks later, sheepishly — the final total. Between them stretches the silence in which campaigns actually die: the community that heard nothing since Tuesday concludes the drive ended, stalled, or never mattered, and the momentum that launch bought expires unused. Updates are the campaign's heartbeat — the cheap, repeatable act that keeps the drive alive in the community's feeds and heads — and they are the most neglected instrument in the organizer's kit precisely because they feel optional. They are not. A campaign that updates daily raises differently than one that doesn't, and the craft of what to say, when, and how is small enough to learn in one reading.
Why updates move money
The mechanics are specific, not vibes. Updates re-surface the campaign: every post is a fresh appearance in the chats where the community actually lives — the donor who meant to give Tuesday gets her second chance Thursday, and "meant to" is the largest donor segment every campaign has. Updates carry social proof: "412 families in" converts fence-sitters the way no appeal can, because the community's own participation is the argument. Updates manufacture deadline weather: the milestone ("halfway!"), the countdown ("94 numbers left"), the match window's clock — urgency renewed honestly, with news instead of adjectives. And updates train trust: the campaign that reports as it goes reads as the campaign that will report at the end — stewardship demonstrated in real time, which is worth actual dollars from the careful givers who watch before they write.
The rhythm and the anatomy
The cadence by phase: daily during launch week and the final 72 hours, every second or third day through the middle, and always within hours of real news (the match opening, the milestone crossing, the gold-slot story). The anatomy of a working update is three lines: the number ("$61,400 — 48% there"), the story (one concrete beat: the class that finished its team goal, the spin that landed ✦$18, the matcher who just joined), and the ask-shaped close ("the wheel's open — 212 numbers left"). Written chat-first per the cascade craft — two to four forwardable lines, the link riding along — because the update's real distribution is the same seeds who launched. The failure modes are equally patterned: the numberless mood post ("amazing energy out there!"), the guilt update ("we're behind — where is everyone?" — shame reads as failure and failure repels), and the wall of text that buries the number a thumb was scrolling for.
Silence tells the community a campaign is over. An update tells them it's alive. There is no neutral — every day you don't post, the silence posts for you.
The sag-week arsenal
Campaigns breathe — launch surge, middle sag, deadline sprint — and the middle is where the update craft earns its keep, because the sag is when there's "nothing to report" and reporting matters most. The working moves, in escalation order: the story update (no new total needed — the bochur who called forty numbers, the grandmother who scratched from Florida, the team captain's voice note), the milestone manufactured honestly (48% isn't a milestone; "one gift from half" is — find the frame that makes today's number news), the match window's opening (the sag's designed answer: "everything doubled through Thursday" is the strongest mid-campaign update that exists), the reserve reveal (the held-back matcher, the anchor prize, the second game per the catalog's pairing move — plot twists planned at launch, deployed at the dip), and the team race's narration (standings turned into story: "6G took the lead at 9:40 last night" per the leaderboard craft). The discipline underneath: the arsenal gets scheduled during launch planning, never improvised at the panic — the sag is the most predictable event in fundraising, and walking into it armed is the whole difference.
The closing update: this year's last word, next year's first
The final update is the campaign's most-read post and its longest-lived artifact — write it like both. Its jobs: the total, plainly and with its meaning ("$127,400 — 43 campers, every bus full"); the gratitude, collective and complete (every giver, every sharer, every caller inside "this community did this" — the thank-you system's public layer); the accounting where promises were made (the match released, the surplus routed as stated — trust's receipts); and the door left warmly open ("the fund runs year-round" / "see everyone at the siyum"). Then the second act ships later: the impact update — the August camper letter, the dedication photo, the built thing — which lands months after the money and is, quietly, next campaign's true launch. Organizations that close loops publicly inherit their own credibility annually; the ones that vanish after the total teach the community to discount the next launch. And the retro happens the same week: fifteen minutes, the committee, what fired and what fizzled — written down, because next year's checklist is this year's notes.
Should updates ever tag or thank donors by name?
With permission and in the collective register — "the Weiss family's team crossed its goal" celebrates; a list of names with amounts exposes. The update stream is public theater; individual gratitude belongs on the personal rails, per the thank-you ladder.
Frequently asked questions
Who should write and post the updates?
One voice for consistency — usually the organizer or the campaign chair — with the rav’s or rosh yeshiva’s voice saved for the two or three moments that deserve its weight (launch, the match, the close). Rotating authors read as committee; one warm voice reads as a campaign.
Do updates go on the campaign page, the chats, or both?
Both, in that order: the page's update stream is the record (and the platform's update feed shows visitors a living campaign), while the chat version is the distribution. Write once, format twice — the page can carry the fuller paragraph; the chat gets the three-line cut.
How do we update when the news is genuinely bad — a stalled week?
With the story-and-path frame, never the confession: skip the "we're behind" and post the concrete next thing ("the match opens tonight — here's the mountain we're taking this week"). Communities rally to a plan; they retreat from an apology.
Is there such a thing as too many updates?
The ceiling is news, not count: daily updates with real beats (launch week, the final push) never fatigue; the same total reposted with new adjectives fatigues by the second day. If you have news, post; if you don't, make some — that's what the arsenal is for.