Scheduling → Configuration is where the rules and preferences behind schedule generation live. It's organized into seven tabs.
Driver configuration
A grid of your drivers and their weekly shift preferences: for each day of the week, whether the driver prefers to work, avoids the day, or doesn't work it, plus preferred shift types and times. An Auto-save switch at the top of the grid controls how edits are saved. It is on by default, and edits save on their own a moment after you make them. Turn it off and edits wait until you press Save now (or Discard to drop them); the grid tracks which drivers have unsaved changes so nothing is lost.
Selecting a driver opens a detail panel with two key toggles: "Schedulable as driver" controls whether they're an option when generating route schedules (new drivers are managed automatically; Viki starts scheduling them once they finish onboarding), and "Schedulable as station staff" also makes them assignable to non-driver station shifts. Once that second toggle is on, "Eligible shift types" on the same panel picks which station staff shifts they can take. Drivers without preferences set are still generated with default availability, but you'll be warned on the generate screen.
The filter chips above the grid are All, Drivers, Helpers, Station staff, Unconfigured, and Inactive, each with a count. Roles sync from Cortex and are shown as read-only chips on the detail panel; someone whose only role is Helper lands under Helpers and is matched to helper shift types, while anyone holding the Driver role is scheduled as a driver. To change a role, change it in Cortex and let the sync bring it across.
Preference templates
Reusable weekly preference patterns. Instead of setting the same Monday-through-Sunday pattern on twenty drivers one at a time, build it once as a template and apply it from each driver's detail panel. A driver who follows a template keeps tracking it until you save driver-specific changes, at which point they keep those preferences but stop following the template.
Schedule templates
Whole-week shift layouts you can apply to future weeks. Start one of three ways: a blank template you build in the editor, a snapshot of any existing week's driver shifts (copied by day of week; the source week isn't changed), or an upload of a Cortex weekly schedule export file, with drivers matched by transporter ID. A snapshot holds driver shifts only: station staff shifts and time off are not part of a template, and applying one never adds or removes a driver's time off. Deleting a template never affects weeks it was already applied to.
Station staff
Defines non-driver station shifts (with a default time and per-day demand) and which people are eligible for them, so warehouse and support roles can be scheduled alongside routes. Eligibility is set per station staff person from their "Eligible shift types"; a roster driver becomes eligible through the "Schedulable as station staff" toggle on the Driver configuration tab.
Custom Driver Shifts
Extra shift types the generator schedules on top of route demand, each with a wave time and a default demand per day, which can be a fixed count or a percentage of the day's forecasted routes. These appear as their own section on the generate screen.
Manager preferences
Company-wide defaults, in seven sections. This tab does not auto-save: edit, then press Save changes at the top.
Schedule generation sets the starting values you see when opening Generate Schedule: fill methodology, week-over-week consistency, default demand source, and the preferred-time match window.
Placeholder shifts configures generic publish-now-assign-later shifts: default start time, shift length, whether drivers see the time, the label, and a note added to every placeholder.
Automation can auto-generate, auto-publish, and auto-sync the schedule to the roster on a set cadence, each with its own time of day. The sync runs once a day at the time you choose and always fills in tomorrow's roster from the published schedule.
Notifications controls whether drivers are notified when a schedule is published.
Shift marketplace has an "Enable shift marketplace" switch, and under it one switch per posting type: "Open shifts", "VTO (voluntary time off)", "Driver drops", and "Driver swaps". All four are on to begin with. The marketplace is only live when the main switch is on and at least one posting type is on; with every type off it behaves as disabled and drivers don't see it. "Auto-publish driver drops & swaps to marketplace" appears while drops or swaps are on and decides whether those requests go straight to drivers or wait for your review. There is no time-of-day cutoff for drops and swaps; to stop them, turn that posting type off.
Start time adjustment derives the start time drivers see from each shift's wave time. It is display only; stored shift times never change. Pick one rule for the company: "Minutes before each shift's wave time" with a "Minutes before wave time" value, or "One start time for everyone" with a "Start time for everyone" time. "Overrides for specific wave times" then lets you send particular wave times to a start time of their own, for example both the 9:50 AM and 9:55 AM waves to 9:30 AM; an override beats the rule above it.
Driver app has "Show shift length on each shift", which shows each shift's planned hours in the driver app.
Compliance rules
The work-hours rules generation must respect. Hard rules cannot be violated by a generated schedule: max shifts in any 7 days, max hours in any 7 days, max consecutive working days, and min rest between shifts. Each can be enforced or not. Record-keeping shifts with zero hours (such as a zero-hour Time Off extra type) don't count as work in these rules: they add no hours and aren't counted as working days. Generation skips zero-duration demand instead of creating a shift from it. The soft rule "Avoid overtime" keeps drivers under 40 hours per week when possible; the generator optimizes toward it rather than treating it as absolute. The same rules power the compliance checks you see on the schedule and in the marketplace.