1
Problème Parallel "sources of truth"
Screenshots, chat threads, and local copies disagree after the first mid-week fix.
Planning 1/3
Le 1/3 tient sur une page — pas sur cinq exports
Avec un cycle 1/3, la grille « papier » reste lisible… jusqu’au premier arrêt malencontreux ou au remplacement de dernière minute. ShiftBox garde le squelette du 1/3 intact tout en absorbant les aléas : échanges, absences, heures réelles.
- Référentiel unique pour tout le cycle 1/3
- Remplacements tracés sans recopier la chaîne
- Signaux sur la charge avant la fin de période
- Accès terrain sans appli à installer
Where 1/3 frays
Why tight 1/3 cycles unravel outside the textbook
Frequent off-days make it easy to lose the thread when reality interrupts the cadence
2
Problème Tiny edits, big ripple
One substitution can shift who thinks they are on tonight—especially with short on-blocks.
3
Problème Hours reconciled at the finish line
Overtime and coverage gaps surface only when payroll asks for proof.
4
Problème Leave punches holes in the rhythm
PTO and sick days force improvised coverage that the static grid never modeled.
1/3 rollout
How teams usually launch a 1/3 (24-on/72-off) schedule in ShiftBox
The base day-on cycle goes in first; real-world changes follow in the same system
Teams usually build the 1/3 template, attach people and sites, then run duty rotations and actual hours inside ShiftBox.
4 étapes
to a working roster
1 jour
to set up the foundation
1
Add people and sites.
2
Build the core 1/3 cycle.
3
Publish shifts to the team.
4
Run moves and hours inside the same tool from there.
Avant et avec ShiftBox
What changes when a 1/3 day-on roster leaves the spreadsheet
For long shifts it is critical to keep one picture of people, sites, and hours
Manual process
Why day-on duty quickly becomes opaque
The more sites and moves you run, the higher the risk that people, hours, and the roster diverge.
- A shift at one site affects the person’s whole cycle.
- Cross-site moves get lost in chat threads.
- Duty posts and actual hours are reconciled separately.
- Overload per person surfaces too late for the lead.
Avec ShiftBox
What one process gives a 1/3 team
Duty posts, sites, and hours sit together, so a long cycle is easier to keep under control.
- One current day-on roster version.
- Clearer view across sites and people.
- Overload is easier to spot early.
- Less manual roll-up at period close.
ShiftBox in practice
Make 1/3 operations readable for planners and crews
Same calendar for the template, exceptions, and the hours that actually happened
1
Solution Publish once, read everywhere
Managers update; staff refresh—no re-emailing a workbook after every change.
2
Solution Swaps with context
Substitutions stay tied to dates and roles so the next shift change is not guesswork.
3
Solution Load shows up sooner
Spot heavy stretches while you still have room to rebalance the roster.
4
Solution Exceptions live beside the base pattern
Vacations and sick leave sit in the same workflow as the core 1/3 rotation.
Ce qui aide au quotidien
Capabilities that matter on a live 1/3 roster
Pas une automatisation abstraite — des points de contrôle concrets à chaque poste.
Pattern and exceptions in one calendar
1/3 no longer lives apart from leave, sick days, and moves: everyone sees the same current shift picture.
Worked hours and variance
Hours per person, coverage swaps, and overload sit together so leads can decide before period close—not after.
A roster the team can trust
After publish, staff open the latest plan in their portal—no new file after every edit.
Interface
How this scenario looks inside ShiftBox
Calendar, people, hours, coverage, and reports share one workflow—no Excel, chat threads, and manual roll-ups.
01Planification
Une grille lisible sans bruit visuel
Construisez les shifts dans une matrice claire, assignez en glisser-deposer et voyez tout de suite les trous de couverture.
shifts en glisser-deposerfiltres par role et sitedetection des conflits
02Suivi du temps
Des feuilles de temps fiables
Heures reelles, retards et heures supplementaires au meme endroit pour eviter la reconciliation de tableurs en fin de mois.
vues feuille de tempsretards et heures supsyntheses pretes paie
03Equipe
Un espace employe leger
Le staff ouvre un lien navigateur, voit ses shifts, marque l indisponibilite et demande des echanges sans onboarding lourd.
pas d app supplementairemarques d indisponibiliteechange de shifts
04Communication
Des mises a jour sans ping-pong dans le chat
Quand les shifts changent, chacun voit le nouveau plan dans son espace — les managers ne reexpliquent pas chaque modification dans des fils paralleles.
publier en une etapeclair sur ce qui changemoins de relances manuelles
Qui en profite le plus
Un flux pour le responsable, le coordinateur et la revue finale
Sur un planning vivant, chaque rôle a besoin de sa part de la même vérité.
Responsable de site
Voit personnes, postes et charge sans attendre le dossier manuel de fin de période.
- Spots overload and coverage gaps sooner.
- Knows where the board already needs intervention.
- Relies less on phone calls and ad-hoc summaries.
1 vue
sur le cycle, la charge et les heures
shift supervisor
Travaille au même endroit : construit les postes, édite le planning et publie sans fils interminables ni renvois de fichiers.
- Records exceptions and swaps faster.
- Keeps a single live version without duplicates.
- Does not rebuild the cycle by hand after every change.
15 minutes
for a typical edit-and-publish block
payroll clerk and finance
Gets a cleaner base for timesheets, hour checks, and payout prep—not scattered sources.
- Hours already collected in one process.
- Swaps and variances survive through close.
- Final picture per person is far clearer.
Less
manual reconciliation before payroll
Case: 1/3 schedule
What transition looks like in practice
What changes after leaving Excel and “latest file” culture
Day-on teams rarely break on day one—they break once real edits pile up. That is when one shared process starts saving time.
"We are sixteen people on day-long duty posts. After a few cross-site moves we used to rebuild the duty roster from chat messages. Now schedule, changes, and hours live in ShiftBox: one calendar for the manager, one published view for the crew."
Before
Every fix meant a new sheet, a people-by-people check, and manual hour reconciliation at period end.
After ShiftBox
Template, exceptions, and shift facts stay in one process that survives each swap.
What changes day to day
The crew stops rebuilding 1/3 by hand after every edit and shares one current picture of people, hours, and shifts.
1 version
of the roster for everyone
15 min
for a typical bulk edit
less
manual reconciliation before payroll
Why it holds up
The template alone fails when changes live elsewhere
Value shows up when schedule, exceptions, and hours share one workflow.
Any base pattern looks simple until real exceptions appear. Once moves, swaps, and deviations stack up, a manual process stops being transparent—for managers and staff alike.
ShiftBox keeps this scenario in one place: calendar, worked time, coverage, and publish act as a single loop. Edits no longer drag a new file version and a final manual roll-up behind them.
What the team gets
A steadier board that survives real-world changes across the week or period.
Especially useful where the pattern looks standard but every exception shifts the final picture of people and hours.
• One current roster for everyone involved
• Swaps, leave, and sick days in the same operational loop
• Worked hours and variance without manual roll-ups
• Staff portal without installing an app
• Cleaner inputs for timesheets and payroll
• Less daily routine for the shift manager
Try 1/3 planning where edits do not fork reality
Start free and mirror your current 1/3 baseline without rebuilding it by hand each week.
We can demo a handoff-heavy 1/3 line if you want to see the flow live.
ShiftBox for 1/3 schedules
ShiftBox is built for rotating crews who cannot afford fuzzy edges—one workspace for the 1/3 template, the exceptions, and the hours story behind them.
FAQ — 1/3
Le 1/3 en pratique
Quand le modèle théorique ne suffit plus
On part d’un modèle déjà utilisé en Excel — ça prend combien de temps ?
En règle générale peu : vous posez le gabarit 1/3, puis les ajustements se font dans le même fil sans dupliquer les onglets.
Un collègue remplace quelqu’un à la volée — où ça se voit ?
Au même endroit que le planning officiel, sans refaire la chaîne à la main ni envoyer une nouvelle capture.
Peut-on anticiper les heures sup sur ce rythme ?
Oui : la charge se lit plus tôt, avant de clôturer la période et de découvrir les dépassements.
Les salariés consultent comment ?
Par un lien personnel, sans application : ils voient toujours la dernière version publiée.
Modèles connexes
Souvent consulté avec le planning 1/3
Scénarios pour longs shifts et nuit