Scheduling Diagnostic Calls of Unknown Length (2026 Guide)

TL;DR

Most scheduling advice assumes you know how long a job takes. A water heater swap is three hours. A quarterly pest treatment is forty minutes. Block the time, move on.

Diagnostic calls break that assumption. "The outlets in the back bedroom stopped working." "The dryer runs but does not heat." "There is a wet spot on the ceiling." Each could be fifteen minutes or four hours, and nobody knows which until a tech is standing in front of it.

As of October 2026, the fix is not better guessing. It is structure. Block a fixed diagnostic window, protect it with buffers, place it where an overrun does the least harm, and give the tech a clear rule for repairing now versus booking a return. This guide walks through each piece. It applies to electricians, appliance repair, HVAC, plumbing, and any trade where "come and have a look" is a large share of the calls.

Why unknown-length jobs wreck a schedule

A known job that runs twenty minutes long is an annoyance. An unknown job that runs two hours long is a chain reaction.

The tech stays because walking away from a half-solved problem feels wrong. The next customer's window passes. The office starts phoning to apologize. The third job gets bumped to tomorrow, where it collides with something already booked. By four in the afternoon one diagnostic call has damaged three customer relationships.

The opposite failure is quieter but just as costly. An office that has been burned starts blocking three hours for every diagnostic. Most take forty minutes. Now techs sit idle half the afternoon and the business does four jobs a day instead of six.

Both failures come from treating the diagnostic as a job of unknown length. The better approach is to treat it as a job of fixed length with an unknown outcome.

The fixed diagnostic window

Decide how long a diagnostic visit is. Not how long the repair might be. How long the visit is.

For most trades the window has three parts:

• Arrive and listen. Five to ten minutes. The customer's description is evidence.
• Find the fault. Twenty to forty minutes of real troubleshooting.
• Decide and act. Either complete a simple fix, or quote the larger repair and book it.

A common window is sixty to ninety minutes. Whatever number you choose, it becomes a standard service in your system with a standard duration, like any other. In GetTimePad's scheduling calendar, that means a "Diagnostic visit" service type with its own color, so the unknown-outcome jobs are visible on the board at a glance.

The rule that makes the window work is the hard stop. At the end of the window, the tech is either finished or has made a decision about what happens next. The tech does not simply keep going.

Better intake shrinks the unknown

The diagnostic starts on the phone, not in the driveway. Good intake often turns an unknown job into a known one before anyone drives anywhere.

Ask what happened just before the problem started. Ask what the customer has already tried. Ask for the brand and model. Ask for a photo.

A photo of a model tag lets an appliance tech check common failures and load the likely part. A photo of a scorched outlet tells an electrician what kind of afternoon it will be. Our guide to customer intake forms for online booking covers which questions to put on the form, and the online booking portal collects those details and photos with the booking.

Returning customers are easier still. If the CRM holds the service history and equipment details, the tech can read what was done last time before knocking on the door.

Where to put diagnostics in the day

Placement matters as much as duration. The same ninety-minute diagnostic is harmless in one slot and destructive in another.

Two patterns work well.

Diagnostics first. Put unknown-length calls at the front of the day with a buffer behind them. If the call is short, the buffer is released and a waitlisted job moves up. If it is long, nothing downstream is touched.

Diagnostics last. Put them at the end of the day so an overrun costs only the tech's time. This needs a clear rule about how late is too late, or it becomes daily overtime.

What does not work is scattering diagnostics between fixed commitments and hoping. Our guide to technician capacity planning covers how many unknowns a day can reasonably hold.

Buffers: the price of predictability

A buffer is unbooked time left on purpose. It feels like waste. It is insurance.

A workable starting ratio is one buffer of thirty to sixty minutes for every two diagnostic calls on a tech's day. Label it on the calendar so nobody books over it by accident. Conflict detection will warn the office if they try.

Buffers need a release rule. If the morning diagnostic finished on time, the buffer after it is free by, say, eleven. The office then offers it to a waitlisted customer or pulls a nearby job forward. Our piece on blocking lunch, admin, and drive time covers the mechanics of holds in more detail.

Repair now or return: give the tech a rule

At the end of the diagnostic window the tech knows what is wrong. The question is whether to fix it now. Leaving that entirely to judgment in the moment is how overruns happen. Give a simple rule.

