The GC's punch list arrives as a PDF with 31 items on it. Four have your name next to them. You send a hand out for a morning and clear them.
Three weeks later the same address calls. A receptacle in the east corridor is dead, and the voice on the phone already knows whose fault it is.
Punch list and warranty callback time tracking on electrical work comes down to one question: which of those hours were already paid for in your contract, and which ones you are entitled to bill. That argument gets decided by whatever got written down at the time — which is usually nothing.
When the only record of the trip says "callback — 2.3 hrs," there is nothing to decide it with. That line explains nothing to the person being asked to pay for it.
The charge was fair. The explanation was missing.
This post gives you the classification rule, the cost-code setup, the exact field note, and a log you can copy into a spreadsheet this afternoon. None of it requires buying anything.
Punch List or Warranty Callback? Final Acceptance Is the Line
A punch item is defective or incomplete work found before the owner accepts the project. A warranty callback is a defect that surfaces after acceptance, during the correction period. The ladder work can be identical. The paperwork, the money, and the person who dispatched you are not.
Punch gets absorbed into the job. You are still mobilized, still under the original contract, and the item is standing between you and retainage.
A callback lands months later, usually through a warranty coordinator rather than the super you knew, and often goes to a crew that never worked the building.
| Punch item | Warranty callback |
|---|
| When it happens | Before final acceptance | After acceptance, inside the correction period |
| Who calls you | Superintendent or PM | Warranty coordinator, owner, or property manager |
| Contract status | Open, you are still on site | Closed out, job is billed |
| What it gates | Substantial completion, final payment, retainage | Nothing financial — it is pure cost unless reclassified |
| Typical window | Days to weeks | One year is common; check your subcontract |
| How it should be coded | Separate punch code on the same job | New callback job tied to the original job number |
The AIA A201 general conditions carry a one-year period for correction of work running from substantial completion. Your subcontract may flow down something longer or shorter, and a correction period is not the same thing as a product warranty. Read yours before you quote a date to anybody.
Who Pays for Punch List Items?
You pay for punch list items that are defective or incomplete work inside your own contract scope. The GC or owner pays when the item is a scope change, or damage caused by someone else after your work was complete and verified.
That is the contract answer and it is correct. It is also useless standing in a corridor at 3:40 on a Thursday.
By the time the argument happens, the contract is already signed. The only live variable left is evidence — what you can show about the condition of that circuit the last time you touched it.
So treat "who pays" as an evidence question, not a legal one. The rest of this post is about producing that evidence in under a minute.
The Four Buckets Every Closeout Hour Falls Into
Every punch item and every callback lands in one of four buckets. Run the item through them before anyone drives, because the bucket decides the cost code, the note, and whether you need a signature first.
| Bucket | What it is | Electrical examples | Who pays |
|---|
Buckets 1 and 2 you absorb without complaint. That is the trade.
Buckets 3 and 4 are where the money is, and they are the two that get silently filed as bucket 1 or 2 because nobody wrote down what they found.
The classification has to happen at the item level, not the trip level. One truck roll can easily contain a bucket-1 cover plate and a bucket-3 severed neutral, and if you code the whole trip as "punch" you just gave away the billable half.
How to Track Punch List and Warranty Callback Hours Separately
Give closeout work its own cost codes on day one, so those hours never contaminate the original contract's job cost. Five steps, and none of them require new software.
1. Add a punch code to every job when you set it up. Not when the punch list arrives — at setup. If job 1042 is1042-BASE, add 1042-PUNCH before the first man-hour is booked.
2. Open a callback job at closeout, tied to the original number. 1042-CB stays open for the correction period. It is where every post-acceptance trip to that address gets booked.
3. Add a disputed code, and use it liberally. 1042-DISP holds bucket 3 and 4 hours until somebody in the office decides. Hours parked in disputed can move; hours already buried under 1042-BASE never do.
4. Give the crew four choices, not a taxonomy. On the timesheet, the phone, or a card taped inside the van door: Punch · Callback · Not ours · Extra work. Four words. If they cannot tell, "Not ours" is the default and the office resolves it the same day.
5. Never let a bucket decision wait a week. The person who saw the condition is the only one who can classify it, and by Friday they have been in six other buildings.
That is the whole method. A fifth column on a paper timesheet does it, a spreadsheet does it, and so does any time-tracking app with a cost code and a notes field on the clock-out screen — FieldTimesheet is one of those, and it is not the part that matters. The code and the note do the work; the tool just decides how much friction stands between the electrician and writing them down.
Once punch and callback hours live on their own codes, two numbers appear that you could not see before: your punch hours as a percentage of contract hours, and your callback rate per job. Both are watchable, and both should shrink. The related setup for the base job is in our job costing guide for electricians.
For context on scale: CII field-rework research has put direct rework near 5% of total construction cost. That is industry-wide, not electrical-specific, and it is exactly the kind of number you cannot confirm or dispute for your own shop until closeout hours have their own code.
What the Electrician Writes at the Callback
One line, written at the truck before the ladder goes back on the rack: when you arrived and left, where you were, what you found, what you did, and which bucket it lands in.
Sixty seconds. It is the single highest-value minute anybody spends on a callback.
| What usually gets written | What settles the argument |
|---|
Three rules make those notes hold up.
Write the condition, not the conclusion. "Neutral severed above ceiling at grid C-4, new low-voltage cable run through the same penetration" is a fact anybody can go verify. "The data guys cut my homerun" is an accusation. Write the fact; let the office draw the conclusion. Anchor to a date when the work was known good. A final or trim inspection where the devices were energized and tested, a walkthrough sign-off, a megger reading, a signed test sheet. Rough-in does not count for devices — at rough inspection the receptacles are not installed yet, so nothing about them was tested. A defect claim dies the moment you can show the circuit tested correct on a specific day and name what changed after. Photograph the defect before you repair it. Once it is fixed, the evidence is gone forever and all that is left is your word against theirs — which is the exact position you are trying to get out of.That last one is the whole reason to bother. This is not paperwork for its own sake, and it is not about proving your electrician was on site. GPS proves presence; it does not prove cause. The note is what protects the crew from being blamed for a hole somebody else's screw made.
The Punch and Callback Log You Can Copy
One row per item, not per trip. Build it in a spreadsheet or print it — the columns are what matter.
| Column | What goes in it |
|---|
| Date / in / out | 8/09, 8:14a–10:32a |
| Job + unit / area | 1042 — Suite 214, restroom |
| Item as the GC wrote it | "Outlets not working, Suite 214 restroom" |
| What we found | Ungrounded conductor severed in the wall at the mirror blocking; drywall cut and re-patched in that bay |
| What we did | Re-pulled the run back to the last accessible box, re-terminated, tested both receptacles |
| Last known good | Final inspection 6/03 — receptacles tested, polarity correct, GFCI verified |
| Photo ref | 3, 4 |
| Bucket | 3 — not ours |
| Hours + who | 2.3, J. Reyes |
| Billable? | Yes — authorization requested 8/09 |
| Authorized by | Name, date, signature or written reply |
Two of those columns do all the heavy lifting. Last known good is what converts your opinion into a timeline, and Authorized by is what keeps a billable callback from turning into a fight at invoice time.
If you would rather not build it from scratch, the T&M Billing Backup Kit has printable versions of the four documents this workflow needs: a labor backup sheet, a daily field report, a change-order log, and a T&M work authorization form. Free, no signup, and they work whether or not you ever run software.
What One Callback Trip Costs: Example Arithmetic
Here is one trip with every input visible. These are example numbers — swap in yours.
| Input | Example value | Cost |
|---|
| Drive time, round trip | 1.2 hrs @ $48/hr loaded labor cost | $57.60 |
| Time on site | 1.5 hrs @ $48/hr | $72.00 |
| Vehicle | 34 mi @ $0.70/mi | $23.80 |
| Material | 2 devices + plates | $14.00 |
| Office time scheduling and closing the item | 0.4 hr @ $35/hr | $14.00 |
| Total, one trip | ≈ $181 |
Now run it forward with your own trip count. Example: 12 callback trips in a month at that cost is about $2,170 of field time. If three of those twelve are bucket 3 or 4 and get authorized and billed at $95/hr for the 2.7 field hours each, that is roughly $770 recovered — from three notes that took a minute apiece.
Change any input and the answer changes. That is the point: the arithmetic is yours, not a claim about your business. If you want to price out the broader version — what disputed and slow-paid invoices cost — there is a calculator for the argument itself.
Getting Paid for a Callback That Isn't Yours
Get authorization in writing before the wrench turns, unless it is life-safety. A billable callback performed without authorization is a donation with extra steps.
Here is wording you can send as-is, from the truck:
Ref: 1042 — Suite 214, restroom receptacles.>
We're on site. Both receptacles are dead with no trip at the breaker. We found the ungrounded conductor severed in the wall at the mirror blocking, in a bay that has been cut open and re-patched. These receptacles tested correct at our final inspection on 6/03, so this looks like damage after our work, not a defect in it. Photos attached.>
We can correct it now, T&M at our contract rate, and send the labor backup with the photos on the invoice. Reply "approved" and we'll take care of it today. If you'd rather we stand down, tell us and we'll pull off.
Three things make that message work. It states the condition before the conclusion. It gives a date the work was known good. And it makes approving easier than arguing.
If it is life-safety — no power to a panel, an exposed conductor, a failed egress light — go do the work. Then send the same note the same day, past tense, with the photos. Never let the record get written the following week.
When the invoice goes out, the backup page beside it should show date, who, what was done, hours, rate, and amount — and nothing about your labor cost. You can see what a finished one looks like on our sample billing packet, and the fuller structure is in T&M billing best practices.
Punch List Hours and Retainage
The punch list is what stands between finishing and getting your retainage released, so a closed-out list with dated notes is a payment document, not paperwork.
Send the closeout package as one packet, not as a string of emails. Ours-in-order looks like this:
- The punch log, every item marked complete with a date and initials
- Test documentation — GFCI/AFCI verification, megger readings, emergency and egress lighting test results
- Panel schedules, as-builts, and arc-flash labeling confirmation
- O&M manuals and warranty letters for owner-supplied and specified gear
- Any change orders written off the punch list, signed
- Your retainage release request, referencing the packet
The Short Version
- A punch item is found before acceptance. A warranty callback is found after. The work looks the same; the money does not.
- Every closeout hour is bucket 1 (punch), 2 (warranty), 3 (damage or another trade), or 4 (scope change). You absorb 1 and 2. You bill or backcharge 3 and 4 — with proof.
- Classify at the item level, not the trip level, or you give away the billable half of a mixed truck roll.
- Set up
-PUNCH,-CB, and-DISPcodes at job setup, so closeout hours never hide inside the base contract. - The note is the evidence: arrive/leave, location, what you found, what you did, last known good, photo, bucket.
- Write the condition, not the conclusion. Photograph the defect before you repair it.
- Get authorization in writing before billable work, unless it is life-safety.
Frequently Asked Questions
Who pays for punch list items on an electrical subcontract?The electrical sub pays for punch list items that are incomplete or defective work inside their own scope — that work was priced into the contract. The GC or owner pays when the item is a scope change written onto the list, or damage caused by another party after your work was verified complete. The contract sets the rule; your field documentation decides which category the item falls into.
What is the difference between a punch list item and a warranty callback?Timing relative to acceptance. Punch items are found during final walkthrough before the owner accepts the project and are handled under the open contract. Warranty callbacks come in after acceptance, during the correction period, on a job that is already closed and billed.
How long does the electrical warranty period usually run?One year from substantial completion is the common default — the AIA A201 general conditions carry a one-year period for correction of work. Your subcontract may flow down different terms, and equipment manufacturers carry their own separate warranties. Read your actual contract rather than relying on the industry default.
Should punch list hours go on the original job in QuickBooks?Keep them on the same customer and job number but on a separate cost code, such as 1042-PUNCH. That way the original contract's job cost stays honest for future bidding, and you can see punch hours as a percentage of contract hours instead of having them disappear into the base labor number.
They can attempt it, and the outcome depends on what you can show. A dated record that the devices tested correct at final inspection — rough-in does not count, since the devices are not installed yet at rough — plus a photo of the found condition and a description of what changed after, is what turns a backcharge into a conversation. A record that says only "2.3 hrs" gives you nothing to stand on.
Do I need photos, or is a written note enough?Take the photo. A note describing a severed conductor is good; a note plus an image of the cut cable in the open wall, taken before the repair went in, is what ends the discussion. Repair destroys the evidence, so the photo has to happen first.
If the callback really is our defect, is there any point documenting it?Yes, for two reasons. Documented warranty work gives you a real callback rate per job and per crew, which is the number that tells you whether an install-quality problem is actually shrinking. It also keeps the honest ones separated from the disputed ones, so a GC cannot lump them together and imply a pattern that is not there.
How do I bill a callback that turns out to be someone else's damage?Stop before you start the repair, send the condition, the last-known-good date, and the photos, and ask for written approval to proceed T&M. Then invoice it with the labor backup attached — date, worker, what was done, hours, bill rate, amount. The approval and the backup are what keep it from being rejected in accounts payable three weeks later.