Another sequence is proposed
An order different from the current sequence is presented for comparison.
Limit : This proposal is not automatically the best possible sequence or a change already applied.
Help Centre · Field operations
What does it mean to “optimize” a route?
Optimization compares or proposes an order based on the available information without automatically imposing a change or guaranteeing a perfect result. This guide helps you compare a proposed sequence with the current order, reread the day’s constraints, and knowingly confirm or keep the schedule.
Distinguish a calculated proposal from the final decision
The current order represents the sequence before any change. A proposal may compare another order when the flow allows it, while route, distance, or duration estimates provide context. Reread the times, periods, addresses, and other available constraints before making a decision. Human adjustment may be necessary, and no proposal should be applied blindly. When a confirmation action is available, reread the proposal before changing the schedule. Depending on the flow, keeping the current order may also be the appropriate decision. A proposal guarantees neither the absolute best order, the shortest route, nor a certain arrival time.
Observed result
Clarify the observed result
Start by identifying what is actually presented in the comparison.
The order remains unchanged
The visible comparison keeps the same order or no other sequence is proposed.
Limit : This result does not prove that no calculation was performed or that the order is optimal in every context.
The proposal appears unusual
The proposed order appears incompatible with a known time, period, address, or constraint.
Limit : An unusual proposal does not automatically reveal the exact cause; the visible data must be reread.
Compared elements
Compare five distinct elements
A proposal becomes easier to interpret when each element is reviewed separately.
Current order
The appointment sequence before any confirmed change.
Limit : It does not necessarily represent an optimized sequence.
Proposed sequence
An alternative order presented for comparison when this function is available.
Limit : It guarantees neither the absolute best order nor the minimum distance.
Travel estimates
Route, distance, or duration information displayed when available.
Limit : They may change and guarantee neither future traffic nor a certain arrival time.
Day constraints
Times, periods, addresses, availability, or other elements considered in the flow.
Limit : Their presence, precision, and role may vary.
Selected schedule
The order kept or applied after the available comparison and confirmations.
Limit : A proposal does not automatically become the final schedule.
Day context
Reread the day’s constraints
Review only information visible or documented in the relevant flow.
- The selected date and day.
- The visible appointments and their addresses or location information.
- Fixed start times when they exist.
- AM, PM, or evening periods and service durations when available.
- Visible or documented constraints and appointments that should not be moved freely.
- The current order, proposed sequence, and displayed messages or warnings.
Limit : The presence and level of detail of this information may vary depending on the flow, available functions, and user role.
Booking models
Distinguish periods from fixed times
The scope for comparison depends in part on how the appointment is presented in the schedule.
AM, PM, or evening periods
When an appointment is associated with a period rather than a precise start time, another sequence may be compared within that period if the flow allows it.
Limit : The presence of a period does not guarantee that reordering will be proposed or applicable.
Fixed start time
When an appointment has a fixed start time, that time must remain a schedule constraint. A route calculation or comparison may remain available without the appointment being presented as freely movable.
Limit : No free movement, automatic time change, or guaranteed punctuality should be inferred from the proposal alone.
Decision flow
From selected day to retained schedule
Each step answers a separate question before any new order is applied.
Day selected
The user selects the date or scheduling context to review.
Limit : Selecting the day does not guarantee that a proposal will be available.
Appointments and addresses reread
The visible appointments and their location information are reviewed.
Limit : A recognized address or available route does not prove that all data is complete.
Constraints and times reviewed
Periods, fixed times, and other available constraints are reread.
Limit : Their presence and effect may vary by flow.
Current order and proposal compared
Both sequences are reviewed with the visible estimates and constraints.
Limit : A difference in order does not automatically prove a real benefit.
Possible human adjustment
The user may keep the proposal, adjust an available element, or reject the proposal depending on the context.
Limit : Actions, roles, and adjustment options may vary.
Application confirmed or schedule kept
When a confirmation action is available, the proposed order may be applied; otherwise, or when the proposal is unsuitable, the current schedule may be kept.
Limit : The presence of a confirmation, how it works, and its effects may vary. No operational improvement or punctuality is guaranteed.
Diagnosis
Review an unusual proposal
Methodically reread the context before applying a sequence that appears incompatible with the day.
- Identify the relevant day and page.
- Record the current order and proposed sequence.
- Reread the appointments, addresses, and visible information.
- Identify periods and fixed start times.
- Compare travel estimates when displayed.
- Check visible constraints or warnings.
- Avoid applying the proposal before understanding significant discrepancies.
- Keep the current schedule or prepare a support request if the result remains unexplained.
Note : Do not change a time or constraint solely to obtain a different sequence without reviewing the possible consequences. A real check may modify the schedule. No universal simulation mode is guaranteed.
Before any confirmation
Check before applying
Reread the full schedule and avoid repeating an action that has already changed the order.
- Use only authorized actions.
- Reread the complete proposed order.
- Check fixed start times and AM, PM, or evening periods.
- Avoid confirming the same change more than once.
- Reread the schedule after any application.
- Preserve the exact message or result.
- Record the date, time, and time zone.
- Prepare a sanitized screenshot if useful.
Note : A real check or application may modify the schedule. No universal simulation mode is guaranteed.
Guardrails
What this article does not guarantee
The guide helps reread a proposal without guaranteeing a particular mathematical, operational, or financial result.
- The absolute best order.
- The shortest route or minimum distance.
- A reduction in kilometres or time.
- A definitive route duration or future traffic conditions.
- A certain arrival time or punctuality.
- A proposal available for every day.
- The same result or actions for every role.
- Universal drag-and-drop or recalculation.
- Automatic application.
- Free movement of a fixed-time appointment.
- Automatic preservation of every constraint.
- A gain in margin, billable time, or revenue.
Related resources
Continue with the right diagnostic
Choose the resource matching the route, booking model, or next stage of the schedule.
Territories and routes
Choose the appropriate guide to review an address, fee, route, or optimization.
View the collection →Why is an address identified as outside the service area?
Distinguish an address-recognition issue from a coverage-related result.
Read the guide →How are travel fees calculated?
Review the applicable rule and available data when a fee is displayed or expected.
Read the guide →Why was a route not generated?
Check the visible information before concluding that there is an outage.
Read the guide →Route optimization
Learn how sequences may be compared, adjusted, and applied according to the data, constraints, and available actions.
View the page →Booking models
Understand the difference between periods and proposed start times.
Read the guide →Modify or cancel an appointment
Learn which elements to reread when appointment modification is available.
Read the guide →How do you prepare an effective support request?
Gather useful steps and results before contacting support.
Read the guide →Help Centre
Browse the other available collections and guides.
Visit the Help Centre →Support
Contact supportDocument the observed proposal
Please provide only:
- the page and flow;
- the relevant date or day;
- the current order;
- the proposed sequence;
- the relevant appointments without unnecessary personal data;
- the visible periods or fixed times;
- the partially masked addresses;
- the distance or duration estimates when displayed;
- the visible constraints or warnings;
- the action attempted;
- the exact result;
- the approximate date, time, and time zone;
- a sanitized screenshot if useful.
Security instruction : Never send a password, authentication code, key, token, technical secret, unnecessary full address, customer name, unnecessary personal information, or unnecessary detailed information about an employee’s movements.