Standard package · on subscription

Recording time. Not behaviour.

For consultancy and secondment firms that track chargeable hours per customer and assignment, and for teams on the shop floor. Hours per project, a weekly timesheet with approval, leave and reporting, without monitoring people. You subscribe to the modules you use; we manage and update them.

Ask about a pilot See the example first

Five modulesOn one base with login, roles and audit log
No monitoringNo screen recordings, no keystrokes
Timesheet with approvalSubmit, approve, correct with a reason
Chargeable hoursPer customer, assignment and consultant, ready for your accounting package

01 — Try the example

Modular

Switch a module on or off and see what happens to the screen.

Every module is a switch, not a new project. Click through the menu, submit a timesheet, open a project, and add leave and reporting as soon as you need them. The base is always there.

Example screen

Time tracking

Click through the menu on the left, submit a timesheet, open a project or a leave request, and switch modules on or off. Everything you see is made up.

Base

3 of 5 modules active

Signed in as Jasper · employee

Fictional example

Today

Tuesday 22 September · week 39

01:24:07Running now · Installer B · planning boardStarted at 09:12

2:39Booked today3 lines

38Hours week 38Approved by Sanne

88%Bakery A · appBudget nearly used up

11.5Leave days left1 request open

Today

Installer B · planning boardDesign · running since 09:1201:24:07
Bakery A · ordering appMeeting0:45
InternalWeek start0:30
Timesheet week 39Not yet submittedOpen

Notifications

yesterdayTimesheet week 38 approved by Sanne, 38 hours
yesterdayBakery A · app at 88% of budget
FriLeave request 20–24 Oct awaiting approval
FriAbsent this week: 2 colleagues, staffing in order
MonSigned in with two-step verification

Timesheet

Week 39 · 21 to 25 September · Jasper

Project	Mon	Tue	Wed	Thu	Fri	Total
Installer B · planning board	5.25	1.5	·	·	·	6.75
Bakery A · ordering app	·	0.75	·	·	·	0.75
Foundation C · intake	2	·	·	·	·	2
Internal	0.75	0.5	·	·	·	1.25
Total	8	2.75	·	·	·	10.75

Open This week is still running; you can submit on Friday or earlier.

Last week · week 38

8Mon

7.5Tue

8Wed

8Thu

6.5Fri

Approved 38 hours · approved by Sanne on Monday · one correction with reason: "Friday, 0.5 hours travel time added"

Projects

3 running · 1 completed this quarter

Installer B · planning boardBudget 100 hours · started 1 Sep · chargeable

62%

Design42 h
Build15 h
Meetings5 h

Per employee

Jasper: 38 hours
Mo: 24 hours

Invoicing

12.5 chargeable hours from the approved timesheet for week 38 are ready for your accounting package or ERP.

Reporting

September 2026 · whole team

612 hours in September

Chargeable74% · 453 h
Internal18% · 110 h
Leave and sickness8% · 49 h

Totals per employee

Employee	Chargeable	Internal	Absent	Total
Jasper	124	22	8	154
Mo	118	30	16	164
Sanne	96	40	9	145
Lieke	115	18	16	149

Totals only. No activity log, no screen recordings, no keystrokes: the package does not record those.

Design principle: the package records time, not behaviour. No screen recordings and no logging of keystrokes. A line manager sees hours per project, not what someone is doing.

All names and figures in this example are made up.

Ask about a pilot

02 — What each module does

Base plus five modules

Hours that add up, without the hassle at the end of the week.

The base handles who may log in and what has happened. Every module on top of it does one thing well and works together with the rest.

Base
Login, roles and audit log

Always included, even if you start with one module.
- Login with two-step verification
- Roles: administrator, line manager and staff member
- Audit log of who changed what and when
- Works on phone, tablet and computer
01
Clock hours

Clock live or fill in afterwards, per project and per task.
- Start and stop on your phone, also on the go
- Fill in afterwards with a start and end time or a number of hours
- Frequently used projects at the top
- A note per line, no mandatory description
02
Timesheet

One overview per week: submit, approve and done.
- Hours per day and per project on one screen
- Submitted by the staff member, approved by the line manager
- Corrections only with a reason, visible in the audit log
- Reminder if a timesheet remains open
03
Projects

Budget in hours, progress and who is working on it.
- Hours per project against the budget
- Warning at 80 and 100 per cent
- Chargeable or internal, per project, customer and assignment
- Completed projects are kept for post-calculation
04
Leave

Balance, requests and staffing, without separate emails.
- Balance per staff member, accrued and taken
- Request and approval in the app
- Staffing per week: who is in, who is not
- Sickness and special leave recorded separately
05
Reporting

