Seeing your team's hours without micromanaging

What you actually need to know

Start with the question, not the tool. Most managers of hourly staff and contractors need three things: how many hours each person worked, what they worked on, and whether a project is running over. For employees, you already have to record the first. Section 130 of the Employment Relations Act 2000 requires a record of the hours each employee works each day in a pay period, and the pay for those hours.

What you rarely need is everything else that monitoring software offers: location all day, screenshots, keystrokes, or minute-by-minute activity. Each of those collects far more than the hours, and each sends a message about how much you trust the people doing the work. Employment New Zealand makes the same point: employees might not feel trusted if they are monitored, and that can affect morale and productivity.

Consent and the Privacy Act

The Privacy Act 2020 does not make consent the test for most collection. It asks other questions, set out in its information privacy principles:

• Principle 1: collect personal information only for a lawful purpose connected with your business, and only if it is necessary for that purpose.
• Principle 3: make sure people know what you are collecting, why, who will see it, and that they can ask to see and correct it.
• Principle 4: collect it fairly, in a way that does not intrude unreasonably on their personal affairs.
• Principle 3A, in force since 1 May 2026: if you collect information about someone from another source, such as a client's site log, take reasonable steps to tell them.

The Privacy Commissioner puts it simply: an employer cannot collect information just because it can, and has to be able to justify why it needs it. If an app provider holds the data for you, the Act treats it as held by you, so the responsibility stays yours. Employment New Zealand's advice for any monitoring is a written policy explaining why and when, consultation with staff and any union, and making sure everyone knows about it.

Biometric clock-ins raise the bar further. The Biometric Processing Privacy Code 2025 has applied to new biometric processing since 3 November 2025, and to processing already under way since 3 August 2026. Its rule 1 asks whether your purpose could be achieved as effectively by an alternative with less privacy risk. For recording hours, there usually is one. Our article on clock-in apps, GPS and fingerprints covers what employees are told about these systems.

The law does not ask you to get consent before recording hours, but asking for it is still the strongest position. A person who chose to share their hours knows exactly what you see and why, which goes a long way to meeting principles 3 and 4 before anyone asks.

Why notes and pay stay private

A timesheet note can hold far more than work: a medical appointment, a child's sick day, a reason for leaving early. Under principle 1, a project view does not need any of that, so the safer default is that notes stay with the person unless they choose to share them.

The same goes for pay. You already hold each person's pay rate in payroll, and a project view does not need it on screen beside their hours. Nor do you need to know about other jobs or clients they work for, as long as their work for you is recorded. Leaving those out is not a favour to staff. It is the necessity test in principle 1, applied honestly.

Budgets instead of surveillance

Most of what micromanagement tries to catch, a budget catches better. Set each project a budget in hours, and watch the total rather than the person. When a project passes most of its budget, ask the team what is happening with the work, not who took a long lunch.

The same goes for gaps. A list of who has not logged this week is a reminder to send, not a case to build. People who log their own hours honestly, and see them used fairly, keep logging them. Our guide to keeping your own timesheet shows the habits that make a self-kept record reliable, start and finish times rather than totals among them.

Team timesheets from jobtracker.co.nz is built that way: each person logs in their own Your Timesheets and chooses whether to share, you see hours by person, project and task with budgets past 80% highlighted, and you never see their pay, rates, other jobs or job hunt, at $6.99 a seat a month, GST included, for at least three seats.

Trust that survives someone leaving

Trust is tested when someone stops sharing or leaves. If they can take every record with them, you have nothing to check payroll against. If you can keep everything, including their notes, they had little reason to share in the first place.

A fair middle is a read-only copy of the hours they shared, without notes, kept as your record. In Team timesheets, that copy is kept for seven years from the date of each entry, or until 90 days after you close the team, whichever comes first, and their own timesheets stay theirs. Principle 9 of the Privacy Act says not to keep personal information longer than you need it for a lawful purpose, so decide how long you need hours records, at least the six years wage records require, and write it into your policy.

Hours on one page, with their say-so