The booking review expands a 09:30–10:00 meeting to a protected 09:15–10:15 interval. Its initial 10:00–10:30 request overlaps for 15 minutes. Move the request to 10:15–10:45 and the supplied comparison has no overlap, while the page keeps the result labeled candidate only.
State the calendar and the interval rule
Use fictional one-person calendar C01 for October 13, 2026, in UTC. The review window is 09:00–11:00. Intervals include their start and exclude their end. Under this declared rule, two intervals that only touch at an endpoint have no overlap. Do not silently substitute a different time zone when copying a request.
Calendly's buffer guidance distinguishes a meeting from its larger meeting-and-buffer window. This example uses that concept with its own stated interval rule; it does not reproduce every vendor scheduling policy or connect a calendar. The unlisted calendars and actual authority to book remain unknown, even after the arithmetic is clear.
Expand the meeting once
B01 is confirmed in the fictional ledger from 09:30 to 10:00. Its supplied before buffer is 15 minutes and its after buffer is 15 minutes. Subtract 15 from the meeting start and add 15 to its end: protected time is 09:15–10:15. Meeting duration is 30 minutes; protected duration is 60 minutes.
Keep both durations labeled. Calling the whole protected hour meeting attendance would change what the record says. The local controls let you vary the declared buffers and recompute the interval. Those edits are scenario inputs, not changes to anyone's calendar settings. A later real rule change needs a source reference and another comparison.
Measure the overlap in minutes
Q01 requests 10:00–10:30. The later start of Q01 and B01's protected time is 10:00. The earlier end is 10:15. That shared interval lasts 15 minutes, entirely within the after-buffer. The original meeting ending at 10:00 does not remove the protected transition.
Q02 requests 10:15–10:45. Its start equals the protected end, so overlap is zero under the declared start-inclusive, end-exclusive rule. No request-specific buffer is assumed. If the request needs one, supply it explicitly in the real review rather than treating this result as an unconditional availability promise. The preview's candidate button fills Q02 but does not reserve it.
Keep cancellation and uncertainty in the record
B02 is the 10:30–11:00 historical appointment, canceled under fictional record R02. Its history remains visible but it contributes no occupied time under that supplied state. A cancellation needs its reference; hiding a meeting because its status is inconvenient would produce a misleading comparison.
No overlap is a finding about these inputs, not all possible calendars. Ask the owner to check other calendar coverage, any additional buffer and booking authority. Missing or reversed times produce an unresolved result rather than an open slot. Keep the actual reply, approved interval and booking reference in the maintained calendar workflow; no message or booking is sent by this example.
Copy this prompt
Create a complete original HTML example in US English for this task: Booking dashboard template. Return one self-contained HTML file. Include all styles, data and JavaScript in the file. Use no remote dependencies. Return the working page, not an outline.
Fictional C01, 2026-10-13 UTC, review 09:00–11:00. B01 confirmed 09:30–10:00, buffers 15 before/15 after, protected 09:15–10:15. Q01 request 10:00–10:30 overlaps 15 minutes. Q02 candidate 10:15–10:45 overlaps 0 under half-open intervals and no request-specific buffer. B02 canceled 10:30–11:00 with R02, retained history not occupied.
Provide labeled start/end time inputs, nonnegative whole-minute before/after buffer inputs, a Check overlap button and Q01/Q02 preset buttons. Recompute protected start/end, meeting duration, protected duration and actual overlap minutes. Draw a responsive labeled timeline and keep its text equivalent. Reject missing, reversed or out-of-window requests and invalid buffers with an unresolved result. Generate an unsent calendar-owner question mentioning other coverage and authority. Do not call zero overlap confirmed availability. Preserve cancellation evidence. Use only local type-button click handlers, with a reset to the original Q01 case.
Use a page design suited to this particular task, readable text at least 16 px, generous spacing, visible keyboard focus and explicit labels. At 360 px, stack the content without page-level horizontal scrolling. Use type="button" click handlers for actions. Keep source facts and sample results distinct from actual observations. Leave unknown details visible rather than inventing them. Controls update only this temporary page; distinguish local changes from actual records. Provide concise task-specific feedback and a reset that clears entered answers and stale results.
Use the result
Show the owner both Q01’s 15-minute conflict and Q02’s boundary comparison so the proposed change has a clear reason. You can view the prepared timeline and unsent review wording in NOS before that discussion. Reserve time only through the actual booking process after the owner resolves the remaining calendar and buffer questions.