Shop Foreman Script: Managing Technician Downtime Between Jobs

A shop foreman can keep technicians productive during downtime by assigning them to preventive maintenance tasks, training sessions, equipment checks, facility improvements, and scheduled documentation work—using a simple script like: "Before your next job, I need you to [specific task]. This is [why it matters to you/the shop]. I've blocked 90 minutes for it. Start at [time], and let me know when you're done." The key is making downtime feel purposeful, not punitive, and communicating the "why" so techs understand the connection to their pay and the shop's success.

Why Technician Downtime Matters More Than You Think

Downtime between jobs kills a shop's profitability. A technician sitting idle—even for 30 minutes,costs the dealership money and frustrates the tech. But here's the hard truth: many foremen avoid addressing downtime because they assume the tech is already busy or because they don't know what to say without sounding bossy or disconnected from the reality of the shop floor.

The best-run shops we see treat downtime as a gift, not a gap. Instead of letting a tech drift to social media or stand around, they have a predefined list of tasks ready to deploy the moment a RO closes out or a customer doesn't show. This isn't micromanagement,it's respect for the tech's time and your labor gross margin.

Technicians actually prefer structure during downtime. They want to know what's expected, how long it will take, and what they'll get paid. Vague direction ("just stay busy") demoralizes them. A clear script removes ambiguity and builds trust.

The Core Script: How to Assign Downtime Tasks

Use this framework every single time a tech finishes a job early or a customer delays their arrival:

Get the tech's attention in person. Don't text or holler across the bay. Walk over, make eye contact, keep it brief.
Name the task clearly. "Before your next job, I need you to..." is better than "stay productive" or "find something to do."
Explain the why in their language. Connect the task to either their paycheck, shop efficiency, or customer safety,whichever resonates with that individual.
Give a time boundary. "I've blocked 90 minutes for this" or "finish by 2 p.m." removes uncertainty.
Confirm understanding. Ask them to repeat back what they're doing and when.
Follow up visibly. Stop by in 30 minutes to check progress. It shows you're serious.

Here's the exact language you can use:

"[Tech name], your next customer isn't here until 10:30, so I'm going to put you on [specific task]. This matters because [reason]. I need you to start at 10 and wrap by 10:45. Sound good? Walk me through what you're going to do."

That's it. Simple. Respectful. Clear.

The Best Downtime Tasks to Keep Techs Occupied

You need a menu of downtime work ready to deploy. Post it in the break room or on your shop management display. Techs should know what's coming.

Preventive Maintenance and Equipment Checks

Tool inventory and organization. "Check your toolbox. Make sure everything is accounted for, organized, and that your air tools are all working. This takes about 60 minutes." Techs appreciate working tools, and you prevent lost equipment.
Lift and hoist inspections. "Walk through the shop with this checklist. Make sure all four bays' lifts are level, the hydraulics are clean, and there are no leaks. Report anything weird to me." Safety + accountability.
Air compressor and line checks. "Check the compressor filters, drain moisture from the lines, and listen for leaks. If you hear hissing, mark it and let me know." A typical check is 45–60 minutes.
Equipment calibration. Tire pressure gauges, torque wrenches, and scan tools need regular verification. "Verify our torque wrenches against the shop standard. Document what you find." This is billable prep work that techs often skip when busy.

Documentation and Paperwork Tasks

RO and estimate review. "Go back through the last 10 ROs you closed. Make sure your notes are clear, times are accurate, and there are no missing parts codes. This takes about an hour." Accurate documentation reduces comeback calls and CSI headaches.
Training module completion. If your DMS or training software has tech certifications, downtime is prime time. "Complete Module 3 on hybrid diagnostics. You'll need it for the Tesla order coming next month." Pays off in capability.
Bureau updates and compliance checks. "Pull your bureau file from the last month and verify all your hours and certifications are logged correctly. Let me know if anything is missing." Takes 30–45 minutes and keeps techs out of trouble.

Shop Cleanliness and Reconditioning

Bay deep-clean. "Your next job isn't for 90 minutes. I need your bay swept, pressure-washed, and restocked. All tool carts organized. Go." Every tech respects a clean workspace, and customers notice.
Parts bin organization. "Work with [parts tech]. Go through the fast-moving bins. Purge expired filters, restock common items, and label anything that's unclear." Parts staff love this, and faster parts retrieval saves hours per RO.
Customer lounge check. "Walk through the lounge. Check the coffee, magazines, bathrooms. Report anything broken or messy." Techs rarely think about the customer experience,this bridges that gap.

Skill Development and Mentoring

Peer training. "Spend 60 minutes with [junior tech]. Walk them through the diagnostic sequence on a brake noise issue. I want them comfortable with your system by end of week." Builds your bench, builds their confidence.
System training. "Go through the last three suspension ROs on your DMS. Pull the images and notes. Be ready to explain the pattern to the team at standup tomorrow." Active learning instead of passive scrolling.
Manufacturer release notes. "Review the latest TSBs for the 2024 model year lineup. Highlight anything that affects your bays. We'll discuss at tomorrow's meeting." Keeps techs ahead of common issues.

How to Handle the Tech Who Resists Downtime Tasks

Some techs will push back. "I'm not a janitor" or "That's not my job" are common objections. Here's how to reframe it.

