A dental booking system should connect an agreed appointment type with the required practitioner, time and room resources, while keeping recall follow-up distinguishable from an actual booking. Start with a schedule defined by the practice’s clinical and administrative owners. Then test shared resources and unavailable repeat dates using fictional appointments before assessing whether the configuration fits the practice.
The clinical team should supply the appointment definitions, appropriate durations and recall decisions used in the brief. The software review can then assess how those inputs are represented and maintained. This keeps scheduling configuration grounded in the practice’s own authorised decisions instead of treating a generic booking label as a clinical instruction.
The original room-and-recall worksheet below uses a hypothetical practice and invented appointment names. Narrow product examples come from Amelia’s service, resource and recurring-appointment documentation, retrieved on 24 October 2026. For the website and connected workflow, see WordPress and business systems.
What should an appointment type specify?
Amelia services represent the appointment types customers can book. Amelia requires a category and at least one assigned employee for each service. Its service documentation provides a product example for representing the agreed appointment catalogue. Keep each fictional appointment’s purpose and owner with the configuration sheet.
Amelia controls online service visibility through Show on website. Decide which appointments the practice wants people to request online and which need an administrative conversation first. Record that decision independently of the service name so a later editor understands why a particular booking option is visible or hidden.
Ask the demonstrator to show how the agreed appointment duration is configured and what time the resulting booking occupies. Include any preparation or turnover requirement supplied by the practice owner in the acceptance brief. Record the observed scheduling result rather than assuming that a display label proves the complete time requirement has been represented.
For the hypothetical practice, use two invented appointment types with different practice-supplied durations. Avoid inserting standard clinical timings into the article or test specification. The useful review compares the configured result with the authorised input for that practice.
How should rooms and equipment affect availability?
Amelia resources can represent rooms and equipment required by appointments. Amelia limits Resources to its Pro and Elite plans. Its resources guide describes the feature and its edition scope. Record the proposed edition before assessing a demonstration that depends on it.
Amelia resource quantity represents simultaneous bookings using the resource. Amelia can share a resource quantity across selected services, employees and locations. These documented options support a concrete capacity test: two practitioners may both be free while the same room or item of equipment is required by both proposed appointments.
Amelia resources are managed in the back end rather than selected by customers. Decide who maintains their assignments and who reviews an unexpected availability block. The person answering a booking enquiry should be able to identify whether the constraint comes from practitioner time, a shared resource or another configured rule.
| Fictional scheduling case | Proposed input | Evidence to inspect |
|---|---|---|
| Ordinary appointment | Agreed type, duration and practitioner | Occupied time and assigned service |
| Shared room | Two requests needing the same resource | Availability under the configured capacity |
| Different room | Alternative resource arrangement | Actual permitted appointment slot |
| Recall follow-up | Authorised recall decision and next owner | Invitation or follow-up record |
| Repeating booking | Agreed booked sequence | Generated dates and changes |
| Unavailable occurrence | Deliberately conflicting sample date | Offered adjustment and review decision |
The table is an original scheduling brief. Populate actual results only after the test configuration has been exercised.
How should recall work differ from repeated appointments?
A recall follow-up can be a task to contact a person about an authorised next step. A booked repeating sequence already contains proposed appointment dates. State which process the practice needs and ask the implementer how each is represented. Keep the decision owner and next action visible when a follow-up has not yet become a confirmed booking.
Amelia recurring appointments create a repeating sequence in one booking flow. Its recurring-appointments guide describes that particular mechanism. Assess it as a scheduling feature against an agreed requirement, rather than assuming it supplies the practice’s complete recall policy or clinical decision process.
Amelia can suggest alternative dates when a recurring occurrence is unavailable. Amelia highlights adjusted dates for customer review. Include that adjustment in the fictional exercise, since a generated alternative may need the practice or customer to assess whether it is suitable for the intended appointment.
Write who reviews an unbooked recall task, an adjusted appointment and a cancelled occurrence. These are proposed operational responsibilities. The acceptance sheet should make it possible for the next administrator to distinguish them without interpreting a notification as evidence of a clinical decision.
Original room-and-recall acceptance exercise
Prepare two fictional practitioners, one shared room and two invented appointment types in a separate test copy. Have the practice owner supply the durations and resource requirements. Record the expected occupied time and relevant assignments before attempting the bookings.
First, create an ordinary appointment and compare the actual time and resource use with the sheet. Then request another appointment that overlaps and needs the same shared room. Inspect the available options and ask the administrator to explain the constraint using the configured resource record. Retain the result and relevant settings.
Next, introduce a sample recall-follow-up task with an explicitly authorised next action. Ask how it remains visible before any appointment is agreed. Record the responsible role and what would establish that the follow-up has become a booking. This identifies the administrative requirement without inventing a built-in clinical recall feature.
Then demonstrate an agreed repeating sequence and deliberately make one occurrence unavailable in the test fixture. Inspect the generated dates, adjustment and review point. Ask another colleague to identify which dates are proposed or booked and what action remains. Retain the explanation alongside the actual records.
Add a practitioner-unavailability case to the fixture and inspect the effect on the proposed appointments. Ask who maintains that availability and how the administrator recognises affected work. Keep the outcome separate from the shared-room result so the cause of each scheduling constraint remains clear.
Finish with the practice owner’s review of the scheduling assumptions and the administrator’s review of the working route. Keep unresolved duration, resource or recall questions with their respective owners. To discuss the booking configuration and evidence still needed, get started with the worksheet and authorised appointment definitions.
Ask the scheduling owner to walk through a proposed change that affects both room and appointment duration. Record which appointment needs review and who will confirm the revised booking before the test is considered resolved.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.