ManageCasa
ManageCasa integrationLong-term residentialProperty management system

AI inspections for ManageCasa

Read the photos attached to your ManageCasa tickets and get back a dated condition record per unit, so a move-out deduction rests on two images rather than on somebody's memory.

What a ManageCasa ticket holds

Overview

In ManageCasa a photo is an attachment on a ticket, not a record of condition. The maintenance module stores images, videos and files against a ticket that names the property, the unit, the category, the requester and the assignee, and violations and architectural review requests hold photos the same way. What no ticket does is compare one photo to the last one taken in that room, which is the comparison a security deposit turns on. RapidEye reads your unit list and lease dates from ManageCasa along with the photos on those tickets, keeps a baseline per unit, and returns a finding for what changed and when.

Move-in to move-outThe baseline photo of a unit and the photo taken the day the keys came back, with the lease dates between them.
Every ticket photo readNot the ones somebody had time to open. Maintenance, violations and architectural reviews all carry images, all get read.
ManageCasa stays the ledgerNo ticket is created, edited, archived or closed. RapidEye reads and reports, you decide what happens next.

How it works with ManageCasa

ManageCasa organises the work as tickets, so the checks follow the ticket. Each of these is an example rather than a boundary: RapidEye reads whatever documentation your team already produces, photos, video walkthroughs, 3D scans, and returns findings against the standard you care about, so if your situation is not on this list, assume it can be done and ask.

  • The move-in ticket. The photos your leasing team takes on the day a resident collects keys become the baseline for that unit: the carpet, the benchtop, the wall behind the door, the state of the blinds. Nothing is flagged yet. This is the record everything later is measured against.
  • The move-out ticket. Same unit, new photos, and RapidEye returns the differences: a burn ring on the vanity, a hole patched badly, a screen door that used to be there. Each difference carries both images and the lease dates from ManageCasa, which is what turns a deduction into an argument you can send to a resident.
  • Vendor work orders. A ticket is assigned, marked complete, and an invoice follows. RapidEye reads the photo attached at the close and says whether the finished work is visible in it, or whether the same damage is still in the frame.
  • Resident-filed requests. A request comes in from the mobile app with one photo of a leaking sink. RapidEye reads it against the last photo of that room and tells you whether this is new damage or a condition that has been sitting there since the previous tenancy.
  • Recurring tickets. ManageCasa's documentation gives regular inspections and routine cleanings as examples of a recurring ticket. Where a team runs a periodic walkthrough that way, each round becomes another dated layer on the unit's history rather than another folder of images.
  • Violations and architectural reviews. An unauthorised exterior change or a common-area complaint arrives with a photo attached. RapidEye compares that elevation against how it looked the last time it was photographed, so the file shows the change and not just the complaint.

A finding names the property and unit, the room, the object, what kind of problem it is, how serious it looks, the two photos it rests on and a suggested next step. It lands in the RapidEye dashboard and, if you want it there, your inbox. Nothing crosses back into ManageCasa: whether a finding becomes a new ticket, a deposit deduction, or nothing at all is your call. If your walkthrough is a video rather than a set of stills, or you have an inspection format of your own that a resident signs, tell us and we set it up that way.

How to connect ManageCasa to RapidEye

  1. Your properties and units in ManageCasa. Findings are keyed to the unit, the same identifier your tickets use, so anything not under management stays out of it.
  2. Somewhere for the photos to come from. If your team already attaches images to tickets, RapidEye reads those. For units where nobody photographs anything today, RapidEye sends a capture link that opens on any phone with no app to install, and the walkthrough is a fixed set of angles per room, lights on.
  3. A RapidEye user in your account. Settings, then Account Users, then Add. The modal above has the name, the email and the role to pick.

What a ManageCasa maintenance ticket actually holds

Checked against ManageCasa's help centre, September 2026.

ManageCasa is a property management platform for community associations and rental portfolios, and the Maintenance section in the left-hand menu is where field work lives. According to ManageCasa's help centre documentation (managecasa.com), a new ticket is built in five steps, and it is worth seeing them laid out because the shape of the form is exactly the shape of what you can and cannot ask of it later.

Add Ticket, the five steps ManageCasa documents
Step 1General information
Property affectedTask titleTask categoryRequesterTask status

All required. ManageCasa's own tip is that the maintenance report carries the unit number but not the property address, so it suggests putting the street address in the task title.

Step 2Photos, videos and files
ImagesVideoDescriptionAttachments

Drag and drop from your computer or pick from files already in ManageCasa. The documented formats run from jpeg and png through mp4 and mov to pdf and csv, up to 150MB per file. This is the only place condition evidence enters the system.

