Field management and site photo capture Solar · HVAC · Generators · Plumbing · Electrical

Send the crew.Show the work

FieldDeploy runs the crew side of a service call. The morning truck inspection, the site photos, the hand-off to the office. On a shared tablet, on a roof or in a basement, with no signal.

6:30AM

One tablet on the truck. A code for every person.

Nobody types a password at dawn. Each tech taps their name and enters a four-digit code. The office signs in with Google Workspace. Subcontractors use their own device.

  • Tablets pair to your company with a one-time code that expires in five minutes.
  • How someone signs in is separate from what they can do. Roles decide that.
Sign in on the tablet
6:40AM

No inspection, no work orders.

The DVIR is a gate, not a reminder. Today's work orders stay hidden until the crew walks the truck and files it. Addresses and plan sets appear only after the inspection is cleared.

  • The form matches the vehicle: truck, van, or truck with trailer.
  • The odometer comes from fleet telematics. The day downloads during the walkaround.
Walk the truck
8:15AM

Every crew shoots the job the same way.

On Site walks the crew through the job section by section. Each field asks for exactly the photo the office needs, and progress shows what's left before the crew can leave.

  • A built-in camera with photo rules set per field.
  • A finish-up crew sees the first crew's photos on the same work order.
Press the shutter
11:20AM

The basement has no signal. The crew keeps working.

Every answer and photo is saved to the tablet first. When the signal comes back, the queue uploads and the server confirms each item. A retry never creates a duplicate.

  • Built for a full day without a connection, not a short dropout.
  • Online or offline is shown on every screen.
Cut the signal
1:30PM

The office changes a form. Tablets have it by the next job.

Forms are templates, not code. When a customer or a utility starts asking for a new label photo, ops adds the field in the console. No app update, no App Store review.

  • Templates are versioned. Work on a draft, then publish it.
  • A financing partner with its own photo requirements gets its own template, picked automatically.
Switch a field on
4:30PM

One bad photo doesn't mean a whole redo.

Submitted work goes to review in the console. If something fails, a rollback opens a new work order with every approved section carried over. The next crew redoes only what failed.

  • Every step from scheduled to approved is tracked.
  • Rollbacks are scheduled for the next day or later, never mid-shift.
Approve or roll back
8:10PM

The truck is parked. The uploads keep going.

A session can end before the queue does, so uploads finish overnight on their own. Each tablet checks in about every five minutes with its network, battery and pending uploads.

  • The office sees which devices have gone quiet, and why.
  • Sessions reset overnight. Tomorrow starts at the DVIR again.
Watch the fleet check in
app.fielddeploy.io
FieldDeployTruck 12 tabletOnline
This tablet is paired toPlugPV · Truck 12Paired
Who is working today?
Any code works here.
Enter Dana's four-digit code.
DVIRTruck 122 of 6
Downloading today's work: 40% Answer all six items to submit.
Today 3 work orders
Finish the DVIR to see today's workAddresses and plan sets stay hidden until the inspection is filed.
On SiteWork Order 104826 of 14 photos
Array: overview
Array overview
Photo 1 of 3 in Array
On SiteWork Order 10482
Signal
Connected
Online
Turn it off, then take photos.
Simulated. Real uploads wait for the server to confirm each item.
Upload queue
ElectricalOn Site templateVersion 7 live
ElectricalWO 10482
Form updated. No app update.
ReviewWork Order 10482
DevicesTonightSimulated, about 60x speed

Our story

We run field crews for a living. FieldDeploy is the software ours needed.

PlugPV is a residential and commercial solar EPC in Troy, NY. Our crews start before sunrise and work in basements and on roofs with little or no signal. Every job is reviewed before it closes. We built FieldDeploy around that work, and our own crews use it. The same day plays out in HVAC, generators, plumbing and electrical: a crew is dispatched, does the work, and has to show it. FieldDeploy is built for that day, whatever the trade.

In the field

A crawlspace has no signal.

Everything saves to the device first.

Uploads retry until the server confirms them.

In the field

Busy mornings skip the truck inspection.

The DVIR is a hard gate.

No inspection, no work orders.

In the office

A new requirement shouldn't need an app release.

Forms are templates.

The office edits them. Tablets pick up the change.

In review

One unreadable photo shouldn't send a crew back for the whole job.

Rollbacks carry approved work forward.

The crew redoes only what failed.

Principles

Four rules the product doesn't bend.

Gate, don't nag

Required steps block the next step.

A reminder can be dismissed. A gate can't. No DVIR means no work orders, and sensitive job details stay hidden until the crew clears it.

Offline first

The tablet holds the truth until the server confirms it.

Work is saved locally before anything else happens. A dropped connection or an expired session never costs a photo.

Walled off

Your company's data stays your company's.

Every record belongs to one company, and the server enforces that on every request. The app's screens aren't trusted to do it.

Graceful failure

An outage somewhere else doesn't stop the day.

If fleet telematics is down, the DVIR still goes through. If the CRM is down, work orders still run.

RULE 1 OF 4

Roadmap

On the bench.

Designed, not shipped. These move to the feature list once crews are using them.

Punch listNot on the tablet yet CrewFieldDeploy StatusDesigned, not shipped
  • QC Check

    Flags a bad photo while the crew is still on site. It flags but never blocks, and a manager can override.

    ON SITE / PHOTO
    Planned
  • Arrival and departure

    Geofenced arrival and departure that can tell a lunch run apart from leaving the job.

    WORK ORDER / LOCATION
    Planned
  • Customer sign-off

    An attributable sign-off at the end of the job. Any later edit voids it.

    WORK ORDER / CLOSE-OUT
    Planned
  • Work order chat

    Conversation tied to the work order that carries over through rollbacks.

    FIELD / OFFICE
    Planned
  • CRM sync

    Schedules and customers come in from your CRM. Completions, photos and DVIR status go back out.

    INTEGRATIONS
    Planned
  • API and webhooks

    Signed webhooks and API keys for connecting your own systems.

    PLATFORM
    Planned

A box is ticked when crews are using it. Then it comes off the clipboard.