The luach-aware calendar: scheduling a life that runs on two clocks

The failure is so routine the community has a whole genre of it: the wedding invitation printed for the night of a fast, the school meeting scheduled for Chol Hamoed, the flight booked home for the second day the family keeps and the airline doesn't. None of these are carelessness — they are what happens when a family's real calendar lives in one system and its scheduling tool lives in another, with a human bridge translating between them under load. The bridge drops things. It always has.

What luach-native means

A calendar built for this community treats the Jewish layer as structural, not decorative:

• Every day wears both dates. The 14th and the yud-daled, together, on every view — because the family's commitments arrive in both currencies: the school ends by the civil grid; the yahrzeit, the bar mitzvah parsha, and the vort all arrive by the luach.
• The Yom Tov topology is load-bearing. The calendar knows what a three-day Yom Tov does to a week — which days cannot host appointments, when the eruv tavshilin reminder belongs, how the erev's afternoon is already spoken for. The block on the grid is not an event; it is terrain.
• Zmanim are grid citizens. Candle-lighting closes the Friday column at the right minute for your location, and the week's planning respects it automatically — feeding the whole Friday-countdown discipline upstream, at the planning layer where erev crunch is actually prevented.
• The recurring Jewish rhythms self-maintain: the omer's count, Rosh Chodesh benching, the fast days, the yahrzeits recurring by the correct calendar — entered once, right forever, including the leap-year wrinkles that break every manual system eventually.

“A frum family's schedule conflicts are rarely two meetings at once. They are one meeting and one mitzvah — and only a calendar that sees both can warn you.”

kolbo.life

The collision detector

The luach-aware calendar's killer feature is the warning at booking time: type the dentist for the 14th and the calendar answers "that's erev Pesach." The family's whole scheduling stack inherits the intelligence — the coordination anchors stop landing on fast days, the seder slots flex around the Yom Tov week automatically, the simcha planning starts from dates that were checked before the hall was called. Institutions need it doubly: the school calendar, the shul's dinner, the kehilla's announcement rhythm all draft against the luach first — and the printed-invitation-on-a-fast-day genre finally dies.

The seasonal planning views earn their own mention: the Tishrei month seen whole (four Yamim Tovim, their erevs, the school's stutter-start), the Nissan runway (Pesach cleaning back-scheduled from bedikas chametz), the summer's three-weeks shading — the year's actual shape, visible, plannable, shared to every family member's device at their tier.

One family, one grid, two clocks

Like the phone book and the postal map, the calendar is household infrastructure: the shared family layer (simchos, school dates, the Yom Tov terrain) visible to all, personal layers per member, the children's tiers seeing what their age needs. On an integrated platform the two-clock intelligence flows everywhere the date matters — the alarm that knows tomorrow is a fast, the reminder that fires before Shabbos instead of during, every app consulting one luach instead of each family member consulting their memory. One calendar, both clocks, zero human bridge — which is what the mainstream grid, built for a world with one clock, structurally cannot offer.

Frequently asked questions