AI inspections for SnapInspect

Overview

SnapInspect is built around a checklist item, and a checklist item is a small, honest package of evidence. A rating, a comment, photos, video, and a timestamp, collected on the phone in the inspector's hand, offline if the building has no signal, then synced and turned into a branded report in PDF, Word or a web link. That package is far better than most portfolios ever manage to collect. What it does not do is compare itself to the last one: the ratings say what the inspector decided, and the photos sit under them unread. RapidEye reads the photos and video on those items across every inspection of the same asset and returns one finding per problem, with the two dated images that show it.

How it works with SnapInspect

SnapInspect names its inspection types on the way in, so the reading follows them. These are examples rather than limits: RapidEye reads whatever a team documents, stills, video or a walkthrough, and reports against the standard the operator cares about.

• Move-in. The move-in checklist becomes the asset's baseline rather than a PDF the resident signed and nobody opened again. Every later inspection is measured against it, which also protects the resident from being charged for the scratch that was in the day-one photo.
• Move-out. The comparison that decides the deposit, done item by item on the pictures. New damage is separated from what was there at move-in and from ordinary wear, and each finding carries both dated photos, which is the form a deduction has to hold up in.
• Routine and periodic inspections. The ones that get walked quickly because the unit is occupied and nothing looks wrong. RapidEye reads them anyway and flags the slow problems that only show as change: a ceiling stain a little larger, a grout line going black, a door that has dropped on its hinges.
• Remote inspections completed by tenants. When an inspection is assigned to a resident or a third party who is emailed a link to the app, the photos come from someone with a reason to frame carefully. A second reading is worth most exactly there.
• Make readies and maintenance follow-ups. The photos taken after the vendor has been in are compared with the ones that raised the job, so the work order that was closed can be shown to have actually happened.

A finding names the asset, the area, where in the area, the type of problem, how bad it looks, both photos and their dates, and a suggested next step. It lands in the RapidEye dashboard, and in an inbox or a Slack channel if that suits your team. Nothing is written back into SnapInspect, so raising a task, charging a deduction or letting it go stays your call. If your inspections lean on video, on a 360 capture or on a checklist format of your own, that is something we set up with you.

How to connect SnapInspect to RapidEye

1. A SnapInspect account with your assets in it. The units and buildings you inspect need to exist as assets, with the checklists you already run for move-in, move-out, routine and maintenance inspections.
2. The photos your inspectors already take. SnapInspect carries the photos and video on the checklist items, so nothing new has to be captured. Inspectors keep using the same app, online or offline, and remote inspections completed by tenants come through the same way.
3. Add RapidEye as a user. An Account Owner opens the Users tab, clicks Add New, and adds RapidEye with the Report Viewer permission. The Connect button on this page has the name, the email address and the permission to pick.

What a SnapInspect inspection holds

Checked against SnapInspect's help centre and product pages, September 2026.

SnapInspect is a mobile-first inspection app for residential, multifamily, student housing and commercial property teams, and everything it produces is assembled from checklist items. According to SnapInspect's documentation (snapinspect.com), you can use its pre-loaded checklist library or bring your own form, inspections run on iPhone, iPad and Android with no internet needed until you sync, and the completed inspection can be edited afterwards on the web and exported as PDF, Word or Excel. One item looks like this.

Multiply that by every item on a move-out checklist and a single inspection is a substantial pile of evidence. SnapInspect then makes it presentable: branded report templates, business logic and scoring on the collected data, customisable emails triggered on completion, and dashboards that track vacancies, maintenance costs and conditions across the portfolio.

Does SnapInspect compare inspections against each other?

It presents them together, which is not the same thing. Side-by-side reporting merges up to five inspection reports into one document so move-in and move-out, or a run of make-ready checks, can be read next to each other. Setting it up is a per-template job: you create the inspection type on the Checklists tab, pick a report template, turn on the Side By Side Report toggle in the config panel, save, repeat for every template you want it on, and ask SnapInspect support to finish enabling it on the account.

That is the honest shape of it. The merge is a presentation step, done per template, on the inspections someone chose to line up, and the comparing is done by eyes. It is genuinely useful when a resident disputes a charge and you want the whole tenancy in one document. It does not scale to reading every asset every time, and it is not meant to.

That is what the integration adds. RapidEye reads all of the media rather than the reports somebody selected, holds the asset's full history rather than five documents, and hands back the differences it found instead of pages to compare. SnapInspect keeps doing the capture and the reporting, which is what it is good at, and the merged report becomes the thing you send to prove a finding rather than the thing you had to read to notice it.

SnapInspect integration FAQ