It happens because more than one place can say yes
- Two calendars: the record system holds the book, and a shared phone calendar, a paper diary or the DM inbox holds the rest. A visit booked from Instagram lands in one and not the other, and both say the slot is free.
- The request queue: Priya accepts a request and types it into Tuesday at 2 pm while the same patient, tired of waiting, self-booked 2:15 with another provider.
- Room against provider: the calendar checks that Dana is free and never checks that the laser room is, so two providers book two patients onto one device.
- The overrun: a consult runs twenty minutes long, the next visit starts late, and by 3 pm the room holds two patients who were each booked correctly.
- The phone hold: the front desk pencils a time during a call and the page sells the same slot before the pencil becomes a booking.
- The event block: the party night was agreed in a text thread and never blocked, so the page kept selling the slots.
The one-calendar rule: everything that takes time lives in one place
Every provider, every room, every device and every block goes into the calendar in the record system, and that calendar is the only one that can say yes. Lunch, charting time, the party night, the rep visit and the training afternoon are blocks in it, not notes elsewhere. A booking from any channel, the phone, the website, a DM, a text or the request queue, is written there before anyone tells the patient the slot is theirs. Every other calendar is read-only or deleted. A system that answers the phone writes into the same calendar under the same rules.
Rooms and devices are resources, and each gets its own column
A provider column alone cannot stop the two most common collisions, because what ran out was the room or the laser, not Dana. Give each room and each device its own resource and tie every treatment to the resources it needs. A laser session takes the laser room and the device, a neurotoxin visit, tox from here on, any injection room, a consult a room or a quiet corner. A booking is then refused when any one is taken, and the page offers the next time when all are free.
The morning check takes ten minutes and catches the rest
- At opening, Priya reads the day three times: once by provider for overlaps, once by room, once by device. Any slot with two names is called before 9 am.
- Then the request queue: anything accepted yesterday and not yet in the calendar is placed now or chased now.
- Then the unconfirmed: visits booked over a week ago with no confirmation reply get a text with the time and a one-tap confirm, to patients with texting consent on record. What counts as consent is for counsel.
- Then the overrun risk: consults and first visits that run long sit next to a buffer or a gap, or the provider gets a note.
- The check ends with the count: collisions found, by cause, on a tally that becomes the month's number.
What the system logs, so every collision has a cause
| Log line | What it holds | What it answers |
|---|---|---|
| Booking created | Channel, who or what created it, the timestamp, the provider, the room and the device | Which channel wrote the slot first |
| Booking changed | The old slot, the new slot, who moved it and why | Whether the overrun or the correction was the cause |
| Hold placed and expired | The slot held during a call or a page visit, and when the hold lapsed | Whether the phone and the page fought over one slot |
| Request accepted | Who accepted it, when, and where it was placed | Whether the queue created a second booking for one patient |
| Conflict refused | The resource that was taken and the alternate offered | How many collisions the rule caught before the lobby did |
A worked example, labeled illustrative
Say Tuesday at 2 pm in this illustrative example: Jess self-booked a laser session with Dana on Sunday night. Say on Monday Priya accepted a request for a laser consult and typed it into the same slot with the other provider. With a provider column only, both bookings stand, and at 2 pm two patients need the one laser room. With the room as a resource, the second booking is refused as Priya types it, and the page offers 3 pm. Say the rule was not in place: the morning check, read by room, finds two names on the laser room, and one patient gets a call at 8:45 with 3 pm. Say neither existed: the log shows which booking came first and which channel wrote the second, so the fix is a rule and not a reprimand.
How to count yours this month
- Count the calendars in use today, the phone calendar, the paper diary and the DM inbox included; the target is one.
- Count the share of this month's visits with a room and a device assigned; anything short of all of them is a collision waiting for a busy Tuesday.
- Keep the morning-check tally for thirty days by cause: second calendar, request queue, room or device, overrun, hold, event block. The largest cause is the first fix.
- Pull the change log and count bookings moved on the day they were due; that is the collision count the lobby saw.
What to do next
NorthCore's Fill the calendar solution books every call, text, DM and request into the one calendar you run, under that calendar's resource rules, and logs the channel and time on each booking. It is scoped in writing and covered by the promise on this site: results in 90 days, or we keep working until you have them.
