If you pay any part of your crew by the piece instead of by the hour, a normal time clock does not tell you what actually matters. You need to know how many bricks got laid, how many yards got poured, how many units got installed. Not just how many hours someone stood on the job site.

Piece-rate work (some call it piecework, some call it production pay, some call it piece-rate payroll) is common in trades like masonry, concrete, scaffolding, and asphalt, where production speed varies by crew and by job. Whatever term your office uses for it, the tracking problem is the same. Here’s a quick look at how it works in CrewTracks:

Why generic time tracking doesn’t work for piece-rate crews

Most time tracking apps were built for hourly work. They log a clock-in and a clock-out, and that’s the whole story. They have no idea what “brick,” “yard,” or “linear foot” means to your business, because they were never built to know.

That gap forces a lot of companies back to paper logs or a spreadsheet someone reconstructs at the end of the week from memory and a foreman’s notes. By the time the numbers make it to the office, they’re late, and nobody is fully sure they’re right.

And a stopwatch alone doesn’t tell you what you actually need to know for piece-rate pay anyway. Two workers can clock the same eight hours and produce very different amounts of work. Piece-rate pay exists specifically to reward output, not just time on-site, so the software tracking it has to be built around output first.

How CrewTracks tracks piece-rate production

CrewTracks lets you set up a production unit for any job item, and that unit can be whatever your crew actually uses. Bricks, tons, squares, linear feet, cubic yards, whatever your bid was written in. There’s no preset list to work around. If your foreman calls it something specific, that’s what goes in the system.

Workers log production from the field on their phone or tablet as the day happens, not from memory at 4pm on Friday. You can track production by crew or by individual worker, depending on how the job is paid. For piece-rate work specifically, tracking by individual worker is what makes the numbers usable, because that’s the number that eventually turns into a paycheck.

Here’s what logging production looks like on an iPad in the field:

Set a production budget and watch it update as the job runs

When you set up a job item, you can also set a production budget, the total units you expect to complete. Say a job is bid at 8,500 bricks. Set that number once, and CrewTracks tracks actual production against it automatically as workers log units in the field.

You can see budget versus actual while the job is still running, not two weeks after it closes. And if you want to stop production once a budget is hit (say, to catch a scope change before more work gets logged against it), you can require approval before anyone submits units past the budget.

If you’re also using CrewTracks for time tracking, you can pair that with production data to see each worker’s hourly production rate and flag whether they’re on pace to finish the job in the expected time:

How do you track and calculate piece rate pay with CrewTracks?

CrewTracks tracks the units. Your office calculates the pay.

To be specific: CrewTracks records exactly how many units each worker produced, by whatever unit your job uses, logged from the field in real time and backed by a clear record instead of a guess. What CrewTracks does not do is multiply those units by a pay rate and cut a check. That math, units times the agreed rate, still happens on your side, in whatever payroll or accounting process you already run.

That’s a deliberate line, not a missing feature. Piece rates change by job, by region, by union agreement, sometimes by worker. Keeping that rate math in your office means you stay in control of it instead of trusting a black box to get it right. What CrewTracks gives you is the one thing that’s genuinely hard to get right by hand: an accurate, timestamped count of what each person actually produced, so the number you’re multiplying is one you can trust.

In practice, the math itself is simple once the units are right: units produced times the agreed rate equals pay. If a worker’s rate is per brick and CrewTracks shows 500 bricks logged against their name for the day, your office multiplies 500 by that rate to get the day’s pay. The part that used to be hard, and the part that CrewTracks solves, is trusting that “500” in the first place.

If you’re looking for software that calculates the paycheck for you automatically, that’s not what CrewTracks is. If you want the production numbers to be right so your office can do that math with confidence, that’s exactly what it’s built for.

Built for the trades that already run this way

Masonry, concrete, scaffolding, and asphalt crews have been running piece-rate and production-based pay for a long time, usually with a clipboard and a lot of trust. CrewTracks was built around how these trades actually bid and run jobs, not adapted from a general time clock app after the fact. That’s also why the production unit is fully custom instead of a dropdown of presets. Your crew already has its own vocabulary for the work, and the software should use it too.

For a step-by-step look at setting up a piece-rate job in the system, see Using CrewTracks for Tracking Piece-Rate Work.

If you want to see how CrewTracks would handle piece-rate tracking for your crew’s specific units and jobs, talk to us. We’ll walk through your setup with you before you commit to anything.