Service Decision Matrix: Equipment Service Call Checklist

Section 1 of 5

Should You Call?

Answer each question honestly. The goal is not to avoid service calls — it is to make sure the ones you do make are necessary and cost-justified. A service call made too early costs money; one made too late costs more. This section helps you find the right threshold for your situation.

Answer each question. Count your "Yes" responses. Scoring guide below.

☐ Yes

☐ No

Does your team have the technical knowledge to diagnose this fault internally? If no one on your crew can form a credible diagnosis path, you are not delaying — you are guessing.
☐ Yes

☐ No

Does your team have the tools required to diagnose and repair this fault? Missing a specialized tool is a legitimate reason to call — attempting a repair without the right tools often creates a second failure.
☐ Yes

☐ No

Is the equipment under an active warranty or service contract? If yes, an internal repair attempt may void coverage. Check the contract terms before proceeding independently.
☐ Yes

☐ No

Is this a safety-of-personnel issue requiring certified or licensed work? Electrical work requiring permits, pressure vessel repairs, and certain OEM-proprietary systems may legally require outside certified personnel.
☐ Yes

☐ No

Is production impact severe enough to justify a service call even before internal diagnosis is complete? If the line is down and every hour costs $X, the math may clearly favor calling immediately rather than spending hours on internal troubleshooting.
☐ Yes

☐ No

Has your team already spent more than 2–3 hours without a clear diagnosis path? Diminishing returns set in quickly when a team is stuck. Fresh eyes from a specialist often resolve in 1 hour what an internal team has spent 4 hours on.
☐ Yes

☐ No

Is this an OEM-proprietary system that requires factory software, firmware, or special calibration tools to diagnose or repair? Some systems physically cannot be serviced without OEM tools.
☐ Yes

☐ No

Is there a qualified technician available in-house in the next 4 hours? If your tech is on another job or off-shift for the next 8 hours, calling a vendor now may result in faster resolution than waiting.
☐ Yes

☐ No

Has this fault recurred more than twice after internal repair attempts? Recurring faults after repeated internal repairs indicate either a misdiagnosis or a systemic issue that requires deeper expertise.
☐ Yes

☐ No

Is the repair scope likely to exceed your team's available bandwidth to execute within the required timeframe? A repair your team can theoretically do but realistically cannot complete before the production deadline is effectively outside your current capacity.

Scoring Guide

Count the number of questions you answered Yes:

Yes Count	Interpretation
0–2	Internal resolution is appropriate. Proceed with internal diagnosis before calling. Document the diagnostic steps taken so the record is useful if a call becomes necessary later.
3–5	Service call is justified. Complete Section 2 before making contact — a prepared caller gets faster and more accurate service than an unprepared one.
6+	Call immediately. Focus your energy on Section 2 documentation and Section 3 quote evaluation — not on further internal troubleshooting.

Section 2 of 5

Pre-Call Documentation Package

Have every item on this list ready before you make the call. Vendors who receive a complete information package spend less time gathering data and more time solving the problem. It also reduces the chance that their first response is "I need more information before I can commit to anything."

Equipment make, model, and serial number — exact, from the nameplate. Vendors often have model-specific knowledge, common failure patterns, or recommended spares. The wrong model number sends them in the wrong direction before they arrive.
Current error codes, fault codes, or alarm history — all of them, with timestamps if available. A single error code tells a partial story. The sequence of codes over the last 24–48 hours often tells the full one. Pull the complete alarm log from the HMI or CMMS before calling.
Symptom description with timeline: when it started, how it progressed, and any changes in symptom pattern. Intermittent faults and gradual degradation are harder to diagnose than sudden failures. A clear timeline helps the vendor determine whether this is a wear-related failure or an acute event.
Last service date and what was done — including PM tasks, repairs, and any software updates. "What changed before this started?" is the first question any competent technician asks. Have the answer ready.
What has already been tried — including any parts replaced, settings adjusted, or temporary fixes attempted. Telling the vendor what has been ruled out saves them from repeating your diagnostic steps. If you replaced a component and the fault returned, say so — it is diagnostically significant.
Photos or video of the fault, error display, or affected component — captured before calling if the fault is visible. A photo sent before the technician arrives often allows them to arrive with the correct parts. A 30-second video of an intermittent fault can save hours of waiting for the fault to reproduce on site.
Your facility's access requirements, safety protocols, and any permit-to-work requirements the vendor technician must complete. A vendor technician who arrives and cannot start work for two hours due to facility onboarding requirements is a preventable cost. Communicate requirements in advance so they come prepared.
Your preferred service window and any production constraints that limit equipment access. Scheduling a service call during a production run that cannot be interrupted creates pressure on both sides. If your equipment access window is narrow, state it clearly — and get a commitment that the technician will arrive within that window.

Before You Hang Up

Confirm: (1) the technician's name and direct contact number, (2) the estimated arrival time with a specific window — not "sometime tomorrow," (3) what information they need you to have on-site when they arrive, and (4) whether they are bringing likely replacement parts or if that depends on their initial diagnosis. Parts availability is a common source of unexpected second trips and extended downtime.

Section 3 of 5

Quote Evaluation Checklist

