Most plumbers have at least one story about a callback that turned into a dispute because nobody could remember exactly what was done on the original visit. The customer says you replaced the cartridge. You remember replacing the whole valve assembly. The cartridge wasn't the problem — the valve seat was eroded — and you charged accordingly. But your handwritten ticket said "fixed faucet leak" and the customer is now arguing the bill.
A clean service ticket prevents most of these arguments. It also makes the customer more likely to call you back next time, refer you to their neighbor, and actually pay the bill without delay. The ticket is the work product. The work product is what builds the practice.
This is a field-tested template for plumbing service tickets, with notes on why each section matters and what specifically to capture. Use it as a structure. Adapt it to your trade. The point is consistency.
The header
Boring; essential. Every ticket needs:
- Date — exact, not "this week"
- Address and unit — the unit number matters in multi-family buildings
- Customer name and contact — name on the ticket, not just "the homeowner"
- Site contact if different — the property manager who let you in, the housekeeper, the tenant
- Job number or reference — your own internal tracking
- Tech name — the person doing the work
The reason this matters: when a callback happens, you need to be able to find the original ticket within 30 seconds, and you need to know who to ask if the details aren't clear.
Symptoms reported
What did the customer call you for, in their own words.
"Customer reports kitchen faucet drip that started over the weekend. Says it drips even with both handles fully closed. Had a plumber out 18 months ago for a similar issue."
The reason this matters: it documents what you were told. If the customer later says they told you about something else, you have the record. It also frames the rest of the ticket — what you tested for, what you ruled out.
Notice the third sentence in that example. A previous service call to address the same issue is information your future self (or the next plumber) needs. Capture it when the customer mentions it.
What you found
Distinct from what the customer told you. This is your diagnosis.
"Confirmed continuous drip at kitchen faucet, approximately 1 drip every 4 seconds, both hot and cold sides. Faucet is a Moen 7565 single-handle, 2018 vintage. Cartridge inspection showed worn seals and erosion at the valve seat. Single-handle base assembly also showed corrosion suggesting prior leaking under the deck."
Specific. A number for the drip rate. The make and model of the faucet, with the year if you can tell. The actual condition of what you saw.
The model and year matter for warranty, parts ordering, and the next service call. "Old Moen faucet" tells you nothing in two years. "Moen 7565, 2018" tells you everything.
A photo of the model plate or product label takes five seconds and saves you 15 minutes the next time. The same applies to water heaters, pumps, pressure tanks, anything with a sticker. Some plumbers use voice memos that auto-transcribe and pull data from photos taken during the call; others just keep a folder per property. Either works. The information has to be findable.
Work performed
The line items. Each one specific.
- "Replaced Moen 1225 cartridge in kitchen faucet."
- "Cleaned and re-greased valve seat with manufacturer-spec grease."
- "Tested for leaks at 60 psi static pressure. No drip after 10 minutes of observation."
Three lines. Specific about what was done, how it was done, and how the work was verified.
The verification line — "tested at static pressure, observed for X minutes" — is worth its weight in gold on a callback. If the customer calls back two weeks later saying the faucet is still leaking, you have a record that it was tested and dry when you left. That doesn't mean the same problem hasn't recurred (different problem entirely is possible), but it means you can defensibly bill for the second visit as a separate issue.
Parts used
Every part, with a part number where you can.
| Item | Quantity | Part / SKU |
|---|---|---|
| Moen 1225 cartridge | 1 | Moen 1225 |
| Plumber's grease | as needed | — |
| Replacement aerator (preventive) | 1 | Moen 169257 |
Three reasons to be specific:
- The customer's invoice should match. If the customer asks "what's this $42 charge for," you can point to the line item.
- Warranty claims. A failed cartridge inside the manufacturer's warranty period gets you a free replacement, but only if you have the part number and the install date.
- Inventory tracking on your end. You need to know what you used today so you can replenish what's on the truck for tomorrow.
Recommendations
This section turns service tickets into renewal opportunities. The customer's faucet is fixed. What else do you see?
"Recommend replacing kitchen supply lines (current lines are original braided stainless from 2018, showing some kinking near the shutoff). Estimate $180 parts and labor."
"Water heater is a 2014 GE 50-gallon electric. Tank shows no immediate concerns but is approaching the end of typical service life (10-12 years). Recommend planning for replacement within the next 1–2 years."
"Pressure-reducing valve at the meter shows mineral buildup. PRV is functional but I'd flag for monitoring; replacement may be needed in the next 1–2 years."
Three recommendations, each with a reason and a rough timeline. This is the section the customer reads twice. It's also the section that produces follow-up bookings — when their water heater fails next year, they'll call you because you flagged it.
The line you don't want here is a list of upsells. A recommendation is something you'd genuinely advise based on what you saw. Customers can tell the difference, and the trust you build is worth more than the marginal revenue from forced upsells.
Photos
Modern service tickets should include photos. The minimum:
- The model plate of any equipment touched.
- The condition before for any major repair.
- The condition after for any major repair.
- Any concern flagged in the recommendations section.
Some shops still resist photos. They take time. They require a phone hand. They can feel like overhead. But the truth is they cut your follow-up time on every callback, and they're the strongest evidence in any disputed bill.
Customer signoff
The customer signs the ticket acknowledging the work was completed and the description matches their understanding of what was done. On a phone-based system, this is a captured signature. On paper, it's a signature line.
The signature is not a magic shield against disputes, but it shifts the conversation. A signed ticket means the customer agreed in writing that this is what was done. They can still dispute the bill, but they cannot credibly claim "that's not what we discussed" — because the ticket they signed was specific.
What separates a clean ticket from a sloppy one
A sloppy ticket says: "Fixed kitchen faucet leak. Replaced cartridge. $245."
A clean ticket says everything in the sections above and also makes you a more defensible business. The customer can read it and understand what happened. The next plumber to look at the property can read it and understand the history. Your future self can read it and remember.
The mechanical work — pulling the cartridge, swapping it, testing the result — takes the same amount of time either way. The documentation is what compounds.
A real example
Here's a ticket as it would actually look in the field, written normally, no formatting tricks:
Service Ticket #2026-0418-A Date: 2026-04-18 Address: 8 Washing Pond Rd, Nantucket — Miller residence Tech: [Name]
Symptoms reported: Kitchen faucet dripping, started over the weekend. Customer says drip continues with both handles fully closed. Mentioned similar issue ~18 months ago.
Diagnosis: Confirmed steady drip at kitchen faucet, ~1 drip every 4 seconds. Moen 7565 single-handle, install date 2018 per data plate. Cartridge teardown showed worn seals and slight valve seat erosion. Base assembly shows corrosion at deck plate suggesting prior leaking. No issue at supply stops; both stops working.
Work performed:
- Closed both supply stops, drained line, removed handle and decorative cap.
- Pulled and replaced Moen 1225 cartridge with manufacturer OEM part.
- Cleaned valve body, applied plumber's grease per Moen spec.
- Reassembled, opened stops, tested at static pressure 65 psi (measured with gauge).
- Observed for leaks 10 minutes — no drip.
- Replaced aerator while accessible (mineral buildup).
Parts used:
- Moen 1225 cartridge — OEM, $32
- Moen 169257 aerator — $14
- Plumber's grease — included
Photos: Faucet model plate (1), worn cartridge before (2), new cartridge installed (3), final test with gauge reading (4).
Recommendations:
- Kitchen supply lines (braided SS, 2018) — kinking near shutoffs. Recommend replacement next visit. Est. $180.
- GE 50-gal electric water heater (2014) — no immediate issues but past mid-life. Recommend planning for replacement in 12–24 months.
- PRV at meter — mineral buildup visible. Functional. Flagged for monitoring.
Customer signature: [signed] Total: $245.00
That's a defensible ticket. It tells the story of the visit completely. The customer reads it and understands what they paid for. The next plumber reads it and knows the history. The plumber's own future self reads it and remembers.
The compounding effect
The shift from sloppy tickets to clean ones doesn't pay off on the first ticket. It pays off over a year. Customers stick. Disputes drop. Referrals climb. The shop's records become a competitive advantage when bidding on larger contracts that require documented work.
The mechanical work is the same. The documentation compounds. Pick a ticket format, use it consistently, and the practice changes.
The compounding effect is biggest on accounts you visit repeatedly — water-heater service contracts, multi-unit residential plumbing, commercial maintenance agreements where the same building gets touched four times a year by three different techs. That's where having every ticket filed under the same property record becomes the asset, not the ticket itself. If that's the kind of work you're doing more of, that's the kind of work Vocalog is built around.