The job

Everything a tech needs about the job, on the job

Each job gets one screen, built for someone standing in a mechanical room with a glove on one hand and a phone in the other. The buttons are big, the wording is plain, and nothing needs two hands or a good signal.

Today’s work

Three tabs keep the day organized, with no searching or filtering.

  • Current shows what the tech is working on now, including anything overdue.
  • Upcoming shows work booked for tomorrow and beyond. Each visit appears separately, so a four-day job shows four days.
  • Complete keeps finished work within reach for parts, photos and paperwork.

Late jobs show 16 HR LATE in red at the top of the card, where nobody can miss it. The customer, the building, the work description, the dispatch number, the address (with a tap through to maps) and the promised time are all on the card, so a tech knows whether to go before opening anything.

Each card has a colored edge for its state (live, overdue, finished or waiting), so you can read it at arm’s length in a truck.

Current jobs list with two jobs, one marked 16 hours late and one 1 hour late.

Overdue work is flagged at the top.

The complete tab listing finished jobs.

Finished work stays within reach.

The three tabs with live counts on each, and a completed job card showing the dispatch number, customer PO and crew size.

Each tab shows a live count.

A job detail screen with the address, contacts, not-to-exceed amount, notes, equipment and history in one place.

Tap a card to see every detail of the job.

The time clock

This is the feature that pays for the app on its own, and it’s the one office managers react to first.

The tech taps, and the server records the time

The tech taps ON MY WAY when they leave, START WORK when they arrive and COMPLETE when they’re done. There’s one button at a time, always for the next step, so there’s no menu of options to get wrong.

The tech never types a time or picks one from a wheel. The time of the tap comes from the server, so a phone with the wrong clock can’t throw it off, and nobody is guessing three hours later.

  • No AM/PM mix-ups. Nobody types 7:00 and means the other one.
  • No negative hours. An end time can’t come before a start time when neither one was typed.
  • No Friday payroll reconstruction. Payroll no longer means a week of asking “what time did you actually get there?”
  • Travel and on-site time are separate, so you can finally see drive time as its own number.
  • Times can’t be back-dated. They record what actually happened.
The clock rail showing travel, work and complete steps with times.

One button, always the next step.

The time clock rail with recorded on-site and off-site times.

Times are recorded as they happen.

The TRAVELING confirmation, with an optional note saying the tech is stopping for parts first.

One tap, with an optional note telling dispatch why.

A job mid-work showing promised, traveling and working times with the drive duration between them.

Drive time gets its own line, to the minute.

And they can’t clock a job they’re not on yet

A tech scrolling ahead to next Tuesday used to be able to put that job into TRAVEL by accident, which threw off the numbers for a day that hadn’t happened yet.

Upcoming jobs don’t show the clock. In place of the button, the tech sees the date the job opens and who to call if they really are going early, so there’s never a dead button or a silent failure.

They can still cancel an upcoming visit, because “I can’t make Monday” is something a tech really does need to say on Friday.

The complete step with its confirmation options.

Completing a job starts with one quick question.

Multi-day and multi-tech jobs

Commercial work is often three people over four days, plus someone who came back for a part.

  • Every visit on the job is listed, with who went, which day, what state it’s in and the hours on it.
  • A tech booked four days in a row sees four cards, one for each visit.
  • The card shows how many techs are on the job, so nobody turns up thinking they’re alone.
  • A tech can finish their visit without finishing the job, and the dispatch stays open for whoever’s next.
The visits list on a job showing several techs and dates with their status.

Every visit on the job, with its hours.

Notes that survive

The note is where the job actually gets explained, so it needs more room than a one-line box.

  • Notes hold up to 8,000 characters, which is plenty for a full end-of-day write-up.
  • Your note can’t be overwritten. If the office is typing in the same job at the same time, both notes are kept, so nobody loses a paragraph they just wrote.
  • The dispatch notes, the location notes and the task list appear together, so you see the building’s standing instructions along with this call.
  • The office sees the note as soon as it’s saved.

The gate code, the tenant’s name, which door to use and why the last fix didn’t hold: the knowledge that usually lives in one tech’s head ends up on the job instead.

Adding a field note on a job.

Room to say what actually happened.

Tasks, location notes and dispatch notes shown together on the job screen.

The building’s standing notes appear alongside.

Contacts and directions

  • Every contact on file for the site is listed, each one labeled by name.
  • Tap to dial or tap to email, so nobody is copying a number into the keypad with gloves on.
  • Duplicate numbers are merged, so each number appears once instead of three times.
  • The address opens the phone’s own maps app with the route ready.

It sounds small until you count how many times a day a tech does it. A twenty-truck shop does it a few hundred times a week.

The contacts panel on a job showing named contacts with phone numbers.

Named contacts with one-tap dialing.

The phone's own call sheet offering to dial from the business line rather than the tech's personal number.

A tech with two lines chooses which one to call from.

Equipment on site

Techs can see what’s installed in the building before they walk in.

  • Each unit shows its make, model, serial number, location in the building, install date and warranty.
  • Add a unit from the field when you find one nobody recorded, and photograph the dataplate while you’re standing at it.
  • Fix what’s wrong. A serial number someone mistyped in 2019 gets corrected by the person looking at the unit.
  • Changes are written straight into ESC’s equipment records.

A dataplate photo takes four seconds and settles every future argument about which unit is which.

Equipment installed at the site, listed on the job screen.

The equipment installed at this site.

Adding a dataplate photo to an equipment record.

Photograph the dataplate at the unit.

Editing an equipment record: type, size and location, make, model and serial.

Fix the serial number while you’re looking at it.

Every photo, every year

Your ESC server has been collecting photos and documents for as long as you’ve run it, and until now almost none of it could be reached from a truck.

The whole history, grouped by year

  • See everything attached to this job, this building, this PO or a piece of equipment.
  • Photos are grouped by year, so finding “what did this look like before the last repair” takes two taps instead of a call to the office.
  • A full-screen viewer lets you swipe through photos and read a nameplate or a wiring diagram on site.
  • Take new photos straight onto the job, including on an iPhone, which saves photos in a format many systems can’t read. ServiceProof converts them on the phone, so they just work.

And you can send one to the customer

Share a photo through the phone’s own share sheet to text it, email it or send it however the customer prefers. The property manager who wants to see the corroded fitting before approving the quote gets it while the tech is still on site.

Site photos grouped by year.

Grouped by year, going back as far as your ESC does.

Sharing a site photo out through the phone's share sheet.

Text a photo to the customer from the site.

One site, one file trail

A tech who can see what the last four visits found walks in already knowing the building. That’s the difference between a callback and a repair.