Shifts

The Shifts settings page lets administrators define the work shifts your facility operates. Each shift is a named configuration record with a start and end time, used to attribute batch activity and production metrics to the correct operating period.

Role required: Administrator only. Shift configuration changes are recorded in the audit trail.

Shift fields

Shifts that cross midnight (e.g., 22:00 to 06:00) are supported. Clarix treats the end time as occurring on the following calendar day when it is earlier than the start time.

When to configure shifts

Define shifts during initial setup or when your facility changes operating hours. Accurate shift configuration supports:

• Batch activity attribution to the correct operating period
• Production throughput and staffing reports by shift
• Trend analysis for deviations or yield issues tied to specific shifts

Managing shifts

1. Navigate to Settings → Shifts.
2. Review the list of configured shifts.
3. Click Add shift to create a new record, or click an existing shift to edit its name, code, or times.
4. Click Save.

Note: Changing shift times does not retroactively reassign batches already attributed to a shift. Only new batch activity uses the updated schedule.

Shift attribution on batch records

When a batch execution begins (the technician clicks Start execution on the batch detail page), Clarix evaluates the configured shift schedule against the execution start timestamp to determine the active shift at that moment. That shift is permanently attributed to the batch record.

• The attributed shift is shown on the batch detail page in the production information section.
• The shift name is included in the MBR PDF export under batch metadata.
• Attribution is based on execution start time, not batch creation time or completion time.

Shift times are evaluated in facility local time. Clarix stores all timestamps internally in UTC and converts to the facility's configured timezone for shift evaluation and display.

Overlapping shift handling

If your shift schedule has overlapping windows (e.g., Day Shift ends at 15:00 and Evening Shift starts at 14:30), Clarix uses the shift that started most recently relative to the batch execution start time.

Example: A batch execution begins at 14:45.

• Day Shift: 07:00–15:00
• Evening Shift: 14:30–23:00

Both shifts are active at 14:45. Because Evening Shift started most recently (14:30 < Day Shift's start of 07:00), the batch is attributed to Evening Shift.

To avoid ambiguity, configure non-overlapping shifts with a clean handoff time. Overlapping windows are permitted but require careful planning if you rely on shift attribution for compliance reporting.

Shift breakdown in reports

Reports → Batch Analytics supports filtering and grouping by shift. This allows you to segment production data by operating period and surface patterns that correlate with specific teams or time-of-day conditions.

Common analyses by shift:

• Deviation rate — number or rate of deviations per batch by shift
• Yield trends — average yield % per shift to identify performance differences
• Throughput — batch completion count per shift per period
• Out-of-tolerance events — measurement failures grouped by shift

Edge cases

Note: If a batch starts during one shift and completes during another, the attributed shift is the one active at execution start, not at completion. Overnight batches are handled the same way — only the starting shift is attributed, regardless of how many shift boundaries the batch spans during execution.

Note: If a shift is deactivated while a batch is in progress, the batch retains its attributed shift. The deactivated shift will not appear in the dropdown for future batches, but all historical records referencing that shift remain intact and searchable in reports.

Note: If a batch is started at a time when no configured shift is active (e.g., early morning before any shift begins), the batch record shows "Shift: Not specified" in reports and the MBR.

Related pages

• Settings Overview
• Production Lines
• Creating a Batch
• Batch Analytics