The Roster That Records Only the Exceptions
Most staff work the same shift most weeks. A roster that asks you to fill in all seven days for everyone every week is mostly copying, and copying is where mistakes come from. AWRA keeps one default shift per person and records only the days that differ.
A bakery in Ruiru runs three shifts: the early bake from five in the morning, the day shift that packs and dispatches, and the night crew that mixes dough from nine at night. Forty people, and thirty-two of them work the same shift every week of the year. Every Thursday the supervisor still rebuilds next week’s roster in a spreadsheet, row by row, and every few weeks a night baker’s name lands in the day column because a row was pasted one line out.
The spreadsheet is not wrong because the supervisor is careless. It is wrong because it asks for forty times seven answers when only a handful of them changed. The useful question each week is not “who works when?” but “who works differently from usual?”, and a roster should be built around that question.
A default for each person, and a grid for the exceptions
In AWRA a shift is defined once: a name, a start and end time, an unpaid break and a grace period for lateness. Each employee is then given one default shift. That is the standing answer, and it applies until someone says otherwise. The assignments screen also counts everyone currently employed who has no default at all, across the whole workforce rather than the page in front of you, so a new starter who was never placed shows up as a number rather than as a gap discovered on payday.
The weekly roster is a grid of people against the seven days from Monday. An empty cell means the default applies. Only a filled cell is stored, as an override for that person on that date. When Wanjiru covers the night crew on Wednesday because a mixer is on leave, one cell changes, and the other two hundred and seventy-nine stay empty because they are already right.
| What you set | Where | How long it holds |
|---|---|---|
| The shift itself: times, break, grace | Shifts | Until edited or archived |
| Each person’s usual shift | Assignments | Every day, until changed |
| A different shift on one date | The weekly roster | That date only |
| Clearing a cell | The weekly roster | Returns that date to the default |
A roster that records only the exceptions has far fewer cells to get wrong, and every filled one was a decision.
Copying last week, without copying the mistakes
Some exceptions repeat. A packer who is on mornings for a month while a colleague is on maternity leave is an override every week. Copy last week takes the previous week’s overrides and places each one on the same weekday this week. Cells already filled this week are overwritten, and if you have filtered the grid to one department, only that department is copied, so the dispatch supervisor can roll forward dispatch without touching the bakery floor.
Because only the overrides are copied, the copy is short and readable. If last week held no overrides, you are told the previous week had no roster to copy rather than shown a grid that looks done. Saving the grid only accepts dates inside the week you are looking at, so a stale browser tab cannot quietly rewrite a different week.
Everything downstream reads the same answer
A roster is only worth keeping if the rest of the system uses it. In AWRA one rule answers “what shift is this person on, on this date?”: the override for that date if there is one, otherwise the default. Lateness, expected hours, overtime and reminders all ask that one question.
- Lateness. A clock-in after the shift start plus its grace period turns a present day into a late one. Nothing else is changed: an absence or a day of leave stays exactly what it was.
- Expected hours. The span of the shift minus its break. A shift that ends at or before its start is treated as ending the next day, because a person defined it that way and reviewed it, which is why a 21:00 to 05:00 night counts as the eight hours it is.
- Overtime. On an ordinary working day, the hours worked beyond the expected hours of that day’s shift, so a night baker covering a day shift is measured against the day shift. On a rest day or a public holiday every hour worked is counted.
- Clock-in reminders. A rostered date is always a working date. A default shift only counts on the organization’s working days and outside the public holidays it takes off.
The night shift deserves its own sentence. AWRA never decides that a shift crossed midnight by looking at clock times, because a night shift and a pair of times typed the wrong way round look identical on an attendance record. It takes the fact from the shift definition. We explained why in a night shift is eight hours of nothing.
Who is actually in on Friday
The Who’s available board turns the roster into a weekly picture. Each cell is resolved in a fixed order: approved leave first, then a public holiday the organization takes off, then the shift, and otherwise the person is off. A holiday you work through is scheduled like any other day. The same check sits behind the workflow task queue, which warns when a task is due on a day its assignee is on leave, on a holiday or not on a shift.
What a swap leaves behind
Two people trading a shift is, in AWRA today, two roster cells edited by someone who manages shifts. The roster ends up correct and the trade itself is not recorded as a request with an approver. We wrote about that in the swap that is only an edit.
The short version
Give every person a default shift and record only the days that differ. Copy last week’s exceptions when they repeat, and let lateness, overtime, reminders and the availability board all read the same answer from the roster rather than from a spreadsheet nobody else can see.
What AWRA OpsHub does today
- Shift definitions with start and end times, an unpaid break of up to eight hours and a grace period of up to four hours.
- One default shift per employee, and a count of everyone employed who has none.
- A weekly roster grid of per-date overrides, where an empty cell means the default applies, filterable by department.
- Copy last week, onto the same weekdays, scoped to the department you are viewing.
- One answer used everywhere: lateness, expected hours, overtime, clock-in reminders and the availability board.
- Night shifts declared by the shift definition, never inferred from clock times.
- Read-only shift, assignment and roster views in the mobile app for people who manage shifts.
More we can add to your workspace
- Each employee’s own roster on their phone, in the app and the no-login employee portal. Commission it
- A message to the employee when their roster changes, naming the date and the new shift. Commission it
- Rotating patterns, such as two days, two nights and four off, laid onto the roster automatically. Commission it
- Minimum cover per shift, with a warning when a day falls below it. Commission it
- A draft roster that is published, so staff see next week only once it is final. Commission it
Where we point you to a specialist
- We will not decide that a shift crossed midnight from the clock times on an attendance record. That fact comes from the shift definition, because guessing it would turn a typing slip into sixteen hours of paid work.
The employee’s own roster and the change notice are one piece of work, since every per-date override is already stored against the person and the date.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsThree questions to ask of any rostering tool
If nobody touches next week, what does it say?
What you will often hear
Next week is blank until someone fills it in.
What it means for you
Every week is a full rebuild, and every rebuild is a chance to paste a row out of line.
Does lateness use the roster or a fixed start time?
What you will often hear
A start time per employee.
What it means for you
Anyone covering a different shift is marked late, or not late, against the wrong clock.
How does it know a shift ran past midnight?
What you will often hear
It compares the clock-in and clock-out.
What it means for you
A night shift and a typing slip look the same, and payroll may pay the slip.
See shift scheduling and rosters
Default shifts, the weekly grid, copy last week, and night shifts that count.
Explore shift schedulingFrequently asked questions
Do we have to fill in the whole roster every week?
No. Each employee has a default shift that applies every day. The weekly roster only stores the dates where someone works a different shift, and an empty cell means the default applies.
Can we copy last week’s roster?
Yes. Copy last week places each of the previous week’s per-date overrides on the same weekday this week, overwriting cells already filled. If the grid is filtered to one department, only that department is copied.
How is lateness worked out?
From the shift the person is on that date, the override if there is one and otherwise their default. A clock-in later than the shift start plus its grace period marks the day late.
How are night shifts counted?
A shift whose end time is at or before its start time is treated as ending the next day, so a 21:00 to 05:00 shift with no break is eight hours. The crossing comes from the shift definition, never from attendance clock times.
Can employees see their roster on their phone?
People who manage shifts can view shifts, assignments and the roster in the mobile app. An employee’s own roster in the app and the employee portal is something we can add to your workspace.