AI inspections for Condo Control

Overview

A Condo Control service request is a conversation with an attachment, not a record of condition. It carries a request type, a priority, a description, the resident's photos, then a chain of public and internal updates until someone saves it as Closed. The pictures inside it are read once, by whoever handled the request that week, and then they are filed under a request number nobody reopens. RapidEye reads those photos, plus the images on incident reports and patrol checkpoint reports, together with the property, the area and the date, and returns a finding per issue with the last picture anyone took of the same place beside the new one.

How it works with Condo Control

Condo Control spreads pictures across four places, each belonging to a different person in the building. RapidEye reads them as one stream about one property.

• Service request attachments. The resident who photographs a bulging ceiling tile or a scratched elevator panel is describing one thing; the picture usually shows two or three. RapidEye returns the ones nobody wrote down, and names the unit or the area they belong to.
• The closing photo on an update. Staff upload files onto an update before saving the request as Closed. That photo is the only proof the work happened, and it goes straight into the archive. RapidEye compares it with the photo that opened the request and says whether the repair covers the damage.
• Incident reports. A guard attaches images, sometimes camera screen captures, to an unlimited-text report under whichever category your community set up. RapidEye pulls the physical damage out of the narrative: the bollard that moved, the door frame that is now splintered, the glass on the floor.
• Patrol checkpoint reports. A route through the lobby, garage, stairwells and amenity rooms is already a scheduled walk of the property. Photos raised at a checkpoint become that area's condition record, and the next patrol becomes the comparison.
• Preventive maintenance activities. Recurring work on a component carries documents and photos. RapidEye keeps the picture from the last service beside this one, so wear on a roof, a pump room or a garage door is visible as a change rather than a memory.

Every finding names the property, the area and the spot inside it, the kind of issue, how serious it looks, the earlier and the later photo, the date, and a suggested next step. It lands in the RapidEye dashboard and, if you want, an inbox or a Slack channel for the management office. Your team decides whether it becomes an update, a violation, a chargeback to a unit or nothing at all. If your buildings document differently, video walkthroughs of common areas, 3D scans after a renovation, an inspection form your regulator requires, tell us what you capture and we set the reading up around it.

How to connect Condo Control to RapidEye

1. A Condo Control workspace with your buildings in it. Units live in the Unit File, and that is what a finding points at when the issue is inside a unit rather than in a shared area.
2. The photo sources you want read. Service request attachments, incident report images, patrol checkpoint reports, preventive maintenance activities, or all four. Where an area produces no photos at all, RapidEye sends a capture link that opens on any phone with no app to install, a fixed set of angles per area, taken on the round your staff already walk.
3. RapidEye as a staff user. Staff accounts are created from the Unit File with the unit number left blank, and the user group decides what the account can see. The Connect panel has the exact fields.

What a Condo Control service request actually holds

Checked against Condo Control's help centre, September 2026.

Condo Control runs condominiums, co-ops and homeowner associations, and the service request is the record almost every physical problem in the building passes through. According to Condo Control's help centre documentation (condocontrol.com), a resident opens one by choosing a request type, a subject and a priority, writing a description, ticking permission to enter their unit, and adding attachments through an upload files step before sending it. Communities rename the feature and define their own request types, so the same record might be called a service request in one building and a work order in the next.

From there the request becomes a thread. Staff with the right permissions add updates, marked either Public, which the resident sees, or Internal, which only staff with the designated permission see. Updates can be typed or dropped in from macros, the pre-written responses a community administrator sets up, files can be uploaded onto any update, and assignees can be changed as the nature of the job becomes clear. Each update is saved with a status: Save as Open when the request has been received but no work has started, Save as Pending when steps have been taken but it is not finished, and Save as Closed when it has been resolved. Notifications follow the visibility, so a public update emails the resident and an internal one emails the team.

The four records in Condo Control that carry a picture

Every one of these accepts an image, and none of them looks at it.

Does Condo Control inspect anything in those photos?

No, and it does not claim to. Its maintenance pages describe logging and storing requests in one location, notifying residents, sending automatic follow-up reminders on open requests, and reporting on which services are requested most often and how long requests stay open. That is throughput: what was raised, by whom, and how quickly it closed. None of it is a statement about condition, because nothing in the platform opens the attachment and compares it with the last picture of the same wall. The photo is evidence with no reader. That is the half the integration supplies, and because the pictures are already dated and already tied to a building and an area, the history a community needs for a chargeback or an insurance file is sitting there before the first new photo arrives.

Condo Control integration FAQ