Straight into the service manual page
WrenchQuarry
More

4 task groups mechanics carry out on routine service work

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

Routine maintenance task groups are the broad kinds of work a mechanic does on a service ticket.

If you assign routine service work, the first question is usually not "what's broken?" but "who can take this?" One service ticket often mixes several groups, and a tech who is strong in one may not be right for another. Naming the groups before you hand out work makes it easier to match people to jobs and to see where your team has gaps.

Key Takeaways

  • Four groups cover most routine service tickets: lifting, brakes and wheels, diagnostics, and routine maintenance.
  • Lifting raises the risk of any job, so plan it before the work starts, not during.
  • Brake, wheel, and reassembly work needs a second-person check before release.
  • Split mixed tickets into groups before assigning, and name one lead who owns the whole ticket.
  • Build a simple skills grid of your techs by group so you can see gaps before an absence.

I took four task statements from the O*NET list and sorted them by what the tech physically does and what risk or skill each one carries. Treat them as a starting point for your own skills list. They are not a certification standard, and they do not tell you what your shop, your customers, or your local rules require.

Here are the four statements side by side. Use the table to compare what each group asks of a tech, then match those requirements to the skills on your team.

Task groupTask statements from O*NET
1. LiftingRaise trucks, buses, and heavy parts or equipment using hydraulic jacks or hoists.
2. Brakes, wheels, fasteners, reassemblyAdjust and reline brakes; align wheels; tighten bolts and screws; reassemble equipment.
3. DiagnosticsAttach test instruments to equipment; read dials and gauges to diagnose malfunctions.
4. Routine maintenancePerform routine maintenance such as changing oil, checking batteries, and lubricating equipment and machinery.

Group 1: Lifting and supporting vehicles and heavy parts

Lifting is the first group. The task statement reads: "Raise trucks, buses, and heavy parts or equipment using hydraulic jacks or hoists." (O*NET OnLine)

Lifting gets its own group because it changes the risk of a job. Much routine work happens at ground level. Once a vehicle or a heavy component is raised, though, the tech is working under a load. A mistake with a jack or hoist can injure someone even on a simple job, so the lift deserves its own line on the assignment list, even when the job it supports is minor.

Before you assign a job that needs a lift, check three things:

  • Is the tech trained on the specific lift or jack in your bay? Familiarity with one type does not automatically carry over to another.
  • Does your shop have a written lifting procedure, and does the tech know where to find it? If there is none, write one before the work starts. The tech should not invent one on the spot.
  • Is the bay free for the full job? Pulling a crew off a raised vehicle to free a shared lift is a common way jobs stall or go wrong.

Lifting also pairs with the next group. A vehicle on a lift usually has its wheels, brakes, or fasteners in reach, so one ticket may need a tech who can do both. If you split the work between two people, write the handoff down and make the vehicle's state clear to whoever picks it up.

Group 2: Brakes, wheels, fasteners, and reassembly

Group 2 is the mechanical work most people picture when they think of service. The task statement reads: "Adjust and reline brakes, align wheels, tighten bolts and screws, and reassemble equipment." (O*NET OnLine)

This group is safety-critical in a way that is easy to miss on routine jobs. Brakes and wheels decide whether a vehicle stops and tracks straight. Fasteners that are loose, or tightened out of sequence, can work free over time. Reassembly is where earlier work either holds or fails, since every removed part has to go back in the right place with the right fit.

For a team lead, three practical points stand out:

  • Say on the ticket whether reassembly is included. A tech who removes a part is responsible for putting it back, and that should be planned, not added later.
  • Tie fastener and alignment work to the manufacturer's service information for that component. Do not have a tech work from memory or from another vehicle's specs.
  • Build in a check before the vehicle returns to service. Require a second person to review brake and wheel work, even if your shop does not do that today.

Brake relining and wheel alignment are specialized enough that not every tech should be signed off for them. Keep that list separate from general service sign-offs so no one is assumed qualified by default.

Group 3: Diagnostics with test instruments

Group 3 is diagnosis. The task statement says: "Attach test instruments to equipment, and read dials and gauges to diagnose malfunctions." (O*NET OnLine)

