How it worksAn interactive map of a RapidEye turnover Damage detectionAI compares turnover photos against baseline Video walkthroughsFull-room coverage from a phone walk-through Turnover checkTry it free on one property, no setup PricingSimple pricing that scales with your portfolio DevelopersHosted connectors for every platform in your stack
New Cleaner Verification just shipped Changelog
Vacation rental managersCatch guest damage between back-to-back turns Hotels & resortsRoom-ready verification at housekeeping scale Large portfolios200+ units, one consistent standard Cleaners & field teamsProof the work was done, the first time
One engine, every kind of property View all industries
Content libraryEverything we know about turnover ops BlogGuides, comparisons, and deep dives Open datasetsFree STR-ops data, cited by anyone ToolsCalculators and free utilities ResearchOriginal studies, every figure verified AboutWho we are and the McGinnis story
Free The STR-Ops open dataset corpus Browse all
Your ops stackSync turnover photos from the workflow you already run SlackFlagged turns pushed straight to your channel Chrome extensionOne-click photo upload from any open tab BoomConnect RapidEye to your Boom PMS turnovers
Works with your PMS and ops stack All integrations
Console Cloud
Console Cloud integrationLong-term residentialProperty management system

AI inspections for Console Cloud

Read the area photos your property managers take on routine, entry and exit inspections, and get a finding per area with the entry photo of the same room beside it.

How the inspection workflow works

Overview

A Console Cloud inspection is a beautifully organised container for photos that nobody looks at twice. The property manager works area by area from the app, takes the pictures, dictates the notes, sets the conditions, and submits. The report goes to the owner and the tenant, the inspection is closed, and the images sit in a report that is only opened again if there is an argument. RapidEye reads those photos as a series about one property: it takes the area, the inspection type and the date from Console Cloud, and returns a finding per area with the earlier photo of the same room next to the new one.

Entry against exitThe baseline the tenancy started with, lined up against the report you are writing today.
Every routine, not the memorable onesEach round is read against the last, so slow damage is caught while it is still small.
Console Cloud stays the recordNo inspection, condition, maintenance request or trust account entry is written by RapidEye.

How it works with Console Cloud

The app already breaks a property into areas and holds each area's photos, conditions and comments together. That structure is what RapidEye reads against.

  • Entry inspections. This is the tenancy's baseline, and it is worth more than anyone treats it as. RapidEye keeps every area photo from the entry report as the reference state for the whole tenancy, so a mark found two years later has a dated picture proving it was not there on day one.
  • Routine inspections. Compared against the last routine, area by area: a water stain that has spread across the ceiling, a fresh dent in a door, a lifting floorboard, mould behind a window that has been building for a quarter.
  • Exit inspections. Compared against entry rather than against the previous routine, because that is the comparison a bond claim rests on. Findings come back separated into what changed during the tenancy and what was already noted at entry.
  • The photos behind a maintenance request. When a property manager taps Maintenance during an inspection, the images from that area are the evidence a trade will work from. RapidEye returns what else is visible in the same frame, which is often the reason the first problem happened.
  • Copied inspections. The app lets you start from a previous closed inspection and bring its photos with you. Where a report is built that way, RapidEye flags areas whose imagery has not actually moved on.

Every finding names the property, the area and the spot inside it, the type of issue, how serious it looks, the two photos and their dates, and a suggested next step. It lands in the RapidEye dashboard, and an inbox or Slack channel for the office if you want one. Nothing goes back into Console Cloud unless a person puts it there. If your agency documents differently, 360 imagery, video walkthroughs, a condition report format your state requires, tell us what you capture and we set the reading up around it.

How to connect Console Cloud to RapidEye

  1. A Console Cloud office with inspections scheduled. Inspections live under Workflows, typed as Routine, Entry or Exit and attached to a property and a tenant, and a finding is named the same way.
  2. The photos your property managers already take. They come from the inspection app, area by area from the sections drop-down. Nothing about the round changes. If a property is inspected some other way, RapidEye sends a capture link that opens on any phone with no app to install and a fixed set of angles per area.
  3. RapidEye invited as a user. Users are invited to your office from Settings, with an access level chosen at invite time. The Connect panel has the exact fields.

How the Console Cloud inspection workflow works

Checked against Console Cloud's knowledge base, September 2026.

