The problem with "Blake teaches Tuesdays and Wednesdays"

It sounds simple until you realize Blake teaches Tuesdays at one location and Wednesdays at another. Update the wrong field and both sessions shift to the same site. A student shows up at the wrong building. Blake drives across town unnecessarily. You spend twenty minutes on the phone sorting it out.

This is not a rare edge case. It is the default reality for any school with more than one site and more than a handful of instructors. The fix is not a better tool—it is a clearer system, one you can build right now with whatever you are currently using.

Why multi-location availability breaks down

There are three distinct failure modes, and most schools are suffering from at least two of them.

1. Availability is tracked per instructor, not per instructor-and-location.
You know that Maria is free on Thursday afternoons. You do not know whether that means she is free at the north campus, the south campus, or both. When someone books her, they pick a location almost at random.

2. Room availability is invisible to the person doing the booking.
An instructor picks a time slot and a room without being able to see whether that room is already occupied. The result is two lessons booked into the same space at the same time—a problem that surfaces only when both students arrive. One music school flagged exactly this: instructors had to choose a room with no way to check whether it was free, and no visibility into the room's schedule for recurring slots across upcoming weeks.

3. Multi-instructor sessions have no clear owner for availability checks.
A lesson that involves two instructors—a lead teacher and an accompanist, for example—requires both to be free at the same location at the same time. Most manual systems check one or the other, not both.

Build an availability matrix before you do anything else

The single most useful thing you can do today is create a simple grid. Rows are instructors. Columns are locations. Each cell contains the days and hours that instructor works at that site.

This takes an afternoon to build and immediately answers the question "who can teach at the south campus on a Tuesday morning?" without a single phone call.

Keep this document somewhere everyone with booking responsibility can see it. A shared spreadsheet, a printed sheet on the front desk, a pinned message in your staff chat—the format matters less than the fact that it exists and is current.

Separate "available" from "available here"

The most common mistake is treating availability as a single dimension. It has two:

• When the instructor can work

• Where they can work at that time

These need to be recorded separately. An instructor who is available Monday 9–5 but only at the east site is not available Monday 9–5 for a student who needs the west site. If your booking process does not capture both dimensions, you will produce conflicts.

Practical fix: When you collect or update instructor availability, always ask for location alongside hours. A simple form works:

"For each location where you teach, list the days and hours you are available there. If your hours differ by location, fill in each one separately."

Send this to every instructor at the start of each term and whenever their schedule changes.

Handle the room-booking problem separately from the instructor-booking problem

These are two different constraints and they need two different checks.

Instructor availability tells you when a person can teach. Room availability tells you when a space is free. A booking is only valid when both are satisfied simultaneously.

If you are managing this manually, keep a separate room calendar for each physical space. Before confirming any in-person lesson, check:

1. Is the instructor free at this location at this time? (instructor availability matrix)

2. Is the room free at this time? (room calendar)

Only when both answers are yes do you confirm the booking.

One DJ academy discovered this the hard way: their system checked instructor availability but not studio availability, which meant double-bookings were only caught when two students arrived for the same room. The fix was to add the room check as a mandatory second step—not a software change, just a process change.

Set a default location for each instructor

Most instructors have a primary site. Capturing that default saves time and reduces errors. When someone is booking a lesson and needs to assign a location, starting from the instructor's usual site is faster and less error-prone than starting from a blank field.

Write each instructor's default location into your availability matrix. When a booking is created without a specified location, the default applies. If the lesson is at a different site, the person booking has to actively override it—which forces a conscious check rather than an accidental assumption.

One conservatory flagged this explicitly: not having a default location per instructor meant extra clicks and occasional errors on every single booking. The workaround is to make the default explicit in your records, even if your current tool does not enforce it automatically.

Multi-instructor sessions need a written protocol

If any of your lessons involve two instructors—a teacher and an accompanist, a lead and an assistant—you need a rule for how availability is checked.

Write it down:

"For any lesson with two instructors, both must be confirmed available at the same location before the booking is created. The person creating the booking is responsible for checking both."

Without a written rule, the check gets done inconsistently. One person checks both; another checks only the lead instructor; a third assumes someone else handled it. The double-booking that results is not a technology failure—it is a process gap.

Review and update availability at fixed intervals

Availability drift is silent. An instructor changes their commute, picks up a second job, or stops coming to one site—and the availability matrix never gets updated. Bookings keep going to a location the instructor no longer covers.

Fix this with a calendar event, not goodwill:

• Start of each term: every instructor resubmits their availability by location.

• Any time an instructor's schedule changes: they notify the administrator within 48 hours, and the matrix is updated the same day.

Make the update process as low-friction as possible. A short form, a reply to an email, a message in a group chat—whatever your team will actually do.

A note on what we built

Managing instructor availability across locations is one of the core problems Noto was designed for. Availability in Noto is tied to specific locations, so a booking can only be offered when an instructor is confirmed available at that particular site. We built it this way because the alternative—tracking availability without location—produces exactly the conflicts described above. If you are at the point where a manual system is no longer keeping up, that is what Noto is for.