Diagnostic work is hard to schedule because the scope stays unknown until someone looks. A ticket that says "warning light on" could point to a sensor, a wiring fault, or something larger. Estimating this kind of job takes more care than estimating a planned service item. Keep "diagnose" tickets separate from "replace" tickets on your board so the two don't get mixed up.

When you assign diagnosis:

  • Give the tech the symptom and the history you have, and say whether the goal is to find the cause or to fix it. Those are often separate tickets, and mixing them up leads to unpaid diagnosis time or repairs nobody approved.
  • Make sure the test instruments are on hand and that the tech knows how to use them. A diagnosis is only as good as the readings behind it.
  • Ask for readings to be written down. If a second tech picks up the job, recorded gauge values and test results save time and prevent repeat work.

Diagnosis also tests judgment. Give vague symptoms to your most experienced techs, and let less experienced techs shadow the work or take it once the fault is clear.

Group 4: Routine maintenance

Group 4 is the work most likely to fill your board. The task statement reads: "Perform routine maintenance such as changing oil, checking batteries, and lubricating equipment and machinery." (O*NET OnLine)

The words "such as" matter. The list gives examples, not a complete checklist. Routine maintenance is a set of planned tasks that repeat across many units, so the risk is less about skill than about missing an item. A tech who changes the oil and forgets the batteries has still left the job unfinished.

Practical points for this group:

  • Use a written checklist for each service type, and have the tech mark each item done. A checklist makes a routine job repeatable and gives a reviewer something to check.
  • Match the work to experience. Routine maintenance is often a good first assignment for someone new to your shop, with a reviewer checking the completed checklist.
  • Batch similar jobs carefully. Oil changes and lubrication for several units in one block can cut setup time, but keep each vehicle's ticket separate so the records stay accurate.

Routine work also surfaces problems. A battery check or lubrication pass is a chance to spot a leak, a worn part, or a loose fitting. Tell techs to report anything outside the checklist and log it on the ticket. A finding logged today can become a planned job next week instead of a breakdown later.

Splitting one ticket into groups

Real tickets rarely fit one group. Take a common request: "service, check brakes, change oil." Split it before you assign it.

  • The oil change is routine maintenance, so it falls under group 4.
  • The brake check starts as a group 2 task. If the tech finds worn parts, the adjustment, relining, or wheel work is also group 2.
  • If the brake check turns up a noise, a leak, or a reading that does not make sense, and the tech has to trace it, that part becomes group 3, diagnostics.
  • If the vehicle has to come up on a lift for any of this, group 1 applies to the whole job, and the lift must be planned before the work starts.

Once the ticket is split, assign one lead tech to own it and list each sub-task with the person doing it. The lead tracks the whole ticket, even when someone else does part of the work. That keeps a job from stalling while one person waits on another to finish a step nobody realized they owned.

When a job changes scope

Routine tickets change scope all the time. A maintenance visit turns into a diagnosis, or a brake check turns into a reline. When that happens, the tech should stop, record what they found, and tell you before continuing. Do not let the job quietly grow into a group the tech is not signed off for.

Re-scoping has three parts. First, update the ticket so it reflects the new work. Second, confirm the assigned tech is qualified for the new group, and reassign if they are not. Third, if the change affects the cost or timing the customer was given, tell the customer and get approval through your normal process. A short pause to re-scope costs far less than finishing a job that was never properly planned.

What belongs on the ticket

A ticket that names the task group makes assignment faster and reduces rework. At minimum, a service ticket should state the vehicle or equipment, the work requested, and any known symptoms in the customer's own words. Add the task groups you expect to be involved, and note whether a lift is needed. If the ticket only says "service," the tech has to guess the scope, and guessing is where missed items and surprise charges come from.

Good tickets also say what is not included. If the request is an oil change only and the tech notices brake wear, the ticket should show whether a brake check is authorized or whether the tech should report the finding and wait. Writing the boundary down protects the customer, the tech, and your shop. See our field service work order checklist for a full field list.

Finally, leave room for notes: readings, replaced parts, items checked and found acceptable, and anything that needs follow-up. Those notes are what you will return to when the same vehicle comes back, so the few extra minutes are worth it.

Handoffs and sign-off

Many jobs cross hands. A lift operator may raise a vehicle, a second tech may do the brake work, and a diagnostician may trace a fault found during the check. Each handoff is a place where information gets lost. Before a job moves on, the current tech should record what was done, what was left undone, and what the next person needs to know.

