Straight into the service manual page
WrenchQuarry
More

Time tickets for direct labor: 3 checks before billing

WrenchQuarry Editorial Team · Published · 13 min read · How these guides are written

Each crew member's hours on a job should get their own time ticket entry, so the job carries its full direct labor cost. That gap is where labor costs drift. This post covers the habit that closes it. The worked example uses two people on one job, and then widens to the cases dispatchers and team leads run into every week.

Key takeaways

  • Give each crew member's hours on a job their own time ticket entry.
  • Record who worked, the job, the date, the hours, and the rate on every entry.
  • Multiply hours by the rate to get each entry's labor cost.
  • Check the labor hours on each job against the day sheets before anyone bills it.

Why crew hours land on the wrong job

Labor rarely goes wrong in one dramatic moment. It goes wrong in small moves. A technician finishes one job at midday, starts the next, and the hours get entered under the first job because that is the one still open on the clipboard. A lead covers for someone who called in sick, and that person's time ends up on a job they never touched. Each slip looks minor. Across a month, enough of them change which jobs look profitable.

The effect runs in both directions. A job that absorbed hours from a neighbor looks more expensive than it was, so the next quote for similar work gets padded, or a good customer is turned away. The job that lost those hours looks cheaper, so it gets priced too low and the shop works it for less than it should. Dispatchers feel this too, because the board shows one story and the cost report tells another.

The textbook answer is job order costing. Under that method, costs are collected for one specific job at a time. OpenStax describes the mechanism in its discussion of product costs: when the accounting department processes time tickets, the costs are assigned to the individual jobs, and labor costs are recorded on the work in process inventory. The job is the unit of tracking. That means the hours have to be tied to the job when the work happens, not rebuilt later from memory and a schedule.

What one time ticket entry records

A time ticket is the record of one person's time on one job. OpenStax shows what time tickets might look like on a specific job, and the useful lesson for a small shop is that the form should be simple enough to fill in at the end of a shift and specific enough that someone else can trace it later. Your form does not have to copy a textbook layout. It only has to carry the same information in a way your crew will actually use.

At minimum, an entry should say who worked, which job the time belongs to, the date, the hours, and the rate that applies. Add a short task note when one job contains more than one kind of work, such as demolition and finish work. A note takes the crew a few seconds and saves someone an hour of guessing when a cost question comes up in the middle of the month.

The rate is the part people skip. Hours alone do not give you a cost. The cost comes from multiplying hours by a rate. Buildxact explains that when you enter a unit cost and a quantity, the resulting cost is calculated as a basic quantity times unit cost, and that result is stored as the total for the estimate item. A time ticket works the same way. The hours are the quantity, the hourly rate is the unit cost, and the product is the amount that belongs to the job.

Direct labor and indirect labor

Not every paid hour belongs to a job. Direct labor is work that can be traced to a specific product or job. Indirect labor supports the shop as a whole but cannot be traced to one job. OpenStax draws this line directly: some individuals' work cannot be directly traced to the product, and those indirect labor costs are assigned to the product as part of manufacturing overhead. The direct labor lines are the ones that get traced to a job's tickets.

That distinction matters for dispatchers. A crew member who installs on one job all day belongs on that job's tickets. A lead who spends the morning ordering materials and handling calls for the whole shop does not belong on one job, even if that job was the one they happened to be standing next to. Their cost still has a place in the books, but as overhead shared across work, not as direct labor on a single job. Putting it on one ticket is the fastest way to make that job look expensive.

The table shows the two direct labor lines from the textbook example, so you can see how hours, rate, and the assigned amount relate. The rate in the first line is stated as including taxes and benefits.

Department (OpenStax example)People and hoursRateDirect labor assigned to the job
ProductionTwo individuals, one hour each$15 per hour, including taxes and benefits$30
FinishingTwo individuals, one hour each$18 per hour$36

Working through the two-entry example

