The appointment book that refuses to double-book.

The honest frame

What this is, and what it is not.

A general-purpose scheduling tool treats every calendar the same: a slot, a booker, a confirmation email. A K-12 building is not that simple. A conference booking is not just an appointment — it is an appointment that only a specific set of adults, the child’s recorded guardians, may make. A room booking is not just an appointment either — it is a shared, finite resource that two different staff members will absolutely try to claim for the same evening at some point in the school year. So this product was built around two refusals before it was built around a calendar grid.

It is a booking engine with a family wall and an overlap check built in, not bolted on. The guardian relationship check and the double-booking check are not validation added at the edge of a generic scheduler; they are the function that decides whether a booking happens at all, and every surface on this page runs through them.

It is not a full replacement for a general scheduling tool. There is no self-serve signup, no mobile app, and no broad third-party integration catalog today. If your school’s need is “book any kind of meeting with anyone, synced everywhere,” a mature consumer scheduling tool is still the better fit, and we would rather say that than oversell.

And it is early access. The conference and facility booking surfaces below are wired to real routes over real tables. Several named surfaces — counselor/nurse booking, a waitlist, two-way sync, and live SMS/voice — are not built. We would rather you read that here than infer it from a quiet quarter after signing.

The one guarantee this whole product turns on

A slot can be taken at most once. That sentence is the product.

Double-booking is the failure mode that makes a school stop trusting a scheduling tool entirely — one bad Tuesday where two families show up for the same conference slot, or two teams show up for the same gym, and the front office goes back to a paper sign-up sheet for the rest of the year. So the check runs at the engine, not at the UI, and it runs the same way for a conference slot and a bookable resource.

Illustration with round example times. The rule is exact: two windows conflict only when one starts strictly before the other ends AND the other starts strictly before the first ends. A window that starts exactly when another ends does not conflict — which is what makes back-to-back bookings of the same room, all day, actually work.

Both booking paths — a teacher’s conference slot and a school’s bookable resource — ultimately ask the same question: does the requested window overlap any window that is already live? A cancelled or released booking frees its window; a merely-held or pending one still blocks. And a malformed time window (a start that is not strictly before its end, or an unparsable instant) fails closed, treated as a conflict rather than let through on a guess. The permissive failure direction — “when in doubt, allow it” — is never the one this engine takes.

Consent, per channel, not per family

Opting into email is not opting into a text message.

It is tempting to treat “this family said yes to reminders” as one flag. It is not one flag, and the law does not treat it as one either: automated text messages and automated phone calls require their own prior, affirmative opt-in, distinct from and stricter than an email communications consent. A family who agreed to email updates has not thereby agreed to an automated text.

The reminder planner enforces that distinction structurally. Each channel — email, SMS, voice — is checked against its own consent purpose from the family’s granted set. A channel with its opt-in present resolves to queued, not sent; a channel without it resolves to suppressed, no consent and is never queued at all, regardless of how convenient sending it anyway would be.

And we are precise about the other half of that sentence: nothing is actually transmitted by this planner. It decides whether a reminder is allowed to be queued for a channel. The real delivery — an email actually leaving an outbox, a text actually reaching a phone — runs through a separate, key-gated transport layer that today has no carrier wired underneath it. A queued reminder is an honest intention to send, not proof that anyone received anything.

Data, walls, and what we hold

Scheduling data, not a student record.

A conference booking or a room booking references a student, a guardian, or a requester by an opaque reference only — there is no name, no contact detail, and no directory field carried in the booking record itself. That is a deliberate design choice, not an accident of a minimal schema: a booking is scheduling data, an appointment fact, and it is kept structurally separate from a student’s census and academic record rather than folded into it.

Access is layered. Publishing a conference slot or requesting a facility booking is staff-only, checked before any booking logic runs. Booking a conference slot is a guardian act, gated by the family wall described above — a non-guardian is denied by the engine itself, not merely hidden from a page. A guardian’s own view of the slot board is a read-only availability projection: free or taken, and their own bookings, never another family’s identity.

Money, where it appears at all, is honest-off everywhere on this product. The deposit quote always returns a status of queued_not_charged with zero cents actually charged, because there is no payment provider wired behind either booking surface. Reminders follow the same honesty: a queued reminder means a channel’s consent check passed, not that a message was delivered, because no carrier is wired underneath any channel today.

To be exact rather than flattering: this is not a claim that no sensitive data exists here. A booking still touches a real relationship between a real family and a real school. The honest claim is narrower — the record itself carries opaque references, the write path is gated twice (staff check and, on the write, an engine re-check), and nothing here is public.