Tenant work orders
Raised from the tenant portal or by the property team, then dispatched, accepted and actioned.
Photos and notes attachedAfter it closes: the tenant sees a resolved request, and the images stay in the work order history.
Read every photo your engineers attach to Tenant, Equipment and Inspection work orders in MRI Angus, and get back the condition nobody had time to look at.
Where photos live in MRI AngusA closed work order in MRI Angus proves that work happened, not what the building looks like. MRI Angus carries the tenant service request, the preventive maintenance schedule, the equipment record and the inspection, and its mobile app puts photos and notes on all three kinds of work order. Those photos are filed against the property, the floor, the tenant and the asset, and then almost nobody opens them again. RapidEye reads them, compares each space and asset against how it looked last time, and returns one finding per issue with the images behind it.
MRI Angus separates work into Tenant, Equipment and Inspection work orders, and the checks follow that split, because each type produces a different kind of photograph.
Each finding names the property, the space or asset, the kind of issue, how serious it is, the photos with their dates, and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for the property management office if you want it there. Your team decides whether it becomes a work order in MRI Angus. If your engineers shoot video walkthroughs, run drone roof passes or 3D scans, or work to an inspection format of your own, that is something we set up with you rather than a reason this does not fit.
Checked against MRI Software's product, training and app documentation, September 2026.
MRI Angus is the commercial building operations product MRI Software acquired with Angus Systems, and its users still describe the work in Angus nouns: tenant service requests, preventive maintenance, inspections. According to MRI Software's own product and app documentation (mrisoftware.com), tenants send requests through a mobile-friendly, branded service portal, maintenance schedules and asset history are held alongside them, and its published training catalogue lists separate courses for Tenant Service Request, Preventive Maintenance and Inspections usage, plus one on the One Work Order list that puts all of it in a single place.
Raised from the tenant portal or by the property team, then dispatched, accepted and actioned.
Photos and notes attachedAfter it closes: the tenant sees a resolved request, and the images stay in the work order history.
Opened against an asset record, which the app can pull up by scanning the asset code.
Photos and up to two videosAfter it closes: the asset gains a maintenance record, and a set of images no report reads.
Built from inspection templates and schedules, then completed task line by task line in the field.
Up to 20 images per task lineAfter it closes: the template is complete and passed, which is a different claim from the building being fine.
All three types appear together in the One Work Order list, filterable by work type, and the mobile app works offline and syncs when the engineer is back in signal, which is how a photo taken in a sub-basement still reaches the record.
Yes, on all three types. MRI Software's app documentation describes attaching photos and notes to work orders for documentation, uploading up to two videos when creating or viewing Tenant, Equipment and Inspection work orders, and an increase in the photo upload limit for inspection task lines from 5 to 20 images. Read together, that is a company investing steadily in getting more visual evidence off the engineer's phone and onto the record, which is the hard half of the problem and the half MRI Angus solves.
What none of that documentation describes, because it is not what a work order system is for, is anything that opens the images afterwards. The photo's job ends when it is attached. Picture a portfolio of forty buildings over a quarter: however many work orders that comes to, each one carries evidence a person would have to click into individually, and no manager has that quarter to spend. So the condition information is captured, indexed by property and asset, and never read. That is the gap this integration fills, and it exists in the workflow rather than in the software.
Yes. RapidEye reads the photos your team attaches to Tenant, Equipment and Inspection work orders in MRI Angus, along with the property, floor, tenant and asset those work orders point at, and returns a finding per issue with the photos behind it. Work orders, schedules, inspection templates and tenant records in MRI Angus are not changed.
Yes, on all three work order types. MRI Software's app documentation describes attaching photos and notes to work orders for documentation, uploading up to two videos when creating or viewing Tenant, Equipment and Inspection work orders, and a photo upload limit of 20 images on an inspection task line. What no documentation describes is anything that looks at those images afterwards.
In most buildings, nobody. The engineer photographs the task line, closes the work order, and the images sit in history until a dispute or an audit sends someone looking. RapidEye reads all of them and returns only the ones that contain something worth a manager's time.
No. MRI Angus stays the system of record for every work order, preventive maintenance schedule, inspection template and tenant service request. RapidEye reads the photos and reports back; your property team decides whether a finding becomes a new work order.
Yes, portfolio breadth is exactly the situation it serves. One engineer sees one building; a regional manager sees a One Work Order list across many. RapidEye reads every property on the same standard, so a floor in one tower and a loading dock in another are scored the same way and rank against each other.
Platforms that hold work orders and asset history for portfolios of buildings, the way MRI Angus does.
Building Engines PrismPrism keeps status updates, comments and photos on the work order; RapidEye reads the photos
Yardi Facility ManagerInspections and scheduled maintenance in Voyager, checked against the images
CorrigoVendor-coordinated work orders at scale, read for what the vendor actually left behind
ServiceChannelMulti-site maintenance activity from one platform, with every site held to one standard
FMXMaintenance requests and scheduling, plus a read of the condition behind them
All facilities integrations
Sources are named at the publisher level and were checked against the publisher's live pages before this page was published.
Integration setup
We accept the invite and email you when your first findings are ready.
Rather have Sam do it with you? Book a call.