Divine Charles · Fullstack Product EngineerLoading
000%
Getting things ready…

(W/02 · F/02) · Case study

Availability blocks

Set when you are free as named blocks you can edit, copy, and reuse for different meeting types.

01

The problem

People’s free time was hard to set up. One flat schedule broke when someone had different hours for different meeting types, or needed a default week they could tweak. Booking showed wrong times at the edges, so people stopped trusting the calendar.

02

The story

Booking only works when free time is accurate. Early Meetwith stored availability as one flat schedule. That was not enough for real calendars. Named blocks let people describe how they actually work: a default week, copies for next month, and different windows for different kinds of meetings.

03

What changed

Users add and edit free-time blocks, mark a default, and copy a block when next month is almost the same. Booking reads those blocks instead of guessing. Groups use the same idea for each member’s hours.

04

How it was built

Availability was rebuilt as something people maintain on purpose, not a single setting buried in the product. The same blocks feed personal booking and group scheduling so free time stays one idea everywhere instead of two systems that drift apart.

05

Outcome

  • People can maintain free time without one flat schedule.
  • Meeting types can use the right hours.
  • Groups reuse the same availability idea instead of a second system.