MEPflow
Sign in Start free
MEPflow Blog

Field Service Reporting for Plumbing, HVAC and Electrical Shops

What a good field service report captures, which reports an owner needs, and how to move a 2 to 30 truck trade shop off paper onto digital job reporting.

Published 14 min read

Geometric records forming a shop-wide report

Field Service Reporting for Plumbing, HVAC and Electrical Shops

Geometric records forming a shop-wide report

Field service reporting is the habit of turning every job into a record the office can use: what was done, by whom, with which materials, for how long, and what the customer saw. For a plumbing, HVAC or electrical shop, the reports that matter are the ones that get the invoice out the same day, show where a job lost money, and prove the work if a customer calls back. This guide covers what to capture, which reports an owner should read, and how to get a crew off paper without a revolt.

MEPflow
mepflow.app
Turn Job Records Into Useful Reports
MEPflow connects field job details with scheduling, invoicing and job costing, with offline capture that syncs when signal returns.
See MEPflow’s reporting tools

TL;DR

Table of Contents

What field service reporting means for a trade shop

Search this topic and you will find plenty of pages written for large service organizations: dashboards, asset registries, enterprise modules. A 2 to 30 truck shop has a simpler need. You need to know what happened on each job and what it means for money.

There are two layers. The first is the job report, the record one technician creates on one visit. The second is management reporting, the roll-up the owner or office manager reads across all jobs: completed work, hours, margin, open invoices, callbacks.

The job report is the raw material. If it is late, vague or missing, every report built on it is wrong. That is why most of the fix is at the truck, not in the office.

A useful reference point comes from the U.S. Department of Energy. Pacific Northwest National Laboratory describes its Quality Installation Report as a record of the work done and its quality at completion for the customer, documentation for the contractor, and a way for quality-assurance reviewers to evaluate work without traveling to the site. That is a good summary of what any job report should do for a trade business too: reassure the customer, protect the contractor, and let someone who was not there understand what happened.

What every job report should capture

The fields below cover almost every residential and light commercial service call. They are the same whether the tech is replacing a water heater, diagnosing a no-cool call or swapping a panel.

Field What it is Who in the office uses it
Technician and crew Who was on the job Payroll, dispatch
Date, arrival and departure time When the work happened Payroll, job costing
Customer and service address Where and for whom Billing, customer service
Reported problem and findings What the customer said and what the tech found Dispatch, future techs
Work performed Plain description of what was done Invoicing, warranty
Parts and materials Items used, with quantities Invoicing, job costing, inventory
Labor hours Time on the job Invoicing, job costing
Photos Before, after, nameplates, problem areas Warranty, disputes, estimates
Follow-up needed Recommended repairs, return visits Sales, scheduling
Customer sign-off Approval or acknowledgment Billing, dispute protection

A few notes on getting these right.

Write findings, not just actions

“Replaced capacitor” is an action. “Condenser fan not starting, capacitor reading low, replaced, fan running, amp draw normal” is a finding that helps the next tech and justifies the charge to the customer.

Measurements are worth the extra minute

For equipment work, readings make the report far more valuable. A U.S. government-backed guide on service contracts, published with EPA involvement, advises building owners to require measurements such as motor amps, volts, temperatures and pressures to be taken and documented for each piece of equipment. The same guide notes that logging those readings over time can help reveal efficiency and reliability problems and support the case for a repair, adjustment or replacement.

That is useful for a service shop selling maintenance agreements. A customer who sees last spring’s readings next to this fall’s has a reason to approve the repair you are recommending.

Photos do the heavy lifting

A photo of the old part, the data plate and the finished install settles most disagreements before they start. It also gives the office something to attach to an estimate when a tech finds a bigger problem. The PNNL approach shows the same thing at scale: standard prompts plus photo documentation make records comparable and let a reviewer judge quality without a second site visit.

Reports an owner or office manager should actually read

