This article explains how to prepare a branch's shift plan for a period with an AI proposal on the AI shift planning screen. The engine forecasts the need from the branch's past shifts, splits it into the company's defined shift types and spreads it over suitable employees. The result is always a proposal: you review it, adjust it and publish it. Managers with the SHIFT_PLANNER_USE permission do this; publishing also needs SHIFT_SHARE. SHIFT_MANAGE covers all of them. You can only plan the branches you are responsible for.
Before you start
The company's shift types must be defined in Shift planning settings; the engine does not invent shift types, it only distributes the defined ones (Shift planning settings).
Legal limits (45 hours a week, 11 hours a day, 7.5 hours of night work, 11 hours of rest between shifts, 270 hours of overtime a year) apply without any record; enter the company's own rules beforehand if it has any.
Today's Shift Settings must be saved; published shifts are created with the rules of those settings (Shift settings and plans).
Step by step
In the left menu go to Time and attendance > AI shift planning, or click Plan with AI on the Shift schedule. In the toolbar under the section strip (Forecast, Proposal, Comparison, History) choose with the chips: Branch, optionally Department, Period (the arrows move to the previous or next period; click the chip to pick from the calendar) and Period length (Weekly, Monthly, Quarterly). From the Forecast basis chip you can pick AI model (default), Last N periods (with Number of periods under it) or Same period last year; when the department or the basis has changed, Clear all puts them back.
On the Forecast tab every day and shift type shows the Required headcount, the Expected number with its confidence interval (lower and upper in brackets), and the Last period and Last year actuals side by side. The line above shows the chosen Forecast model, the Forecast error (WAPE) and the Actuals source (Attendance records (PDKS) or Planned shifts). When the branch has less than 3 months of history the forecast starts from similar branches and the Low confidence label appears. Click Refresh forecast to recalculate; manual adjustments are kept.
When something the engine cannot know applies (for example a campaign week), click the pencil in the cell. In the Adjust forecast dialog enter the Required people and the Reason, then click Save. The adjustment is stored and used as feedback for later forecasts; Remove adjustment goes back to the calculated value.
Click Create proposal. If there is no forecast it is calculated first. Two proposals are created for the period: Cost focused (fills contract hours and keeps overtime and borrowing low) and Preference focused (puts employee preferences and a fair spread first). A one month plan for one branch takes less than 30 seconds; the screen moves to the Proposal tab.
The Proposal tab shows an employee by day calendar. Select the strategy at the top; the Coverage row shows assigned and required people per day, the Open shifts row shows shifts nobody could take. Icons in the cells mark risky assignments: Pending leave request, Borrowed staff, Overtime, Awaiting consent, Written consent given, Employee declined. Turn on Risky assignments only to see only those. In the current period the proposal starts today: days before today are hatched and locked, are not counted as understaffed in the coverage row, and no shift can be added to them.
Click an assignment. The Assignment details panel shows its Reason (for example "Elif K. assigned: position fits, worked 2 weekends this month (team avg. 2), 36/45 hours this week."), the Score components and the Alternative candidates. Assign a candidate with Swap with this, change the Shift type and click Apply, or take it out with Remove assignment. The + in an empty cell opens the Add shift dialog. For an open shift the Suggested solutions are listed (borrowed staff from another branch, extra part time hours, overtime). Every manual change is stored as a manager adjustment, and a rule violation is shown right away.
The Warnings panel on the right lists Hard rule violations in red and Warnings in yellow; clicking an item goes to its cell. For an assignment over 45 hours a week or 7.5 hours of night work click Send consent request and choose Send in the dialog: a written consent document goes to the employee as an e-document, and the employee approves it with an SMS code under My e-documents (Reading and approving an e-document). Overtime consent covers the whole week concerned. If an open or approved request already exists for the period, no new one is sent and "A consent request for this period already exists." is shown. Once approved, the item moves under Covered by written consent and no longer blocks publishing; if the employee declines or the request expires (Expired), the violation stays hard. Free text rules (such as collective agreement terms) appear in Rules to check by hand.
Open the Comparison tab to see both proposals side by side: estimated cost hours, total hours, overtime, preferences met, weekend and night fairness, open shifts, understaffed and overstaffed people, borrowed staff and warnings; the better value of each metric is marked. Choose this switches to that proposal.
When no hard rule violation is left, click Publish. The dialog shows how many shifts and employees there are; if open shifts remain, tick I accept publishing with open shifts and choose Publish. Publishing archives the other draft proposals of the same branch and department whose period overlaps; the History tab shows this.
If leave or a sick note is entered for an employee after publishing, a red warning appears on the proposal and the publisher and the branch's planners are notified. Click See conflicts and pick one of the Backup candidates with Assign backup. Only that shift changes; the rest of the plan stays. If no one can take over without breaking a rule, the warning says so; change that shift on the Shift schedule.
The History tab lists the branch's earlier proposals with period, strategy, status (Draft, Published, Archived) and summary; draft proposals can be deleted there.
Result
Published assignments are added to the Shift schedule as Shared Shift. They are created the same way as a manually added shift, so night shift splitting, breaks, Shift Settings rules, timesheets, the Patron PDKS push and shift reminder e-mails/SMS work as today (Planning and sharing shifts).
Every assigned employee gets an in-app "Your shift plan was published" notification. The other proposal of the period becomes Archived.
Shifts that already exist in the period appear locked in the proposal and are not created again.
The engine never receives leave types, sick note reasons or health information; it only knows whether the employee is available that day. Employees with approved leave or a sick note are not proposed that day; an assignment for someone with a pending leave request is marked risky.
Common problems
Symptom: The Publish button is disabled and "The plan cannot be published while hard rule violations remain" is shown below.
Cause: An assignment breaks a legal or company rule.
Fix: Click the red item in the Warnings panel and change the assignment, or ask the employee for written consent for overtime and long night work.
Symptom: Send consent request fails.
Cause: An SMS code approval uses one digital credit and you have none.
Fix: Top up digital credits and try again.
Symptom: The forecast screen says "No forecast for this period" and points to shift types.
Cause: The company has no shift types.
Fix: Add types in Shift planning settings > Shift types or use Suggest from history.
Symptom: Publishing stops with "A rule in the shift settings stopped publishing".
Cause: A limit in Shift Settings is stricter than the proposal. No shift is created in that case.
Fix: Set the same value in Shift planning settings > Rules and create the proposal again.
Symptom: Create proposal says "A published plan already exists for this branch and period.".
Cause: The plan of this period is already published; a second plan is not created for the same period.
Fix: The screen opens the published plan. For changes use Assign backup for conflicts after publishing, or the Shift schedule.
Symptom: "Shifts cannot be planned for past days."
Cause: The whole period is in the past, or you tried to add, publish or assign a backup on a day before today.
Fix: Plan for today or later.
Symptom: Publishing shows "Another publishing is in progress, try again shortly.".
Cause: Another publish for the same proposal or period is running at that moment.
Fix: The proposal is refreshed; check its status after a few seconds and publish again if needed.
Symptom: Publishing shows "The company's shift settings are not saved".
Cause: The company's Shift Settings are not saved yet; shifts published without them do not show on the Shift schedule.
Fix: Save the Shift Settings and publish again (Shift settings and plans).
Note: Natural language commands ("add one more person to the cash desk on Saturday"), external demand signals such as sales and appointments, a productivity score and a chat assistant are planned for later phases.