Go through this checklist before signing any service authorization or purchase order. A quote that does not answer these questions is incomplete — and incomplete service authorizations are how unexpected invoices happen.

Is the scope of work clearly defined in writing? A verbal scope is not a scope. The quote should specify exactly what will be done — and by implication, what is explicitly excluded. "Diagnose and repair conveyor motor fault" is not a scope. "Remove and replace failed motor contactor, verify all phases and test motor under load" is a scope.
Are labor rates and estimated hours both specified? A quote that lists only a total labor cost without rates and hours cannot be validated. If the job runs over, you need a basis for evaluating the additional charge — which requires knowing the agreed rate.
Is travel time billed separately, and if so, at what rate and for how many hours? Travel time billing is common and legitimate — but it should be stated upfront. An invoice that includes 3 hours of travel not mentioned in the quote is a negotiating problem after the fact.
Are parts marked up, and if so, at what percentage above cost? Parts markups of 15–30% are common. Markups above 50% on standard catalog items are worth pushing back on. Ask for the parts to be listed at cost with markup stated separately — this is a reasonable commercial request.
What is the escalation process if the initial diagnosis turns out to be wrong? If the first replacement part does not fix the problem, who pays for the next diagnostic step? Clarify whether there is a re-diagnosis fee, whether the technician will return at no additional travel charge, and who is responsible for the cost of the incorrect initial repair.
Is there a warranty on the repair, and what does it cover? At minimum, labor and parts installed should carry a 30–90 day warranty. A vendor who offers no warranty on their work is signaling something. Get the warranty terms in writing before work starts, not after.
What is the payment trigger — diagnosis completion, repair completion, or successful restart verification? Tying payment to restart verification (equipment operating normally under production load) protects you if the repair appears complete but the fault returns under operating conditions. This is standard in most well-structured service contracts.

Emergency Service Rates

Emergency or after-hours service typically carries a premium of 1.5–2.5x the standard rate. This is normal and acceptable — but it should be disclosed before the technician is dispatched, not listed as a line item on the invoice. If the rate is not mentioned when you call, ask explicitly: "What is the rate for a same-day emergency call?"

Section 4 of 5

Post-Service Documentation

Collect these items before the vendor technician leaves the site. Once they are off-site, getting documentation becomes much harder — and some vendors treat documentation as optional unless you ask for it explicitly.

Written fault finding summary — what was found, not just what was replaced. The failure mode and contributing factors are as valuable as the repair itself. A summary that says only "replaced motor" tells you nothing useful for future maintenance planning or recurrence prevention.
Parts replaced with exact part numbers, quantities, and (if available) lot or serial numbers. Part numbers are necessary for stocking spares and verifying that the correct parts were used. Generic descriptions like "replaced relay" are not sufficient for parts records.
Root cause identified — confirmed or still under investigation? A repair without a confirmed root cause is a repair that may recur. If the technician cannot confirm root cause, that should be explicitly stated so you know a follow-up investigation is still needed — not assumed complete.
Recommendations for preventing recurrence — specific PM tasks, monitoring points, or operating adjustments. A good service technician will leave you better prepared than when they arrived. If the fault was caused by an inadequate PM frequency or a missing inspection task, that recommendation should be captured and acted on.
Warranty terms in writing — coverage period, what is covered, and the process for making a claim. A verbal warranty is worth nothing six weeks later when the equipment fails again and the technician does not recall committing to anything. Get it in writing on the service report before signing.
Technician contact information for follow-up questions — direct number or email, not just a general service desk number. If the equipment behaves abnormally in the week following a repair, the technician who performed the work is the most useful person to talk to. A direct contact is significantly more effective than starting over with a service desk intake process.

File It Now, Not Later

Attach the completed service report to the work order in your CMMS before the end of the shift. Service reports that go into a physical file, a desk drawer, or an email inbox are frequently lost before the next PM review cycle. The asset record is where this information belongs — not in someone's inbox.

Section 5 of 5

Build vs. Buy Tracker

Use this table to track patterns in your service calls over time. If you are repeatedly outsourcing the same repair type, you are paying a vendor for a skill your team could develop in-house — and the cost of developing that skill is likely far less than the cumulative outsourcing cost over two or three years.

Repair Type	Times Outsourced in Last 12 Mo.	Estimated Total Cost ($)	Could Team Have Done It? Y/N	Skill Gap Identified	Training Plan? Y / N / Pending

How to Use This Table

Review it quarterly. Any repair type that appears more than twice in 12 months with a "Yes" in the "Could Team Have Done It?" column is a candidate for internal capability development. Common examples: VFD fault diagnosis, laser shaft alignment, hydraulic system troubleshooting, and PLC-based fault diagnosis. Each of these can be developed through targeted training at a fraction of the annual outsourcing cost.

Reduce Service Calls Through Better Prevention

Two Resources Worth Knowing About

Preventive Maintenance Playbook ($99) — A complete PM system that helps you prevent the faults that generate service calls in the first place. Includes failure mode analysis, frequency selection logic, task-building templates, and a 90-day tracking system.

Service Requests — If you need to request outside service through Equipment Uptime Systems's network, you can submit a service request directly from the site. Providers in the network are familiar with the documentation standards on this checklist.

PM Playbook → Submit a Service Request →