How to Build a Field Service App in AppSheet With Photos

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Build a Field Service App in AppSheet With Photos.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Build a Field Service App in AppSheet With Photos.

A field service app can be built in AppSheet from a Google Sheet: add an Image column for before-and-after photos, a Signature column for customer sign-off, and a bot that emails a PDF report once the status reaches "Signed off". Budget $5 to $10 per user a month.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The decision that matters is not the build, it is whether to build at all. A crew that needs invoicing, card payments and route planning will be better served by bought software; a crew that needs a clean job record with photos and a signature can often have it running in a few days. The numbers below help you choose.

Is it cheaper to build a field service app in AppSheet or buy one?

Building in AppSheet is usually cheaper on list prices, at $5 or $10 per user a month, while a finished five-user product such as Housecall Pro lists from $149 a month on annual billing. Your own build time is the hidden cost.

Take a six-person heating and plumbing firm: four engineers and two in the office. AppSheet's pricing page lists Starter at $5 per user a month, Core at $10 and Enterprise Plus at $20, with up to 10 test users at no cost while you build. The subscription help adds two facts that change the sum. Core is included in most paid Google Workspace plans, so a firm already on a Workspace Business edition may pay nothing extra. And you count unique app users across all your apps, not apps.

Route (6 users)Monthly list priceWhat you getWhat you still build or buy
AppSheet Starter6 x $5 = $30Basic app, automated emails, Google SheetsRoles, scheduled events, barcode scanning are not in Starter
AppSheet Core6 x $10 = $60, or $0 if Workspace includes itRoles, secure image access, scheduled eventsInvoicing, payments, dispatch map
Housecall Pro Essentials (5 users)$149 billed annually, $189 monthlyA finished productA sixth user: check the price per extra seat
Housecall Pro Max (8 users)$299 annually, $329 monthlyA finished product, more seatsNothing structural
Jobber, five-user tiersFrom $149 billed annually to $299 monthly, depending on tierJob forms, photos and quote signature approvals are listed on its pageCheck which tier includes which feature

On those list prices the gap is roughly $90 to $270 a month. Over a year that is about $1,000 to $3,200 against your own time, which I would estimate at two to three working days for a first version and a few hours a month after that (an estimate, not a vendor figure). If you value an hour of the owner's time at $50, the build pays for itself in under a year only when the app does what you need without constant tinkering. Buy if you lose more than that in tweaking, or if you want customer-facing payments and scheduling from day one. The comparison of Jobber, Housecall Pro and ServiceTitan covers what the finished products add, and AppSheet's pricing has the plan detail.

How should you set up the Google Sheet for a field service app?

Use four tabs, Customers, Jobs, Job photos and Staff, each with its own key column and Ref columns that link them, so one job can hold as many photos as it needs.

Good apps start from tidy data. Google's own guidance for preparing a sheet says each row is one entry, each column one category, no calculator blocks wedged in the middle, and a unique key column on every table. A product code or an employee email makes a good natural key; if there is none, AppSheet can generate one with the UNIQUEID() function.

For the heating and plumbing firm, four tabs do the job:

TabColumnsNotes
CustomersCustomer ID, Name, Phone, Email, Address, Access notesOne row per property; Customer ID is the key
JobsJob ID, Customer (Ref to Customers), Job type, Description, Technician (email), Scheduled date, Status, Started, Completed, Customer signature, Signed by, SummaryStatus is an Enum with five values
Job photosPhoto ID, Job (Ref to Jobs), Stage (Before, After, Fault), Photo, Caption, Taken atMany photos per job
StaffEmail, Name, Role (Engineer, Office)Drives who sees what

Keep photos in their own tab rather than as Photo 1, Photo 2 and Photo 3 columns on the job. A job with a fault and two stages of repair might need nine photos; a column-per-photo design stops at whatever number you planned for. A separate table also keeps the Jobs sheet narrow and the app quick.

The sums behind that choice: 40 jobs a week is about 2,080 jobs a year, and four photos each is about 8,320 photo rows. Google Sheets allows up to 20 million cells per spreadsheet, per Google's help, so a photo table of six columns (about 50,000 cells a year) is nowhere near it. If you built the same app on AppSheet's own database instead, Starter and Core are capped at 2,500 rows per database, so the photo table alone would stop accepting new rows in about four months. For a service business that logs photos daily, the sheet is the safer home.

If building tidy sheets like these is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.

Create the app and fix the column types

