ZenotiHelp

Run an on-demand recompute

ZTZenoti Docs Team Updated November 3, 2026 5 min readGuide

After certain mid-week changes — such as an approved leave request, a new hire whose start date falls within the current scheduling window, or an update to your center's target utilization — the AI Employee Scheduler's existing suggestions may no longer reflect your actual provider pool. Running an on-demand recompute regenerates the suggested schedule against the demand forecast already on record, without re-running the underlying prediction process. The recompute typically completes in under 10 seconds.

Availability: AI Employee Scheduler is in Beta. Your center is enrolled automatically by Zenoti; no customer enable step is required.

Audience: Center managers who need to refresh the suggested schedule after a staffing or configuration change mid-week.

Before you begin

  • Your center must already have an active scheduling run visible on the Demand based Scheduling page. If no run exists for the current week, select or confirm the calendar week before running a recompute.
  • You must have made at least one of the triggering changes described in this article (leave request approval, new hire onboarding, or target utilization update) before recomputing. Running a recompute when nothing has changed produces the same result as the existing suggestions.
  • Confirm that any leave request or new hire change has been saved in the relevant provider record before triggering the recompute, so the updated eligible pool is reflected in the new suggestions.

Note: On-demand recompute is the recommended path after the specific changes listed above. It uses the demand forecast already on record — it does not re-run demand prediction. If you need a completely new forecast, contact your Zenoti administrator.

Steps

Open the Demand based Scheduling page

  1. From the main navigation, go to Employee > Schedule.
  2. In the schedule toolbar, select AI Scheduling. The page opens titled Demand based Scheduling.
  3. Confirm that the correct calendar week is displayed. If not, use the calendar-week selector to choose the week you want to recompute.

Verify the triggering change is in place

Before recomputing, confirm that the change you made is already saved:

  • Leave request approved — The provider whose leave was approved should no longer appear as available for the affected days in the provider roster.
  • New hire start date within the window — The new provider's record exists with a start date that falls inside the active 28-day window.
  • Target utilization updated — The new target utilization value (between 50% and 100%) has been saved in the scheduling rules rail.

Important: The recompute reflects the eligible provider pool and configuration settings at the moment you trigger it. Save all changes before proceeding.

Trigger the recompute

  1. On the Demand based Scheduling page, locate the recompute control in the page toolbar.
  2. Select Recompute. The Schedule Grid refreshes. The recompute typically completes in under 10 seconds.
  3. Review the updated day-level coverage summary across the week to confirm the new suggestions reflect your change.

Tip: After a leave request approval, look for days that previously showed Optimised or Reallocation but may now show an understaffed state — those are the days most likely to need attention. See Review the day-level coverage summary for details on each day state.

Review and act on the updated suggestions

After the recompute finishes, the Schedule Grid displays fresh recommendations for each provider and day. Common outcomes to look for:

  • New hire whose start date falls inside the window — The recompute assigns the new provider a New shift recommendation on days where demand supports their inclusion. Because a new hire's start date equals the schedule date, they are always included in the schedule when any demand exists on that day.
  • Leave request approved — Days where the departing provider was previously suggested may now show an understaffed state or a New shift recommendation for another available provider.
  • Target utilization updated — Changes to the target utilization value affect how aggressively the solver fills or trims shifts across the entire week. A lower value may result in more Reduce hours or Remove recommendations; a higher value may result in more Add hours or New shift recommendations.

Review each affected day and edit suggestions as needed before copying the week into Zenoti.

Note: Nothing reaches the live schedule until you select Copy all on the Manager review surface. Recomputing updates the suggestions only.


Worked example — leave request mid-week

Your center has six providers rostered for Thursday. On Tuesday afternoon, one provider submits a leave request for Thursday that you approve. The Schedule Grid still shows that provider's Thursday shift as No change based on the original run.

You navigate to Employee > Schedule, select AI Scheduling, and confirm Thursday falls within the active week. You select Recompute. Within 10 seconds, the grid refreshes. Thursday now shows a {h}h understaffed day state, and the recompute has added a New shift recommendation for an available provider whose historical utilization is highest among unscheduled staff. You review the suggestion, make a manual adjustment to the start time, and proceed to Manager review.

Tips

  • Run a recompute any time you approve a leave request that changes who is available for the current week — do not wait until the end of the day, as other scheduling decisions may compound the gap.
  • When a new hire's start date falls inside the active 28-day window, trigger the recompute as soon as their provider record is saved so the solver can factor in their availability across all remaining days in the week.
  • After updating target utilization, run a recompute immediately and review the full week — the change affects every day in the window, not only the days you expect to be impacted.
  • Recomputing is non-destructive: any manual edits you have made to the suggested schedule are recalculated. Review the Schedule Grid carefully after each recompute to confirm your intended changes are still reflected or re-apply them as needed.
  • If the recompute result looks unchanged, verify that the triggering change (leave approval, new hire record, target utilization setting) was actually saved before you triggered the recompute.

Troubleshooting

Symptom Likely cause Resolution
The Schedule Grid looks identical after recomputing The triggering change was not saved before the recompute was triggered Save the leave approval, new hire record, or target utilization update, then select Recompute again.
A new hire does not appear in the updated suggestions The provider's start date is not within the active scheduling window, or their record was not saved before the recompute Confirm the provider's start date falls within the current 28-day window and that the record is saved, then recompute.
The recompute takes longer than expected or does not complete A temporary connectivity or service issue Wait a few moments and select Recompute again. If the issue persists, use the in-product feedback surface to report it. See Send in-product feedback.
Days that were Optimised before the recompute now show an understaffed state A leave approval removed a provider the original run relied on This is expected behavior. Review the understaffed days and consider whether the New shift or Add hours recommendations for other providers are appropriate before copying the week.
Was this article helpful?
Your feedback helps us improve our documentation.