Straight into the service manual page
WrenchQuarry
More

Job standard time: setting a 45 or 55 minute target

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

If you run a small field-service firm, you probably already have a rough sense of how long a repeat job takes. The monthly inspection, the routine swap of a common part, the standard tune-up: you have done them many times, so you know about how long they run. The trouble is that "about" is hard to schedule, hard to quote, and hard to hold anyone to. A standard time turns that rough sense into a number you can write down, use, and check.

This post explains what a standard time does, why two reasonable people can land on two different targets for the same work, and how an owner or dispatcher can build a standard for a recurring job. The example we use comes from a textbook case about production output, where one firm's target was 45 minutes and another level of management wanted 55 minutes for the same amount of work. The job in that case is not yours, but the reasoning carries over to a service call.

What a standard time does for your shop

A standard is a benchmark. It says what a unit of work should cost in time and materials, so that actual results have something to be compared against. The OpenStax managerial accounting text, in its chapter on how standard costs are developed, shows standards applied down to the level of the individual worker. It describes an automobile assembly plant with approximately 5,000 employees, where each part has a standard cost and, in addition, each employee has standards for the job he or she performs.

What a standard gives youPractical useExample of a condition to note
A time for the quotePrice reflects the work, not a guessParts list and labor rate
A time for the scheduleDispatch board reflects real visit lengthTravel, parking, paperwork
A yardstick for checkingShows there is a gap to explain after the factAccess panel, equipment age

That idea scales down well. A shop with a handful of technicians does not need a plant's paperwork, but it does benefit from one standard for one recurring job. A good standard gives you three practical things:

  • A time you can put into a quote, so the price reflects the work and not a guess.
  • A time you can put on the schedule, so the dispatch board reflects how long a visit should really take.
  • A yardstick for checking, after the fact, whether a visit ran long and why.

The third point matters most early on. When a job runs long, a standard tells you there is a gap to explain. It does not tell you who is at fault. The explanation might be a missing part, a hard-to-reach access panel, an older unit than the one the standard was built on, or a technician who needs more coaching. You cannot sort those out without a number to compare against.

The people in your shop also use the standard in different ways, which is part of why it needs to be written down clearly. The owner uses it to price work and judge whether the business is keeping its margin. The dispatcher uses it to decide how many visits fit in a day and how much room to leave between them. The technician uses it, whether or not anyone says so, as a sense of whether the day is going well. A single written standard, with its definition attached, gives all three the same starting point. Without one, each person carries a private number in their head, and those private numbers rarely match.

Why two targets can both be reasonable

The clearest case in the OpenStax chapter involves a consulting firm that set a production standard for a plant making ice cream. The firm's standard was production of 100 gallons of ice cream every 45 minutes. The plant's middle level of management, however, thought the standard should be 100 gallons every 55 minutes, while the top management of the company thought that the consulting firm's standard would provide more motivation to the employees.

Look at what is and is not in dispute. Everyone agrees on the output: 100 gallons. The disagreement is only about the clock, and it is a disagreement about purpose. A tighter target pushes people to move faster, and it can look fair to leadership that sees what is possible on a good day. A looser target is easier to hit on an ordinary day, and it is more likely to match what the people doing the work can sustain. Neither view is careless. Each one is answering a different question.

For a dispatcher, the same tension shows up in a familiar form. Schedule every visit at the fastest time anyone has ever done it, and the board looks efficient until the first slow visit throws the whole day off. Schedule every visit at the slowest time, and the board looks padded and customers wait longer than they need to. The standard you choose sets which mistake you will tend to make.

Comparing the two targets

The table below lays out the three positions from the ice cream case side by side. The output is the same in every row; only the time changes.

PositionOutputTimeWhat the source says about itSource
Consulting firm100 gallons45 minutesIts own standardOpenStax
Plant middle management100 gallons55 minutesThought this should be the standardOpenStax
Plant top management100 gallons45 minutesThought the consulting firm's standard would give more motivationOpenStax
PositionOutputTimeWhat the source says about it
Consulting firm100 gallons45 minutesIts own standard
Plant middle management100 gallons55 minutesThought this should be the standard
Plant top management100 gallons45 minutesThought the consulting firm's standard would give more motivation

Read the table as a disagreement about what a standard is for, not as a disagreement about arithmetic. Ten minutes on a single output is the whole gap. In a small shop, that same ten-minute gap on a recurring job, repeated across every visit in a week, can change the schedule, the quote, and the margin. That is why it is worth deciding deliberately rather than letting the number drift.

One practical way to keep the discussion productive is to write both competing numbers down next to each other, along with the reason behind each one. Ask the person who favors the tighter time what they expect it to change on the job, and ask the person who favors the looser time what conditions they are assuming. Often the two positions turn out to rest on different assumptions about the same visit, and those assumptions can be tested against the measurements you already collected. If they cannot be settled that way, write down which purpose the standard serves first, because that purpose should decide which number wins.

Building a standard for a recurring job

You do not need a consultant to build a usable standard. You need a clear definition of the job, a set of honest measurements, and a rule for turning the measurements into a target. Here is a practical sequence.

