Skip to content

Guide · Rollout

How to introduce time tracking to your crews

To introduce time tracking to employees, tell them before anything arrives: what is recorded, when, who sees it and why you are changing. Answer privacy questions plainly, including what you cannot promise. Start with one pilot crew for a pay period, run the old method alongside it, and fix what the pilot finds before the rest of the company switches.

Last updated By ZeroBadge

When and how should you tell crews about time tracking?

Tell them before the device or the app shows up, in person, from someone they know, with time for questions. A change that arrives in a text on Sunday night reads as being watched. The same change explained at the Monday meeting by the superintendent reads as a decision with reasons.

  • Give a week of notice. Long enough to talk it over at the truck, short enough not to fester.
  • Use the people they trust. Foremen and the super carry more weight than the office does. Brief them first, and answer their questions before the crews ask the same ones.
  • Lead with the reason. Pay that matches the work, fewer corrections, no Friday sheet. Say it before you say how it works.
  • Put it in writing. A one-page notice they can keep, covering what is recorded, when, who sees it and how to raise a mistake.

How do you answer crews' privacy questions honestly?

Answer in specifics and say what you do not know. Crews can tell vague reassurance from a straight answer, and a promise you cannot keep costs you more than a limit you admitted to. The questions below come up on nearly every rollout.

Common privacy questions and plain answers
What they askA straight answer
Are you tracking me all the time?Only on the clock. Recording starts when the shift starts and stops when it ends. Outside of paid time, nothing is collected. (Say this only if it is true of your method.)
Is it on my phone?Not unless you chose a phone app. With a company-owned device, nothing goes on a personal phone, so there is nothing to see on it.
Who can see where I was?Name the roles: payroll, your supervisor, the owner. Say who cannot, and say the worker can see their own hours if your system allows it.
How long do you keep it?Give the actual figure. If you do not know it, find out before the meeting rather than guess.
Will this be used to fire me?It will be used to pay you correctly and to settle disputes. If it will also be used for discipline, say so, and say how you will treat everyone alike.
What happens if it is wrong?Corrections are made with a reason, in writing, and the worker can raise one. Estimates are estimates, and location is not exact.

The broader policy questions, such as drafting the notice, are in the construction time tracking guide.

Why start with a pilot crew, and how do you run one?

A pilot lets you find the problems with six people instead of sixty. Run one crew for a full pay period, keep the old method going alongside it, and compare. What you learn in two weeks decides how you brief everyone else.

  1. 1

    Pick the crew

    A foreman who is willing, six or so people and a mix of work: some days on one site, some on two. Skip the crew with the worst morale and the crew on the easiest job.

  2. 2

    Set what you will measure

    Pick two numbers before you start, such as exceptions per 100 shifts and the minutes the office spends on that crew's week. Without them, the pilot is just an opinion.

  3. 3

    Run both methods for one pay period

    The old method stays the source of truth for pay. The new one is compared against it, and every difference is sorted by cause.

  4. 4

    Meet once at the end

    Fifteen minutes with the foreman and two workers. What was confusing, what broke, what would they tell the next crew?

  5. 5

    Decide, then brief the next crew

    Use what the pilot crew said in the briefing. A worker explaining it to another worker lands better than the office doing it.

A pilot scorecard: exceptions per 100 shifts (illustrative numbers)

Week 1
14 exceptions across 60 shifts: 14 / 60 x 100 = 23.3 per 100
Week 2
5 exceptions across 60 shifts: 5 / 60 x 100 = 8.3 per 100
Change
23.3 - 8.3 = 15.0 per 100 shifts fewer
Reading
Exceptions fell by about two thirds as the habit settled

Early exceptions are mostly forgotten steps and missing end times. If week 2 had not improved, that points at the instructions or the device, not the crew. The shift counts are made up to show the arithmetic.

What should you say on day one?

Say four things: what to do at the start of the shift, what to do at the end, what to do when something goes wrong, and who to ask. Keep it to five minutes at the truck and hand each person the one-page notice.

