Scheduling

Problem Context

• The user is arranging time for a meeting, event, availability schedule, class, service window, internal review, reminder, or recurring series.
• The schedule may involve required and optional attendees, rooms, resources, calendars, conferencing, location, agenda, attachments, and reminders.
• Availability can depend on free/busy calendars, hidden calendars, working hours, buffers, minimum notice, maximum bookings, resource capacity, and attendee response.
• Timezone, daylight saving, locale, recurrence expansion, and travel can change what a displayed time means.
• Scheduling may create invitations, reserve calendar time, publish availability, notify people, update a series, or reschedule/cancel existing events.

Selection Rules

• Choose scheduling when users coordinate time across participants, calendars, availability, resources, recurrence, reminders, or invitations.
• Use booking when an invitee or customer reserves an available service, resource, or appointment slot with capacity, confirmation, cancellation, or payment rules.
• Use calendar view when users need to inspect existing scheduled events by spatial placement rather than complete the scheduling workflow.
• Use date picker or time picker for single field entry inside scheduling only when availability and conflict rules are handled elsewhere.
• Use date range picker when selecting a span is the main input, not when attendees, recurrence, reminders, and invitations define the task.
• Use notification center for schedule-related alerts and responses, not as the scheduling editor.
• Expose required attendees, optional attendees, room or resource availability, selected calendar, timezone, duration, recurrence, reminders, and send/save outcome before committing.
• Show conflicts and suggested alternatives when required attendees, rooms, checked calendars, or buffers are unavailable.
• For recurring events, show recurrence pattern, timezone, end condition, exceptions, and edit scope for one occurrence or the whole series.
• Distinguish draft, saved only, invitation sent, pending responses, accepted, declined, tentative, rescheduled, canceled, and failed-send states.

Required States

• Draft event state
• Attendee entry and resolution state
• Availability loading state
• Free/busy conflict state
• Suggested time state
• Room or resource unavailable state
• Timezone selected or changed state
• Recurring series setup state
• Edit one occurrence or full series state
• Reminder and notification setup state
• Save without sending state
• Send invitation state
• Pending attendee response state
• Accepted, declined, or tentative response state
• Reschedule state
• Cancel event state
• Failed send or stale availability state

Interaction Contract

• Changing date, time, duration, attendees, resources, timezone, recurrence, or checked calendars recomputes availability before send.
• Required attendee and resource conflicts block or warn before sending, while optional attendee conflicts are clearly marked as optional.
• Suggested times identify why they are available, which people and rooms are free, and what timezone is displayed.
• Saving to a personal calendar and sending invitations are distinct actions when the platform supports both.
• Recurring events preserve timezone and require users to choose whether edits affect one occurrence, future occurrences, or the full series.
• Rescheduling retains agenda, conferencing, attachments, reminders, attendees, and response history unless the user changes them.
• Cancellation explains whether notifications will be sent and whether rooms, resources, and availability slots are released.
• Notifications and calendar updates deep-link back to the current event state rather than stale draft details.

Implementation Checklist

• Define event fields, attendee roles, room/resource model, availability sources, checked calendars, timezone policy, recurrence rules, reminder rules, save/send semantics, and audit or notification requirements.
• Build availability checks for attendee free/busy, rooms, resources, buffers, working hours, minimum notice, maximum bookings, hidden calendars, and permission-limited calendars.
• Expose date, start time, end time, duration, timezone, recurrence, location, conferencing, calendar selection, reminders, attachments, and description with validation and conflict states.
• Add suggested time logic that names available people/resources and explains why a time is blocked.
• Implement recurrence expansion, exception editing, timezone stability, daylight-saving checks, and series edit scope.
• Support save draft, save without sending, send invitations, reschedule, cancel, remove attendee, change room, and update reminders with clear status messages.
• Test required attendee conflict, optional attendee conflict, room unavailable, hidden calendar, timezone change, recurring series, one-occurrence edit, daylight-saving boundary, stale availability, failed invitation send, mobile, keyboard, and screen reader status updates.

Common Generated-UI Mistakes

• Treating scheduling as only a date field and a time field.
• Hiding attendee or room conflicts until after invitations are sent.
• Sending invitations when users expected to save a draft.
• Changing an entire recurring series when users intended one occurrence.
• Showing times without timezone when attendees are in different regions.
• Ignoring buffers, minimum notice, maximum daily meetings, or checked calendars.
• Treating optional attendee conflicts the same as required attendee conflicts.
• Letting stale availability produce double-booked meetings.

Critique Questions

• Who or what is being scheduled, and which participants or resources are required?
• Which calendars, working hours, buffers, and availability rules are included or hidden?
• What timezone is the user seeing, and will attendees see the same local time?
• Is this a one-time event, recurring series, one occurrence, or availability schedule?
• Does the action save a draft, reserve time, send invitations, publish availability, reschedule, or cancel?
• What happens when availability changes between viewing the schedule and sending it?