AI inspections for SiteCompli

Overview

An InCheck inspection is a set of answers with pictures attached, and only the answers get read afterwards. SiteCompli built the harder half well: inspections custom-built per organization, dynamic flows that expand based on what the inspector logs, offline capture, in-app translations, workflows that assign the walk to the right person at the right building and raise follow-up work from the result. The pictures then land in the property record and in a PDF, and after the day they were taken almost nobody opens them. RapidEye reads them, against what that same unit or area looked like on the last walk, and returns a finding per issue tied to the building and the inspection.

How it works with SiteCompli

InCheck organises inspections by the kind of thing being inspected, so the checks follow the same shape your team already navigates.

• Unit inspections. The apartment on a make ready, a turn, or a scheduled check. RapidEye reads the pictures against the last set for that unit and names what changed: a burn on the counter, a missing smoke detector, a radiator cover off, paint that was signed off but is not there.
• Property walks and common areas. Lobbies, stairwells, laundry rooms, roofs and yards, the places curb appeal actually lives. A finding names the area and the spot in the picture rather than "3rd floor hallway, fair".
• Preventive maintenance routines. Recurring equipment checks are where a satisfactory answer is easiest to give twice in a row. Reading the pictures on the same standard every cycle is what turns a slow leak into something visible before it is a repair.
• Due diligence and onsite incidents. Both are one-shot walks where the evidence has to hold up months later. RapidEye returns a dated, itemised read of the pictures so the file is more than a folder of images nobody sorted.
• Follow-up work raised from a result. InCheck can trigger work in real time from inspection results. When the follow-up is inspected in turn, RapidEye compares the two sets of pictures and says whether the fix actually landed.

Each finding names the building, the unit or area, the spot in the picture, the kind of problem (damage, work not done, missing item or safety), how serious it is, the pictures from before and after, and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for your property team if you want it there. InCheck keeps the record; what the finding turns into there is your call. And if the thing your team captures is not a still picture, a video walkthrough of a vacant line, a scan of a mechanical room, an inspection format you built yourself, tell us and we set the read up around that instead.

How to connect SiteCompli to RapidEye

1. A SiteCompli account with InCheck inspections running. Tell us which buildings and which inspection categories to start with; unit inspections and property walks are the usual first two, because that is where condition changes fastest.
2. The pictures your inspectors already take. If your team taps the photo icon on components as they swipe through, RapidEye reads those and nothing in the field changes. For an inspection type with no picture habit yet, RapidEye sends a capture link that opens on any phone, no app to install, with a fixed set of angles per space.
3. A user for RapidEye, and the properties linked to it. Add the user under Company, then User Administration, and link the buildings you want read. The Connect panel on this page has the exact details.

How an InCheck inspection is built, component by component

Checked against SiteCompli's support centre, September 2026.

InCheck is SiteCompli's work management side, sitting next to the compliance monitoring the company is best known for in New York, where it tracks agency data from the FDNY, DOB, HPD, DOHMH, Sanitation, County Clerk and DOT. According to SiteCompli's support centre documentation (sitecompli.com), inspections can be logged from the desktop platform or the mobile app, and they are always custom-built for your organization: a new inspection type or a change to an existing one goes through SiteCompli support rather than a template editor. On the desktop the inspector picks the property and the inspection type and fills out each component. On a phone the same inspection becomes a stack of cards, answered one at a time and swiped left to reach the next, with an option to close and continue later that leaves the task in the tasklist.

What matters for condition is the attachment pattern, and it is per component rather than per inspection.

An illustration, not a screenshot: inspections are custom-built per organization, so your components and answer options will be your own.

Does InCheck let you attach photos to an inspection?

Yes, on every component. SiteCompli's support documentation describes clicking the photo icon to take a picture or the speech bubble icon to add a comment against any component of an inspection, on the desktop and in the app, and its inspections product page lists onsite signatures, pictures and notes as capturable fields, with offline logging for buildings where there is no signal. The company also publishes performance metrics per building and on-demand PDF reports per inspection. What none of those pages describes is anything comparing this walk's pictures with the last one's, which is the read that turns a stack of inspections into a condition history.

What that means for a property manager in a portfolio

Your compliance side is already automatic: the agency data arrives whether or not anyone goes looking for it, which is precisely why violations rarely surprise a SiteCompli customer. Condition works the other way. It only enters the system when a person notices it and taps the right answer, and a portfolio measured in millions of square feet cannot be held to that standard by attention alone. Reading the pictures is how the condition half of the record catches up with the compliance half.

SiteCompli integration FAQ