FieldproxyAI-native field service software

Work orders

How do I track not-to-exceed (NTE) limits on work orders?

Put the NTE amount on every work order as its own field, add labor, parts and trip charges to the job as they happen so spend against the NTE is always current, and alert the technician and the office at a set point such as 80% of the limit. Before the job would go over, the technician stops, photographs the problem and sends a proposal for an NTE increase; work continues only once the client approves and the new NTE is on the job. Check every invoice against the approved NTE before it goes out, because many clients refuse invoices above it.

  • NTE is a field on the work order, not a note in the description.
  • Spend against the NTE must update from the field, not at invoicing.
  • Alert early (e.g. 80%), stop before 100%, and get a written increase with photos.
  • Labor, materials, trip charge and freight all count toward the NTE.
  • One client's NTE rules are not another's: store the rules per client.

Pick a time for your demo

60 minute video call

An NTE caps what you can bill; it does not price the job. A limit set too low still costs you a second visit, so push back on unrealistic NTEs at intake.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How it works, step by step

This is the provider side: you receive work orders from facilities clients or their portals, each with an NTE, and must not invoice above it.

1. Capture the NTE at intake

The NTE arrives on the work order, the client's PO or in their portal. Put it in an NTE field on the job with the currency, the client's work order number and the source (portal, email, phone). ServiceChannel defines NTE as the maximum amount a provider may charge for the services listed on the work order.

2. Check it before you accept

Compare the NTE with what this kind of job usually costs you. If a roof leak NTE will not cover a lift and two technicians, say so before accepting. ServiceChannel's 2026 trade partner guidelines ask providers to accept or decline within 30 minutes, 15 for emergencies, so this check has to be fast.

3. Show the technician what is left

The technician needs the NTE and the remaining amount, not necessarily your prices. Show "NTE $500, $180 left" on the job so they know when to stop.

4. Post costs as they happen

Labor from check-in and check-out, parts as they are fitted, trip charge and freight. If spend is only added up at invoicing, the alert comes after the overrun. Count everything the client counts; ServiceChannel's guidelines ask for a breakout of labor, number of techs, materials, trip charge and freight on the invoice.

5. Alert at a threshold, block at the limit

Send an alert to the technician and the coordinator at e.g. 80% of the NTE. At 100%, block adding more labor or parts until there is an approved increase, or let it through only with a manager override and a reason.

6. Stop, quote and get the increase approved

If the work will exceed the NTE, the technician photographs the issue and the office sends a proposal for a higher NTE. ServiceChannel's guidelines say to call for approval before proceeding if a first-visit fix will exceed the NTE, to get a proposal approved before ordering parts that exceed it, to submit proposals within 48 hours (24 for emergencies), and to always upload photos.

7. Update the NTE, then continue

When the client approves, record the new NTE, who approved it and when, and attach the approval. The job's remaining amount resets against the new limit.

8. Check the invoice against the NTE

Before the invoice goes out, compare its total with the approved NTE. If it is over, it either needs an approved increase on file or it gets cut back. ServiceChannel's guidelines say an invoice must be within the agreed NTE to be approved, and that the customer can refuse invoices for work that was not approved.

Where it breaks

Why it goes wrong

Contractors on our sales calls asked for not-to-exceed alerts. These are the usual reasons the alert comes too late or not at all.

The NTE lives in the PDF

The amount is on the client's work order PDF or in their portal, and nobody types it onto the job. The technician never sees it, and the office finds out at invoicing.

Costs arrive after the work

Hours are added from a timesheet on Friday and parts from a supplier invoice next week. By then the job is over the limit and the client will not pay the difference.

Every client works differently

One client sets the NTE by trade and priority, another by problem type, a third sends it per job by email. ServiceChannel's own advice to clients is to set NTEs per problem type rather than only by trade or SLA priority. A contractor serving several clients needs the rules per client, not one company-wide limit.

Technicians stop early to avoid the limit

A facilities services firm writing about NTEs notes that technicians may stop work early to avoid exceeding limits, which brings repeat visits. The fix is a fast increase request from the job, so stopping means minutes, not another trip.

Increases approved by phone, not on file

A coordinator approves an increase on a call and nobody records it. The invoice goes in above the original NTE and is rejected, and there is nothing to show the client.

The options

Ways to do it

ApproachHow NTE is trackedWeak spotGood for
Spreadsheet of open work ordersNTE typed in a column; spend added by handNo alert until someone looks; spend is days behindA few NTE jobs a month
The client's portal (e.g. ServiceChannel)NTE set by the client on each work order; proposals request increases; invoices checked against itCovers that client's work only, and not your internal costs as they happenContractors whose work mostly comes through one portal
Microsoft Dynamics 365 Field ServicePrice, cost, or price and cost margin NTEs, applied by customer, incident type or location; technicians see warning icons as they approach or pass itWarns but does not stop saving; an enterprise implementationLarge operations already on Dynamics
FSM with an NTE field, live job costing and approval gates (Fieldproxy)NTE read from the work order, spend posted from the field, alerts and an approval step before going overRules per client need setting up at go-liveContractors juggling several clients' NTE rules

