Tracking NTE limits so techs stop and get approval

The property manager sends over a work order for a running toilet in unit 9D, not-to-exceed 300 dollars. Your tech pulls the tank and finds the fill valve shot, the supply line corroded, and the shutoff seized so hard it will not close. He does the thorough job: new fill valve, new supply line, new angle stop while he is in there. He clears the call, writes it up at 640, and moves on to the next unit feeling like he did the customer a favor.

Two weeks later the PM refuses to pay the 340 over the limit. Not because the work was bad. Because nobody asked. The number on the work order said 300, and your tech drove past it without a word. Now you are eating the difference, or you are having a hard conversation with a PM who sends you fifty tickets a month and can send them to someone else tomorrow.

That is the trap with a not-to-exceed limit. It is not a suggestion, it is the ceiling on what the PM already agreed to pay without a second signature. Blow past it in the field and you have created a billing dispute before the invoice even goes out. This piece is about the habit that stops it, and where the ask needs to live so it actually happens. It sits in the same family as the rest of the proof and getting paid guides, because an NTE fight is a getting-paid fight that starts the moment a tech keeps working.

Why the limit gets blown in the field, not the office

The office understands NTE limits. The problem is the office is not under the sink. The tech is, and in that moment three things push him straight past the number.

The fix feels obvious. He can see the whole repair from where he is kneeling. Stopping to call in a 640 approval feels like bureaucracy slowing down work he already knows how to do.

Calling in is a hassle. He has to stop, wash his hands, find the ticket number, dial the office, explain what he found, wait for someone to reach the PM, and hope the PM picks up. Ten minutes of standing around, easy. So he skips it and keeps his hands moving.

Nobody told him the number was a wall. Half the time the tech does not even remember the NTE was 300. It was one line on a ticket he skimmed at 7 in the morning. The limit lived in the office system and never made it to the guy doing the work.

None of that is the tech being careless. It is the limit failing to travel from the ticket to the hands. A number the tech cannot see when he is deciding whether to keep going is a number that does not exist.

Run the real cost, once

Here is why this is worth a whole habit and not just a reminder.

Say you run PM work with NTE limits between 250 and 500, which is the common range. Your bread and butter is small tickets: a garbage disposal, a running toilet, a broken blind, 120 to 200 dollars a pop, and your margin on each after the tech’s time and the drive is maybe 60 dollars. You do 40 of those in a month. Call it 2,400 dollars of margin, the money that keeps the lights on.

Now one tech finds a bigger job under a sink and rolls it to 900 on a 400 limit. The PM refuses the 500 overage. You either eat it or you fight it, and fighting it with the PM who feeds you 40 tickets a month is not really a fight you can win. Eat the 500 and you have wiped out eight of those small tickets. One unapproved repair erased a fifth of the month’s margin, and it was work your tech did well.

That is the math that makes the ritual worth teaching. You are not protecting against bad work. You are protecting against good work nobody approved.

The stop, shoot, ask ritual any tech learns in a day

The fix is small enough to teach on one ride-along. When a tech hits the point where the repair is about to cost more than the ticket allows, he does three things in order, and then he waits.

Stop. The second the fix is clearly going past the number, tools down. Not after the valve is already off. The moment he can see it is a bigger job than the ticket covers.

Shoot. One photo of what he found: the corroded line, the seized valve, the mold behind the panel. The photo does the explaining so he does not have to write a paragraph.

Ask. A short message with the photo, the diagnosis in one line, and the new number. “Shutoff seized, supply line shot, need both. Puts it at 640, over the 300 NTE. OK to proceed?” Then he waits for a yes before the meter runs past the limit.

The whole thing takes ninety seconds if the ask has somewhere to go. That is the catch. If the only way to ask is a phone call to an office that has to relay it to a PM, the tech will skip it every time, and you are back to eating overages. The ask has to be as fast as the shortcut, or the shortcut wins.

This is the same discipline behind getting approval before you open up more than the ticket covers, and it is the field version of never doing verbal change orders that small shops get burned on. The pattern is the same in every trade: the moment the scope grows, the money question comes before the next tool touches the job.

Where the ask has to live

An approval that lives in a phone call has two problems. It is slow, so techs skip it, and it is spoken, so when the PM says “I never approved 640” a month later, it is your tech’s memory against the PM’s. You lose that one every time.

The ask needs to land in a place tied to the job, where the PM can see the photo, see the number, and answer with a yes that stays put. When the work order is its own thread, that is exactly what happens. The tech shoots the photo onto the task, writes the one-line ask with the new number, and the PM approves it right there, by rank, before the tech touches the next fitting. The approval is not a memory anymore. It is on the record, next to the photo that justified it, with the PM’s own yes attached.

That does two things at once. The tech gets his answer in a couple of minutes instead of standing around on the phone, so he actually asks. And when the invoice goes out at 640, the approval is already sitting in the thread, dated, with the photo. There is nothing to dispute, because the PM said yes when it mattered, on the same record you are billing from. The NTE limit stops being a trap the tech falls through in the field and becomes a line he stops at, shoots, and asks about, which is all it was ever supposed to be. If you want to see how it feels, put one PM account on it and watch the first overage get approved in the thread instead of argued about in an email.