About this project

Coordinating an extended family around a single temple visit usually means a long group text, several conflicting calendars, and someone quietly giving up. This tool gathers everyone’s constraints in one private place and helps the family find an option that is genuinely fair — not just convenient for whoever asked first.

The hardest part was never the arithmetic. It was getting eleven relatives to each make an account. So in August 2026 the product was rebuilt around a single idea: only the person arranging the trip signs in. Everybody else opens a link, types their name, and answers. The family group, the member roles, the join codes and the vote all went with it.

• It does not read anything from Church websites.
• It does not sign in to a Church Account, and never asks for those credentials.
• It does not check live appointment availability.
• It does not book anything. The organizer books on the official site.
• It does not verify or record anyone’s temple recommend status.
• It does not use Church logos, names, or imagery in a way that implies endorsement.

1. Phase 1Built

   Accounts, for the people arranging a trip

   Sign in with Google or a one-time email link, revocable sessions, co-organizer invitations, and a per-plan activity log.

2. Phase 2Built

   A plan, and one link

   A trip is the top-level thing. Name it, give it a window of days, send one link. Nobody signs up for anything — the host keeps a private link, and everyone else types a name and says which days work.

3. Phase 3Built

   Temples and the fairness engine

   A dataset of 96 United States temples, a shortlist of up to five per trip, a two-tap “can you get there?” from everyone, and an engine that ranks by how many people can genuinely come rather than by what suits the organizer.

4. Phase 4Built

   Choosing, without a vote

   The answers already say who can come where and when, so the options are ranked from them and an organizer picks one. Anybody a choice would shut out is named on it rather than counted.

5. Phase 5In progress

   Booking handoff and confirmed appointments

   Handoff to the official scheduling site, recording what was booked, and calendar files all work. Reschedule and cancellation workflows are not built.

6. Phase 6Planned

   Production hardening

   Rate limiting that survives a restart, scheduled deletion of expired links, backup verification, an accessibility review, and deleting an organizer account. Deleting a plan and everything on it is already built.