Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
Hours and booking rules
Leave, stored hours, and the gaps this guide will not paper over.
The 1.2.104 pilot approved a leave record and kept stored hours across an upgrade. Split shifts, breaks, and reopening a closed day were shown on an earlier candidate and were not repeated in that pilot.
The accepted services slice includes weekly hours for the business and for a practitioner.
Previously accepted slice, carried forward
Weekly availability was part of the 22 October 2026 acceptance. The later pilot preserved stored hours on upgrade and did not repeat the hours editor. An ordinary save must not turn an unavailable practitioner into an available one; that correction is described on the later working tree and was not part of the frozen 1.2.104 acceptance.
Before you start. The accepted M2A slice. Public booking also has to be published.
Limit. Split-shift editing was not repeated on 1.2.104. Practitioner hours are not the same thing as a room or a second staff member being free.
Technical details
Why it matters. Customers only see times the business has actually opened, once those hours are in force.
Example. The owner sets Monday morning and Monday afternoon as two blocks, then checks the booking page for that day.
Who uses it. The business owner. The owner hours controls.
Status: Cited local evidence. This is not commercial acceptance. Origin: Accepted as a local slice, then carried into 1.2.104. Not rerun on the fresh pilot. Candidate 1.2.104 is not an accepted commercial release. M2A local acceptance dated 2026-10-22. The later 1.2.104 candidate contains that slice and is not accepted as a whole. This guide did not re-run the slice.
Activating the candidate on a populated clone kept the stored hours.
New pilot result on 1.2.104
The upgrade clone preserved hours. The pilot did not rebuild the week from a blank form.
Before you start. Hours that were already stored.
Limit. Preservation is not a new editor test. It does not prove a backup restore.
Technical details
Why it matters. An update does not wipe the week the business already configured.
Example. After two activations, the cloned site still has the hours it had before the upgrade.
Who uses it. The installer, with the owner’s existing data. Upgrade of an existing installation.
Status: Cited local evidence. This is not commercial acceptance. Origin: New result recorded on the 1.2.104 local pilot. This guide did not re-run that pilot. Candidate 1.2.104 is not an accepted commercial release. R11 local-pilot ledger, record dated 2026-10-24. This guide did not re-run the pilot. Candidate 1.2.104 is not an accepted commercial release.
Holiday 1 was approved on the fresh site. The ledger does not attach a customer-facing screenshot of the resulting empty day for that specific leave.
Before you start. A practitioner record and an approved leave row.
Limit. This single approval does not demonstrate sick leave, partial-day leave, and closures as three separate controls. Closures were shown on an earlier candidate.
Technical details
Why it matters. A person on approved leave is not offered as if they were working, where the scheduler honours that record.
Example. The owner approves leave for a practitioner. Later booking checks should treat that person as unavailable for the leave dates.
Who uses it. The business owner. The owner leave control.
Status: Cited local evidence. This is not commercial acceptance. Origin: New result recorded on the 1.2.104 local pilot. This guide did not re-run that pilot. Candidate 1.2.104 is not an accepted commercial release. R11 local-pilot ledger, record dated 2026-10-24. This guide did not re-run the pilot. Candidate 1.2.104 is not an accepted commercial release.
An earlier candidate found a closed day outside the short list and reopened it.
Shown on an earlier local candidate, not repeated on 1.2.104
The earlier browser found 6 June 2031 closed and reopened it, which cancelled that block. The 1.2.104 ledger did not repeat the check.
Before you start. The earlier candidate’s closure tool. Do not assume the 1.2.104 screen is identical until it is re-checked.
Limit. Not repeated on 1.2.104. Reopening cancels the closure block; it does not move existing appointments in the evidence cited here.
Technical details
Why it matters. A one-off closure can be recorded and later reopened without deleting the business’s normal week.
Example. The owner closes one date, confirms the booking page has no public times that day, then reopens it.
Who uses it. The business owner. The closure control on that earlier candidate.
Status: Earlier local evidence. Not a new 1.2.104 result. Origin: Shown on an earlier local candidate and not repeated on 1.2.104. Candidate 1.2.104 is not an accepted commercial release. Earlier local candidate. Not repeated in the 1.2.104 pilot ledger. This guide did not re-run it.
An earlier candidate showed a split Monday and a Wednesday with no public times.
Shown on an earlier local candidate, not repeated on 1.2.104
The earlier browser showed Monday 10:00–12:00 and 14:00–17:00, and Wednesday 28 October had no times. Wednesday 11:00 was refused in that candidate’s recovery proof.
Before you start. Not repeated on 1.2.104.
Limit. Do not describe split shifts as freshly proved on 1.2.104. A missing time can also be caused by leave, duration, or staff eligibility.
Technical details
Why it matters. A long lunch or an afternoon-only day can be represented when that editor is in use.
Example. The owner enters a morning block and an afternoon block. A customer does not see the gap between them.
Who uses it. The business owner. The hours editor on that earlier candidate.
Status: Earlier local evidence. Not a new 1.2.104 result. Origin: Shown on an earlier local candidate and not repeated on 1.2.104. Candidate 1.2.104 is not an accepted commercial release. Earlier local candidate. Not repeated in the 1.2.104 pilot ledger. This guide did not re-run it.
It is not determined whether staff can save a visit outside the public booking window on 1.2.104.
Not determined
No 1.2.104 result in the ledger shows an owner override of public hours.
Before you start. Unresolved.
Limit. Do not promise out-of-hours booking. Public rules and staff-created visits are different, and only the public side has fresh booking evidence.
Technical details
Why it matters. Front desk sometimes need a time the website does not offer. This guide will not invent that permission.
Example. The owner tries to book before opening. Treat the result as unverified.
Who uses it. The business owner, if the control exists. The owner diary.
Status: Not determined. Origin: Not determined. Candidate 1.2.104 is not an accepted commercial release. Not verified for this guide. Described as unresolved rather than as an available feature.