Skip to main content
ShieldBook

Jobs and field operations

The office's day and the technician's day, on the same job.

The office books visits and works from queues that show what needs doing. The technician runs the day from a phone. Both are looking at the same job, so nobody has to call to find out what happened.

01In the office

Work from queues, not from memory.

In development On the roadmapEverything else is built and working today.

Every open question has a queue

The office home answers the questions a service business asks every morning. Each queue is worked out from what's on the record, so a job leaves the queue when the work is actually done, not when someone remembers to tick a box.

  • Today's visits, with arrival windows, technicians and progress
  • Estimates approved but not sold yet
  • Sold work waiting to be scheduled
  • Work done but not invoiced, and balances due

Book visits with a real arrival window

Customers get a window they can plan around, and the technician gets a day that matches it. A full dispatch calendar with day, week and month views is being built now, on the same visits.

  • A date, an arrival window and a technician for every visit
  • Sold work gets a next step: do it now, schedule it, or pending reschedule
  • A full calendar with technician lanes and drag-and-drop(In development)
  • Google Calendar mirroring(On the roadmap)

02In the field

Designed for a phone in one hand.

The day on one screen

ShieldBook is designed on an iPhone first, for a technician standing in a driveway. The buttons are big, the next step is obvious, and nothing important hides behind a menu.

  • The current visit first, then the rest of the day
  • Call, text and directions from the visit
  • On my way and Arrived updates(In development)
  • Keeps working without a signal(On the roadmap)

Document the work while it's fresh

A job summary in four plain parts tells the office, the customer and the next technician what was wrong, why, what was done, and what should happen next. The Recommendation is where the next job starts.

  • Concern, Cause, Correction and Recommendation on every job
  • Photos taken or chosen on the job, kept with it
  • Tasks and notes the office can act on

Complete it with what actually happened

"Done" hides too much. ShieldBook asks how the visit ended: work completed, customer deciding, part needed, return visit needed. Each answer sends the job where it belongs next.

  • 8 real outcomes, from work completed to return visit needed
  • The outcome creates the follow-up, so it lands in the right queue
  • A return trip is its own job, linked to the first

What's next

Scheduling, on a full calendar.

Show us a day in your business.

We'll walk through it in ShieldBook, from the first visit of the morning to the last invoice.

Request a demo

ShieldBook is being developed and proven inside a working service business as it prepares for broader use. A demo is a walkthrough and an honest conversation about fit.