Skip to content
Mesa Web Designers

Project galleries

ServiceTitan Job Photo Review & Publishing Workflows

One careless photo can cost more trust than fifty good ones earn. We build the private review tool where every job photo is checked, cropped, consented and approved before it can reach your website.

Demonstration · custom admin screen
  • Demo job 10482 · Heat pump

    Clean install photo, no address visible

    Approved
  • Demo job 10477 · Tile roof

    House number visible: crop or reject

    Needs review
  • Demo job 10469 · Water heater

    Customer in frame

    Rejected
  • Demo job 10451 · Kitchen

    Customer consent on file

    Approved
Illustrative admin screen with demo job numbers and drawn images. Not real jobs or customers.

The photo that shows more than the water heater

A technician's photo of a new water heater looks harmless until someone notices the family calendar on the garage wall, a child's name on a bike, or the house number on the door behind it. Publishing that is a privacy problem for the customer and an awkward phone call for the owner. Plenty of companies avoid the risk by not publishing at all, which is why their galleries are empty.

A review tool makes the safe path the easy one. Every photo that might go public passes through one screen where a person checks it against a short list, crops what needs cropping, confirms consent, and approves or rejects it. The tool remembers the decision, and nothing reaches the website without one. It sits at the center of every ServiceTitan project gallery we build.

What the review screen does

  • A queue grouped by job

    Photos arrive under the job number the technician entered, newest first, each with a status: needs review, approved, rejected or published.

  • Job association

    Where your admin approves read access, the tool confirms the job number and shows the job type and business unit through a lookup. Those details are shown in the tool only, not stored or published. Without it, the reviewer picks the service from a list.

  • Crop, blur, choose a cover

    Basic edits in the browser, built as a small custom web application. The original stays untouched in your private repository; the website only ever gets the edited, approved version.

  • Captions and alt text

    Short fields with clear guidance: what was done, which service, which neighborhood. No addresses, no customer names.

  • Consent on record

    Who agreed, how (work order language, a text reply, a signed form) and when. A photo can't be approved without a consent record for its job.

  • Publish and unpublish

    Approved photos go to the website on the next publish, whether into the automated project gallery or a written case study. Unpublishing removes them everywhere.

The sensitive-information checklist

The reviewer sees this list beside every photo. If something can't be cropped out, the photo is rejected.

  • House numbers and street signs

    On doors, curbs, mailboxes, garage doors and fences, including reflections and the edges of the frame.

  • Faces and people

    Customers, family members and neighbors, and your own staff unless they've agreed to appear.

  • License plates and vehicles

    Cars in the driveway or on the street, which can identify a household as easily as an address.

  • Documents and screens

    Mail, invoices, permits showing an address, whiteboards, calendars, alarm panels and smart-home screens.

  • Personal belongings

    Family photos, children's names on toys or rooms, anything that says more about the household than the work.

The approval workflow

  1. 1

    Photos arrive

    From the technician upload app, an office upload, or your existing photo library. An API feed of ServiceTitan attachments is an option only where ServiceTitan has approved that use in writing for your account.

  2. 2

    First check

    The reviewer works through the checklist and crops or rejects. Most photos take seconds.

  3. 3

    Consent confirmed

    The tool checks the job's consent record. Missing consent puts the photo on hold rather than rejecting it, so the office can ask the customer.

  4. 4

    Caption and tag

    Service, job type and neighborhood-level area, plus a caption and alt text.

  5. 5

    Approve

    Gallery photos need one approval; case studies can require a second. Completed jobs to case studies.

  6. 6

    Optimize and publish

    Metadata stripped, sizes generated, files published, and every step recorded in an audit log.

Roles and permissions

  • Technicians

    Upload only. They see their own recent uploads and can't approve or publish anything.

  • Reviewers

    Office or marketing staff who crop, caption, approve or reject photos in the queue.

  • Publishers

    The owner or a manager who gives final approval on case studies, manages consent records and can unpublish anything.

  • An audit log

    Who approved, edited or removed what, and when, for the day a customer calls with a question.

  • Credentials kept server-side

    Staff sign in to the tool with their own accounts and never type a ServiceTitan password into it. API credentials stay on the server with the least access needed. How ServiceTitan API access works.

What ServiceTitan handles vs what the tool adds

NeedIn ServiceTitanCustom-built
Photos on the jobAttachments live on the job record inside ServiceTitan.Copies your company owns, in your own repository, tagged with the job number.
Showing the customerPhotos marked customer-facing appear for that customer in the New Customer Portal.Public publishing with approval status, consent record and unpublish.
Privacy reviewThe customer-facing setting controls what that one customer sees.Checklist, cropping, metadata stripping, roles and an audit log before anything is public.
Job detailsOn the job record, for your team.A read-only lookup inside the private tool where your admin approves it, not stored or published.

What to have ready before we talk

None of this is required for a first call, but each answer makes the scope and the quote sharper.

  • Who will review and approve photos, and whether case studies need a second approver
  • How customer consent is collected today: work order language, a text after the job, a form
  • Which sources feed the queue: technician uploads, office uploads, an existing library
  • Whether your admin will approve a read-only job lookup for the tool
  • How long to keep originals and rejected photos
  • Where the published gallery and case studies live on your website

Related ServiceTitan development

Mesa Web Designers is an independent developer. We are not affiliated with, endorsed by, or a partner of ServiceTitan. ServiceTitan is a trademark of its owner. What an integration can do depends on your ServiceTitan products, the permissions your admin grants, and the APIs available to your account.

Start the conversation

Make the safe photo the easy one to publish.

Tell us who takes photos, who should approve them and how you handle consent today. We'll design the review tool around that.

  • Web apps, portals and integrations start from $575, priced by complexity
  • The developer who scopes it builds it and answers the phone
  • Built for ServiceTitan contractors nationwide
Step 2 of 4 · The details50%

What do you need built?

Pick what fits (pick any)

Rather talk? (480) 525-7582. 0% financing on any project, 25% down. See all pricing

Photo review & approval: questions we hear a lot.

Does ServiceTitan have a photo approval workflow for websites?

ServiceTitan lets your team mark photos as customer-facing so that customer can see them in the New Customer Portal. It isn't a website publishing tool, so reviewing and approving photos for a public gallery is the part we build.

Who should review the photos?

Someone in the office who knows the jobs and can spot a house number at a glance, often the person who handles marketing or reviews. The queue is quick enough to clear in a few minutes a day.

Can the tool blur faces and house numbers automatically?

We build the review around a person, with crop and blur tools that make fixes quick. Every photo is looked at before it's approved, because a missed house number is exactly the mistake the tool exists to prevent.

Why strip GPS data if captions only name the neighborhood?

Because the image file itself can still carry exact coordinates, which anyone can read after downloading it. Stripping metadata closes that gap on every published file.

Does the tool store our ServiceTitan data?

It stores your photos, your captions, consent records and the job number the technician entered. Job details from the API are looked up when a reviewer needs them and aren't kept, in line with ServiceTitan's API Terms on storage.

Make the safe photo the easy one to publish.

Tell us who takes photos, who should approve them and how you handle consent today. We'll design the review tool around that.