Console Cloud is property management and trust accounting software for Australian and New Zealand agencies, now sold as Reapit PM, and its inspection app carries both names too: Reapit PM Inspect is the app a lot of teams still call Console Go, and it is included with the subscription. According to Console Cloud's knowledge base documentation (console.com.au), an inspection is created from Properties, Residential, Inspections, or added in bulk from the Workflow screen, and each one is typed as Routine, Entry or Exit, given a date and a start and end time, and attached to a property and a tenant. A routine can be marked recurring with a frequency, and the system schedules the next one at the close of each routine, which is why a well-run tenancy generates the same rooms photographed on the same cadence for years.

  • Start of tenancy

    Entry inspection

    The condition report the whole tenancy is measured against. A workflow setting can carry entry condition and comments through onto the exit report, which is the platform's own acknowledgement that these two documents are one comparison.

  • Every few months

    Routine inspections

    Filtered by type, status, assignee, date range and category on the Inspections workflow. Tenancies with no upcoming routine can be listed and exported, dates rescheduled in bulk, and notices sent to a whole batch of tenants at once.

  • On site

    The app round

    Select the property, Start Inspection, then either copy a previous closed inspection, with or without its photos, or start from scratch. The camera is the landing screen, with a sections drop-down for the areas, voice-to-text notes, conditions and quick notes per area, a Maintenance button that raises a request on the spot, then Mark as Done, a summary, and Complete Inspection.

  • End of tenancy

    Exit inspection

    Exit reports add a Tenant Checklist: notes on items needing the tenant's attention, merged into an email at the end of the round, with a copy saved to the property file under Notes.

  • After

    Close inspection

    Fees can be selected and a reason entered on closing. Once an inspection is closed it cannot be reopened or edited, so whatever the photos showed and nobody noticed is now fixed in the record.

Can you get the photos back out of a Console Cloud inspection?

Only from some of them. The documentation for downloading inspection images describes locating a completed Entry or Exit report in the Inspections workflow, choosing Download Report with images, and following a link inside the report to a zip file of every image, foldered by the area each photo was attached to. It states plainly that images can only be extracted from Entry and Exit inspection reports, and that where a tenant completed an entry inspection through paperless inspections and the tenant app, the entry report also includes a link to the tenant's own images. Reports over 20MB are sent without photos, with the owner pointed at the portal to see the full version.

Two things follow from that. First, the routine photos, the ones that would show damage arriving, are the hardest for a manager to work with in bulk, which is exactly why they go unexamined. Second, the app has started generating descriptive quick notes from images itself, in beta, on the first five images in each section, which tells you where the platform thinks value sits and how far along that path it currently is. A note describing a photo is not the same as a comparison against the same room last quarter, and the comparison is the part RapidEye supplies.

Console Cloud integration FAQ

Does RapidEye integrate with Console Cloud?

Yes. RapidEye reads the area photos captured in your routine, entry and exit inspections, along with the property, the inspection type, the area name and the date, and returns a finding per area with the earlier photo of the same room beside the new one. The inspection, its conditions, its comments, the maintenance requests it raised and everything in trust accounting stay as they are.

Does the Console Cloud inspection app take photos?

Yes, and the camera is the first screen. Reapit PM Inspect, the app many teams still call Console Go, opens on the camera with a sections drop-down for the areas of the property, and the documentation describes taking photos, adding voice-to-text notes, selecting the conditions for the area, and tapping Maintenance to raise a request without going back to the office.

Can RapidEye compare an exit inspection against the entry condition report?

That is the main job. The entry report is the tenancy's baseline and the exit report is the claim, and the two are usually months or years apart. RapidEye lines up the same area across both and returns what changed, with the two photos and the dates, which is the shape a deduction argument has to take.

Will RapidEye change or reopen an inspection in Console Cloud?

No. Once an inspection is closed it cannot be reopened or edited, and RapidEye respects that. Findings live in the RapidEye dashboard beside the inspection they came from, and your property manager decides whether anything is raised in Console Cloud as a result.

What about routine inspections, where nothing is being claimed?

Routines are where the drift shows up first. A tenancy schedules a new routine at the close of the last one, so the same rooms are photographed on a cadence, and RapidEye reads each round against the one before it: the leak stain that is bigger, the wall mark that arrived this quarter, the smoke alarm that has come off the ceiling.

Can RapidEye read the inspection history we already have?

Yes. On connection RapidEye reads the inspection photos your agency already holds and builds a baseline per property from them, so the first new inspection has something to be compared against instead of starting the record from zero.

Other systems RapidEye reads inspections from

Platforms holding the same routine, entry and exit reports, mostly for the same agencies.

PropertyMeEntry, exit and routine photos from the manager app, including 360 imagery Inspection ExpressAustralian condition reports read area by area SnapInspectMobile inspection photos across residential and commercial portfolios Re-LeasedCommercial property condition tracked between inspections zInspectorRental inspection photos read alongside the PMS they sync to All long-term residential integrations

Sources

  • Console Cloud knowledge base, inspection creation and management, app inspection and user invitation documentationconsole.com.au
  • Console Cloud product pages, inspection app and maintenance workflowconsole.com.au

Sources are named at the publisher level and were checked against the publisher's live pages before this page was published.