AI inspections for Innago
Read the photos on every Innago damage report and maintenance ticket, and get the move-in and move-out condition of a unit compared item by item before you sign.
Inside the Innago damage reportOverview
Innago's damage report collects the condition of a unit as words, and the photograph is optional. The tenant enters a location, an item, a condition from a dropdown and a description, may attach an image, then signs; you review, approve and sign, and a PDF lands under Leases and Files. Everything about that flow is sound except the part that decides a deposit dispute, which is whether anyone compared the move-in report to the move-out one and looked at the pictures. RapidEye reads the property, unit and lease term from Innago along with the images on your damage reports and maintenance tickets, and returns a finding per item with the earlier and later photo attached.
How it works with Innago
Innago already puts the condition of a unit into two places, the damage report and the maintenance module, and both of them can hold images. The integration reads both.
- The move-in damage report. Initiated during lease setup or from the lease detail, filled in by the tenant, signed by both sides. RapidEye reads every image on it and builds the unit's baseline from what the pictures show rather than what the condition dropdown says.
- The move-out damage report. The same locations, months later. Findings come back as differences: the burn on the counter that was not there in May, the missing closet door, the wall the report called Good with a photo that disagrees.
- Locations nobody entered. The tenant chooses which locations to add, so a report can be signed with the second bathroom absent from it entirely. RapidEye tells you which rooms of a unit have no visual evidence at all, while you can still ask for it.
- Maintenance tickets in between. A tenant ticket carries a category, a description and uploaded images, and you can add photos while managing the ticket. Each one is a dated look inside the unit during the tenancy, which is the stretch neither damage report covers.
- Resolved tickets. A ticket is closed by marking it resolved, with an internal note the tenant never sees, and Innago keeps tenant-created tickets on the record permanently. RapidEye compares the photos on that ticket against the room's earlier state, so a repair that was closed but not finished still surfaces.
Each finding names the property, unit and room, the item, the kind of problem, how serious it is, the two photos, and a suggested next step, and it lands in the RapidEye dashboard or an inbox if you want it there. Whether you reject the report, deduct from the deposit or let it go is your decision and Innago is where you make it. If your documentation is not photos, say a video walkthrough at move-out or your own inspection format, tell us what you capture and we set the checks up around it.
How to connect Innago to RapidEye
- The units and leases. An Innago account with the properties and units added and the lease terms in place, because the lease term is what a damage report hangs on and what gives a finding its dates.
- The photos. RapidEye reads the images already attached to your damage reports and maintenance tickets. For rooms nobody photographed, it sends a capture link that opens on any phone with no app to install, a fixed set of angles per room, and reads a video walkthrough just as well.
- The invite. In Innago, turn on Multiple User Setup under Settings, then open Users, choose Add New User, and add RapidEye with the Maintenance Staff role and the properties you want covered. The connect panel on this page carries the exact details.
Inside an Innago damage report, item by item
Checked against Innago's help centre, September 2026.
Innago calls it a Damage Report and also a move-in and move-out checklist, and it is a signing flow rather than an inspection app. According to Innago's help centre documentation (innago.com), you initiate one by ticking Include Damage Report on the Finalize Lease step of a new lease term, or from the action menu on the Lease Detail page of an existing one; the tenant gets a notification, completes it, and signs; you review it from the Lease Detail page and cancel, reject or approve and sign; the finished PDF is filed under Leases and Files. From the Lease Detail page you can also open View Status to see whether tenants have viewed or signed, remind everyone, or cancel the report. The unit's whole condition record, then, is whatever the tenant typed into one repeating item block.
One item in a damage report, as the tenant fills it
Typed by the tenant. Add Location starts another one; nothing requires the list to cover the unit.
An option, not a requirement. This is the only field on the form that can be checked by anyone later.
What RapidEye does with it
- LocationMatched to the room in the unit's own history, so the same window has one thread across tenancies.
- Item and conditionKept as the tenant's claim, and reported next to what the image shows.
- PhotoRead against the baseline: damage, wear, a missing item, a cleaning failure, with a severity.
- Missing roomsFlagged as gaps before you sign, not after the tenant has moved out.
Fields and their order as documented by Innago's help centre. The panel on the right is what the integration adds.
Can an Innago damage report prove what the tenant damaged?
Only if someone compares two of them, and Innago does not do the comparing. The documented flow is deliberate about consent and signatures: the tenant acknowledges a legal disclaimer before completing the form, you can reject and have them resubmit as many times as needed, and once one tenant and the landlord have signed, Innago says the document is binding for the unit regardless of how many tenants live there. All of that is about agreement. None of it is about evidence. The condition dropdown is a word the departing tenant chose, the photo beside it was optional, and the two PDFs that would settle the argument sit in Leases and Files as separate documents with no relationship between them. RapidEye is the part that opens both, lines them up by location, looks at every image, and hands you a list of what changed, so the deduction you take into a deposit conversation has two dated pictures behind it instead of two adjectives.
Innago integration FAQ
Does RapidEye integrate with Innago?
Yes. RapidEye reads the property, unit and lease term from Innago along with the photos on your damage reports and maintenance tickets, and returns a finding per item: what it is, where it is, how bad, and the earlier and later photo behind it. The damage report, the signed PDF under Leases and Files, and every maintenance ticket stay exactly as they are.
Are photos required in an Innago damage report?
No. Innago's help centre describes the tenant entering a location, an item, a condition from a dropdown and an optional description, with an option to upload a photo. The condition is the field that gets filled in every time and the photo is the field that does not, which means a signed report can say Fair for a whole kitchen with nothing behind the word. RapidEye reads whatever photos are there and tells you which rooms have no visual evidence at all.
Can RapidEye compare a move-in damage report against a move-out one?
That is the main thing it does on Innago. A damage report can be initiated for an upcoming or an active lease term, so most landlords end up with one at each end of a tenancy sitting as two separate PDFs. RapidEye lines up the two by unit and location and returns the differences as findings, each one carrying the move-in image and the move-out image and the dates on both.
Does RapidEye read Innago maintenance tickets too?
Yes. A tenant-submitted ticket carries a category, a description and uploaded images, and you can add more photos to the ticket while managing it. Every one of those is a dated look inside the unit between move-in and move-out, which is exactly the stretch a damage report cannot cover.
Will RapidEye change anything in my Innago account?
No. RapidEye does not approve, reject, sign or cancel a damage report, does not resolve or reopen a ticket, and does not message a tenant. Innago stays the system of record and the signed document stays the signed document. RapidEye reads and reports.
My tenant filled the damage report in themselves. Why would I trust it?
You should not have to. The tenant chooses the locations, the wording and whether to attach a photo, and at move-out they are the party with the most to gain from a thin report. RapidEye reads the images rather than the words, so a scuffed floor the report called Good and a location nobody entered at all both surface as findings before you sign.
Other residential platforms RapidEye reads
Systems that, like Innago, keep the leases and the units while unit condition arrives as an attachment.
HemlaneMaintenance request photos turned into a condition record
TurboTenantMove-in and move-out evidence for a self-managing landlord
TenantCloudTenant portal photos read room by room
AvailCondition checked across a tenancy, not just at the ends
BuildiumEvery inspection photo reviewed rather than sampled
All long-term residential integrations
Sources
- Innago help centre, damage report, maintenance and sub-user documentationinnago.com
- Innago product announcements, damage report and maintenance module releasesinnago.com
Sources are named at the publisher level and were checked against the publisher's live pages before this page was published.

