Skip to content
MapMyStaff
Help Centre · Booking

Why is a time proposed — or refused?

An empty time on screen is not enough. MapMyStaff evaluates whether the service can actually fit into the day with its duration, available team and travel.

A displayed period remains a candidate.Necessary information may be rechecked before final saving.

The system evaluates a booking possibility, not just an empty hour

A candidate period depends on the available context: date, booking model, address, service and option duration, selected or eligible employee, existing appointments and travel. A proposal can therefore change if any of these elements changes before saving.

01Build the context

Bring together what actually changes availability

The calculation needs the request context before it can propose a time.

A

Date and model

Selected date and AM/PM/EV presentation or proposed start-time model.

B

Address

Visit address and territory when that feature is configured.

C

Service and options

Package, options and total duration that must fit into the day.

D

Employee

Selected employee or eligible employees depending on the workflow.

A one-hour slot indicates a proposed start time; it does not fix service duration at 60 minutes.

02Evaluate the day

Check whether the request can actually fit

Availability also depends on what is already planned around the new booking.

01

Schedule and absences

Working hours, breaks and documented absences limit the usable window.

02

Existing bookings

Already-planned visits use time and define the gaps that are actually available.

03

Travel

Travel before and after the booking can make a visually empty time unusable.

04

Full duration

The service and its options must fit together within the day context.

03Read the result

A proposal, recalculation and refusal do not mean the same thing

The result reflects the context at calculation time; it does not always reveal a single cause.

01

Proposed

The current context allows this period to be attempted, subject to final checks.

02

Recalculated

A change in date, option, employee or day can change the displayed choices.

03

Refused

The request does not fit the evaluated context; check the factors instead of assuming a bug.

A refusal can come from several combined constraints. Change one variable at a time when diagnosing the context.

04Check before saving

Displayed availability is not yet a confirmed booking

The documentation calls for another check when context changes and before final save.

01

Before saving

Recheck the context-sensitive elements instead of treating the earlier display as final.

02

After a change

If a booking, option or employee changes, recalculate the affected availability before concluding.