Daily Job List
Each technician sees assigned calls in route order, with site notes from the office.
HVAC contractors run tune-ups, no-cool calls and changeouts with crews who are rarely at a desk. We build a custom staff operations app that gives each technician assigned work, a checklist for the job type, a place for readings and photos, and a direct line of updates back to the office.
Many shops still start the morning with a dispatch board updated by phone, a route sheet and a group text. By mid-morning two calls have moved, a changeout has slipped and the lead installer is calling the office to ask which house needs the three-ton condenser. The information exists, but it reaches the truck in pieces.
Information also leaks at every handoff. A technician who finds a cracked heat exchanger writes it on the back of an invoice, the comfort advisor never hears about it and the homeowner gets a second visit to explain the same problem. Startup readings stay in a notebook on the dash, and photos of line sets and condensate traps sit in personal camera rolls when a warranty question comes up months later.
The first build should cover what a technician touches on every call: the day's assigned jobs with site notes, checklists for the common job types, fields for readings and photos tagged to each step, and internal notes that reach the office. If those work well, crews keep using the app when the larger features arrive.
Parts ordering from supply houses, time cards with payroll export and in-app training can wait for a later phase. Each is useful, but each depends on decisions the office has not yet made, such as which supplier accounts to connect or how overtime is calculated.
The lead installer opens the app at seven fifteen and sees one job: remove an older split system and set a new heat pump and air handler. The job card lists the attic access, the breaker panel location and a homeowner note about a dog in the backyard. The changeout checklist is already loaded.
As the crew works, each step asks for a reading or a photo. Recovery, the nitrogen pressure test, evacuation to the target micron level and startup all need an entry before the app will mark them complete. At the end, the installer notes that the return duct is undersized and attaches two photos. The office sees the note at once, and the comfort advisor can quote a duct correction before the truck is loaded.
Each technician sees assigned calls in route order, with site notes from the office.
Separate step lists for tune-ups, diagnostics, startups and changeouts, editable by the service manager.
Structured fields for pressures, temperatures and electrical readings, so values compare across visits.
Every picture is stored with the job, the address and the checklist step it supports.
Technicians post notes and flags that reach dispatch, sales or the service manager at once.
Many HVAC companies already run dispatch and invoicing in platforms such as ServiceTitan, Housecall Pro, Jobber or FieldEdge. A custom staff app should not replace those systems. It should pull assigned jobs from them and send back the checklist results and photos that the platform does not capture well.
Where a platform exposes its data to outside software, we use that connection. Where it does not, we look at scheduled exports or a sync through the accounting package, such as QuickBooks, for the pieces that matter. Scoping is where we check what is realistic, so no connection is promised before it has been tested.
Demand swings with the weather. A heat wave in July can turn a normal dispatch board into a queue of no-cool calls, and a cold snap in January brings furnace startups and heat exchanger checks. A technician may run eight or ten calls a day in hot attics with weak signal, so the app has to keep working when the connection drops.
The app saves entries and photos to the phone first, then uploads them when the signal returns. The office can switch seasonal checklist sets, moving cooling steps to the front in summer and heating steps in winter, without waiting for an app release. Helpers and apprentices can receive shorter lists so they are not slowed by steps meant for senior installers.
Start with two or three respected lead technicians for a couple of weeks before the full crew. Their feedback shapes the checklists, and their support carries more weight in the shop than any memo from the office. Keep the first checklists short, because a technician who has to scroll through forty questions on a simple filter change will quietly stop filling them in.
Show the crew what the data does for them. When a callback is settled in the company's favor because the startup readings and photos are on file, adoption tends to follow. Review the first month of checklists with the service manager and trim any step nobody uses in practice.
Yes. Checklist entries, readings and photos save on the device and sync when a connection returns. The app will not mark a step complete until the required item is attached, even while offline.
No. The app sits beside your existing system, pulling assigned jobs and returning checklist data where the platform allows. During the free scoping call we review what your software can share.
Yes. Checklists live in an admin dashboard, so the service manager can add a step, mark a photo as required or retire an old form without waiting for a new app store release.
Mobile apps start at $4,500. Price follows the number of checklists, the offline requirement and the integrations, and each figure is written down before any build begins.
Book a free scoping call to walk through your job types, checklists and current software. We then plan a staff app your techs will actually open between calls.