NTE increase requests: how commercial HVAC contractors get approval before the work

When a repair will cost more than a work order’s not-to-exceed (NTE) amount, ask for the increase before you do the work. Price the repair from the technician’s notes and photos, add everything already on the work order, compare the total with the NTE, and submit the increase in the customer’s portal with the reason and the evidence. In ServiceChannel that request is a proposal; in Corrigo it is a quote. Once the customer approves it, the work goes ahead and you can invoice the full amount.

What an NTE is, and why going over it costs you

A not-to-exceed amount is the most a customer has agreed to pay on a work order without approving more. Facility portals enforce it. ServiceChannel’s invoicing guide for providers says it plainly: “An invoice cannot be submitted for more than its not-to-exceed (NTE) amount.”

So the cost of a missed increase isn’t only a delay. Work done above the NTE without approval is work the portal won’t let you bill until the customer agrees to it after the fact, if they agree at all.

Take a preventive maintenance (PM) visit. The technician finds a failed part or a worn belt, the repair is real, and the work order’s NTE was set for the visit, not the repair. The question is how fast the office can turn the finding into an approved increase.

How the increase works in ServiceChannel

In ServiceChannel, raising the NTE on an existing work order is a proposal. Its help page on creating a proposal says: “You can submit proposals to your clients to bid on work, increase the NTE, or change the scope of work for an existing work order.” ServiceChannel’s proposals page adds that the customer approves a proposal before the work starts.

Your customers may also set their own terms for how quickly a proposal is due, so check each agreement.

How the increase works in Corrigo

In Corrigo, the provider requests an increase as a quote on the work order. Corrigo’s training guide for managing work orders describes what happens next: “The customer will be notified of the requested NTE increase and will have the opportunity to either accept or reject the quote.” Its developer documentation is just as clear about timing: “NTE limit is not increased instantly, it is increased only after customer’s approval.”

Corrigo’s guide dates from 2018, so the screens may look different today. The pattern is the same as ServiceChannel’s: the provider asks with an amount and a reason, and the customer decides.

Where the time goes between the visit and the approval

The portal step takes minutes. The work before it is what stretches an increase into days, because it crosses people and tools:

1. The visit is closed in the field service app, with the technician’s notes and photos.
2. Someone reads the notes and works out what the repair is: which unit, which part, how many hours.
3. Someone prices it from the price book and the customer’s labor rate.
4. Someone adds up the work order: the repair plus anything already on it, such as the diagnostic or the PM visit itself, and compares the total with the NTE.
5. Someone writes the request in the customer’s portal, with the reason, the photos and whatever that portal requires before it will accept the submission.
6. Someone keeps the field service system in step, so the job, the notes and the NTE match what the portal says.

Each handoff is a place for the request to wait. When a coordinator is working through many visits at once, the clear repairs wait in the same queue as the ones that need a manager’s judgment.

Some of this is already connected. ServiceTitan’s ServiceChannel integration, for example, lists “Not-to-Exceed (NTE) Transfer to Custom Field: Seamlessly send NTE values to custom fields in ServiceChannel for accurate financial tracking during job creation.” What usually stays manual is the middle: turning a deficiency into a priced repair and a request someone can approve.

A checklist for getting increases approved faster

1. Price from the technician’s own notes and photos. Ask techs to name the unit, the deficiency and the part in a consistent way, so the office doesn’t have to call them back.
2. Add everything already on the work order before you compare. The NTE covers the whole work order, so a diagnostic or trip charge already billed counts against it.
3. Say why, with evidence. Attach the photos and a one-line reason a property manager can approve without a call: what failed, what happens if it isn’t fixed, and what it costs.
4. Ask before the truck rolls back. Submit the increase as soon as the finding is priced, inside any time limit your customer sets.
5. Learn each portal’s rules. Required attachments and check-in and check-out records differ by portal and by customer. A missing check-out can hold up a request that is otherwise ready.
6. Keep one record of the truth. Whatever the portal approves should be what your field service system and your invoice show, so the invoice goes through the first time.
7. Track the time from finding to approval. Measure it for a month before you change anything. It tells you whether the delay is in pricing, in writing the request or in the customer’s approval.

A worked example (illustrative, with fictional data)

A technician on a PM visit finds two deficiencies on a rooftop unit, RTU-3, and attaches four photos. The repair, priced from the price book and the labor rate, comes to $1,298.52. The work order already carries a $500.00 diagnostic. Together that is $1,798.52 against a $1,500.00 NTE: $298.52 over.

The request that gets approved quickly says exactly that: the unit, the two deficiencies, the photos, the price and the $298.52 increase it needs. The service manager approves the price and the scope, the coordinator submits it in the customer’s portal, and the customer raises the NTE before the repair is scheduled. The technician’s missing check-out from the PM visit goes to the coordinator first, because the portal would otherwise hold the request.

Where Kestrel fits

Kestrel, an AI-native consulting firm in St. Louis, brings an AI agent that only reads: it finds where PM findings and NTE requests take your team’s time. Then we help your team build the automation for the office part of this: the visit’s notes and photos read, the repair priced from your price book, the work order total checked against the NTE, and the proposal and the increase request drafted for your service manager to approve. Your coordinator submits it in the customer’s portal, and the customer approves. The agent is ready for testing: see how this works for commercial HVAC contractors, or book a call with the founders.

Key takeaways

• Work above the NTE can’t be invoiced until the customer approves an increase, so ask before the work, not after.
• In ServiceChannel the increase is a proposal; in Corrigo it is a quote. Either way, the customer decides.
• The delay is usually in the office, between the visit and the portal: reading notes, pricing, adding up the work order and writing the request.
• Count the whole work order against the NTE, attach the evidence, and keep your own system in step with the portal.