Where the time goes, per project, customer, staff member and period.
- Chargeable versus internal and absent
- Per project and per customer, also across several months
- Chargeable hours on to your accounting package, overview for payroll
- Only totals per person, no activity log

03 — What we have already built

Anonymised

The building blocks come from these projects.

Three projects in which hours, rosters and staffing were central, without customer names. What is in use is in use; what is a design, we call a design.

Business services · secondment

Timesheet and approval as part of a CRM design

For a secondment agency we designed a CRM with an hours module: a timesheet per seconded staff member, approval by the assignment lead and reporting per assignment. In the end the customer kept only the planned deployment per assignment; the timesheet and the approval flow from that design form the basis of this module.
- Timesheet per staff member, per assignment
- Approval with feedback on rejection
- Hours reporting per assignment and per customer
DesignClickable, with fictional data
Trade · human resources

Calculation tool for overtime: pay out or time off in lieu

An internal tool for the HR administration of a trading company. For each staff member it calculates what paying out overtime means compared with time off in lieu, including the consequences for allowances, and puts that in a chart.
- Calculation per staff member, behind its own login
- Consequences for allowances visible in one chart
- Advice in plain language, generated on request
In useInternal tool, behind its own login
Healthcare · veterinary clinic with three sites

Roster and staffing with travel time and qualifications as hard rules

A clickable design for a clinic whose branch sites run on people from the main site. Travel time between sites, qualifications per shift and opening hours are hard rules; the roster shows where it pinches.
- Shifts as chains of segments across sites
- Bottlenecks per day visible, with the reason
- Fictional staff members, realistic team size
DesignClickable, with fictional data

We do not name customers on this site. In a conversation we show more, with the customer's permission.

04 — Principles

Time, not behaviour

Time tracking should build trust. Not take it away.

There are packages on the market that make screen recordings and count keystrokes. We deliberately do not do that. These agreements apply to this package and are set out in the data processing agreement.

Hours only
The package records start, end and project. No screen recordings, no keystrokes, no websites, no location.
The staff member sees everything about themselves
Their own hours, their own timesheets, their own balance, and who approved them.
The line manager sees hours per project
Not what someone is doing, but how much time goes to which project. That is what a planning and an invoice need.
Corrections with a reason
Nobody silently changes an approved timesheet. Every correction has a reason and is in the audit log.
Works council
A system that records staff hours can fall under the works council's right of consent. We provide the description of what the package does and does not record, so that this assessment can take place.
Your data remains yours
Hosted in the European Union. You can take your data with you at any time; at the end of the subscription you receive it and we delete it.

05 — Works together with

One base

The same users, permissions and audit log for every package.

Packages work together because they sit on the same base. And whatever does not quite fit, we build to measure alongside.

06 — Practical

Subscription, pilot and switching

What you get, and what you arrange in advance.

Subscription: Per month, per package and per module. Management, updates, backups and hosting are included. No server or administrator of your own is needed.
Pilot: You try the package with a small team, for a few weeks. Then you decide whether to continue and with which modules.
Set-up: Together in a few half-days: your team, your projects, who approves what, and your leave rules. You import staff members and projects from an Excel file.
Staff: In advance you agree with your team and, if you have one, your works council what is recorded. We provide the description for that.

Curious whether this time tracking suits your team?

In a half-hour conversation we discuss what you want to know about your hours, what you deliberately do not want to record, and which modules go with that.

Ask about a pilot

Recording time. Not behaviour.

Switch a module on or off and see what happens to the screen.

Today

Today

Notifications

Clock hours

Fill in afterwards

Tuesday 22 September · 2:39 booked

Monday 21 September · 8:00 booked

Your frequently used projects

Timesheet

Last week · week 38

Projects

Per employee

Invoicing

Per employee

Per employee

Leave and attendance

My requests

Team this week

Reporting

612 hours in September

Hours per project

Chargeable hours per customer

Totals per employee

Hours that add up, without the hassle at the end of the week.

Login, roles and audit log

Clock hours

Timesheet

Projects

Leave

Reporting

The building blocks come from these projects.

Timesheet and approval as part of a CRM design

Calculation tool for overtime: pay out or time off in lieu

Roster and staffing with travel time and qualifications as hard rules

Time tracking should build trust. Not take it away.

Hours only

The staff member sees everything about themselves

The line manager sees hours per project

Corrections with a reason

Works council

Your data remains yours

The same users, permissions and audit log for every package.

CRM

Machine dashboard

Custom work alongside

What you get, and what you arrange in advance.

Curious whether this time tracking suits your team?