Time Tracking for Solar Installers: Labor by Project Across a Multi-Day Array

A solar install isn't a shift. It's a project that runs across several days, moves through distinct phases, and often has two crews at two addresses on the same morning. Racking goes up one day. Modules and rail land the next. The electrician sets the inverter and pulls the DC and AC runs after that. Then everything stops until the utility and the AHJ sign off.

By the time the array is producing, the labor that built it's scattered across four or five calendar days and two or three crew members. If you're tracking hours on paper or in a group text, you can't say what that array actually cost you to install.

This guide is about the method: how to capture labor by project across a multi-day array. When the job closes you know your real cost per install, your crews stay coordinated across sites, and payroll exports clean without a Sunday-night reconstruction. If you want the case for why Clox fits solar specifically, that lives on the solar installers page. Here we're talking about the workflow.

01

The 6:45 a.m. reality on a solar crew

The lead pulls into the yard before seven, loads rail and clamps and a couple of pallets of modules, and reads off the day. One truck goes to the residential reroof-and-mount on the north side, the other to the ground-mount out past the county line where there's barely a bar of signal. Both are the same job in your head, but they're different addresses, different crews, and possibly different phases of two different arrays.

The thing that breaks tracking here is not laziness. It's that the person who knows which hours belong to which array is on a roof with nitrile gloves on, and the person who needs that number for the invoice is at a desk two days later. The gap between those two people is where cost data gets lost.

The fix is to move the tagging to the moment of the punch, on the phone that's already in the installer's pocket, so nobody has to remember anything after the fact.

What a solar crew actually bills by

Roofers bill by the square. Framers bill by the linear foot. Solar installers bill the customer by the system, usually priced off watts or kilowatts, but you don't cost the job that way. You cost it in labor hours against the array.

A 9.6 kW residential rooftop and an 11 kW ground-mount can quote within a few hundred dollars of each other and cost you wildly different labor. The ground-mount ate two extra days in trenching and pier setting, and the rooftop ate a half day fighting an old shake roof. You only find that out if every hour was tagged to the array while it happened.

02

The method: one project per array, tagged at the punch

The whole method comes down to a single discipline. Every array you install is one project. Every installer, every day, clocks in against that project from the phone before the first module comes off the truck. When the punch carries the project tag, the labor sorts itself. You're not reconstructing anything at the end of the week; the hours were already in the right bucket the moment they were worked.

Setting this up on your own crew takes an afternoon, not a rollout. You can start a free trial and put your next job on it today. It runs 14 days, needs no card, and is backed by a 30-day money-back guarantee.

In practice this means you create the project once, when the job is sold. Name it something the crew will recognize on a phone at 6:45 a.m.: the customer name and the address, not an internal job number nobody memorized.

From then on the installer's clock-in screen shows the array they're assigned to, they tap once, and they're on the clock against that project. When the crew splits to a second site, the second crew clocks in against the second array. Two addresses, two projects, zero confusion at payroll.

Multi-day and multi-phase, without losing the thread

Because the project outlives the day, the multi-day array stops being a tracking problem. Racking day, module day, electrical day, and commissioning day all land against the same project. When you pull the report, you see the full labor arc of that install:

• How many hours went in before the inverter was even set.
• How much the inspection-day wait cost you.
• Whether the second crew you sent on day three actually shortened the schedule or just added hours.

How one array accumulates labor across a typical multi-day install. Illustrative hours. Every row is a phase tagged to the same project, so the total is your real labor cost for that array.

That 73-hour total is the number you could never get cleanly off paper timecards, because on paper the hours were organized by person and week, not by array and phase. Tag at the punch and the array view assembles itself.

03

Keeping two crews coordinated across two sites

Solar rarely runs one crew on one roof all week. You have a racking crew finishing one array while the electrical crew starts the next, and a lead bouncing between both. Scheduling the shift against the array, and enforcing clock-in only during that scheduled window, keeps the two from bleeding into each other. If an installer is scheduled on the ground-mount today, that's the project their clock-in offers, and their hours can't accidentally land on yesterday's rooftop.