As of November 2026, from each vendor's own documents (sources below). Check the current version before relying on any one setting.

Worked example

A worked example: a $500 NTE plumbing call

Say a facilities client sends a work order for a leaking backflow valve at a retail store, NTE $500, alert set at 80%. Made-up numbers.

MomentSpend on the jobLeft of NTEWhat happens
Accepted, trip charge posted$85$415Technician sees NTE $500 on the job
1.5 hours on site$265$235Nothing yet
Repair kit fitted$410$9082% reached: alert to technician and coordinator
Valve body cracked, needs replacing ($380 part plus 1 hour)$410$90Technician stops, takes photos; office sends a proposal for a $1,000 NTE
Client approves next morning$410$590 (new NTE $1,000)Approval and approver saved on the job; part ordered
Return visit, valve replaced$935$65Job closed
Invoice check$935Under NTEInvoice goes out with labor, techs, materials and trip charge broken out

Without the alert, the technician would likely have fitted the kit, found the crack and either stopped with nothing billable above $500 or replaced the valve and sent an invoice the client could refuse.

Before you buy

What to check before you buy

Good signs

  • NTE is a field on the job, filled from the work order or PO without retyping
  • Spend against NTE updates from check-ins, parts and trip charges as they happen
  • Alert threshold is configurable, per client if needed
  • Adding cost above the NTE needs an approval or an override with a reason
  • Increase requests carry photos and keep the approver and time
  • Invoices are checked against the approved NTE before they go out
  • Technicians can see what is left without seeing prices or margin

Red flags

  • NTE is only a note in the job description
  • Spend is totaled only when the invoice is built
  • One company-wide limit, no per-client rules
  • Increases are approved outside the system with no record
  • Overruns are found by a report someone has to remember to run

In Fieldproxy

Setting it up in Fieldproxy

Fieldproxy is set up around your process, so NTE fields, thresholds and approvals follow your clients' rules. Field names and thresholds are examples.

NTE read from the work order

The Document intelligence agent reads emailed and PDF work orders into the job, including the NTE amount, PO number and SLA deadline, and flags fields it could not read confidently instead of guessing. It can also check whether the NTE is above your minimum before the job is accepted.

Spend against the NTE on the job

As labor and parts go on, the job's costing shows what has been spent against the NTE, so the office knows before the limit is reached. Work orders carry your own fields and rules: see work orders and jobs.

Alerts before the limit

The Watcher agent takes a rule in plain English, such as "ping me when a job's spend gets within 10% of its NTE", and flags the job to the coordinator. The technician sees the remaining amount on the technician app.

Approval before going over

Approval workflows pause a step until the right person signs off, such as adding cost above the NTE or sending a proposal over a set value. The approval and approver stay on the job record.

Proposals for the increase

The office builds the increase proposal on the job from your price book (custom estimates), with the technician's photos attached. In the Command Center you can ask for an estimate and have it flagged against the NTE before it goes out.

Per-client rules

Each client can carry its own default NTE by trade or problem type, alert threshold and invoice breakout. For work that arrives through ServiceChannel or Corrigo, see the page on managing those work orders in your own system.

How switching works

How switching to Fieldproxy works

We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.

  1. Send us three work orders

    One from each client you serve, with the NTE, and an invoice that was rejected or cut, if you have one.
  2. We set the NTE rules

    NTE field, alert threshold, block or override at the limit, and the increase proposal, per client, live within a day.
  3. We connect intake

    Work order emails and PDFs are read into jobs with the NTE filled in.
  4. Run a week and tune

    We check where alerts fired and where costs arrived late, and adjust thresholds with you.

FAQ

Questions people ask

What does NTE mean on a work order?
Not to exceed: the most the provider may charge for the work on that order without approval. ServiceChannel defines it as the maximum amount a provider may charge for the services listed on the work order.
What counts toward the NTE?
Usually everything the client is billed: labor, number of technicians, materials, trip charge and freight. Check each client's terms, and track all of them on the job.
What should I do when a job will go over the NTE?
Stop before you go over, take photos, and send a proposal for a higher NTE. Continue only once it is approved and recorded on the job.
At what point should the NTE alert fire?
Early enough to stop and ask: many teams use 75% to 85% of the NTE. Use a lower threshold for jobs where one part can blow the limit.
Can I invoice above the NTE if the client approved it by phone?
Only if the approval is on file. Record the new NTE, who approved it and when; otherwise the invoice can be refused.
Is NTE the same as a quote?
No. An NTE is a ceiling set before anyone has seen the problem. A quote prices the actual work. When the work will cost more than the NTE, the quote is how you ask for a higher one.
Should technicians see the NTE?
Yes, or at least the amount left. They are the ones who find the cracked valve. They do not need to see your unit prices or margin to know when to stop.

Sources

Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.