1. Name the job tightly. "Service the unit" is too vague to time. "Replace the filter and check the drain on a standard unit at a customer site" is specific enough to measure. Write down where the job starts and where it ends. Decide whether travel, parking, paperwork, and cleanup are inside the standard or outside it, and write that decision down too. Most disputes about a standard time are really disputes about where the job begins and ends.

2. Break the job into steps. List each step in order, along with the tools and parts it needs. This list is also your checklist for the technician, and it shows you where time is most likely to go.

3. Time it on several visits, not one. A single visit tells you what happened that day. Several visits, ideally with different technicians and different sites, tell you what the job usually takes. Record who did the work and the conditions: access, weather, equipment age, and whether any surprises came up.

4. Look at the spread. Put the times side by side. A tight cluster suggests the job is well defined. A wide spread suggests either the scope is still fuzzy or the conditions vary a lot. Find out why the outliers are outliers before you average them away. A single very long visit might have been a bad access situation that will not happen again, or it might be a step your process is missing.

5. Pick the target and say what kind it is. Decide whether the number is the expected time, meaning what a competent technician should hit on a typical visit, or a stretch target, meaning something the crew should work toward. Write the choice next to the number. Without that label, the dispatcher, the technician, and the owner will each read the number differently.

6. Put it in a spreadsheet. A simple spreadsheet keeps the standard, the labor rate, and the parts list in one place. Excel's easy-to-use formulas, as the FreshBooks estimate examples page notes, allow you to itemize your products, services, and prices. For a field firm, that means you can link the standard time to the quote line by formula.

Keep the first version simple. A standard that is written down, measured, and used is worth far more than a perfect one that sits in a drawer.

Keeping the standard current

A standard is a snapshot of conditions on the day you measured. Conditions change. Parts get more expensive, a new model arrives with a different access panel, a technician gets faster or slower, and the mix of customers shifts. The OpenStax text makes the point plainly in its discussion of cost standards: it is not reasonable to expect the price of all materials and labor to remain constant for 12 months.

Review itemWhat to checkWhy it mattersSource
Overhead kindsBroken into its kinds before spreadingAvoids false precisionOpenStax
Material and labor pricesNot assumed constant for 12 monthsKeeps the standard honestOpenStax

For a shop, that means reviewing standards on a regular schedule rather than treating them as permanent. A yearly review is a reasonable starting point. At each review, check three things: whether the job steps still match what technicians actually do, whether the recent actual times still cluster near the standard, and whether the prices built on the standard still cover the costs of the job.

Overhead deserves the same attention. The same OpenStax chapter, working through a coffee shop example, notes that to determine the standard for overhead, the coffee shop would first need to consider the fact that it has two types of overhead. The lesson for a field firm is to break overhead into its kinds before you spread it across jobs. Vehicle costs, insurance, office time, and tool upkeep do not all behave the same way, and lumping them together can make a standard look more precise than it is.

Keep a short change log for each standard. Each time you revise a number, note the date, the reason, the conditions that changed, and who approved the change. A log like this does two jobs. It shows you, a year later, why the standard moved, and it gives your technicians confidence that changes are made for a reason rather than on a whim. It also makes the next review faster, because you can see which assumptions have already been tested and which ones have never been checked at all.

Choosing between a tighter and a looser target

When you face the choice the plant faced, between 45 minutes and 55 minutes for the same output, start with the purpose. Ask what the standard is for.

If the standard is mainly for quoting and scheduling, lean toward the number your crew can hit on a typical visit. A quote built on an unrealistic time will often be wrong, and the shortfall lands on the owner's margin or on the customer's patience. A realistic target protects both.

If the standard is also meant to push performance, a tighter target can help, but only if the people doing the work believe it is fair. The top-management view in the ice cream case rests on motivation. That only works when technicians can see how the number was built, know which conditions it assumes, and have a say in changing it when the conditions change. A tight target that feels arbitrary tends to be ignored, or worse, it encourages rushed work and callbacks.

Whichever way you lean, communicate the target the same way every time. Tell the crew what the standard covers, what it leaves out, and how it will be reviewed. A dispatcher who schedules by the standard and an owner who prices by it should be using the same numbers, written in the same place, with the same definition of where the job starts and ends.

It also helps to decide in advance what you will do when the actual times disagree with the standard. A simple rule works: if several visits in a row run well past the standard, review the steps and conditions before changing the number. Investigating is cheaper than a season of wrong quotes. How many visits count as several, and how far past counts as well past, is yours to set. The point is to decide in advance and write the rule down, so the number does not get changed by whoever happens to be annoyed that week.

A short checklist before you publish a standard

  • The job has a written name, a start point, and an end point.
  • Travel, parking, paperwork, and cleanup are either inside or outside the standard, and the decision is written down.
  • The steps are listed in order, with the tools and parts each one needs.
  • The time came from several visits, with conditions noted.
  • The outliers were explained, not simply averaged away.
  • The target is labeled as expected time or stretch target.
  • The number lives in one spreadsheet that feeds the quote and the schedule.
  • Someone owns the review date, and the standard is checked against recent actual times and current prices.

A standard time is not a promise about every visit. It is a shared reference that lets owners price honestly, dispatchers plan realistically, and technicians see how their work is measured. Start with one recurring job, measure it carefully, and write down what you decided and why. Once you have done that for one job, the next one is much easier.

Sources

More field guides