Open the sheet, choose Extensions, then AppSheet, then Create an app (Google's Workspace guidance describes this route; from appsheet.com you can also choose Create, App, Start with existing data). AppSheet reads the headers, guesses a type for each column and builds a first app. Open each table in the editor's Data section and check the guesses:

  • Customer, Job columns: type Ref, pointing at the right table. A wrong reference breaks every list view.
  • Status: type Enum with the values New, Scheduled, On site, Complete, Signed off; initial value New.
  • Photo: type Image. AppSheet's column-types page says images are captured with the device camera or from the camera roll.
  • Customer signature: type Signature. A header containing the word Signature is detected automatically after you regenerate columns, or you set it by hand.
  • Technician: type Email, initial value the signed-in user.

Set Required on Job type, Technician and Scheduled date, so a job cannot be saved half-empty. Then use the editor's preview, not your head, to test: add a customer, add a job, add two photos.

What should a job card show on an engineer's phone?

A job card should show the address, access notes and job description first, then the action buttons, with IDs and timestamps tucked into the detail view so the engineer sees what to do at a glance.

AppSheet's default views are tables and forms. For a field crew, three views are enough:

  1. My jobs today, a slice of Jobs where Technician equals the signed-in user's email and Scheduled date is today, shown as a deck sorted by time.
  2. All open jobs for the office, with Status not equal to Signed off, grouped by technician.
  3. Customers as a plain list for look-up.

Show the card fields in the order an engineer needs them: address, access notes, job description, then the buttons. Hide Customer ID, Started and Completed behind the detail view. A format rule that turns a card orange for Status = On site and green for Signed off costs two minutes to add and saves the office constant phone calls.

For access control, the plan table shows "Manage users by roles" for Core and above. Put Staff roles in the Staff tab and show the "All open jobs" view only to Office. Also switch on user sign-in: AppSheet's subscription help warns that without authentication it counts every device that launches the app as a separate guest user, which can inflate the licence count.

How do you add before and after photos to a job?

To add before and after photos, make Photos a child table of Jobs by setting Job to Ref and turning on "Is a part of" for it. The job's detail view then shows an inline list of photos with an Add button that fills the job automatically. In the photo form, set Stage as an Enum (Before, After, Fault), make Photo required, and set Taken at to NOW() as the initial value.

Add a simple completion rule so a job cannot be marked Complete without both stages. A Valid_If or button-visibility expression such as this one (a pattern to adapt, not a tested recipe: change the column names to yours and try it in the editor's preview before you rely on it) keeps the Complete button hidden until both exist:

AND(
  COUNT(SELECT(Job photos[Photo ID], AND([Job] = [_THISROW].[Job ID], [Stage] = "Before"))) > 0,
  COUNT(SELECT(Job photos[Photo ID], AND([Job] = [_THISROW].[Job ID], [Stage] = "After"))) > 0
)

Photos are stored as files in a folder on the connected file system, which for a Google sign-in is Google Drive. The column's "Image/File folder path" setting lets you choose that folder, so you can keep customer photos in a restricted Drive folder rather than the default location. For customer images, the Core plan lists "Secure image access" and "Require image and file URL signing" in its security features; Starter does not.

A filled-in photo checklist for the crew

The app only helps if photos are consistent. A one-line rule on the job card keeps them useful: "Before: the fault in context, the fault close up, the meter or serial plate. After: the finished work, the area cleaned, the isolation or test result." Three Before and three After per job makes 6 photos, so 40 jobs a week gives 240 rows. That is well within a Google Sheet, and each job has evidence if a customer disputes the work.

How does the customer signature step work?

The customer signs on a touch pad on the engineer's own screen, using a Signature column. AppSheet's help says signatures are captured on a touch pad and stored as small inline images in the spreadsheet, and you can optionally set a folder path for the files. Keep two companion columns: Signed by (a name typed by the customer) and Signed at (initial value NOW()).

Two practical rules:

  • Make the signature field required only on the Signed off action, not on the job form generally, so engineers can save progress.
  • If you use a background image behind the pad, upload it through an Image column in the app rather than linking a Drive file; AppSheet's help notes that Drive export links fail as signature backgrounds because of CORS restrictions.

How do you control job status without free typing?

Control job status with action buttons rather than free typing, because free-typed statuses go wrong within a week. Build them from AppSheet's data-change action, "Set the values of some columns in this row", which Google's help describes as modifying values through expressions. Create four:

  1. Start job: sets Status to On site and Started to NOW(). Show it only when Status is Scheduled.
  2. Finish work: sets Status to Complete and Completed to NOW(). Show it only when Status is On site and the photo rule above is true.
  3. Sign off: sets Status to Signed off. Show it only when Status is Complete and the signature is filled.
  4. Reopen: office role only, sets Status back to Scheduled.

Give Status an initial value rather than an app formula, because a formula recalculates the column and could undo what a button sets; check this in the preview by pressing each button on a test job. The buttons mean the status history is believable, because only the button path produces a timestamp.

How do you email the customer a PDF report when a job is signed off?

A bot in the Automation section can email the customer a PDF report when the job's status changes to Signed off. Create the bot and set the event to updates on the Jobs table, with a condition that fires only when the status changes to Signed off. AppSheet's own email help gives the pattern, using references to the row before and after the change:

AND(
  [_THISROW_AFTER].[Status] = "Signed off",
  [_THISROW_AFTER].[Status] <> [_THISROW_BEFORE].[Status]
)

Add a Send an email task using the Custom template type. Put the customer's email column in To, a subject such as "Job report for <<[Address]>>", and a short body. In the attachment settings, the content type defaults to PDF; you can supply an attachment template, choose to attach and archive the file (it saves to Drive by default under an Attachments folder), and set page orientation and size. Timestamps are added to file names unless you disable them, which is why you should leave them on.

Two limits matter. While the app is in test mode, which means you have not run a deployment check and deployed, any email goes only to the app creator, so a colleague who says "I never got it" has not got a bug. And on a free account email can go only to the owner. Once deployed, plan limits apply: AppSheet's automation limits page lists 200 to 400 email recipients an hour and 1,000 to 20,000 a day on Starter and Core. A firm sending 40 reports a week sits comfortably below that. A deeper treatment of status emails is in the notifications tutorial.

Can an AppSheet field service app work offline in lofts and basements?

Yes, an AppSheet app keeps working with no signal, provided it has first been launched on that device while online. AppSheet stores the app definition and data on the device, so an engineer can keep working offline. Set it up under Settings, then Offline mode in the editor. For a field crew, the combination that suits is Delayed sync switched on with Automatic updates switched on: changes queue and sync in the background when the app starts, when changes are queued, and when local data is more than 30 minutes old. The help notes that after coming back online, changes might not sync until the next automatic sync, up to 30 minutes later, so train engineers to tap Sync before leaving a site with signal.

Also enable "Store content for offline use" if photos must be viewable without signal, and avoid long offline stretches; Google advises against prolonged offline use over days or weeks.

A realistic test day

Give a spare phone to one engineer for one day. Ask them to open the app at the depot, switch to airplane mode before the first job, complete two jobs including photos and a signature, then reconnect and check the office view. If a job shows twice or a photo is missing, you have found a sync problem while it is cheap to fix. Repeat with a second engineer before you roll it out to the crew.

The mistake of building the app before agreeing the job flow

A common failure is building fields for every job type at once. Picture a firm that adds forty columns so that gas, electrical and drainage jobs each capture everything. The form takes eight minutes to fill and engineers stop using it. The fix is to start with the six columns every job shares, then add a second Job type-specific table, such as "Gas safety record" or "Drain survey", linked to the job by Ref. Engineers open the extra form only when the job type requires it, and the main card stays short.

Write the flow on a page before you build: who creates a job, who changes status, what proves completion, who gets the report. If two people disagree about a step, the app will encode the disagreement.

If you want help agreeing the job flow before you build, I offer one-to-one AI consultations for small businesses.

When buying beats building

SituationBetter route
Under 10 people, jobs need photos, signature and a reportBuild in AppSheet
You want customers to book online and pay by cardBuy field service software
You need route planning across many visits a dayBuy, or add a scheduling tool
No one in the firm will maintain the appBuy; a home-built app needs an owner
You already pay for Workspace with Core includedBuild first; the licence is already paid

There is also a middle path: build the job card and report in AppSheet and keep your existing accounting package for invoicing. Many small firms end up here. For help choosing between AppSheet and the alternatives, compare Airtable and AppSheet for a job tracker and AppSheet and Glide, and look at AI scheduling for field service teams if dispatch is your real pain.

Start with one engineer and one job type for a fortnight. If the card, photos, signature and report work for them, add the second type; if they do not, you have lost two days rather than a quarter's subscription.

AppSheet field service app: questions owners ask

Which AppSheet plan does a field service app need?

Core, at $10 per user a month, suits a crew working with customer photos. Starter ($5 per user a month) covers basic apps, automated emails and Google Sheets, while Core adds barcode scanning, scheduled events, role-based access and secure image access. Core is also included in most paid Google Workspace plans, so check your Workspace edition first.

Do my customers need an AppSheet licence to sign?

No, not if the technician captures the signature on their own phone. The licence depends on who uses the app, and the customer only signs on the technician's device. If you give customers their own login, count them as users. Always require sign-in, or AppSheet counts each device as a guest user.

Does the app work with no signal on a site?

Yes, once the app has been opened online on that phone. AppSheet stores the app definition and data on the device and syncs later. Avoid staying offline for days or weeks, and test the exact setup in a basement or loft before you depend on it.

How many jobs can the sheet hold?

A Google Sheet holds up to 20 million cells, so a job table of 8 columns would need 2.5 million rows to reach that. The 2,500-row cap on Starter and Core applies to AppSheet's own database, not to a Google Sheet you connect.

Further reads

Sources: AppSheet pricing page and help-centre articles on subscriptions, limits, columns, automations and offline use; Jobber and Housecall Pro pricing pages; Google Drive help; all read on 17 Nov 2026.

Ready to put AI on the jobs that eat your week?

No data team or big budget needed. In a 1:1 consultation I show small and medium-sized businesses and self-employed people which AI tools they can use, one workflow at a time.

Book a 1:1 call with me