TodayManager1 / 10

Business Operations PeopleLive

Attendance Tracking

5.0 out of 511 sold

Attendance systems fail when people stop trusting them. This one records hours against a shift rather than a clock, lets anybody claim work it could not see, and shows each person exactly what is held about them.

Function
24
Roles
3
Users
Unlimited
  • Next.js
  • TypeScript
  • PostgreSQL
  • Auth.js

Inside the app

What it does out of the box

24 connected functions on one schema, from the manager’s board to the record each person holds about themselves. Everything below is in the template before a line of customisation.

  • Today

    Who is in, who is late, who is on leave and who has said nothing at all. The last group is named rather than counted as absent, because at nine in the morning that difference is usually a phone call.

  • The live board

    Every person, site and shift with time at work, active time and offline time. Idle means the agent saw nothing, which is as often a meeting as it is a break, and the board says so.

  • Attendance

    A day scored against the shift rather than the clock. Somebody who starts early and leaves early has no shortfall, which is the entire point of having shifts.

  • Leave

    Requests, decisions, balances, carry-over and expiry. Sickness reported by phone is recorded as reported by phone rather than backdated into a tidy request.

  • Offline hours

    A site visit, a workshop, a laptop left at a desk. Anybody can claim the stretch the agent missed, and somebody has to decide it, which is why it is a queue and not an automatic adjustment.

  • Holidays

    A closure calendar per site, because remote staff follow where they live rather than where the company is registered. Days falling at a weekend are flagged with whatever your policy does about them.

  • Shifts

    Start, end, grace, paid and unpaid breaks, minimum hours, overtime thresholds and rounding. Rounding is to the minute rather than the quarter hour, because quarter-hour rounding always favours the same side.

  • Reports

    Hours against expected, absence by reason, lateness by weekday and overtime, by team and by site. Where the data has a gap the report says gap rather than absent.

  • Your day

    The employee sees their own hours, their own activity and their own breaks, and can claim anything missed. This is the screen that decides whether people accept the rest.

  • What is recorded about you

    A plain list of what the agent collects, what it does not, how long it is kept and who has looked. Every access is written to the audit log and the person can read it.

  • The desktop agent

    Clocks in, records whether input happened, names the application in front. It does not log keystrokes, cannot be installed silently, and can be paused visibly rather than in secret.

  • People and rollout

    Who is tracked, on what shift, and whether the agent is installed at all. Working without it is supported and the reporting gap is labelled instead of being counted as absence.

Permissions

Three roles, and the third one matters most

A monitoring tool people do not trust gets worked around, and then it measures nothing. The employee side is a real application: it shows the same numbers the manager sees, names everything that is collected, and lets somebody correct a day that is wrong.

  1. Administrator

    22 of 24 functions

    Sets the rules everything else is measured by

    Preview as an administrator
    • People, teams, shifts and sites
    • Shift rules: grace, breaks, minimum hours, rounding
    • Holiday calendars, per site
    • What the agent records, and whether screenshots are on at all
    • Retention periods and the audit log
  2. Manager

    14 of 24 functions

    Decides the things a rule cannot

    Preview as a manager
    • The live board across their teams and sites
    • Attendance by day, measured against the shift
    • Leave requests, with balances and cover visible
    • Offline-hour claims, approved or queried with a reason
    • Reports on hours, absence, lateness and overtime
  3. Employee

    7 of 24 functions

    Sees everything held about them

    Preview as an employee
    • Their own hours, activity and breaks for the day
    • Their leave balance, requests and decisions
    • A claim for any work the agent could not see
    • The full list of what is recorded, and for how long
    • A download of their own record, and the log of who looked

The build

Every function in the box

13 screens, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.

Access

  • Sign in

Today

  • Today
  • The board
  • Attendance
  • Reports

Requests

  • Leave
  • Offline hours
  • Holidays

Employee

  • Your day
  • Your profile
  • Desktop agent

Administration

  • People
  • Shifts

What you get

Delivered as a repository, not a login.

Operations and people teams running a rota on spreadsheets, a punch clock nobody trusts, or a monitoring tool staff have quietly worked out how to defeat.

  • 12 production functions spanning the manager side and the employee side
  • Full source code and PostgreSQL schema in your repository
  • Role-based access control, enforced server-side
  • Immutable audit log written on every change
  • Responsive layouts, usable on a phone, not just resized
  • CSV import and export on every core record
  • Deployment configuration for your cloud account
  • Twelve months of updates, and no per-seat charge ever

Access and evidence

Built to survive an audit

Recording how people spend their working day is the part that needs care. What is collected, who can see it, how long it is kept and how somebody corrects it are structural here, not a policy document filed once and forgotten.

  1. Row-level permissions, enforced server-side on every query
  2. An employee sees their own record in full and nobody else’s
  3. Every category of collected data named on screen, for the person it is about
  4. Screen capture off by default, and re-consented per person if it is ever enabled
  5. Activity data deleted after 90 days; attendance kept 6 years for payroll
  6. Corrections raise a request rather than silently overwriting a day
  7. Immutable audit log recording every read of a person’s record, readable by them

Related

Apps that pair with this one

HR & PortalsLive

Payroll

Pay runs and variance checks, inside the HR portal around them: attendance, leave, documents, benefits, onboarding and self-service.

5.0 out of 510 sold

From$799View details
HR & PortalsLive

Employee Hub

Announcements that require an action, tracked per employee, with reach reporting for managers.

4.5 out of 59 sold

From$649View details
Project ManagementLive

Site Operations

Daily logs, tasks, issues, drawings, approvals, change requests and punch lists across every site, for all six people who look at them.

4.5 out of 53 sold

From$699View details

Questions

Attendance Tracking, in practical terms

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultantAll questions
Do I get the source code for Attendance Tracking?

Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery. There is no licence key and nothing that calls home.

How many people can use it?

As many as you like. Pricing is per application, not per user, so every employee, manager and administrator can have an account at no extra cost.

How are shift rules configured?

In settings, without a developer. A shift pairs a start and end with a grace period, break rules, a minimum-hours threshold and the working days it applies to. Changing a rule applies from that day forward rather than restating history, so last month’s report does not move because somebody edited a shift today.

What can an employee see?

Their own record in full: hours, activity, breaks, leave balance, every category of data held about them, how long it is kept, and the log of who has looked at it. They cannot see anybody else. That visibility is deliberate, a monitoring tool people cannot inspect gets worked around, and then it measures nothing.

Does it take screenshots?

Not in the template. Screen capture is switched off for every role and stays off until somebody deliberately turns it on. If it is enabled, each person re-accepts before it starts, sees their own captures first, and images are deleted after seven days. Whether screen capture is lawful depends on where your staff are, so it is a decision for you and your own advisers rather than a default you inherit.

Can Attendance Tracking be changed to match our process?

That is the usual route. A fitted build adjusts shifts, grace and rounding rules, holiday calendars per site, what the agent collects, leave types and entitlements, branding and up to two integrations, and typically takes one to three weeks from a signed scope.

What does it cost to run?

Hosting only, paid to your own cloud provider, roughly $50 to $200 a month depending on order volume and document storage. There is no recurring fee to us unless you choose managed hosting.

Start here

Want Attendance Tracking shaped around your process?

A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.

  • No sign-up to open one
  • One-time price, no seats
  • Source code transferred on delivery