Every mosad sits on an inventory it rarely catalogs: its honors. The day of learning, the week of the kollel, the shiur's month, the beis medrash's lights for Elul, the seforim shelf, the daf on a yahrzeit — units of the institution's actual Torah life that families will fund, gratefully and repeatedly, when they are offered as dedications. The dedication program is the discipline of running that inventory like the asset it is: a published menu, honest prices, flawless delivery, and the calendar-driven flows (yahrzeits above all) that make it the steadiest revenue engine most Torah institutions will ever own — steadier than campaigns, because it monetizes memory and love, which do not have fundraising seasons.
The menu architecture
A working dedication menu is built on three principles. Units of real life: every menu item corresponds to something the institution actually does — a day of learning at a kollel that learns, a shiur at a shul that gives it. Invented units ("platinum circle of light") read as pricing theater; real units carry their own dignity. The full ladder: from the anchor dedications (the year of learning, the beis medrash annually, the building's naming tiers) through the workhorse middle (day/week/month of learning, the shiur series, the daf) to the participation floor (a sefer, a siddur, the coat room's mezuzah) — every family in the community should find a rung it can reach, because breadth is the program's growth engine and its chinuch. And published prices: the menu with numbers, visible on the campaign page and the office wall — dedications negotiated in whispers stay rare; dedications priced in daylight become customs. The pricing anchor is honesty: the day of learning priced near the day's real cost ("the kollel's day costs $840; the day's dedication is $1,000") gives every number a foundation nobody can argue with.
The yahrzeit engine
The program's steadiest flow — and its most sacred service — is the yahrzeit dedication: the parent's day carried in learning, annually, at the place the family trusts. Building the engine: the yahrzeit ledger (every dedication's date recorded permanently — this is decades-long data, guard it institutionally per the same care as the kiddush perpetuities), the reminder rhythm (the note three weeks ahead: "Reb Yaakov, your father's yahrzeit falls on the 14th of Kislev — the day of learning is available, as you dedicated last year" — gratitude-first, service-toned, and the single highest-converting message the office sends all year), and the perpetual tier (the endowed yahrzeit: one gift that dedicates the day permanently — the program's anchor product, beloved by estate-planning conversations and by children settling a parent's affairs who want one thing that never lapses). A mosad ten years into a well-run yahrzeit engine has hundreds of standing annual dedications arriving without a single ask — the closest thing to endowment income a community institution can build without an endowment.
A dedication program is a promise ledger: every honor sold is a commitment to remember — and the institution that remembers impeccably for twenty years can fund itself on trust alone.
Delivery: the program's entire reputation
Dedication programs live and die on one operational truth: the honor delivered is the product, and any failure of delivery is total. The delivery standard: the name right (spelled, pronounced, announced correctly — captured once at purchase in the family's own rendering), the moment real (the day-of-learning dedication announced at that morning's seder, the family notified "the kollel began today's learning l'zecher nishmas your father"), the record visible (the dedication board — physical or the campaign page's rolling honor roll — where the family can see their commitment standing), and the anniversary honored (the perpetual dedications recurring without the family ever needing to check). The platform rails matter here precisely because volunteer memory fails at exactly these stakes: the dedication calendar that fires the notifications, the ledger that never forgets a perpetuity, the update stream that shows the family their day arriving — infrastructure as kavod. One mangled name costs ten years of program reputation; one decade of flawless delivery makes the program the community's default way to remember.
Dedications inside campaigns
The standing program and the campaign layer feed each other by design. Campaign ladders borrow the menu: the building fund's naming tiers, the siyum's masechta honors, the annual campaign's day-of-learning gifts — all draw from one dedication architecture, priced consistently so the community never sees the same honor at two prices. Campaigns seed the standing program: the family that took a campaign dedication converts naturally to the annual yahrzeit flow ("would you like your father's day held every year?"), which is how campaign spikes become permanent revenue. And the simcha flow balances the yahrzeit flow: dedications in honor — the bar mitzvah boy's first daf, the anniversary's week of learning, the new partnership's opening month — keep the program's emotional register full-spectrum, and give the community a giving language for joy that most mosdos only offer for grief.
What belongs on a dedication board versus the campaign page?
The board carries the permanent tiers — the perpetuities, the anchor dedications, the named spaces — while the page's rolling honor roll carries the year's flow. Both are delivery surfaces, and the rule is the same for each: current, correct, and beautiful, or the honor economy notices.
Frequently asked questions
How do we price honors without seeming to sell mitzvos?
By anchoring to the learning's real cost and framing the gift as carrying it — the family funds the day; the zechus attaches to what they funded. The tradition of dedicated learning is ancient and universal; discomfort almost always traces to invented units or negotiated prices, both of which the published-menu architecture eliminates.
What happens when two families want the same date?
The yahrzeit ledger's standing dedications hold their dates permanently; open dates go to the first commitment, with shared dedications (the day carried by two families) offered gladly — learning, unlike a kiddush, divides gracefully. The visible calendar prevents most collisions; the office's warmth handles the rest.
Should dedication revenue be restricted or general?
General by default, stated plainly ("dedications support the kollel's learning") — restriction bookkeeping at the day-of-learning scale creates cost without meaning. The exceptions are the anchor tiers, where a family endowing something specific deserves specific accounting.
How does a brand-new mosad start a dedication program?
With the menu published from day one and the first honors seeded by the founding families — the founders' dedications establish both the prices and the custom. A program begun at the founding grows with the institution; one bolted on at year ten fights a decade of informal habits.