Community class bookings — Business Assumptions

Fictional public example. Every proposal, scenario, rationale and confidence figure is illustrative; none represents a real stakeholder decision.

Last Updated: 2026-10-13

Status: DRAFT — Pending business validation

Document Purpose: These are the proposed business rules for community-class booking. A project using this register would proceed on them while stakeholders confirm or correct anything that is wrong.

Related requirements: Full PRD. This public example does not include a technical design.

---

Waiting-List Assumptions

RULE-001. Should waiting-list invitations be managed by staff?

Assumption: Staff choose whom to invite when a place opens. Nobody on the waiting list is enrolled automatically, and joining the list never guarantees a place.

Evidence and Reasoning: In the fictional scenario, staff already manage class attendance and invitations. Keeping that responsibility with them avoids introducing an unconfirmed queue policy. Staff may need to consider accessibility needs or whether someone can attend at short notice.

Automatic first-in-line invitations would be a different business policy, rather than just another way to send the same message.

Example: The gardening class is full. A resident joins its waiting list. When someone cancels, staff decide whom to invite; the waiting resident does not yet have a reservation.

Confirm or Correct:

• Correct as stated
• Wrong — correct answer: _______________

Confidence: 70% | Impact if Wrong: 🟡 MEDIUM — An automatic queue would change the invitation workflow and what residents are promised.

---

Reminder Assumptions

NOTIF-001. Should residents get a reminder 24 hours before class?

Assumption: Send one email reminder, 24 hours before the class. Skip it for bookings made less than 24 hours before the start and for bookings canceled before the reminder is due. The booking confirmation email is sent separately.

Evidence and Reasoning: The fictional scenario aims to reduce missed classes but establishes no reminder schedule. One day’s notice gives residents time to change plans without repeated messages. A different interval or several reminders would be a different policy.

Example: For the watercolor class starting Tuesday at 6:00 PM, an existing booking receives its reminder Monday at 6:00 PM. A booking made Tuesday morning receives its confirmation, but no reminder.

Confirm or Correct:

• Correct as stated
• Wrong — correct answer: _______________

Confidence: 75% | Impact if Wrong: 🟢 LOW — The reminder schedule or number of messages changes.

---

Cancellation Assumptions

RULE-002. Can a resident cancel until the class starts?

Assumption: Allow cancellation before the class’s start time. At or after that time, remove the cancellation action and decline cancellation. Confirmation releases the place immediately; staff manage any waiting-list invitation under RULE-001.

Evidence and Reasoning: The fictional scenario calls for self-service cancellation but establishes no cutoff. Allowing late changes keeps residents from needing staff help. A 24-hour cutoff would give staff more notice, but would shift late cancellations back to them.

Example: A resident can cancel the watercolor booking before Tuesday at 6:00 PM. At 6:00 PM, self-service cancellation is closed. Canceling earlier immediately makes one place available.

Confirm or Correct:

• Correct as stated
• Wrong — correct answer: _______________

Confidence: 80% | Impact if Wrong: 🟢 LOW — The cancellation eligibility rule and its explanation change.

---

Validated Assumptions

No assumptions have been validated in this fictional example.

ID	Assumption	Validated	Notes