Candidates and call-out
Find eligible workers with Candidates, or use a call-out to offer a shift best fits first until it is filled or offers close.
On this page
CandidatesAssign anywayHistoryHow a call-out runsStep inWhat your workers seeSettingsSet up texts and the accept pageCandidates
Select Candidates from any open or assigned shift’s menu. Chrona asks the solver once who could take it as an open shift, and ranks workers who keep every Must rule:
- Rank. The best fit comes first, by the scheduler’s goal order.
- What the shift does. Each worker shows what taking the shift does to their rules, against leaving it open, for example Adds overtime · A more even share of work. A worker the shift changes no rule for shows no line.
- Assigned now. On an assigned shift, its worker comes first, marked Assigned now. You cannot assign them.
- Pick a worker to see each rule’s effect and goal, such as Adds overtime or Closer to contracted hours.
- Use Search workers for anyone listed on the scheduler. Grayed workers break a Must rule; selecting them checks and explains each breach, such as an overlapping shift. Assign then reads Assign anyway…: see Assign anyway.
- Select Assign once an eligible worker other than Assigned now is selected. The bar explains why Assign is disabled.
Assignment removes an open shift from its lane. A published shift is republished immediately, notifying both workers as for a published edit. Confirmation names the shift and worker. A failed save leaves the dialog open with the reason and the board unchanged.
When Chrona cannot rank now, the dialog says so, with Try again: it never lists workers it has not checked. When no one can take the shift without breaking a Must rule, the dialog says so: search a name to see why.
Assign anyway
Sometimes a shift has to go to a worker who breaks a Must rule. Every planner on the scheduler, a Chrona Workforce Admin and a System Administrator can assign them anyway, with a reason. Chrona checks these changes you make by hand on the board, once:
- Drag a shift. When you drop it, Chrona checks the worker who gets it and the worker who loses it. Nothing is checked while you drag; the marks under the pointer show as before.
- Reassign shifts. Chrona checks the set when you select Apply.
- Candidates. Pick a grayed worker and select Assign anyway….
A change that breaks a Must rule of the worker’s agreement, or a scheduler rule set to Don’t allow, opens Assign anyway. A rule set to Warn still saves the change with a warning, and a Should rule still only warns. The dialog lists each rule the change breaks, marked Must, with why. For several shifts, it lists the rules under each shift. A dropped shift waits where you dropped it, marked Waiting for a reason.
Enter a Reason and select Save: the worker gets the shift, and the shift is pinned, so Auto Schedule keeps it. Chrona keeps who made the change, when, which rules it breaks and why in the shift’s history. Save stays off while the reason is blank. When Chrona refuses the change, such as when you are not on the scheduler, the dialog says why and nothing is saved. Cancel puts the shift back.
When Chrona cannot check a change, for example when it could not read the agreements, it does not save it. The bar above the board says so, with Try again.
A shift assigned anyway is marked on its card in the warning color. Hover it to see the rules it breaks, who assigned it and when, and why, with See history. Outcomes counts the period’s overrides apart from Must breaks; select the count to list them. Auto Schedule’s review lists their breaks as Approved overrides, not as Must breaks. The override ends when the shift is unpinned or gets another worker; its record stays in the shift’s History.
A move to the open row is not checked, because no one gets the shift. Workers in Chrona Workforce Mobile and Auto Schedule keep every Must rule.
A worker on call from home during the shift is listed in Candidates only when their agreement’s On call during work rule is On: without it, the duty and the shift would overlap. A call-out never offers an on-call duty; fill an open duty with Find cover. See Agreements.
The order of the goals is the scheduler’s. See Goals.
History
Right-click a shift and select History, or select See history on an overridden shift, or a shift in Outcomes’ list of overrides. History lists what happened to the shift out of the ordinary, newest first: a new worker on a shift that had one, an accept (by a worker in Chrona Workforce Mobile, or a planner’s decision), a swap or cover, a worker cleared from the shift, and each override and its end, with the reason and the rules it breaks. Each entry says who made the change and when. Creating a shift, Generate, Auto Schedule’s own fill and moves, time or role edits and publishing are not listed. History is kept for 90 days after the shift.
How a call-out runs
A call-out starts when a shift loses its worker and is published open within the scheduler’s Start offering days before it starts. Sick reports, withdrawn shifts, Mark absent and a planner removing a worker then publishing can trigger it. The hourly task starts it if the shift comes within them later.
Only workers listed on that scheduler receive offers. Shifts that never had a worker, including unfilled Auto Schedule shifts, get no call-out: the scheduler’s workers see them in Mobile Open shifts, where a tap checks every Must rule. Candidates also works before then.
- Level by level. Chrona offers the shift to level 1 first. The next levels open at even steps until the cut-off: 60 minutes before the shift starts unless the scheduler sets another number. Earlier levels can still accept. A call-out that starts after its cut-off offers every level at once. Levels after the first, and the cut-off, run on the Chrona Call-out timer cloud flow, which set-up turns on.
- Fresh each time. When a level opens, Chrona ranks again the workers who are still free.
- Each channel. The offer is saved in Mobile first, then emailed with Accept / Decline links. Texts require the scheduler’s texts setting and the worker’s mobile number. Mobile More > Notification preferences can turn either channel off; the app offer remains. Unconfirmed delivery is recorded and not automatically resent.
- The first accept. Every channel uses the same request and rechecks Must rules. With Review open-shift requests on, a manager or scheduler’s planner must approve; acceptance alone does not fill the shift. Otherwise the first accept fills it. Before approving, planners see added overtime hours, rate and estimated cost on Requests; managers see it in Mobile. Once assigned, other offers become Filled by someone else.
- Unfilled. At the cut-off, a call-out for a shift that is still unassigned becomes Unfilled. The shift shows a warning, and an alert under the period bar tells the scheduler’s planners, with Find cover to find someone yourself.
For example: a sick report at 17:00 for a 22:00 shift, a 60-minute cut-off and four levels. Level 1 gets the offer at 17:00, level 2 at 18:00, level 3 at 19:00 and level 4 at 20:00. At 21:00, if no one has taken it, the planners get the alert.
While a call-out runs or is paused, only the workers with an offer see the shift under Open shifts in the app. When it stops or finds no one, the workers its scheduler lists who can take the shift see it again.
Step in
On a shift with a call-out, select Call-out in the shift’s menu. The Call-out panel opens beside the board. It shows the call-out’s state and when the next level opens, and the workers it offered the shift:
- Levels. Each header shows when it was offered. Level 1 costs nothing against your goals; later levels add goals from lowest priority upward, leaving top-goal breaches last. Empty levels are skipped.
- Offer status. Sent in app, Seen, Accepted, Declined, Expired, Filled by someone else or Assigned by planner, with the original rank and reasons. No reason appears when there was no goal cost. Sent in app confirms app availability.
- Email and text status. Waiting, sending, queued, accepted for delivery, not sent, could not send, or delivery not confirmed. No line means neither channel was used. Queued or accepted does not confirm receipt. Twilio reports only whether the send call worked; Chrona does not track text delivery.
The panel’s actions:
- Pause holds the next level. Resume runs it again, at once if its time passed while paused.
- Stop call-out asks first, then ends the call-out. The open offers expire, and the shift stays open.
- Find cover opens the shift’s Candidates. Assigning a worker there fills the call-out, because the shift is covered. The chosen worker’s unanswered offer shows Assigned by planner, and the link they were sent says a planner assigned them the shift. Other offers show Filled by someone else, and those workers get This shift is filled.
A shift that a call-out filled keeps Call-out in its menu. The panel shows who took it first, then the offers.
What your workers see
- In the app. The offer shows under Open shifts: Can you take this shift?, with Accept shift and Decline. When someone else takes it, the offer reads This shift is filled. When a rule changed since the offer, it reads You can no longer take this shift.
- By email. Accept and Decline open a page on the worker mobile site with no sign-in. The page shows the shift, and the answer goes only when the worker taps Accept shift or Decline. A link takes one answer and works until the shift starts.
- By text. The text carries the offer link only, and the worker answers on the same page as from an email. A reply to a text does not work reliably in every country, so workers answer on the page, not by reply. Chrona sends the text and does not track its delivery.
- Overtime. When the shift puts the worker into overtime, the offer says so before they accept, in the app, in the email and on the offer page: This shift puts you into overtime: 6 h at 150% pay. Chrona counts it from the shifts the worker has at that moment. A worker the shift puts into no overtime sees no line.
Settings
Open the scheduler’s settings and expand Call-out. Set when to start and stop offering, and whether to send texts. An agent with the Chrona Model Context Protocol (MCP) server can also set these values.
Each setting and its default is in Call-out.
Set up texts and the accept page
Texts need your own Twilio account. The call-out timer flow and the public accept page need set-up steps. See Set up call-out.
