Skip to main content

Shift management

While the Fabriq app mainly operates on a daily basis, we've made possible a few hour-level functionalities to allow you to align with your on-site working practices.

Margaux Reynaud avatar
Written by Margaux Reynaud
Updated this week

Define the shift patterns for you site

A shift usually represents a period of time during which a group of people operate together.

You can define shifts pattern from the site page, in the Shift pattern tab.

A shift pattern is a sequence of shifts that apply to specific days.

You can create as many shift patterns as you want. The most common case is one shift pattern for week days, and one for week-ends.

Click on Create a new shift pattern,

  • In General settings, enter the shift pattern name and days concerned.

  • In Shifts, add new shifts with a name, start time and end time. Shifts a fully customizable and flexible.

Shift pattern applications

We've designed the first iteration of shifts to solve the most critical day-to-day operational pain points: filtering tickets by shift and scheduling routines to run at shift boundaries. These two capabilities directly support how frontline teams actually work, ensuring the right people see the right routine, and facilitating shift handover rituals, and controls.

Ticket filtering

Check what ticket was created during a specific shift for handover or control, by using the dedicated ticket filter from the task plan and ticket widgets on the dashboard.

Routine scheduling

To come soon.

What about KPIs?

Shift-level insights are fully achievable today. Here’s an example of how they can be visualized with current KPIs.

  • After creating one KPI per shift, create a dynamic KPI for consolidation

  • In graph format settings, select

    • Multi-series display: grouped

    • Show legend and series data labels

KPIs are kept at the day level to maximise flexibility and clarity. Teams can define KPIs per shift (e.g., “Production Output – Morning Shift”) and roll them up into daily or weekly views. This approach gives full control over how performance is measured, without locking teams into rigid, shift-specific structures.

Introducing a native shift dimension would add significant complexity and make configuration and visualization harder at scale. Our KPIs, combined with composable aggregation, let every team tailor monitoring to their operations while keeping the platform simple, clear, and scalable.

Did this answer your question?