Purpose
What this page is for
- Provide the time blocks that requirements attach to.
- Make weekly schedules easier to read by separating distinct duty periods.
- Support consistent reporting and planning language across the workspace.
Workspace guide
Shifts
Shifts define when work happens. They provide the time structure that requirements and schedule coverage are built around.
Use this page when you need to
- Create the time windows the planner uses for staffing and reporting.
- Keep shift names consistent so requirements and schedules stay readable.
- Retire or simplify unused shifts so the editor does not get cluttered.
Workflow
Recommended workflow
- Create the real shift windows your team actually uses.
- Name them in a way that is clear in requirements, schedules, and exports.
- Return to Edit Requirements after adding or changing shifts so counts stay aligned.
- Review schedules to confirm the shift structure matches how leadership expects to see coverage.
Detailed guidance
How this page fits into the product
Why clear shift structure matters
The more ambiguous the shift structure is, the harder it becomes to explain coverage. If the organization really thinks in day, swing, and overnight windows, the workspace should reflect that rather than forcing generic buckets that no one recognizes.
How to keep the shift table readable
The shifts page should stay compact and legible. If a shift is no longer part of your planning model, retire or archive it instead of leaving the requirements matrix cluttered with outdated structure.
How shifts interact with requirements
Requirements are set by role on a shift. That means the shift list is one of the main dimensions that shapes how large or complex the coverage matrix feels. Cleaner shifts usually produce a cleaner requirements editor.
Practical tips
What helps in real use
- Keep shift labels short enough to fit in tables and summary strips.
- If the requirements matrix feels bloated, review whether every shift still belongs there.
- Use consistent names across the whole workspace.
Common questions
Frequently asked questions
Why does the shifts table look so important?
Because shifts are one of the main structural inputs into scheduling and requirements. Bad shift structure cascades into messy coverage editing.
Should I create many micro-shifts?
Only if they reflect real planning needs. Too many rarely used shift windows make the editor harder to maintain.
Related