Daybook
Built for hourly teams

Hours you can actually pay people from.

Track time, catch everything that deviated from the schedule, approve the week and export payroll-ready numbers. Every figure traces back to a real punch and the person who approved it — months later, in front of anyone who asks.

Free to set up · takes about a minute

Home · Northgate Logistics
Good morning, Sarah
Monday, 4 May
This week
Needs a decision4
PPriya Raman11 min after 09:30 + 5 graceMon 09:41Late
TTom WhitfieldScheduled 08:00–16:00, no punchMon —Absent
AAisha BelloSpring bank holiday — payableSun 12:04Worked holiday
MMarcus ColeOut 32 min before 18:30Tue 17:58Left early
On shift right now14of 19 expected
Payable this week612:20incl. 7:30 worked holiday
Every figure traces back to a punch, a correction and a named approver.
Nothing is deleted the audit trail is append-only — edits add rows, never replace them.
One calendar public holidays are set once and inherited by every person.
Scoped by design a manager sees their own team and nobody else’s pay rates.
What it does

The whole week, in one place

Attendance is only useful if the numbers survive an argument. Everything here is built so a figure can be traced, explained and defended long after the week it came from.

Punch from anywhere it makes sense

Phone or laptop for people with an email, a shared kiosk with a PIN for people without one. Both obey the same rules — the kiosk is never a side door around a schedule.

One queue for everything odd

Late arrivals, absences, forgotten clock-outs, correction requests and time off land in a single list. Resolve it or accept it with a reason — nothing is silently swept away.

Schedules decide what late means

Fixed shifts, flexible days or a weekly target, each with its own grace period. Change a schedule and the past is never quietly recalculated behind you.

Approve, then lock

Managers approve their own team. Locked means locked — reopening is owner-only, always audited, and everyone affected is told what changed.

Payroll numbers, not guesses

Hours, paid leave, worked holidays and pay rates roll into a summary and a CSV your payroll system can read without a spreadsheet in between.

Managers see only their team

Assign a person to a manager’s team and that manager gets their queue, their board, their timesheets, their PINs and their leave balances — and nothing outside it.

Approvals

A week you can sign off in one pass

Each person’s week is one screen: what they were expected to do, what they actually did, what was corrected and by whom. Breaks are already deducted. Paid leave is already separated from worked time.

  • Submitted weeks queue up in the order they arrived.
  • Corrections show the original time beside the new one.
  • Approving is per person, so one disputed week never blocks the rest.
  • Locking the period is a separate, deliberate step.
Priya Raman · week of 4 MaySubmitted
DayInOutWorkedNote
Mon08:5817:047:3630 min break
Tue09:1217:007:18Late — accepted
Wed08:5517:027:37
Thu——0:00Annual leave
Fri09:0016:317:01Corrected 16:31
Total29:32+ 7:36 paid leave
Approve weekAsk for a change
Everywhere the work is

A phone for some people, a tablet by the door for the rest

Not everyone has a work email, and pretending otherwise is how attendance systems quietly stop reflecting reality. People with an account punch from their own device. Everyone else uses a shared kiosk with a personal PIN.

  • The same schedules, grace periods and exception rules apply to both.
  • PINs lock out after repeated wrong attempts.
  • Every punch records where it came from — web, kiosk or a manual correction.
Aisha BelloEnter your PIN
123456789⌫0↵
Today is a public holiday — this time is recorded as holiday work.
You are on shift03:41:12Clocked in 08:58 · break 30 minClock outStart break
Mon7:36
Tue7:18
Wed7:37
A week, in five moves

Follow one shift all the way to payroll

The same eight hours, seen by everyone who touches them. Scroll on.

Swipe across →

01

Priya clocks in at 08:58

One button on her phone. The server stamps the time the moment it arrives; her device clock is recorded beside it so any gap between the two is visible rather than hidden.

Never overwritten. A punch is an event, not a field. Nothing that happens later edits it.

02

The schedule decides what that means

She was due at 09:00 with five minutes of grace, so 08:58 is simply present. Had it been 09:20, the day would surface as late — against the pattern that was in force on that date, not the one in force today.

The past is judged by the past. Editing a schedule never recalculates a week that has already closed.

03

Thursday, she forgets to clock out

The overnight job closes the shift at the rule, not at midnight, and flags it. Priya proposes the real time herself with a note; it goes to her manager as a correction rather than an argument.

Both numbers survive. The correction is a new row pointing at the original. The record shows what the clock said and what was agreed.

04

Manny clears the queue on Friday

Two items, both his own team. He approves the correction and accepts a late arrival with a reason. His name and that reason are stored with the day, permanently.

