AI inspection photo review for Mitti

Overview

A Mitti inspection is a superb capture instrument and an honest one. It records who answered what, when they changed it, which site it belongs to, and the images they attached to each question, and it keeps that history for years. What it is not asked to do is look at the picture. Mitti's own homepage counts more than three million new photos uploaded a day across the platform, which is the scale of the problem and the scale of the opportunity. RapidEye reads those images, compares each one to how that area at that site normally looks, and returns a finding per issue, with the image and the question it came from.

How it works with Mitti

Mitti organises work by site and by template, so the review follows the same shape. Point us at a template and the sites it runs at, and every image that arrives on a completed inspection gets read. These are examples rather than a menu: RapidEye reads whatever documentation a team already produces, including video walkthroughs and 3D scans, and reports against whatever standard you care about, so if your case is not on this list the answer is almost certainly still yes.

• Pre-start and shift handover checks. The same guard, the same walkway, the same panel, photographed shift after shift. RapidEye holds the earlier images and says when the guard is off, the walkway is blocked or the panel is open, even when the question was answered Pass.
• Housekeeping and 5S rounds. Spills, cabling across a floor, a fire door propped, pallets stacked past the line. These are the findings that live in the background of a photo taken for another reason entirely.
• Asset and equipment condition. Mitti links inspections to assets and maintenance programs. The photos taken against an asset become a condition record for that asset: corrosion spreading, a cracked housing, a guard that came off two months ago and never went back.
• Contractor and external work. Mitti lets you assign actions to people outside your organisation by email, and its help centre notes those external assignees can attach media. That media gets the same reading as everyone else's, which is exactly where an independent look is worth most.
• Corporate and multi-site audits. One standard across forty sites is only as consistent as the eye applying it. Reading the images gives every site the same reviewer, which is the only way that phrase means anything.

A finding names the site, the area, where in the frame the issue is, what type it is, how serious, the images before and after, and a suggested next step. It lands in the RapidEye dashboard, and in an inbox or a Slack channel if your team wants it there. What happens next in Mitti is yours: you decide whether it becomes an action, an issue or nothing at all. If you want a specific use case covered, or you capture something other than photos, that is a conversation we have with you rather than a feature you have to find.

How to connect Mitti to RapidEye

1. A Mitti account with the sites you want read. Sites are how Mitti organises inspections, so the site hierarchy you already use is the scope of the review. Start with the sites where a missed finding costs the most.
2. The questions that carry media. Most templates already have them. If a template you care about has no image on it, a RapidEye capture link opens on any phone with no app to install and supplies a fixed set of angles instead.
3. Add RapidEye as a user in Mitti with view access to the inspection results you want read. The connect panel on this page has the path and the address.

What a Mitti inspection question actually holds

Checked against Mitti's help centre, September 2026.

Mitti is the operations platform from SafetyCulture, the one that used to be branded SafetyCulture and, before that, iAuditor; the rename is recent enough that a lot of the workforce still says the old names out loud. An inspection is a template answered question by question, and each question is a richer object than a checkbox. According to Mitti's help centre documentation (mitti.com), a question can hold a response, a note, attached media, an annotation drawn on that media, and a full history of who changed what.

Access is the other half of the design, and it is unusually well thought through. Templates carry their own levels, from Conduct up to Conduct, edit, delete, and inspections carry a separate set from View up to View, edit, delete, so the person who writes the template is not automatically the person who reads every result. Access rules can hand results to the right group automatically. This is why connecting RapidEye is a scoping decision rather than a data decision: you give it the view level for the results you want read, and nothing else moves.

Does Mitti review the photos attached to an inspection?

It stores and presents them, which is the right job for a system of record. The help centre describes attaching media to a question, annotating an image, saving photos to the device gallery, duplicating an inspection along with its media attachments, and exporting the full change history. None of those articles describes anything that looks at the content of an image, and none of them should: Mitti's contract is that what the frontline captured is preserved exactly, attributed, and available. That contract is what makes the images worth reading. Every photo already carries the site, the area, the template, the question and the person, so a finding RapidEye returns arrives with all of that context attached rather than as an orphan observation.

What about the images you already have?

They are the reason this works on day one. A new photo of a walkway means very little on its own; the same walkway across eleven months means a great deal. On first connection RapidEye reads the images already sitting on your completed inspections and builds a baseline per site and per area, so the first findings you see are drift you never had a way to notice: the extinguisher that moved, the label that came off, the corner that has been getting worse one shift at a time.

Mitti integration FAQ