Here is the example in full. Two people in the production department each work one hour at $15 per hour, including taxes and benefits. That is two time ticket entries, one per person, each for one hour at the same rate. Together they assign $30 of direct labor to the job. Two people in the finishing department then each work one hour at $18 per hour, which makes two more entries and $36 of direct labor. Each department produces its own pair of entries, and the pairs add up on the same job.

The source states the result directly: the direct labor costs of $30 and $36 assigned to Job MAC001 are shown. The same chapter also spells out the scope. It says that the authors are only going to track the expenses for Job MAC001. That one line describes the discipline. Pick the job, track its costs, and when you read that job's numbers, leave the rest of the shop out of them.

Work the same arithmetic on your own jobs. Take each person's hours, multiply by their rate, write one line per person, and then add the lines for the job. Do this with real entries from last week before you trust any labor figure. If the job total does not match the sum of its entries, the problem is in the add-up or in an entry, and you can find it by reading the lines one at a time.

Adding a late entry changes the total in the same way. A forgotten hour from a Tuesday that goes onto the job is one more line, not a reason to rebuild the whole summary.

Illustrative example: one job, two entries

Suppose one crew member works 1 hour at $15 per hour and another works 1 hour at $40 per hour on the same job. The first entry assigns $15 of direct labor to the job, and the second assigns $40, so the job carries $55. If the second hour belongs to a neighboring job, correcting that entry drops this job's total to $15.

Setting the rate on each ticket

The rate on a time ticket is a policy decision, and it should be made once and written down. Some shops put the plain hourly wage on every ticket. Others load the wage with taxes and benefits so the labor figure reflects what the hour really costs the business. The OpenStax example uses a loaded rate for the production department: $15 per hour, including taxes and benefits. Either approach can work. What causes trouble is mixing them, so one job carries plain wages and the next carries loaded rates.

Write the rate basis into your procedures. Name the rate for each person, and say whether it is plain or loaded. When someone's pay changes, update the rate on the date it takes effect, and note the change so that older jobs are not silently repriced. The rate list deserves the same review you give any other price list in the business, because your quotes depend on it.

Decide also how the rate applies when someone works outside their normal role. A carpenter who runs a saw for a finishing crew may be on a different rate for that shift, or may not. The right answer depends on how your business pays and prices its work. Whatever you decide, put the decision in writing so that a dispatcher and a bookkeeper reach the same number from the same entry.

Splitting shared costs on a stated basis

Some costs serve more than one job or the whole shop. Shared space, a service van used by every crew, and a supervisor's time often fall in this group. You cannot place them on a single ticket without guessing, so they need a split on a stated basis. The OpenStax chapter gives a clear example. A 10,000 square foot building is physically allocated at 4,000 square feet for administrative purposes and 6,000 square feet for production. A company might allocate its annual $30,000 property tax expense on a 40%/60% basis, which gives $12,000 as a period cost for the administrative offices and $18,000 as a production overhead cost.

The lesson for a service shop is not about property tax. It is that the split has a basis that anyone can check. The example uses floor area, which is easy to measure and hard to argue with. If you divide the shop rent by floor area, write down the areas and the percentages, and use the same split every month. A basis you can explain holds up better than a split you adjust whenever the numbers look wrong. For more on overhead allocation, see the overhead base allocation guide.

Labor is harder to split than space, and the same discipline applies. If a crew spends a day loading for four jobs, decide how that time is divided before the day starts, or write the rule for it afterward, and then stick to it. Changing the method from job to job is how one job ends up carrying the shop's bad weeks.

Some bookkeeping tools can carry these groupings into reports. Zoho Books notes that you can also associate reporting tags to items. Check whether your own tool supports something similar before you build a workaround in a spreadsheet.

Setting up entries for dispatchers and team leads

Dispatchers decide which job a crew is on, so the correct job number starts with them. Put the job number on the dispatch sheet or board, and have each crew member copy it onto their ticket from that source rather than from memory. A number written from memory at the end of a long day is where most wrong-job entries start. For the handoff itself, see Field Service Work Order Checklist for Dispatch Handoffs.

