The job

Everything a tech needs
about the job, on the job

One screen per job, built for somebody standing in a mechanical room with a glove on one hand and a phone in the other. Big targets, plain words, and nothing that needs two hands or a good signal.

Today’s work

Three tabs. No hunting, no filtering, no menu.

  • Current — what’s on them right now, including anything overdue.
  • Upcoming — booked for tomorrow and beyond. Each visit shows separately, so a four-day job shows four days.
  • Complete — finished work, still reachable for parts, photos and paperwork.

Late jobs say 16 HR LATE in red at the top of the card — not a subtle badge somebody has to notice. 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 they open anything.

Cards are color-edged by state: live work, overdue, finished, waiting. It reads at arm’s length in a truck.

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

Current work. Overdue shouts.

The complete tab listing finished jobs.

Finished work stays reachable.

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

Live counts on the tabs. Nothing to hunt for.

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

Tap the card. Everything’s here.

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. The server writes the time.

ON MY WAY when they leave. START WORK when they’re on site. COMPLETE when they’re done. One button at a time, always the next real step, never a menu of options to get wrong.

The tech never types a time and never picks one from a wheel. The moment of the tap is the time, taken from the server — so it can’t be a phone with the wrong clock, and it can’t be a guess made three hours later.

  • No AM/PM mix-ups. Nobody is typing 7:00 and meaning the other one.
  • No negative hours. An off time can’t land before an on time when neither was typed.
  • No Friday archaeology. Payroll stops being a week of “what time did you actually get there?”
  • Travel and on-site are separate. You can finally see drive time as its own number.
  • It can’t be back-dated. The times are what happened, not what somebody remembered.
The clock rail showing travel, work and complete steps with times.

One forward step, never a menu.

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

Stamped as it happened.

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

One tap — plus a line telling dispatch why.

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

Drive time, on 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 quietly wrecked the numbers for a day that hadn’t happened.

Upcoming jobs simply don’t offer the clock. The button is replaced by the date it opens and who to ring if they’re genuinely going early — never a dead button, never a silent failure.

They can still cancel an upcoming visit, because “I can’t make Monday” is a real thing a tech needs to say on Friday.

The complete step with its confirmation options.

Finishing asks one question first.

Multi-day and multi-tech jobs, straight

Commercial work isn’t one tech for one hour. It’s three people over four days, plus somebody who came back for a part.

  • Every visit on the job is listed — who, which day, what state it’s in, and the hours on it.
  • A tech booked four days running sees four cards, not one. Nothing hides behind a roll-up.
  • The card tells you how many techs are on the job, so nobody turns up thinking they’re alone.
  • Finish your visit without finishing the job — 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. It shouldn’t be a one-line box.

  • 8,000 characters — a full end-of-day write-up, not a shorthand scribble.
  • Your note can’t be clobbered. If the office is typing in the same job at the same time, both survive. Nobody loses a paragraph they just wrote.
  • You can see the dispatch notes, the location notes and the task list together — the standing instructions for the building as well as this call.
  • The office sees it the moment it’s saved, not at the end of the day.

The gate code, the tenant’s name, which door to use, why the last fix didn’t hold — the knowledge that usually lives in one tech’s head ends up in 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, too.

Contacts and directions

  • Every contact slot the site carries — named, not a wall of numbers.
  • Tap to dial. Tap to email. No copying a number into the keypad with gloves on.
  • Duplicate numbers are folded together, so you get the one that matters instead of the same line three times.
  • The address opens the phone’s own maps app, with the route already in it.

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, one tap to dial.

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 gets asked which one.

Equipment on site

What’s installed in that building, in the tech’s hand, before they walk in.

  • Make, model, serial, 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.
  • Edit what’s wrong. The serial somebody transcribed badly in 2019 gets fixed by the person looking at it.
  • It writes straight into ESC’s equipment records — not a side list.

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.

What’s in the building.

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 while you’re looking at it.

Every photo, every year

Your ESC server has been quietly collecting photos and documents for as long as you’ve run it. Almost none of it has ever been reachable from a truck.

The whole history, banded by year

  • Everything attached to this job, this building, this PO or a piece of equipment.
  • Grouped by year, so “what did this look like before the last repair” is two taps, not a support call.
  • Full-screen viewer that swipes, for reading a nameplate or a wiring diagram on site.
  • Take new photos straight onto the job — including from an iPhone, which stores them in a format most systems choke on. We convert it on the phone so it just works.

And you can send one to the customer

Share a photo out to the phone’s own share sheet — text it, email it, drop it in whatever the customer uses. 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.

Banded by year. Decades deep.

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

Text it to the customer from site.

One site, one file trail

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