Cutaway miniature office: two floors of desks above an entrance turnstile, on a navy plinth.
Example workflow · Illustrative demo6 running todayFor HR heads, principals, branch managers and finance

F · People, Attendance & Workforce

Who came, who approved, who did what.

Attendance from the cameras at the door, payroll from the same record, a login and an approval limit for each person, and every decision logged.

Illustration

01 · The problem

Attendance is argued over at month end, payroll is rebuilt in a spreadsheet, and shared passwords mean nobody knows who approved what.

Policy changes are announced in a group chat and never confirmed as read.

Who it is for: HR heads, principals, branch managers and finance.

02 · How it works

The workflow, stage by stage.

  1. 01Marked at the door
  2. 02Exceptions raised the same morning
  3. 03Manager confirms or asks
  4. 04Payroll reads the same record
  5. 05Every change logged with who and when

03 · Try it

Attendance and limits, with sample data.

An illustrative demo for a fictional organisation. Click through it; nothing is sent, paid or changed anywhere.

Attendance and limits · Illustrative demo
Attendance · Tuesday 7 October · head office
Present
21 of 24 marked at the door by 9:15
Exceptions
2 late, 1 not marked: each sent to the manager
Leave
1 approved by the line manager, within her limit
Payroll
Reads the confirmed record; nothing is retyped

Example output · sample data for a fictional organisation

04 · Example output

What lands on someone’s desk.

The kind of page this module produces each day, shown with sample figures.

Attendance · Tuesday 7 October · head office
Present
21 of 24 marked at the door by 9:15
Exceptions
2 late, 1 not marked: each sent to the manager
Leave
1 approved by the line manager, within her limit
Payroll
Reads the confirmed record; nothing is retyped

Example output · sample data for a fictional organisation

05 · Capabilities

What runs today, and what we would build.

Status as of 4 October 2026.

  • RunningIn daily use, in our own organisations or at a client.
  • Done onceA service delivered once, as a written finding.
  • PlannedIn our planned range. Intended, not yet built.
  • ConceptAn idea shown to explore what we can build.

Running today

  • Camera attendanceAttendance marked from the cameras at the door, every day at our own campuses.
    Running
  • PayrollPayroll from the same record as attendance and leave.
    Running
  • Logins and approval limitsA login per person, limits per role, every decision logged.
    Running
  • Acknowledged updatesEach policy change confirmed as read.
    Running
  • Floor assistantStaff on the floor ask how a task is done and get the answer from your manuals.
    Running
  • PerformanceEach person’s few numbers that matter, from the work itself.
    Running

Explore what we can build

  • One login for everythingEach person signs in once, sees only their own work, and loses access the day they leave.Your DS or your own servers
    Planned
  • Expense claims and petty cashA claim made from a phone with a photo of the receipt, approved by limit, paid and posted.Your DS or your own servers
    Planned
  • Help deskEvery internal request logged, assigned, timed and closed.Your DS or your own servers
    Planned

Nothing in this list is claimed as running. Each would be scoped in a written finding and delivered one department at a time.

06 · How it connects

Part of one record, not a separate tool.

Tracer

Tracer tells the head of HR what needs a decision today: exceptions, leave and approvals waiting.

Atelier OS

People, payroll and approvals sit on the same record as money and operations.

Where it runs

Where attendance images are processed and kept is written into your data schedule before anything is installed.

Connections

The cameras at the door, your bank for salary payments, email and WhatsApp for notices.