Task Flow Mickael Rutembya · Flow Atlas

Office Hours Scheduling

Atomic steps for an owner to create and manage office hours slots for prospects and clients.

Task intent

What the user is trying to do

« Define available office hours slots so visitors can book time. »

Entry points

Element	Destination
Owner nav Office Hours	`/owner/office-hours/`
Dashboard Schedule shortcut	`/owner/office-hours/`
Direct URL Authenticated owner	`/owner/office-hours/`

Flow

Adjacent routes — click a node to open it.taskflow

flowchart TD A["Start: owner opens office hours"] --> B["/owner/office-hours/"] B --> C["Review existing slots"] C --> D{"Action?"} D -->|Create| E["Add slot"] D -->|Edit| F["Edit slot"] D -->|Cancel| G["Cancel slot"] E --> H["Set date, time, capacity"] F --> H H --> I["Save slot"] G --> I I --> J["End: schedule updated"] click B "https://mickael-umt.com/owner/office-hours/" "Open Office Hours" click J "https://mickael-umt.com/office-hours/" "Open Public Office Hours"

Step inventory

ID	Step	Action	System state
S1	Open schedule	Navigate to office hours	Schedule loaded
S2	Review	Scan slots and bookings	No state change
S3	Act	Create, edit, or cancel slot	Form or confirmation
S4	Save	Persist changes	Schedule updated

Flow scenario

Scenario OH1

Owner opens weekly office hours

Trigger

Owner opens office hours management
Needs to add slots for next week

Experience

Schedule loads with current slots and bookings.
Owner adds new slots for Tuesday and Thursday.
Saves and publishes updated schedule.
Visitors can now book the new slots.

Trust and safety rules

Slots are owner-controlled; no double-booking.
Cancellations notify booked visitors.
Capacity limits are enforced per slot.

Interaction rules

Calendar view for slot management.
Recurring slots supported.
Changes trigger notifications to booked users.

Result states

State	What the user sees	What happens next
Schedule	Calendar with slots	Owner creates or edits
Form	Slot create/edit form	Owner submits changes
Published	Updated schedule	Visitors can book