Availability, unbundled from event types
One place to manage the weekly hours that back every event type — because scheduling logic shouldn't be duplicated across a dozen booking links.
If you've ever tried to shift your Friday hours by an hour, you know the problem. Every event type had its own idea of when you were free, and updating them one-by-one was the kind of chore that made you consider just declining the meeting instead.
So we pulled availability out into its own thing.
Schedules as first-class objects
Availability schedules now live on their own page, separate from any individual event type Manage Availability Schedules. A schedule is just a named set of weekly hours — "Working Hours," "Mornings Only," "Post-lunch Focus Blocks" — that you define once and then point your event types at.
This matters more than it sounds. It means the mental model matches how people actually think about their time: you have a handful of recurring patterns for when you're bookable, and many kinds of meetings that draw from those patterns. Not the other way around.
One edit, everywhere
Because event types reference schedules rather than owning their own hours, changing your Tuesday availability updates every event type using that schedule at once Manage Availability Schedules. Move to a new time zone, take Fridays off, block out a sabbatical — it's one edit, not twelve.
The editor itself loads the weekly grid inline so you can scan Monday-through-Sunday at a glance and adjust without hunting through nested settings Manage Availability Schedules.
What's next
This is the foundation for a few things we've been wanting to build: date-range overrides, team-wide default schedules, and smarter conflict handling when a schedule changes underneath existing bookings. Getting the primitive right first makes the rest tractable. More soon.