AI condition inspections for Reapit

Overview

Reapit holds the tenancy, the works order and the certificate, but not a picture of the room. Its property management module keeps the tenancy record where inspections and post-tenancy activities are tracked, the works order record where maintenance jobs are raised and chased, and the certificates panel where safety checks and expiry dates live. What none of those hold is a reviewed photograph of what a property actually looked like on the day. RapidEye reads the property, tenancy and works order records from Reapit alongside the photos your managers take on site, and returns one condition finding at a time against the address they belong to.

How it works with Reapit

Reapit organises lettings work around records rather than around a checklist, so the checks follow the record a photograph belongs to. A property manager who already lives in the tenancy screen does not learn a new place to look.

• The routine visit on the tenancy record. Reapit tracks inspections and post-tenancy activity against the tenancy. RapidEye reads the visit photographs, compares each room to the last time it was photographed, and names what is new: a scorched worktop, a cracked pane, damp climbing the wall behind a wardrobe that was not there in March.
• Works orders and the contractor who says it is done. A works order is raised, approved and assigned to a supplier, and the invoice gets authorised before posting. If a photograph came back with the job, RapidEye reads it against what was ordered and flags a job billed with a picture that does not show that work.
• Check out, before the deposit conversation. Every cleaning miss and every bit of damage becomes its own line with its own photograph, which is what makes a deduction easy for a tenant to accept and hard to argue with.
• Furnished lets and what has gone walking. Oven shelves, a dining chair, a lamp, the shower screen. RapidEye knows what stood in that frame last time and tells you what is not in it now.
• Compliance risk sitting in an ordinary photo. An alarm hanging off its bracket, a loose banister, a blocked flue. Reapit tells you when the certificate expires; the photograph is where you find out the thing itself is wrong.

A finding names the property, the room, the spot in the frame, the kind of problem, how serious it is, the earlier photograph beside the new one, and a suggested next step. It lands in the RapidEye dashboard and, if you want it, an inbox or a channel for the lettings office. The examples above are the common ones, not the boundary: RapidEye reads whatever documentation your team already produces, including video walkthroughs and 3D scans, and checks it against whatever standard your agency cares about, so if your use case is not on this list it is a conversation, not a no.

How to connect Reapit to RapidEye

1. Name the managed portfolio. Point us at the properties you manage in Reapit rather than the whole database. The property record and its tenancy are what each finding gets filed against, so a sales-only branch stays out of it.
2. Decide where the photographs come from. If your managers already shoot visits into a document store or an inventory app, RapidEye reads those. If they do not, RapidEye sends a capture link that opens on any phone with nothing to install, and the manager takes a fixed set of angles per room while standing in it.
3. Agree access with your Reapit administrator. Reapit's own developer documentation is clear that the customer approves what an installed app may see, and that the approval email goes to the person who installed it. Tell us who that is at your agency and we handle the rest with them.

What a Reapit record actually holds about condition

Checked against Reapit's product and developer documentation, September 2026.

Reapit is an end to end platform for estate and lettings agencies, sold across the UK and Ireland, Australia and New Zealand, and Denmark, with a Sales CRM, a Lettings CRM, Bookings, Property Management, Client Accounts and a DataWarehouse under one login. According to Reapit's developer documentation (reapit.cloud), third parties request access permission by permission, and the list of those permissions is the most honest inventory anywhere of what the CRM actually stores. Read it as a lettings manager rather than as a developer and a pattern jumps out: Reapit is exhaustive about the paperwork of a tenancy and quiet about its condition.

Put plainly: an inspection exists in Reapit as a document attached to an appointment, and a property's images are the ones you would put on a portal. A file called 14 Elm Road check out.pdf is a fine archive and a poor dataset. Nobody opens it again unless there is an argument, and by then the photograph that mattered was taken eleven months ago and nobody compared it to anything.

Does Reapit Go let a manager capture condition on site?

Not as a documented condition capture. Reapit Go is the mobile app, and what Reapit describes it doing is the diary and the deal: full access to the office calendar, creating and editing viewings, submitting viewing feedback without going back to the office, property and contact records with quick notes, a link out to a map, and drafting SMS or WhatsApp messages from templates. Updates and journal entries made in the app sync straight to the desktop CRM, and Reapit's release notes for April 2026 add an AI viewing summary email generator and improved offline support for pages already loaded. That is an app built for the negotiator on the road, and it is good at that. It is not a room-by-room inventory tool, which is why so many Reapit agencies run a separate clerk or a separate inspection app and end up with the condition history living somewhere the CRM cannot see.

That split is exactly the gap the integration closes. RapidEye does not ask you to move the record: Reapit keeps the tenancy, the works order and the certificate, and RapidEye takes the photographs, wherever they are produced, and turns them into dated findings filed against the same property.

Reapit integration FAQ