Scheduling Configuration

Scheduling → Configuration is where the rules and preferences behind schedule generation live. It's organized into seven tabs.

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. Changes auto-save shortly after you edit. 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. Drivers without preferences set are still generated with default availability, but you'll be warned on the generate screen.

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.

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. Deleting a template never affects weeks it was already applied to.

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.

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.

Company-wide defaults, in six sections. "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. "Notifications" controls whether drivers are notified when a schedule is published. "Shift marketplace" enables the marketplace and whether driver drops and swaps auto-publish. "Start time adjustment" derives the start time drivers see from each shift's wave time — display only, stored shift times never change.

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. 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.