Powstania Warszawskiego 15
31-539 Kraków
A change order app for contractors solves a small problem that adds up to a large one: extra work found on site, agreed in a sentence, done the same afternoon and never invoiced. This guide shows how a field change order should flow from the plant room to the invoice, what it must record, and who should be allowed to approve it.
A change order app for contractors lets a technician record extra work the moment it is found: a description, photos of the condition, how it will be priced and the customer's signature, all on the device and working without a signal. The approved change order is attached to the job, so the office sees it the same day and can invoice it without a phone call. The details that make it work are recording who approved the work and in what role, and sending the request to the right decision maker when the person on site cannot approve costs.
Most contractors do not lose money on extra work because customers refuse to pay. They lose it because the work was never recorded in a way that could be invoiced. The pattern is familiar: a technician finds a problem, mentions it to someone on site, gets a nod, fixes it and moves on.
A week later the office receives a service report with a line that says "also replaced valve". There is no price, no approval and no photo of the condition before the work. Either someone calls the customer to explain, or the line is quietly absorbed into the job. Repeated across a year, that is a real share of the margin.
Here is how the same situation runs when the change order is part of the field app. Times are illustrative, but the order of events is the point.
During a scheduled service visit the technician finds a corroded isolation valve that will fail soon. Replacing it is not part of the visit.
From the open job, the technician starts a change order: a short description, two photos of the valve and the part needed. Customer, site and equipment are already filled in.
The valve is on the company price list, so the price is added from it. For unusual work the technician would choose time and materials or mark it to be quoted instead.
The site contact signs on the device and the app records name, role and time. If the contact could not approve costs, the request would go to the account decision maker for approval instead.
After the repair, photos of the new valve are added to the same change order. Everything is saved on the phone, even though the plant room has no signal.
The office sees the approved change order attached to the job, checks it in the panel and adds it to the invoice. The cost also appears in the job total.
A change order is evidence as much as it is a request. If it is ever questioned, these eight elements answer the question without anyone having to remember the afternoon.
Linked to the job and the specific unit, so it appears in job costing and in the equipment history.
What was found and why it needs work, in plain words the customer can read later.
The condition as found, taken inside the change order before any work starts.
A price from your list, time and materials, or to be quoted, chosen explicitly.
Name and role of the person who approved, not only a signature image.
Captured on the device with a timestamp, also when there is no signal.
The completed work, added to the same record when the repair is done.
Requested, approved, done, invoiced. The office always knows where each one stands.
On commercial sites the person who meets the crew is often a caretaker or a site supervisor, while costs are approved by a facility manager or an owner somewhere else. A signature from the wrong person is the most common reason an approved change order is still disputed.
The fix is simple to design and easy to forget: record the approver's role, and let the technician send the request from the app to the person with authority when needed. Work waits until approval arrives, which for small items usually takes minutes, not days.
Two things from our own field projects apply directly here. Requirements that decide whether crews use an app often appear only once it runs on real jobs, which is why your own technicians should test it during the build, not after it.
And when an app has no place for something the crew meets on site, technicians start writing it in the notes on their phones, and the office never sees it.
For change orders that second point is critical. If starting a change order takes longer than telling the customer "we will sort it out", the app will lose. It has to open from the job in one tap and ask only for what the invoice needs.
Change orders rarely stand alone. They share the job record with time and materials, so the natural first version covers all three: technicians record time, materials and extra work against the job, and the office reviews and corrects them in one panel before they go to accounting.
The cost side of that picture is covered in mechanical contractor job costing, and the forms side, including service reports and sign offs, in digital forms for mechanical contractors. How we build the whole system, from the technician app to the office panel and accounting, is described on our mechanical contractor app development page. For HVAC service companies the same approach is set out in custom HVAC software development.
It is a part of the field app where a technician records extra work found on site, attaches photos, sets how it will be priced and collects the customer's signature before doing the work. The approved change order is linked to the job, so it reaches job costing and invoicing without being retyped.
Yes, if the app is built for offline work. The description, photos and signature are saved on the device with a timestamp and sent when the connection returns. The office sees the approved change order as soon as the phone reconnects.
The app should record who signed and in what role. When the site contact has no authority to approve costs, the change order can be sent from the app to the person who does, for example the facility manager or the account owner, and the technician waits for approval before starting the work.
Small, repeatable items can be priced from your own price list on the spot. Larger or unusual work is better approved as time and materials or marked as to be quoted, so the customer still confirms the scope in writing before the crew starts.
A first version built around one workflow, for example extra work approval plus office review, typically takes 8 to 12 weeks from kickoff to the stores. It is often combined with time and materials on the job, since all three feed the same job record.
We price a fixed scope after a scoping call and a written scope document, so the number is agreed before development starts. This article does not quote figures. Current information is on our pricing page.
Thomas sets the company's long term strategy and direction, identifies market opportunities, and owns business development and client acquisition. He builds strategic partnerships that last beyond a single project. He works with clients from the first strategy conversation, so their business goals, not just their feature list, drive every decision.
Walk us through how extra work is agreed on site today. We will show you what a first version would record and how it reaches the invoice.