For a lead who genuinely splits a day across two arrays, the move is simple: clock out of the first project when they leave, clock in to the second when they arrive. Two clean punches, two clean buckets, no mental math at the end of the week about how to divide their eight hours.

If you fence a single residential worksite so clock-ins are locked to that address, that's a deterrent worth setting up. We won't re-explain how geofencing works here; the mechanics live in the geofencing pillar.

04

Roofs and rural sites: the punch has to work with no signal

A residential rooftop with the truck parked in a dead zone, or a ground-mount an hour out of town, is exactly where a cloud time clock quietly fails. The installer taps clock-in, sees a spinner, and either gives up or writes a time on their hand to enter later. Both outcomes corrupt your cost data.

The punch has to be captured on the device the instant it happens and sync when a bar of signal comes back, so the timestamp is the real one and not a guess typed in from the parking lot.

This isn't a nice-to-have for solar. Ground-mounts and rural residential are a real share of the work, and if half your installs are in weak coverage, an online-only time clock is systematically undercounting the hours on your hardest, most labor-intensive jobs. Offline capture is what keeps those arrays honest in your numbers.

05

Reading cost per array, then bidding the next one from it

Once every array carries its own tagged labor, the report is where the method pays off. You're no longer asking "how many hours did the crew work last week." You're asking "what did the Delgado array cost me to install, and how does that compare to the last three like it." That's the question that protects your margin as you take on more systems than you can hold in your head.

The payoff loop is the same one every trade wants and few actually close: bid the next array from the actual hours of the last one, not from memory. If your last three comparable rooftops came in fifteen to twenty hours over the phase estimate, you bake that into the next quote and stop giving margin away one array at a time.

For the broader version of this argument across trades, the small-crew job-costing guide walks through the bid-versus-actual habit in detail.

06

Clean export, so payroll is not a reconstruction

The last mile is payroll, and this is where tagged hours save the office its worst afternoon. Because overtime and break math are already handled and every hour is already bucketed, you export once and hand it off. Clox exports to:

• Gusto, ADP RUN, ADP Workforce Now, and Paychex Flex.
• QuickBooks Online as CSV, or an optional live QuickBooks Online sync.
• QuickBooks Desktop as IIF.
• Zapier if you want it automated.

Overtime that spans a multi-day array is calculated for you rather than reassembled by hand.

There's one more solar-specific benefit to tagged, exported hours. When a manager edits a shift after the fact, the crew member's certification of that shift is cleared and they re-certify, and the record is tamper-evident once captured.

That matters on solar because so much of the labor happens where nobody in the office was watching. Being able to show a clean, integrity-checked labor record per array is useful when a homeowner questions an invoice or a commercial GC wants backup for a change order.

07

The method in five steps

1. One project per array. Create it when the job sells, name it by customer and address so the crew recognizes it on a phone.
2. Tag at the punch. Every installer clocks in against the array before the first module comes off the truck. No after-the-fact reconstruction.
3. Schedule split crews against the array. Enforcement windows keep two sites from bleeding hours into each other; the lead clocks out and back in when they move.
4. Trust the offline punch. Roof and rural clock-ins capture on the device and sync later, so your hardest arrays are counted accurately.
5. Read the array, then bid the next one from it. Cost per array in the report; export clean to payroll; feed the actuals back into your next quote.

None of this asks the crew to do more. It asks them to do one thing, one tap against the right array, at the moment they were already clocking in. Everything downstream, the cost report, the coordination, the clean export, falls out of that single habit.

If you want to try the method on your next array, you can start a free trial. It runs 14 days with no card required, and there's a 30-day money-back guarantee. You can tag a real install end to end, pull the cost-per-array report, and see whether the number matches what you thought that job cost you.