Repair now if all three are true:

1. The part is on the truck.
2. The repair fits in the time before the next commitment, including any buffer.
3. One person can do it safely.

Book a return if any one is true:

1. A part has to be ordered.
2. The repair would make a later customer late.
3. The job needs a second tech or special equipment.

When the answer is "return", the visit gets booked before the tech leaves. The tech, or the office by phone, picks the date with the customer standing there. The confirmation text arrives while the tech is still in the kitchen. A return that is promised but not booked is the most common way these jobs are lost. Our guide to appliance repair second-visit scheduling covers the parts-on-order version of this in depth, and two-technician crew jobs covers the return that needs a second person.

In Tech Mode, on the Pro plan, the tech records notes and photos of what was found on the job itself, so whoever returns, even a different tech, starts from the diagnosis instead of from zero.

Set the customer's expectations before arrival

Customers handle uncertainty well when they are told about it early and badly when they discover it late.

At booking, say three things plainly.

• What the visit is. "This is a diagnostic visit. The tech will find the problem and fix it on the spot if it is a simple repair."
• What it costs. If you charge a diagnostic fee, state it at booking, along with whether it is credited toward the repair. That is your pricing decision; the scheduling point is that it must not be a surprise.
• What might happen next. "If it needs a part, we will book a second visit before we leave."

Then keep them informed on the day. Automated reminders handle the confirmation and the on-the-way text. If an earlier job overruns, a short message through two-way SMS before the window passes is worth more than an apology after. Our guide to arrival time windows covers how wide a window to promise on days with unknowns in them.

Learn your real numbers

After a month of running diagnostics as a fixed window, you will have something most shops never collect: data on what actually happens.

Look at three things.

• How often does the diagnostic end in a same-visit repair? If it is most of the time, your window may be slightly short and worth extending.
• How often does it need a return? If returns are frequent for one fault type, stock the part.
• Which job types overrun most? Those deserve a longer standard window or a guaranteed buffer.

The reporting view gives you job counts by type and outcome to work from. Adjust the window by trade and by job type rather than using one number for everything. For a neutral description of what diagnostic work involves across trades, the U.S. Bureau of Labor Statistics Occupational Outlook Handbook is a useful reference when writing job descriptions and training plans.

A simple starting setup

If you want to try this next week:

1. Create a "Diagnostic visit" service with a fixed duration.
2. Place diagnostics first or last in each tech's day.
3. Add one labeled buffer per two diagnostics.
4. Give techs the repair-now-or-return rule in writing.
5. Book every return before leaving the site.
6. Review the outcomes after thirty days.

Pricing shows what each plan includes, and the electrician software and appliance repair software pages show how the calendar, intake, and Tech Mode fit together for diagnostic-heavy trades.

Frequently asked questions

How long should you schedule for a diagnostic service call?

Block a fixed diagnostic window, commonly sixty to ninety minutes including travel margin, rather than trying to guess the repair. The window covers finding the problem and completing a simple fix; anything larger is quoted on site and either done in a held buffer or booked as a separate return visit.

Where in the day should diagnostic calls go?

Put them where an overrun does the least damage: as the first job of the day when a held buffer follows, or as the last job before an open block. Avoid placing an unknown-length call directly before a fixed commitment such as an installation or a tight arrival window.

Should a technician repair on the spot or book a return visit?

Repair on the spot when the part is on the truck and the work fits inside the time you have before the next commitment. Book a return when a part must be ordered, when the repair would push later customers past their windows, or when the job needs a second person.

How much does GetTimePad cost?

GetTimePad is $79/mo Starter for one staff member, $199/mo Pro for up to five staff, and $499/mo Agency for unlimited staff. Calendar scheduling with conflict detection and automated reminders is on every plan; Tech Mode, two-way SMS, and payments are part of Pro. Annual billing gives you two months free. See /pricing.

What is buffer time in a service schedule?

Buffer time is a block left deliberately unbooked so that an overrunning job has somewhere to go without making the next customer late. For days containing diagnostic calls, one buffer of thirty to sixty minutes per two unknown-length jobs is a common starting point.

How do you tell a customer the repair needs a second visit?

Tell them on site, before leaving, with a specific date. Explain what was found, what is needed, what it will cost, and when you will return, and book the visit in front of them so they receive the confirmation text while the technician is still there.