An appointment request is a small event with a surprising number of moving parts. Someone has to receive it, check what is missing, find a slot, confirm it in writing and make sure the right department is ready. In many orthopaedic hospitals that sequence lives in the habits of one scheduler. Below, in eight numbered stages, is a way to convert that habit into a hospital appointment request runbook that any trained colleague can use. It addresses administration only; it does not cover clinical triage, advice or decisions, which remain with medical staff.
Step 1: Define what the runbook covers
Write one sentence stating the start and end of the routine. For example: “From the moment a request arrives by any channel until the patient receives written confirmation and the department’s schedule is updated.” A clear boundary prevents the document from sprawling into billing, records or clinical queries, each of which deserves its own page. Add a second sentence naming what is out of scope, such as medical questions and urgent cases, with the route staff should follow for them.
Step 2: List every way a request can arrive
Walk the desk and note each channel: phone, email, web form, messaging app, referral letter, walk-in. For each, record who monitors it, at what times, and who covers when that person is away. Gaps appear immediately. A shared inbox that no one owns after five o’clock is a common one, and so is a web form that sends to a single person’s address. Replace personal addresses with a role-based mailbox wherever you can.
Step 3: Write the intake record
Decide the minimum set of details the scheduler needs, and print it as a form or template. Typical administrative fields include the requester’s name, a preferred way to be contacted, the department or specialty requested, preferred dates, language, and any accessibility needs for the visit. Mark which fields are mandatory. Do not ask for clinical narrative at this stage; that belongs in the consultation. Having a fixed template means every request is recorded identically, which makes covering for a colleague easy.
Step 4: Set the response standard
Agree on one acknowledgement time and write it down. Staff should say the same thing to every caller, and the written confirmation should repeat it. If the desk cannot reliably meet a promise, shorten the promise rather than missing it. A modest commitment that is met every time builds more trust than an ambitious one that is met half the time.
Step 5: Describe the scheduling routine
- Open the department calendar and check availability for the requested period.
- Offer the earliest suitable options, usually two or three, in writing.
- Hold the chosen slot provisionally and note the expiry of the hold.
- Send the confirmation containing date, time, location, the name of the contact person and a short list of documents the hospital asks patients to bring.
- Update the calendar and mark the intake record as confirmed.
Each line should name who does it and which system they use. If two systems are involved, add a reminder about which one is the source of truth.
Step 6: Add a reminder and no-show routine
Many delays begin with a missed visit that nobody followed up. Specify when reminders are sent, by which channel and who handles replies. Include the polite wording used when rescheduling. Define how a cancellation is recorded and how the freed slot is offered to someone else, so the practice is the same on every shift.
Step 7: Cover the international and out-of-town requester
Requests from far away often need extra coordination: time zones, travel documents the hospital asks to see, and arrival planning. Add a short sub-section with a different acknowledgement template and the name of the person who handles it. Staff can point such families to general reading on the topic, for example the walkthrough on how to approach choosing an orthopaedic hospital for long-standing hip trouble and the overview for patients coming from overseas for hip care, while making clear that these are background articles and that decisions are made with the treating team.
Step 8: Test, then keep it alive
Give the draft to a colleague who has never scheduled in your department and ask them to process three sample requests using only the page. Note every hesitation and fix the wording. After launch, set a quarterly review, name the owner and keep a change log at the bottom. Technology teams do the same with their operating procedures; TheDataOps.org is one place where data engineers write about keeping routine pipeline work consistent, and the discipline carries over neatly to a scheduling desk.
Checklist for a finished runbook
- States where the routine starts and ends.
- Lists every channel, its owner and its cover.
- Includes a standard intake template with mandatory fields.
- Gives a single, realistic response time.
- Describes scheduling, confirmation, reminders and cancellations.
- Draws a firm line around clinical questions.
- Carries a date, an owner and a change log.
A note on tone
Professional does not have to mean cold. Include two or three sentence examples for the most common situations, such as confirming a date, explaining that a requested slot is unavailable, or passing a question to a clinician. Staff are free to adjust them, but a starting point stops people from searching for words while a patient waits on the line.
When the runbook is done, the real measure is quiet: the desk handles a week without anyone asking “who normally does this?” That is the signal that the knowledge has moved from one scheduler’s head into the department’s shared toolkit.
