How to allocate crew labor hours to cost codes

1. Start with the project, the date, and the crew

Before any hours go down, fix three things: which project or job number the day belongs to, which work date it covers, and who was on the crew. One report covers one project on one date. If part of the crew moved to another job after lunch, that job gets its own report with the hours they spent there.

Keeping the crew list explicit matters more than it looks. “Alex” on a two-Alex crew is a different problem from “Alex” on a crew with one, and the office can't resolve that later from a sheet.

2. Use the project's permitted code list

Cost codes (some contractors call them phase codes) are the numbers the office uses to track labor by kind of work: branch raceway, feeder raceway, wire, fixtures, switchgear, and so on. Each company configures its own list, and a project usually permits only a subset of it.

Allocate only to codes the project permits. If a task genuinely doesn't fit, record the hours against the closest permitted code and flag it for the office, or ask before the report goes in. Never invent a code on the sheet; a number the office doesn't recognise becomes a phone call or, worse, a silent miscategorisation.

The codes in this guide (1000, 3000, 3500) are a sample reference list from the PhaseNote demo, not an industry standard. Substitute your company's own numbers.

3. One row per employee per code

Take the day as the lead describes it and break it into rows. Here is a three-person electrical crew on a fictional job:

“John, Mike, and I worked eight hours each. John and Mike spent six hours on branch raceway, code 1000, and two on lighting fixtures, 3500. I spent four on branch raceway and four on switchgear, 3000.”

Six rows, not three. Combining John's day into a single “8 hours, mostly raceway” row loses exactly the information the code list exists to capture. Decimals go to two places at most (8.5, 2.25), which keeps totals exact when they're added up.

4. Per-person hours are not crew totals

“The crew spent sixteen hours on raceway” and “John and Mike each spent six hours on raceway, and I spent four” describe the same work, but only the second can be written down as rows. A crew total is the result of adding employee rows; it is not an input.

When a lead reports a group figure, the question to ask is how it splits: who, and how many hours each. If the honest answer is “we didn't track that,” the report should say so rather than divide evenly and present the result as fact.

Also keep in mind that crew total is the sum of employee hours, not elapsed time. Three people for eight hours is twenty-four crew hours in an eight-hour day.

5. Reconcile against stated totals

Leads often state a person's day total and then describe parts of it. Check the two against each other:

A gap in either direction is a question, not a correction. “John worked eight hours, six on 1000” leaves two hours unallocated; the right move is to ask which code got them, not to pad the raceway row to eight. Likewise, nobody can exceed twenty-four hours on a date; if the rows say otherwise, something was double-counted.

6. Resolve ambiguous activities before they become rows

Some descriptions map cleanly to one code. Others don't, and the ambiguity is usually in a common word:

• “Six hours installing conduit.” Branch raceway or feeder raceway? Above ground or underground? On most electrical code lists those are different numbers.
• “Pulled wire all morning.” Wire and MC cable may be separate codes.
• “Worked on the panels.” Switchgear, equipment connections, or devices and plates?
• “Phase 999.” A code the project doesn't permit. Which listed code did the work actually belong to?

The rule: when a phrase could reasonably land on more than one permitted code, ask the person who was there. Write the answer down as the row. A sheet with a confident wrong code is harder for the office to catch than a sheet with a blank and a note.

7. Review and hand off

Before the report leaves the field, run four checks:

1. Every employee on the crew list either has rows or is explicitly marked as not having worked.
2. Every code is on the project's permitted list.
3. Each employee's rows add up to their stated day, and no one exceeds twenty-four hours.
4. The crew total equals the sum of the employee totals.

On the office side, the administrator checks completeness, sends the report back with a note if something doesn't reconcile, and once satisfied, enters the rows into whatever job-tracking system the company uses. That entry step is theirs. A clean report makes it faster; it doesn't make it disappear.

8. What hours alone can't tell you

Hours by code say where labor went. They don't say how productive it was. Sixteen crew hours on branch raceway means one thing if the crew hung four hundred feet and another if it hung forty. Productivity needs quantities installed alongside hours, and quantities need a measurement method the field agrees on. Daily labor allocation is the foundation for that comparison, not the comparison itself.

Likewise, this guide is about labor allocation for job tracking. Payroll has its own rules about overtime, classifications, and certification that a labor report doesn't address and shouldn't pretend to.

Do it on paper, in a spreadsheet, or by voice

The free daily labor report template has the four-column sheet, this worked example, and a workbook with the employee and phase totals as formulas. PhaseNote is a demo of the same method by voice: the lead describes the day, reviews the suggested rows against the project's permitted codes, answers the questions above when they come up, and confirms before the office sees anything.