Once job reports are consistent, a short list of roll-ups covers most of what a small shop needs. Skip the sprawling dashboard and start here.

  1. Completed jobs and open jobs. What got finished, what is still waiting on parts, approval or a return visit.
  2. Completed but not invoiced. The most expensive gap in a small shop. Work that is done and unbilled is cash you have already spent.
  3. Hours by job and by technician. Labor is usually your largest cost. You need to see planned hours against actual hours.
  4. Materials by job. Parts used against parts quoted, so you can see which jobs leak margin.
  5. Job margin. Revenue less labor, materials and a share of overhead. This is where job costing earns its keep.
  6. Callbacks and repeat visits. A cluster of returns on one tech, one equipment type or one supplier is a training or purchasing signal.
  7. Estimate-to-close. Which Good, Better or Best options customers choose, and which techs convert recommended work.
  8. Accounts receivable. Who has been billed, who has paid, who needs a nudge.

Notice what is not on the list: vanity numbers. Every report above leads to a decision a person in your shop can make this week.

Track real onsite time

Accurate hours depend on knowing when a technician arrived and left. The same federal service-contract guide recommends that building managers require technicians to sign a log on entering and leaving a facility so actual hours onsite can support payment authorization. Your customers on commercial and property-management accounts may ask for exactly this. Timestamps captured automatically in the job report answer the question without a clipboard. If you are also thinking about forecasting labor for contractors, documented actual hours per job are the data that makes any forecast honest.

How job information gets from the truck to the office

There are really only three ways a report travels.

Paper and a drive-by. The tech fills out a carbon form, drops it at the shop at the end of the week, and someone types it in. Invoices go out late and details are lost.

Photo of the paperwork. Better, but the office still retypes, and nothing is searchable.

Capture on the phone, sync to the office. The report is built during the job, and the office sees status, photos and materials without calling the tech.

The third path only works if it works without signal. Plenty of service work happens below grade or inside buildings with poor coverage. A public example shows how this is meant to function: Pinellas County, Florida, publishes a contractor guide for its VuSpex field-report tool that lets contractors start a report without internet, add photos, video and comments, save it, and send it once connectivity returns. The generated summary carries the permit information, inspection type, media, date and time, and GPS verification.

Three paths for sending field reports

That is a county inspection workflow, not a service-business tool, but the principle transfers: capture first, sync later, and make the record complete when it arrives. If you want to see how we test that on a phone in a real truck, our piece on mobile field service software for small shops walks through an offline check you can run yourself.

The EPA-backed guide makes a related point for handheld recording devices: data should reach the maintenance office in a timely manner, whether entered into a computer or sent as a hard copy. “Timely” is the whole game. A report the office sees tomorrow is a report that cannot drive today’s invoice.

Our perspective: reporting is a byproduct, not a chore

We build MEPflow in Rogers, Arkansas, and the team is a master plumber, a master electrician and an HVAC technician. We run the software on our own trucks before anyone else sees it. That shapes how we think about reporting.

Technicians do not hate reports. They hate typing the same thing twice, and they hate being asked for paperwork at the end of a ten-hour day. So we do not think of field service reporting as a separate task. The report should fall out of the work: the tech adds a photo because the photo is how they show the problem, adds a part because that is how it gets billed, and taps a status because that is how the office knows to send the customer a text.

Three convictions come from that.

One record, not three. The schedule, the estimate, the invoice, the timeclock and the job cost should all read from the same job. When a report lives in a separate app from billing, someone in your office becomes the human bridge between them, and that someone makes mistakes at 6 p.m.

Reports belong to the office and the truck equally. A phone-only tool leaves the office manager squinting at a small screen. An office-only tool leaves the tech guessing. You need a full desktop side and a mobile-first field side running the same data.

Our perspective: reporting is a byproduct, not a chore — overview diagram

Do not paywall visibility. Every feature in MEPflow is on every plan; plans differ only by how many people are on them. A 3-truck shop should be able to see job costing the same way a 25-truck shop does.

We would rather a shop run five clean report fields consistently than fifty fields half the crew skips.

— Jonathan

Moving from paper, spreadsheets or a whiteboard to digital reports

Most shops we talk to are not starting from nothing. They have a paper invoice book, a spreadsheet for jobs, a whiteboard for the week and a lot of texting. The risk in switching is not the software. It is getting seven technicians to change a habit on a Tuesday.

