AI inspections for Palace

Overview

A Palace inspection is a very good container for evidence; judging that evidence was never its job. The app walks a property manager through rooms and features from the master template, records a status and a comment against each one, holds up to a thousand photos per inspection, and uploads the lot into the property diary for a report the owner receives. Every status in it is a human opinion typed on site. RapidEye reads the property and tenancy details from Palace and the photographs your app uploads, then returns a finding wherever the image and the status do not agree, or wherever this inspection differs from the last one of the same property.

How it works with Palace

Palace already sorts inspections by the reason you are standing in the property, so the checks follow that. These are examples rather than limits: RapidEye reads whatever a team already produces, photos, walkthrough video, 3D scans, and reports against whatever standard you hold properties to, so if your situation is not listed here, assume it can be done and ask us.

• Full inspections on an empty property. Ingoing, outgoing, condition and status reports all use this type. The ingoing set becomes the baseline for the tenancy; the outgoing set comes back annotated with what changed since, each difference carrying both images and the tenancy dates in between.
• Routine inspections during a tenancy. Quarterly rounds produce hundreds of photos nobody looks at twice. RapidEye compares this quarter against last quarter on the same feature and flags the slow ones: a stain spreading, a seal failing, a wall mark that was smaller in April.
• Feature statuses. A feature marked clean and undamaged whose photograph shows otherwise is the single most useful thing to catch, because the report has already been generated and sent by the time anyone notices.
• Comments and summaries. Where a summary says a repair was made, RapidEye reads the photograph attached to that feature and says whether the repair is visible in it.
• Video inspections. Palace supports video in the app. A walkthrough sees ceilings, corners and behind doors that a fixed photo list never reaches, and RapidEye reads it the same way it reads stills.
• Maintenance raised on site. Palace's own product pages describe lodging maintenance requests from the inspection app while at the property. A RapidEye finding gives the person deciding whether to raise one something specific to point at.

Each finding names the property, the room, the feature, the object, what kind of problem it is, how serious it looks, the images it rests on, and a suggested next step. It lands in the RapidEye dashboard and, if you want, your inbox. Nothing is written back into Palace: whether a status changes, a work order is raised, or a bond deduction is claimed is a decision a person makes in Palace. If your team inspects in a format of its own, or the input is video rather than stills, tell us and we set that up with you.

How to connect Palace to RapidEye

1. Your Palace database and master inspection template. Findings attach to the rooms and features your administrator configured, so the template you already use is the structure RapidEye reports against.
2. Inspections uploading from the app as usual. Start a Full or Routine inspection, photograph each room, submit. The queue uploads when there is a connection, and RapidEye reads what arrives. Where a property is inspected without the app, a capture link opens on any phone with no app to install.
3. A RapidEye user in your database. Users, then Add a user, then activate the login from Current users. The modal above has the details.

How a Palace inspection is built

Checked against Palace's knowledge base, September 2026.

Palace, now MRI Palace, is a property management system built for New Zealand letting agencies, and its inspection app is where condition evidence is created. According to Palace's own knowledge base documentation (mrisoftware.com), an inspection is a nested structure rather than a form: the master template in your database supplies the rooms, each room supplies its features, each feature takes a status, and photographs hang off the room. Understanding that nesting is what tells you where the gaps are.

1. Inspection Full or RoutineStarted against a property address from Inspections or Contacts, then submitted. It sits in Drafts until it is submitted and in the upload Queue until there is a connection.
   1. RoomComes from the master template your administrator set up. On site a manager can add a room, duplicate an existing one, rename it, or delete it, then reset back to the master template afterwards.
      1. FeatureThe items within the room. Features can be added or renamed at the property, so the template bends to the house rather than the other way round.
         1. Status and summaryChosen from a status list, tapped by the person holding the phone. The list itself is edited back in Palace on the status tab of the master template. A summary can be added beside a feature.
      2. Photos, up to 1,000 per inspectionTaken in the app per room and named by the Palace naming sequence, or imported from the device library when they were taken outside the app. Nothing in the inspection reads them.

Once uploaded, the inspection lands in the property diary. From Property, Current properties, the address and then Diary, a manager opens the inspection and clicks Report, toggles which items appear, and either generates a web report that opens in a browser tab or prints a PDF. The email to the owner goes from the same screen, with the digital report attached as a link, and it is saved back into the property diary. Palace notes that the report displays the tenancy commencement date, falling back to the tenancy start date when there is none, which is exactly the dating a bond claim depends on.

Two inspection types, two jobs

Does the Palace app check the photos it collects?

It does not, and nothing in the documentation claims it does. The app's settings are about capture and delivery rather than judgement: a tenant signature that lands as the last image in the report, saving photos to the camera roll as a backup, a highest-resolution toggle for video, upload on Wi-Fi only, a fourteen-day list of what has been uploaded. Those are good decisions by people who understand field work in a country with patchy rural coverage. They are also the whole of it. The status against a feature is true because somebody said it was true, and by the time the report has been generated and emailed to the owner, that opinion has become the record.

So the evidence exists and is well organised, which is more than most systems manage, and it is never read a second time. That is the work RapidEye does: your team keeps using the app exactly as it does today, and what comes back is a second opinion on every photograph before the report goes out.

Palace integration FAQ