VIEW MORE

Designing friction to save everyone time

Problem indicator - frame 1 of 5

Inaccurate worker time entries made contractors distrust our system & left the ops team cleaning up payroll for 3 days

Solution indicator - frame 1 of 3

Redesigning the time tracking flow resulted in fewer errors, more accurate hrs from workers, & reduced days of manual payroll cleanup

Role & Scope

Staff Product Designer
Iterative Design
Data Analysis
Design Systems
Interaction Design
Mobile App
Research
Visual Design
Web App

Duration

6 weeks · 2024

Team

Buildforce
Colin Harman
Lillian Situ
Mark Di Marco
Michael Harman
Buildforce time tracking app.

[I]

Final Design & Outcomes

Workers fixed their own time, contractors edited less, and ops finally didn’t have to spend half their week supporting payroll.

Once we released time tracking v2, everyone did less but in the best way. Workers made more accurate submissions up front, contractors barely had to touch them because they aligned with their own logs, and our ops team didn’t have to mediate every payroll cycle. The time tracking system stopped being a problem that needed constant fixing. It wasn’t perfect, but it was going to help us scale the business.

Downward trend - frame 1 of 4

42%

Less edits made by all parties

~2,500 → ~1,450 edits/wk

Upward trend - frame 1 of 4

15%

Workers corrected their own time

~35% to ~50%

Downward trend - frame 1 of 4

21%

Contractors/ops had to fix less

~45% to ~24%

Upward trend - frame 1 of 4

20%

More time approved without intervention

~55% to ~75%

Time tracking for Buildforce worker app

I redesigned the time entry flow to show workers exactly what the contractor sees. It made workers pause and think.

The new flow added a summary screen that showed workers their exact clock-in and clock-out locations on a map just like the contractor would see it. This made mistakes more obvious and accountability more real. We also added automatic rounding to the nearest 15 minutes and snapped unusually long shifts to the project schedule, so payroll ops didn’t have to clean up the mess later. What workers saw matched what was sent to contractors. That small shift in visibility and friction made a huuuge difference.
Electrician clock-out flow in the Buildforce web app

The new clock-out flow adds friction and clarity; I designed a step-by-step review with location data and 15-minute rounding, so workers know exactly what gets submitted.

Letting workers edit time throughout the week sounded like a logical improvement. Most didn’t do it.

I designed a way for workers to review and edit time entries anytime before they were submitted to contractors. In theory, it gave them more flexibility. In practice, almost not many used it. My guess is either they nailed it on the first try (best case), didn’t know they could make edits later (plausible), or still assumed the contractor was ultimately in charge of time (unfortunately still true in some cases).
Worker time entry edit flow in Trades app

End-of-week flow to double-check entries before it auto-submits on Monday. Similar to the old design, but workers can edit throughout the week and don’t have to explicitly “submit“ hours.

Contractors used worker data to resolve disputes, and workers could challenge edits without needing us.

We added clock-in and clock-out maps to give contractors a clearer view of when and where shifts started and ended. We didn’t have direct metrics on trust, but we saw contractors using that data to settle disputes, which in my view suggests they believed it. On the flip side, workers were notified when their time was approved or changed and could dispute it directly. Instead of ops chasing people down, both sides had the info they needed. Our team went from spending 3 days a week resolving time disputes to just a couple of hours.
Contractor time approval screen detailing worker time entry

Contractors can view location and time entry details for each worker. This helped build trust in the system, even though the main approval surface stayed unchanged aside from new brand styling.

Trades app showing contractor adjusting worker total hours and option to dispute the change

Workers are notified when time is approved or edited so they can dispute issues directly. This removed ops from having to chase down confirmations.

Trades app showing contractor adjusting worker total hours
Buildforce electrician using mobile phone

[II]

Problem Framing

Workers were submitting hours that didn’t reflect reality, so contractors and our ops team had to clean up the mess in time to run payroll every week.

Clock-in and clock-out times were all over the place, sometimes showing 24-hour shifts, other times missing entire days. Some clocked out hours after their shift ended, or forgot entirely and only noticed when clocking in the next day. Many workers didn’t review their time before submitting. This led to inaccurate time sheets getting sent to contractors and a cascade of manual corrections later.
Trades app clockout flow in previous version

Our time tracking system works like a stopwatch: easy to forget. Most workers forget to clock in or out, and about 65% of these time entries go uncorrected.

Trades app submit time flow at the start of the following week in previous version

Workers get a second chance to fix their hours at the start of the week but most skip it, either unaware or assuming the original entry is “good enough.“

Contractors didn’t trust the hours and inputted their own time sheets. As a result, our ops team spent 3 days of their week untangling the truth.

Each week followed the same painful pattern. Our payroll team rounded worker-reported hours and sent them to contractors, who cross-checked them against their own logs usually treating theirs as the source of truth. When the numbers didn&’;t match (which happened a lot), payroll and support ops were left sorting it out. That meant chasing foremen, piecing together timelines, and trying to resolve disputes with limited context. Workers were often left in the dark sometimes waiting weeks to get paid correctly.
Contractor time approval in previous version

Contractors use this web app surface to approve worker hours but usually end up editing them. They often overwrite worker entries to match time sheets from their own systems.

The system created friction for contractors, gave workers little feedback, and left ops stuck in the middle.

Hiring through Buildforce was supposed to be easier, but our time tracking flow added more overhead for contractors. Many already had systems in place, so using ours felt like extra work... not an upgrade. On the worker side, the flow was too easy to speed through (they didn’t know they were doing anything wrong) and too hard to correct later. Meanwhile, our ops team was stretched thin, manually reconciling time across three disconnected perspectives.

Workers didn’t review or correct their hours with ~65% of entries were submitted without worker edits

Contractors often ignored worker-submitted time with 45% of entries edited by contractors

Ops had to intervene constantly with only ~55% of time sheets getting auto-approved

How & why did we start using the Shape Up process?
How did we tackle product education, comms and support?
How did we introduce a brand refresh alongside this work?
Which decisions kept us on the worker's side?
What challenges arose throughout the project?

The Nitty Gritty

Want the Details?