AI inspections for GoAudits
Every photo your inspectors attach and annotate on a GoAudits checklist gets read, and you get a finding back for what else was standing in the frame.
Inside a GoAudits questionOverview
A GoAudits inspection answers the questions you asked. The photos on it contain answers to questions nobody thought to ask. GoAudits gives an inspector a custom digital checklist that works offline on a phone, tablet or laptop, with colour-coded responses, conditional logic, automatic scoring, annotated photos, timestamps and geolocation, and it turns all of that into a branded report the moment the inspection ends. The score gets read carefully. The images travel with the report and are opened once, if that. RapidEye reads them: every attached photo, against the same area's earlier photos, returning a finding for each thing it can see.
How it works with GoAudits
The structure GoAudits already imposes on an inspection is the structure the reading uses.
- Questions with a mandatory photo. Where the form builder requires an image before an inspector can move on, there is a guaranteed photo of that thing on every single inspection. That is the strongest input a site can hand us, and it is already there.
- Sections. A checklist grouped into sections is a site grouped into areas. RapidEye keeps a baseline per section, so the goods-in bay is read against the goods-in bay and not against the canteen.
- Annotated photos. An inspector circles the thing they came to record. RapidEye returns the rest of the frame: the housekeeping behind it, the label peeling off the drum on the left, the gap in the rack that was full last time.
- Photos on a passing answer. Nothing gets skipped for having scored well. A green response with a photo behind it is read exactly like a red one, which is where most of what nobody expected turns up.
- Photos closing a corrective action. When an assignee uploads an image with their resolution, RapidEye holds it as the after shot for that area and reads the next inspection against it.
Each finding names the site, the section, where in the frame it sits, the type of issue, how serious it looks, and the earlier photo it is being compared against. Findings land in the RapidEye dashboard, and in an inbox or a Slack channel if you want them there. Your team decides whether one is worth an action plan in GoAudits, because GoAudits keeps that job. If your inspectors capture video walkthroughs, drone footage or 3D scans as well as stills, RapidEye reads those; tell us what you have and we set it up.
How to connect GoAudits to RapidEye
- Pick the checklists and locations. Start with the ones your teams run most often. Sections are how RapidEye separates one part of a site from another, so a checklist that is already grouped by area needs no work at all.
- Leave the photo questions as they are. Anywhere your form builder already requires a photo, or an inspector habitually adds one, the input exists. Nothing gets added to the checklist and no inspector is asked to do anything differently.
- Add RapidEye as a user. In the admin portal, Users, Add New User, with access to the web admin portal. The connect box has the details.
What one GoAudits question actually holds
Checked against GoAudits product pages and help centre, September 2026.
The unit of a GoAudits inspection is not the report. It is the question, built in the Form Builder in the admin portal and answered in the app. According to GoAudits help centre documentation (goaudits.com), a question carries a response type whose buttons can be colour-coded, an optional score, instructions in text or an image, and a mandatory setting that can require a comment, a photo, or both before the inspector is allowed to move on. In the app the inspector selects an answer, enters a comment, and takes a photo or picks one from the gallery; tapping the photo opens it for annotation, and the annotated version is what appears on the generated report. Preloaded reference photos can sit on the question too, with a setting to keep them off the printed report.
Are pallet racking uprights free of impact damage?
Instruction: check the bottom two metres of every upright on aisle A.
The example is hypothetical. The fields are not: colour-coded responses, instructions, a mandatory comment and photo, annotation, timestamp, geolocation and inspector name are all documented parts of a GoAudits question and the report it feeds.
So what happens to the photo after the report goes out?
It gets attached, distributed, and then it waits. GoAudits does a great deal with the structured half of the inspection: automatic scores by section, recurring failures, historical trends, dashboards that let a head office compare sites, and distribution rules that put the report in front of the right manager for approval. That is genuinely the hard part of running inspections at scale, and it is why an operator on GoAudits already knows more about their sites than one on paper ever did. The image half is different in kind. It is unstructured, there is a lot of it, and the only way to get anything out of it has historically been a person opening it and looking. So a manager reads the score, skims the fails, acts on those, and the forty photos behind the answers that passed are filed unopened. RapidEye is the part that opens all of them.
GoAudits integration FAQ
Does RapidEye integrate with GoAudits?
Yes. RapidEye reads the photos your inspectors attach to questions on a GoAudits checklist, along with the site, the area and the date, and returns a finding for each issue it sees in those frames. Your GoAudits checklists, scores, reports and action plans stay exactly as they are.
Where do the photos come from?
From the checklist itself. GoAudits help centre documentation says an inspector selects an answer, enters a comment and takes or picks a photo on the question, then taps the photo to annotate it before saving, and that the annotated image appears on the generated report. Those are the images RapidEye reads.
Does RapidEye change our scores or reports?
No. GoAudits stays the record: the automatic scores, the section scores, the branded report and the corrective actions are untouched. RapidEye findings arrive beside them, and your team decides whether one is worth raising an action for.
We use mandatory photo fields already. What does reading add?
Mandatory photos guarantee an image exists for a question. Reading tells you what is in it. A required shot of a mixing area answers the question it was attached to and also happens to contain a leaking seal, a missing guard and a pallet in a walkway, none of which any question asked about.
Can it compare one inspection against the last one?
That is the main thing it does. On connection RapidEye reviews the photos in your past GoAudits inspections to build a baseline for each area, so a new photo of the same bay is read against the same bay in April rather than against nothing.
Does this only work for manufacturing sites?
No. GoAudits runs in hospitality, retail, food, facilities, healthcare and logistics too, and RapidEye reads photos from a checklist the same way whatever the site is. Tell us what your inspectors photograph and what you want caught.
Other inspection and EHS software RapidEye reads
Platforms where a checklist on a phone is the thing that produces the photos.
MittiChecklist photos from the frontline app formerly branded SafetyCulture
EHS InsightImages filed through the mobile app into audit and incident modules
SafetyChainPlant floor checks and quality forms across food and beverage sites
IdeagenAudit and quality evidence from regulated manufacturing operations
Vector EHSPhotos on safety incident and EHS records inside Vector Solutions
All manufacturing and EHS integrations
Sources
- GoAudits product pages and help centre documentation for the auditor app, reports, workflows and user setupgoaudits.com
Sources are named at the publisher level and were checked against the publisher's live pages before this page was published.

