Skip to main content
FGFG BookingHTML DEV 0.5.62
Public booking New appointment
Appointment operations

Check-in & booking lifecycle

Use explicit booking states instead of free-form status changes, with every accepted transition recorded in history.

State-machine rule: only valid next states are offered. Completed, cancelled, rejected and no-show bookings are terminal in this DEV contract.

Main operational path

Pending → Confirmed

Approval or payment can confirm a booking.

Confirm
Confirmed → Checked in

Customer has physically/virtually arrived.

Arrived
Checked in → In progress

Staff has started delivering the service.

Start
In progress → Completed

Service is finished and ready for final payment/follow-up.

Complete

Protected outcomes

CancellationEnds active workflowExisting policy engine decides customer fees separately.
No-showRecorded explicitlyCan feed no-show reporting and future booking rules.
RejectedPending onlyUsed for booking requests that fail approval.
HistoryAppend, do not eraseEvery accepted state change creates a status-history record.