The crew, on one record.
Who works here, who reports to whom, who is in today and who is off next Friday. One record per site. Edit it once and scheduling, training and production all follow.
- Scope
- Rotation depth
- Leave presets
- Reorg cost
Edit once. It flows everywhere.
People is the workforce system of record: the one place a person exists. Change a shift, a manager or a job title here, and every downstream module reads the update. No re-keying the same name into five tools.
Scheduling
Default shift drives the plan
Training
Live compliance per person
Production
Weekly output attributes here
Absences
Days counted from the shift
Org Structure
Reporting line draws the tree
The live tree. Or a what-if.
The reporting chart draws itself from each person's manager link. No second diagram to maintain. Want to test a reorg? Draft a variation, drag people onto new managers, and compare. A variation stores only what differs, so it never touches a real record.
Generated on the fly from every employee's reporting line. Re-parent anyone in a variation and the real records stay exactly as they are.
Shifts that rotate.
A shift isn't a single start and end time. It's a pattern that can run one to six weeks deep, with a different rhythm each day. Bulk calculates every pattern against an anchor date, so a rotation stays aligned week after week without anyone touching a calendar.
Early
Counted by shift, not by hand.
Log a leave request and Bulk works out the chargeable days from that person's actual shift. Rest days don't count, a Saturday on a rotation does. Requests that need a sign-off land in one queue; everything else auto-approves and shows on the calendar.
of a 7-day span
On the Rotating shift this week, Sunday and Friday are rest days, so they don't burn allowance. Wednesday is a half shift. The system does the maths, not the employee.
- MCM. ColeEMP-0188 · requested 2d agoAnnual22 Jul → 26 Jul · 3.5 daysApproved
- LTL. TanEMP-0203 · requested 1d agoSick15 Jul · 1 dayApproved
- DVD. VargaEMP-0156 · requested 4h agoUnpaid28 Jul → 30 Jul · 3 daysApproved
Everything a workforce actually needs.
Beyond the directory: bulk moves, the reference data the floor runs on, and the announcements that keep the shop in the loop, all entity-scoped and protected against deletion while they're in use.
Bulk add & edit
Convert existing logins into employees in one pass, or re-assign shift, manager, department and site across up to 100 people at once, with a per-row results report.
100 at a timeDepartments & job titles
Nested departments with managers, colours and cost centres; a sortable job-title list that maps straight into the training matrix. Both block deletion while staff are attached.
hierarchical · colour-codedCompany news
A rich composer pushes facility-scoped announcements to the floor (draft, schedule, publish, archive) with autosave, version checkpoints, audiences and tags.
draft → publishedAbsence types & allowances
Leave categories carry approval and pay rules and default allowances (seedable from ~20 national labour-law packs) with per-person, per-year entitlements and carry-over.
~20 country presetsAbsence calendar
The whole team's month at a glance, approved and pending coloured by type. Click a day to pre-fill a request, or a record to manage it inline.
team availabilityEntity-scoped, soft-deleted
Every record belongs to one facility at a time, moves between sites with validation, and is soft-deleted. Nothing the floor relied on simply vanishes.
per facility · recoverableOne record. Many consumers.
at a time
patterns
packs
touched
People doesn't sit in a silo.
It's the upstream record the rest of the platform reads from: a name, a shift and a reporting line, defined once and consumed everywhere a person shows up.
Scheduling
An employee's default shift drives availability and the job plan. Change it here, the schedule follows.
Training
Each record carries a live compliance summary; job titles map into the training matrix per role.
Production
Link a person to a login and their weekly output attributes back to them on the detail page.
Identity & access
An employee can link to a user profile for system access, or stay a directory-only record.
Home & news
Published announcements surface on the home screen and shared deep-links across the floor.
Dashboards
Headcount, on-leave counts and a 90-day forecast feed the People home and cross-module boards.
Questions, answered.
What is Bulk People & Working Hours?
It's the single record of your workforce for a facility: employees, reporting lines, shifts and absences in one place, so you're not running the team from five spreadsheets and a group chat.
Is the data shared across all my sites?
No. Employees, shifts, departments and news are entity-scoped to one facility at a time. The active site decides what you see, so each location keeps its own record.
Do I have to update the same person in several tools?
No. You edit the record once and it flows everywhere. The same change moves into scheduling, training and production instead of being retyped in five places.
How do shift rotations work?
Each shift defines seven days per week, every day with its own times and breaks, anchored to a date. Patterns can run one to six weeks deep.
How are absences and leave handled?
Absences are counted by shift, and you can seed a new facility with around twenty labour-law leave packs (UK, Germany, USA, UAE, Japan and more), so leave categories start out sensible.
Can I try a reorg without breaking the live org?
Yes. A what-if variation stores only the differences, so you can drag people around and test a new structure without touching a single real record.
Stop running the team from five spreadsheets.
We'll take your real org (shifts, reporting lines and a week of absences) and stand it up in Bulk, so you can see one record do the work of five tools.