A rollout that tends to hold up looks like this.

  1. Start from your existing paper form. Keep the fields your people already fill out. Strip the ones nobody in the office reads.
  2. Pilot with one crew. Pick the tech who is least afraid of a phone and the one who is most skeptical. If both can use it, the rest will.
  3. Fill out the first report together. Do it side by side on a real job so questions get answered in the truck.
  4. Decide what is required. Work performed, parts, time and at least one photo are a reasonable floor. Everything else can be optional.
  5. Review the same day. The office should open reports that afternoon or the next morning, fix gaps and give feedback while the job is fresh.
  6. Set a retirement date for paper. Without a date, paper lives forever and you run two systems.

Two practical details make the cutover smoother. First, bring your history with you. We import your existing customer and job data for you, so techs see the customer’s past work on day one rather than starting from a blank screen. Second, keep your accounting in place: MEPflow integrates with QuickBooks, so reports flow to invoices and invoices flow to your books rather than the other way around.

From report to invoice to job cost

The payoff of consistent reporting shows up in two places.

Faster invoicing

An accurate report hands billing the documented labor, materials and work performed. Nothing needs to be guessed or reconstructed from a tech’s memory on Friday. If the job began as an estimate, the best setup carries those line items forward so the invoice is not retyped; we cover that in our estimate to invoice workflow. When the invoice can go out with a payment link from the driveway, the money arrives sooner, and the customer still has the job fresh in mind.

Spotting job-cost problems

When parts and labor hours are recorded per job, a few patterns jump out:

None of these show up in a revenue total. They only show up when you compare actual cost against what you charged, job by job. For a broader look at where else time leaks out of a service day, see our seven steps to improve field service efficiency.

What to look for in field service reporting software

Most software pages will promise reports. Use these criteria to separate a tool built for trade shops from a generic one.

If you are coming from a larger platform, ask whether you will use the depth you are paying for. Many shops switching from Housecall Pro, ServiceTitan or Jobber tell us the reports they used were a handful, not dozens.

Do not forget maintenance work

If you sell recurring service, reporting should also cover scheduled visits. Repeat reports on the same equipment build the history that sells the next repair. Our 30-day preventive maintenance scheduling pilot shows one way to start small.

Field service reporting in MEPflow

MEPflow puts scheduling and dispatch, Good/Better/Best estimates with photos, invoicing with instant payment links, job costing, customer texting, timeclock and payroll, a per-trade pricebook and trade calculators in one mobile-first app with a full desktop office side. It works offline, and photos, materials and job status sync when signal returns. KPI and reporting tools sit on the same data, so what the tech records in the field is what the owner reads in the office.

Every feature is on every plan, and plans differ only by crew size. See the details on the MEPflow home page and the pricing section at https://www.mepflow.app/#pricing.

There are two ways to start. Free signup is capped at 5 customers and does not include the trade tools. If you want the full product in front of your crew, call 866-808-4996 to book the 14-day trial. When you are ready, Create your company account.

FAQ

What is a field service report?

It is the record a technician creates for a visit: who went, when, where, what was found, what was done, which parts were used, how long it took, and often photos and a customer signature. The office uses it to invoice, to track job costs and to answer warranty or callback questions.

What is the purpose of a field report for a plumbing, HVAC or electrical contractor?

It gives you proof of work and a base for billing. It also gives the customer a record of what was done and gives you something to point to if a problem comes up later. Over time, a stack of consistent reports shows you where jobs make or lose money.

How is field service reporting software different from a paper form?

Paper has to be carried, read, and retyped before anyone can invoice from it. Software captures the same fields on a phone, attaches photos, timestamps the work and makes the record visible to the office right away. The best tools also tie the report to invoices and job costing so nothing is entered twice.

Does field service reporting software need cell signal?

It should not. Look for software that saves the report on the phone and syncs photos, materials and status when signal returns. Test this before you commit by running a job in airplane mode and checking that nothing is lost on reconnect.

Where can I see what MEPflow costs?

Pricing is on the MEPflow pricing section of our site. Plans differ only by the number of people on them, and every feature is included on every plan.

Sources

MEPflow
Talk Through Your Reporting Needs
Contact MEPflow to discuss how its field-service software supports job records, invoicing and job costing for plumbing, HVAC and electrical shops.

Recommended

Where to next