Shift fields & statuses reference

Last updated: August 27, 2026

Note

Fleet and the Shifts page are gated. Availability varies by organization — if you don't see it, reach out to Nash.

This is a field-by-field reference for a shift and its statuses. It doesn't cover the calendar itself, templates, or the CSV flows — for those, see schedule and edit shifts, create and use shift templates, and import shifts by CSV.

Shift fields

Field Notes
Name A label for the shift. Required.
Date The day the shift runs. Required.
From / To The start and end times. Required; the start must be before the end.
Driver or Vehicle Who or what the shift is for. Which field shows depends on whether the calendar is in the Driver or Vehicle view — see schedule and edit shifts.
Status The shift's state. Required. See the six statuses below.
Store Location The store the shift is tied to. Required if your access is scoped to specific locations.
Zones The zones the shift covers. Required unless your access is scoped, in which case this field is hidden.
Metadata (Optional) Additional data as JSON, if you use it.

The six statuses

Status Meaning
Active The shift is on and currently in effect.
Inactive The shift is off.
Planned The shift is scheduled for the future.
Completed The shift has finished.
Cancelled The shift was called off.
On Break The driver or vehicle on this shift is on a break.

Note

Only Active and Inactive are choices you can set from the Create/Edit Shift dialog. Planned, Completed, Cancelled, and On Break only appear on a shift if it already carries that status — you can't pick them yourself when creating or editing a shift.

Reports and the Audit Log

Two read-only surfaces sit alongside the calendar:

  • Reports shows planned versus actual shift times. This tab is available to Nash superusers only — most users won't see it. To pull shift data yourself, use Export on the Shifts tab instead (see below).
  • Audit Log records who created, changed, or deleted a shift, and lets you filter by change type. The Updated filter doesn't currently return results — treat it as not working, and use All types or search instead.

See shift reports and the activity log for more.

Import vs. export

These are two separate, one-way flows — neither is a sync:

  • Create CSV Upload (also labeled CSV Upload) imports shifts from a spreadsheet into Nash, creating or updating shifts in bulk. See import shifts by CSV.
  • Export downloads a CSV of existing shift data for a date range and scope you choose. See schedule and edit shifts.

Related