Step 3Priority and access
Priority levelRequested byAssigned toTask type

Task type follows your own internal classifications, which is how most teams end up with a category that means inspection without there being an inspection object.

Step 4Recurring, optional
Start dateFrequencyEnd condition

A toggle with a start date, a frequency and an end condition of a date, a number of occurrences, or until cancelled. ManageCasa's examples for it are regular inspections and routine cleanings.

Step 5Share
Share with others

Visibility is deliberate. For violations, the documentation is explicit that the resident does not see the ticket unless the person who created it shares it with them.

Once created, a ticket lives in a table or a Kanban board where status moves by dragging the card between columns, by the Change Status option on the three-dot menu, or in bulk with checkboxes. Tickets that are no longer relevant get archived rather than deleted and stay reachable in the Archive tab. There is a Recurring tab for the repeating ones. The Minii AI assistant can create, update and bulk-edit tickets by conversation, including a documented example of raising tickets across a range of units for an annual filter replacement and thermostat inspection.

Three ticket types, one shape

The help centre says the same steps create violations and architectural review requests, and that their views behave the same way. For an operator running both rentals and associations, that is useful: the evidence you gather is one kind of object no matter which side of the business it came from.

MaintenanceProperty, unit, category, assignee, and the photos of the fault and of the repair.
ViolationsA predefined category, a description, photos, and a resident who sees it only once the ticket is shared.
Architectural reviewsA requested change to a property, documented with images, tracked to an approval.

Does ManageCasa have an inspection module?

Not a separate one, on the evidence of its own documentation. The help centre's category for field work is titled maintenance, architecture reviews and violations, and the articles inside it describe tickets: how to create one, how to attach files and photos, how to change status, how to make one recurring, how to communicate about it. None of them describes an inspection object with rooms, a condition rating per item, a comparison against a previous visit, or a resident signature. The product pages describe maintenance requests and work orders with photo and document attachments, which is the same object seen from the outside.

So a ManageCasa unit accumulates photographs without accumulating a condition history. Somebody has to open the tickets in date order and remember what the carpet looked like in March. That is the work RapidEye takes: the photos stay where your team already puts them, and what comes back is the comparison nobody had time to make.

ManageCasa integration FAQ

Does RapidEye integrate with ManageCasa?

Yes. RapidEye reads your property and unit list and your lease dates from ManageCasa, along with the photos attached to maintenance tickets, violations and architectural review requests, and returns a condition finding per unit: damage, wear, a missing fixture, or work that was billed but is not visible in the photo. The ticket, its status and its attachments in ManageCasa are left exactly as they are.

Does ManageCasa have a move-in or move-out inspection module?

Not a separate one in its help centre documentation. Photos in ManageCasa live on tickets: maintenance, violations and architectural review requests, which its documentation says all behave the same way. Most teams run the move-in and move-out walkthrough as a ticket, or on paper outside the system. RapidEye reads whichever of those you use and produces the dated condition record the ticket itself does not.

Can RapidEye compare a move-out photo against the move-in photo of the same unit?

That is the main thing it does for a long-term rental. RapidEye holds a baseline per unit from the photos taken at move-in, and when the move-out photos arrive it returns what changed between the two dates, with both images side by side and the lease dates from ManageCasa in between. A deduction argued that way is an argument about a photograph rather than about memory.

Will RapidEye create or close tickets in ManageCasa?

No. ManageCasa stays the system of record for tickets, statuses, ledgers and leases. RapidEye reads and reports, and you decide whether a finding becomes a new ticket, a deposit deduction, or nothing at all.

Our maintenance photos come from vendors and residents rather than staff. Does that still work?

Yes, and that is the usual case. A resident files a request from the mobile app and attaches a photo, a vendor sends back a photo of the finished work. RapidEye reads both and tells you whether the after photo shows the repair that was billed. Where a unit has no photos at all, a RapidEye capture link opens on any phone with no app to install.

Does this work for an HOA portfolio rather than rentals?

Yes. Violation tickets and architectural review requests carry photos the same way maintenance tickets do, so RapidEye can read the photo attached to an unauthorised exterior change or a common-area complaint and compare it against how that elevation looked before. The finding names the property and the unit number.

Other residential platforms RapidEye reads

Systems that hold units, leases and maintenance in one place, the way ManageCasa does.

Sources

  • ManageCasa help centre, maintenance ticket, violation and account user documentationmanagecasa.com
  • ManageCasa product pages, rental and association property management softwaremanagecasa.com

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