Expect it, and don't take it personally. The tech is defending their identity and their hourly rate. They worry downtime pay won't be fair or that you're using them for grunt work. Address that head-on.

Use this response: "I hear you. Here's the deal: you clock in at your regular rate for downtime. You're not losing money. And these tasks keep the shop running so you have jobs lined up back-to-back. If I don't do this, you sit around unpaid, or we have to turn away work. Your choice,but this is how we stay competitive."

Then don't negotiate. You're the foreman. Set the expectation once, and enforce it every time. Consistency kills resistance.

And here's the unpopular opinion: if a tech consistently resists downtime work, that's a performance issue. It's not insubordination, but it's a failure to buy into how a professional shop operates. Document it. Address it in your one-on-one. And if it continues, it's a conversation about fit. A shop that tries to keep everyone happy with zero downtime expectations will eventually have quality problems and margin issues.

The Role of Scheduling and Planning in Reducing Downtime

The best defense against downtime is a good scheduling system. If you're stacking ROs intelligently, downtime should be rare and short.

Front-load your schedule. Know which jobs are coming three to five days out. Assign them to techs based on skill and bay flow. A tech who finishes one diagnostic job should have the next one ready, not sitting around waiting for parts or for the next customer to arrive.
Use time estimates from your DMS. If your system tracks hours per RO by job type, use that data. Don't assign a tech three 2-hour jobs and expect zero downtime in an 8-hour shift. Plan for gaps, training, and buffer.
Stage parts ahead. Nothing kills efficiency like a tech finishing a job and then waiting 30 minutes for parts to be pulled. Work with your parts team. If you know a transmission fluid change is coming at 10 a.m., have it staged by 9:45.
Build in training time officially. Don't treat training as a surprise task during downtime. Schedule it. "Every Wednesday 2–3 p.m. is diagnostics training. Every tech rotates through. No exceptions." It becomes expected, not punitive.

This is the kind of operational thinking that Dealer1 Solutions was built to handle,visibility into your RO pipeline, parts staging, and tech assignments so you can see downtime coming and fill it strategically.

Communicating Downtime Expectations to Your Team

Don't spring downtime tasks on techs without context. Use your next team meeting to set the standard.

Say something like this:

"Starting this week, when you finish a job and your next one isn't ready, I'm going to assign you a specific task. It might be a bay clean, training, equipment checks, or paperwork. You'll know exactly what it is, how long it takes, and why it matters. You clock in at your regular rate. This isn't punishment,it's how we stay busy and keep the shop running smooth. Any questions?"

Then post your downtime task menu somewhere visible. Laminate it. Update it quarterly. Techs respect predictability.

Tracking Downtime and Using It to Improve Scheduling

Keep a simple log. Every time a tech has unassigned time, note it.

Date and time
Tech name
Duration (15 min, 30 min, 60 min, 90+ min)
Reason (customer delayed, job finished early, parts wait, scheduling gap)
Task assigned

After 30 days, look for patterns. If one tech consistently has 90-minute gaps on Tuesdays, that's a scheduling problem, not a tech problem. If customer delays are your biggest downtime driver, that's a check-in and communication issue. Use the data to fix the root cause, not just the symptom.

Frequently asked questions

Do I have to pay techs for downtime at their regular rate?

State labor laws vary, but in most cases, yes,if a tech is on the clock and you're directing their work, they're entitled to their regular pay. Some shops use a lower "standby" rate for true downtime, but that often backfires as a morale killer. Pay them right, expect good work, and move on. The cost of downtime pay is negligible compared to a motivated tech's output.

What if a tech finishes a task early and their next job isn't ready?

Have a second-tier task list ready. "If you finish the bay clean by 11 a.m., move to the parts bin organization." Stack contingencies so they always have direction. A tech who knows there's always something next is a tech who stays engaged instead of checking the clock.

How do I handle downtime tasks in a flat-rate or commission environment?

Frame it clearly: "Downtime tasks are paid at [your flat-rate minimum/hourly equivalent]. They're not flat-rate jobs, so you're guaranteed that pay." Some shops pay a slightly higher rate for downtime work to compensate for lost commission opportunity. Whatever you choose, be consistent and transparent. Techs will accept lower-paying downtime if they know it's coming and it's fair.

Should I assign the same downtime tasks to all techs, or customize them?

Mix both. Some tasks (bay cleaning, equipment checks) should rotate evenly. Others should be skill-based. A senior tech might handle TSB review or training; a junior tech does facility work. Tailor assignments to skill and development goals when possible, but don't overthink it. Consistency matters more than personalization.

What if a tech says downtime work isn't "real work" and refuses to do it?

Set the boundary immediately. "I understand. Here's the reality: downtime work is part of this job. You're clocking in, I'm assigning work, you're doing it. If that's not going to work for you, we need to have a different conversation." Document the conversation. If refusal continues, it's a disciplinary issue. Don't let one tech set the culture for everyone else.

How can I reduce downtime in the first place instead of just managing it?

Build your schedule three to five days out based on confirmed appointments. Stage parts 24 hours before the job starts. Cross-train techs so jobs can move between bays if one tech is delayed. Use your DMS to forecast hours and avoid overscheduling one tech while another sits idle. The goal is downtime tasks to be the exception, not the standard.