If a crew moves from one job to another during a shift, they should write two entries rather than putting the whole shift on the first job. Each entry gets its own hours, so the time spent on each job is visible. This costs the crew a minute. Without it, the first job absorbs time it never had.

Team leads do the check. At the end of each shift, the lead should look at each person's entries and confirm three things: every crew member on the job appears, every entry has a job number and hours, and the rate matches the rate on file. A missing entry is far easier to fix the same day, while the crew can still remember the afternoon. By the time the month closes, the people involved have moved on and the details are gone.

Give the crew one short rule to follow: one entry for each person on each job, written before they leave. Post the rule near the time clock or in the truck, and keep it short enough that people actually follow it. A long procedure gets skimmed. A two-line rule gets used.

Fixing an entry after the fact

Entries will be wrong sometimes. A person writes the wrong job, a clerk mistypes hours, or a rate changes after the work is done. The fix should leave a trail. Do not erase the original line and quietly write a new one. Strike the wrong entry through, initial it, and record the corrected entry with the date the correction was made. Someone reviewing the job later can then see what was recorded, what was changed, and when.

Correct the entry first, then the totals. It is tempting to adjust the job summary directly because it is the number people look at. That creates a summary that no longer matches the entries underneath it, and the next person who rebuilds the total will get a different figure. Keep the summary as a calculation from the entries, so that fixing a line fixes the total automatically.

Same-day corrections are routine. A correction made after an invoice has gone out needs a second look, because the customer may have been billed on the old number. Decide who may approve a late correction, and write that down with the rest of your procedure so the decision does not depend on who happens to be in the office.

Checking job totals before they reach the invoice

Before anyone bills a job, run three checks. First, compare the labor hours on the job with the hours on the day sheets for the crew assigned to it. Second, check each rate against the rate list, so a new hire's entries do not carry a default number that nobody reviewed. Third, look for jobs with no labor at all. A finished job with zero labor usually means the hours were charged somewhere else.

Totals also tell a story. If one job shows far more labor than its scope suggests, look for entries that belong to a neighboring job or to general shop time. If a job's labor looks too small, look for crews who worked it but never wrote the ticket. Either way, fix the entries first and reprice second. Repricing a job to match a wrong total only hides the problem for the next job. For a broader view of closed jobs, see job margins.

Keep the record that makes these checks possible. Each job should show its labor lines with the person, date, hours, and rate, so anyone who asks can follow the number back to the source. A job report that shows only the total cannot answer the question an owner will eventually ask, which is why the total came out that way.

Reading a job's labor report

A labor report for one job should answer four questions at a glance: who worked on it, how many hours each person logged, what rate was applied, and what total labor cost the job carries. If a report cannot answer those four questions, the entries behind it are missing a field, or the report is grouping things in a way nobody intended.

Read the report by person before you read it by total. A single line that says sixty hours of labor tells you little. Ten lines, each with a name and a rate, tell you whether one crew member carried most of the work, whether a new hire is logged at the wrong rate, and whether someone who should be on the job is missing from it. The detail is where the errors show.

Compare the report with the schedule, not with memory. Memory tends to remember the big jobs and forget the small ones. The schedule and the time tickets record what happened on each day, so the comparison is between two records made at the time, not between a record and a feeling.

Finally, look at the report across several jobs, not just one. A pattern across jobs shows things a single job cannot. If the same lead's hours appear on every job, that is worth asking about, because the lead's time may belong in overhead rather than in each job's direct labor. That question takes minutes to ask and can change how the next quote is built.

Writing one time ticket entry for each crew member on each job is a small habit, but it is the one that makes job costing work. The entries tie each crew's hours to a job when the work happens, the rate turns those hours into money, and the checks at the end of the week keep the numbers honest. Start with the crew on the next dispatch, and review the first week's entries together before you trust the job totals.

Sources

More field guides