Sign-off should match the group. The person who did the work signs off on their own items, and a reviewer signs off where your shop's rules require one. Keep sign-offs visible on the ticket so anyone can see who completed each part. When a vehicle goes back to a customer, you should be able to answer "who checked this?" for every group that was touched. Our work order statuses guide lists the words to use at each step.

How to assign techs by group

Build a simple skills grid. Rows are your techs, and columns are the four groups. Mark each cell as trained and signed off, supervised only, or not yet trained. Update it whenever someone completes training or gets signed off. When a ticket arrives, you can see which techs can take each group and where you need a second person.

The table below pairs each group with its main risk and the sign-off that suits it. Use it to decide what check to require before a job goes back out.

Task groupMain riskSign-off to require
1. LiftingA load shifts, or a jack or hoist fails under weightTech trained on that specific lift, plus a bay check before work starts
2. Brakes, wheels, fasteners, reassemblyThe vehicle fails to stop or track straight, or parts work looseSecond-person review of brake and wheel work before release
3. DiagnosticsThe scope grows, or repairs happen without approvalApproval before repair; experienced tech on vague symptoms
4. Routine maintenanceA checklist item gets skippedReviewer checks the completed checklist

Some assignment rules that work well in practice:

  • Assign by the hardest group on the ticket, not the easiest. If a job needs a lift and a brake reline, the tech has to be signed off for both.
  • Keep at least one signed-off tech available for each group on every shift, so one absence does not halt an entire category of work.
  • Route diagnosis and brake work through a review step before the vehicle goes back out, regardless of who did the work.
  • Review the grid on a regular schedule, and again whenever a new tech joins or new equipment arrives in the bay.

The grid also shows training needs. If only one person is signed off for lifting, that is a risk you can plan around now, before that person is out sick.

Worked example: splitting one ticket

A ticket reads: "service, check brakes, change oil." Split it before you assign it.

  • Oil change: group 4, routine maintenance.
  • Brake check: group 2. If worn parts are found, the relining or wheel work stays in group 2.
  • If the brake check turns up a noise or an odd reading the tech must trace, that part moves to group 3, diagnostics.
  • If the vehicle comes up on a lift, group 1 applies to the whole job.

Name one lead tech to own the ticket and list each sub-task with the person doing it. If the brake check becomes a reline, stop, update the ticket, confirm the tech is signed off for group 2, and tell the customer before the work continues.

What this post does not cover

This post does not tell you which certifications your techs need, how many techs a shop must have, or what your local rules say about lifts, brake work, or inspections. Those depend on your jurisdiction, your equipment maker, and your customers. Check your own requirements before adopting any of these groups as a standard.

Public work adds another layer. The New York State Department of Labor lists the topics to read up on: the Public Work and Prevailing Wage Enforcement laws and regulations, OSHA 10 compliance, worker notifications, and certified payrolls. If your shop takes public work in New York, start with its public work and prevailing wage guidance.

The four groups are drawn from one occupational summary. Other sources may split the work differently, and your shop may have good reasons to use different groups. The goal is the same either way: know which tech is qualified for which kind of work before you hand it out.

Next step today

Take one open ticket on your board and tag every sub-task with one of the four groups. Then check whether the assigned tech is signed off for the hardest group on that ticket. If not, reassign it or split the work before the vehicle comes in.

Related guides: Bundled maintenance plan sales tax: 8 steps to check · Federal labor standards exclusions: 2 groups to check · Maintenance plan billing: 3 settings to check first.

Questions people ask

What are the four routine service task groups?

They are lifting, brakes and wheels with reassembly, diagnostics, and routine maintenance, sorted by what the tech does and the risk each one carries.

Why does lifting get its own group?

Because raising a vehicle or heavy part puts the tech under a load, raising the risk of even a simple job.

How do I split a mixed ticket before assigning it?

Break the request into sub-tasks, tag each one with its group, and name one lead tech who owns the whole ticket.

What should I do when a job's scope grows mid-repair?

Stop, record what was found, update the ticket, confirm the tech is signed off for the new group, and tell the customer if cost or timing changes.

What goes in a skills grid?

Rows are your techs, columns are the four groups, and each cell reads trained and signed off, supervised only, or not yet trained.

Sources

More field guides