AI photo review for Coast

Overview

A Coast work order records what was done. Its photos are the only part that shows what the asset now looks like. Coast gives every work order an upload box, a message thread with a camera button, a checklist, a procedure, an asset and a location, and a status that ends at Complete. Once Complete is set, that photo trail stops being read. RapidEye reads it: every image on the work order, the work request and the asset record, matched to the asset and site they came from, returned as a finding you can act on.

How it works with Coast

Photos enter a Coast account at four different moments, and each one answers a different question. The checks follow them.

• The work request that opened the job. Anyone can scan the QR code on an asset and submit through your external work order form, describing the problem in their own words. Those first photos are usually the truest picture of the fault, so RapidEye reads them as the before state and holds them against whatever comes back at the end.
• The upload box on the work order. Up to ten images, files or videos ride here. RapidEye reads them for damage the technician was not sent to look at: a corroded bracket in the corner of a shot about a fan belt, a floor left slick, a panel that has been off for three visits.
• The message thread. Coast lets anyone attach further pictures next to the message field while the job runs. Those mid-job photos are where a small repair quietly turns into a bigger one, and a finding says so while the technician is still on site.
• The checklist and the procedure. A work order can carry to-do's and a procedural sub form built for your organisation. When photos are taken against those steps, RapidEye checks the photo against the step rather than against a general idea of tidy: guard refitted, filter replaced, valve closed.
• The asset record. Assets carry their own photos, files, manuals and description in Coast. RapidEye uses them as the baseline for what that asset looks like healthy, which is what makes drift visible: rust that was not there in March, a mount that has worked loose.

A finding names the asset, the location, the kind of problem, how serious it is, the photos behind it and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox if your maintenance team would rather see it there. Nothing is written back into Coast; you decide whether a work order gets reopened or a new one raised. If what your team captures is not photos, or the standard you care about is your own, that is a setup conversation and not a limit: video walkthroughs, 3D scans and inspection formats of your own are all things we read.

How to connect Coast to RapidEye

1. A Coast account with the Work Orders workspace running. Coast builds it from the Maintenance Work Order Management workflow, and the assets and locations you care about should exist there, since every finding lands on one of each.
2. The photos you already attach. Work orders, work requests and asset records in Coast all take images, so RapidEye reads those, including the history already in the account. If a crew is not photographing yet, a RapidEye capture link opens on any phone with a fixed set of angles and no app to install.
3. An invite for RapidEye. Coast invites people from your profile icon, by email, link or text. The modal has the details.

What a Coast work order holds

Checked against Coast's help centre, September 2026.

Coast is a mobile-first work order and maintenance app, and the work order is the whole product in one record. According to Coast's help centre documentation (coastapp.com), a work order needs only a title to exist, and everything else is a field you fill as the job goes: the problem description, a checklist of to-do's, a procedural sub form, an asset, a part, a location, a priority, a due date and an upload box that takes up to ten images, files or videos. Technicians work the same record from the Coast mobile app in the field.

The record above is an illustration of the fields Coast documents, not a screenshot.

Status is the spine. A new work order is tagged Open, and from the Update Status button a person moves it along by hand.

• Open default
• Pending Review
• In Progress
• On Hold
• Complete set by hand

Around the work order sit the parts of Coast that give a finding its address. Assets hold photos, manuals and a maintenance history, sit in a parent and sub-asset hierarchy, and can be identified by a QR code stuck on the equipment itself. Locations nest into a multi-level hierarchy, so a site, a building and a floor are all real places in the account. Work requests arrive from outside the team through an external form shared as a public link or a QR code, with a requester email field that sends status updates back automatically. Work orders can also be shared out to a vendor.

Can Coast tell you what the photos on a completed work order show?

No CMMS can, Coast included, because that is not what a work order is for. Coast's help centre describes attaching images, adding them from the thread while a job runs, storing them against an asset, and moving the status to Complete. Nothing in the maintenance workflow, at Coast or anywhere else in the category, then opens those images and asks whether the repair actually looks finished, whether the surrounding space took damage, or whether the same asset has been photographed in a worse state three times this quarter. Complete is a statement about the job. The photos are the statement about the asset, and reading them is the part the integration adds.

Coast integration FAQ