A day-one script for a crew meeting

  1. Minute 0 to 1Why: pay that matches the work, no more Friday sheets, fewer arguments over a day nobody wrote down.
  2. Minute 1 to 2What is recorded and when: your shift, which site, and nothing outside paid time. Who sees it.
  3. Minute 2 to 3What each person does: how to start, how to end, how to charge or turn in the device if you use one.
  4. Minute 3 to 4If you forget or it fails: tell the foreman, and the hours get fixed with a note. Nobody loses pay for the device failing.
  5. Minute 4 to 5Questions. Answer what you can and write down what you cannot, then come back with the answer the next day.

Check in with the pilot foreman at lunch and again at the end of the day. Most day-one problems are one forgotten step, and fixing them on the same day is what builds trust.

How do you handle pushback?

Listen first, answer the specific objection, and change what you can. Pushback usually points at something real, such as a rule that docks pay too hard or a worry about what the data is for. Treat it as information.

Common objections and responses
What you hearWhat is usually behind itWhat helps
You do not trust usTracking feels like an accusationExplain the pay and dispute benefits, and apply rules equally to foremen and office staff
I do not want it on my phonePersonal device, personal data planUse company-owned equipment, or pay for the phone use and say so in writing
It will get me in trouble over small stuffA strict grace rule or a history of write-upsLook at the grace rule, and say what a one-off miss will and will not lead to
The old way worked fineHabit, and fear the new way will be worseShow the pilot crew's numbers and let a worker answer it
What if it breaks?Fear of losing pay for something not their faultState a fallback and put it in the notice: report it, get it fixed with a note, no loss of pay

A real objection is not a reason to quit the rollout. It is a reason to change one thing and tell people you did.

What should be ready before the first crew starts?

  • A one-page notice that says what is recorded, when, who sees it and how long it is kept.
  • Foremen and the super briefed first and able to answer the same questions.
  • A written fallback for a forgotten or failed device, with no loss of pay.
  • A pilot crew, two metrics and a date to review them.
  • The old method still running for one pay period.
  • Notice, consent and union steps checked with counsel where they apply.
  • A named person crews can call with a problem.

For the full switch plan from paper, see how to switch from paper timesheets and the replace paper timesheets page. The cost side is in the hidden cost of paper timesheets.

How ZeroBadge handles this

ZeroBadge badges are company-issued and company-managed, so nothing goes on a worker's personal phone and no app or login is needed. Tracking runs during paid shifts, and badges are powered off between shifts. Raw location history is deleted after 90 days and timesheets are kept. An optional worker portal lets people see their own hours and request corrections. A badge records the badge, not who wears it, and location answers which jobsite, not which room. Time tracking without phones is covered in time tracking without phones.

Frequently asked questions

How do I tell employees we are starting to track their time?
Brief the foremen first, then tell crews in person about a week before the change, with a one-page notice. Cover what is recorded, when, who sees it and why. Leave time for questions.
Do I need employee consent to track time with GPS or a badge?
It depends on your state, your contract and your method. Some states require written notice or consent before monitoring, and union agreements often require bargaining. See is it legal to GPS track employees. This is general information, not legal advice.
Will workers be tracked outside work hours?
Not with a company-issued badge that is powered off between shifts. Tracking runs during paid shifts. If you use a phone app instead, say plainly whether location is collected off the clock, and set it up so it is not.
How long should a pilot run?
One full pay period for one crew, with the old method running alongside. That is long enough to cover a payroll cycle, a few exceptions and one end-of-week review.
What if workers refuse to use it?
Find the reason first. It is often a rule, not the device. Where a refusal continues, follow your written policy and any agreement, and ask counsel before taking action on pay or employment.

Get started

See ZeroBadge on your workforce.

Tell us how your crews work today. We will show you a badge-recorded week built from your own jobsites.

What we will walk through

  • 01How the badge records a shift
  • 02Your jobsites as geofences
  • 03The weekly timesheet and approval
  • 04Sending approved hours to payroll