Nobody is scored. There is no punctuality ranking anywhere in the product, by design.

05

The week is signed, locked and exported

Priya submits, Manny approves, the period locks. Payroll gets payable minutes, unpaid break, paid leave and holiday worked as separate columns — the shape a payroll run needs.

Reopening leaves a mark. Only an owner can, only with a reason, and the reason sits next to the original approval.

How it works

Four steps to a payable week

Setup is front-loaded on purpose. Once the calendar and the schedules are right, the weekly routine is just clearing a queue and pressing approve.

01

Create the organisation

Country, timezone and workweek in one screen. Those choices set the defaults everything else inherits.

02

Set the calendar and the rules

Import your country’s public holidays in one click, then create the schedules that define what “late” means.

03

Add your people

Anyone with an email is invited automatically. Anyone without one gets a kiosk PIN instead. Assign them to a manager’s team.

04

Run the week, then export

People clock in and out, exceptions collect in one queue. Clear it, approve each timesheet, lock the period, export payroll-ready hours.

Evidence

Nothing disappears quietly

Every decision that touches someone’s pay is written down as it happens: who did it, when, and the reason they gave. The trail is append-only, so a record can be added to but never edited away.

  • Accepted exceptions keep the reason and the person who accepted them.
  • Corrections keep the original punch alongside the replacement.
  • Reopening a locked period notifies everyone whose week reopened.
Audit trailAppend-only
12 May 09:41Accepted “Late” for Priya RamanSarah Nkomo · “Train cancellation, agreed in advance”
12 May 09:44Requested correction: Fri out 16:31Priya Raman · “Forgot to clock out”
12 May 10:02Approved correctionSarah Nkomo · “Confirmed with shift lead”
13 May 08:15Locked pay period 4–10 MayDara Okonjo
Rules that never bend

The parts we refuse to make configurable

Most of the product adapts to how you work. These six do not — they are the reason the numbers are worth anything.

A locked period stays locked

Once a pay period is locked, nothing inside it can move. Reopening is an owner-only act, it records a reason, and it notifies every person whose numbers are back in play.

History is never rewritten

Corrections add a new row and keep the original visible next to it. You can always answer “what did this look like before, and who changed it?”

Accepting is not deleting

When a late arrival is fine, you accept it with a reason. It leaves the queue but stays on the record, attributed to you — and it can be revoked.

The product reports, it does not score

There are no productivity ratings, no rankings and no league tables. It records what happened against what was expected, and stops there.

A holiday is not a lock

Public holidays cover everyone, but they never block a punch. If someone works one, they clock in, confirm, and the day is recorded as worked holiday — payable, and visible in reports.

Scope is enforced, not decorated

A manager requesting a person outside their team gets “not found”, not a greyed-out button. The boundary lives in the database, not in the interface.

Who sees what

Four roles, drawn tightly

Nobody sees pay rates they should not. Managers are scoped to their own people, and the person who locks a period is never the person who can reopen it.

Owner

Everything an admin can do, plus the only role that can reopen a locked pay period and transfer ownership.

Admin

People, schedules, holidays, pay rates, kiosk setup and locking the period. Sees the whole organisation.

Manager

Their own team: the exception queue, the live board, approvals, schedules, kiosk PINs and leave balances — plus their own timesheet like anyone else.

Member

Their own hours. Clock in and out, take breaks, ask for a correction, request time off, see the week so far.

Questions

The things people ask first

What happens if someone forgets to clock out?

The entry is closed automatically at the end of the day and flagged as auto-closed rather than counted as a full shift. The person is asked to confirm the real time, and the confirmation is recorded next to the original.

Do people without an email address work?

Yes — that is what the kiosk is for. Give them a PIN and they punch from a shared tablet at the door. They still get schedules, timesheets and exceptions like anyone else.

How do public holidays work?

They are one calendar for the whole organisation. Import your country’s published days, or add your own, and every person inherits them — there is no per-person holiday list to keep in sync. Anyone who does work that day is recorded as working a holiday.

Can a manager change someone’s hours?

A manager can approve a correction, and every correction keeps the original time visible with a reason and their name against it. Nobody, including an owner, can silently overwrite a punch.

What can a manager actually see?

Only the people on their team. Their queue, board, timesheets, schedules, PINs and leave balances. Pay rates stay with admins and owners.

Can we get the numbers out?

Every report exports as CSV — attendance summary, payroll summary and raw time entries — with the same figures you see on screen, for the same date range.

More detail, including every term the product uses, is in the product guide.

Start tracking this week

Create an organisation, import your holidays, add one person and clock in. You can have a real record inside five minutes.