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
MPulse
MPulse integrationFacilities and commercial real estateMaintenance management system

AI condition inspections for MPulse

RapidEye reads the photos your technicians attach when they close an MPACT work order, and returns a finding for each problem in them, filed against the asset and location the work order already names.

How photos reach an MPACT record

Overview

MPACT documents the work completely, and a complete record of the work is still not a record of the condition. The closed work order tells you which technician worked which tasks, which parts came off the shelf, how long it took, and what failure code was chosen. The photos beside all of that hold something none of the fields do: what the space and the machine actually looked like when the technician walked away. RapidEye reads those photos and returns a finding for each problem in them, against the asset MPACT already filed the job to.

The closeout photo, readEvery photo attached at the machine gets opened, not the handful someone pulls up when a complaint arrives.
Condition by buildingMPACT already places every asset in a location hierarchy, so findings arrive sorted by site, by room and by asset type.
MPACT stays the recordNo work order, task, asset, part or schedule is written to. RapidEye reads and reports back.

How it works with MPulse

MPACT organises work by where it came from, so the checks follow the same routes. Treat these as examples rather than boundaries: RapidEye reads whatever a team already produces, photos, video walkthroughs or 3D scans, and reports against whichever standard your operation holds its buildings to.

  • Requests from a QR scan. Anyone can scan the tag on an asset and file a request against the right record with no login, usually with a photo of what they saw. RapidEye reads that photo, sizes the problem, and tells you whether the same asset was reported for the same thing two quarters ago.
  • Scheduled preventive work orders. A PM comes back to the same asset on a calendar or a meter reading, so the same equipment is photographed from roughly the same spot over and over. Corrosion, seepage and worn belting are visible in that sequence long before a failure code is.
  • Checklists and required fields at closeout. Where a required field asks for a photo, RapidEye reads the photo against the step it was attached to, and says whether it supports what the technician recorded.
  • Multi-asset work orders. One job spanning several assets stays one record in MPACT, with history landing on each asset it touched. Findings split the same way, so a single walk of a mechanical room becomes separate findings per unit.
  • Buildings and rooms as assets. MPulse counts buildings and rooms as maintainable assets alongside equipment and vehicles. That means cleaning standards, damage and missing fixtures are checked with exactly the same machinery as a pump.

Every finding names the asset, the location, the kind of problem, how serious it is, the photos behind it and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for the maintenance office if that suits your team better. Nothing is written back into MPACT, so whether a finding becomes a new work order is your call. If your inputs are not photos, or you inspect against a standard of your own, we set that up with you rather than asking you to fit the default.

How to connect MPulse to RapidEye

  1. An MPACT system with your assets and locations in it. Equipment, vehicles, buildings and rooms all count as assets, and MPulse puts no cap on how many records or locations you keep. The hierarchy you already use is what findings get filed against.
  2. The photos your technicians take at closeout. Nothing new to learn: they keep logging hours, readings and photos as they close the job, in the adaptive web app or the offline technician app. If a crew does not photograph its work yet, RapidEye sends a capture link that opens on any phone, with no app to install.
  3. A user for RapidEye. Your MPACT administrator creates one the way they create any teammate, with access to the work orders and assets you want read. The modal has the details to hand them.

How a photo reaches an MPACT record

Checked against MPulse's product documentation, September 2026.

MPACT is the cloud CMMS from MPulse Software, and its work order is the operating record of the whole maintenance function: the asset, the technician, the tasks, the parts and the costs on one record, connected to preventive schedules, requests and inventory. According to MPulse's product documentation (mpulsesoftware.com), a technician opens the day's queue with priorities in colour, works the job with its checklist and the asset's history one tap away, and closes it with hours, readings and photos attached, standing at the machine rather than back at a terminal. There are two ways that photo travels, and which one a site uses decides when the picture becomes readable.

Path one The adaptive web app A browser on any device, part of every MPACT edition, with grid, form and card views that reshape to the screen in hand.
  • InstallsNothing. It is the browser the technician already has.
  • Where it runsDesktop for triage, phone for completion, tablet for scanning a queue.
  • The photoLands on the work order as it is taken.
Path two The offline technician app An add-on for work beyond the signal: basements, remote sites and dead zones, on iOS and Android.
  • InstallsYes, from the App Store or Google Play.
  • Where it runsFully disconnected, with the whole job completable offline.
  • The photoHeld on the device, then synced when it reconnects.

Both paths end in the same place: the work order, and through it the asset's permanent history.

What do required fields actually enforce?

That the field is filled, which is more than most systems manage. MPulse's own framing is that required fields make closeout documentation a condition of finishing rather than a favour, and it is why MPACT records tend to be unusually complete: checklists define the steps, failure, reason and repair codes structure what went wrong, and time, parts and downtime post to the work order and roll up to the asset. What a required field cannot do is look at the picture attached to it. A photo satisfies the requirement by existing, whether it shows a finished job, a half-finished one, or the floor. Nobody has built the system that could check that by hand across a portfolio, which is the whole reason this integration exists.

Where else do photos live in MPACT?

On the asset. MPulse says manuals, warranties, drawings and photos attach directly to the asset record, so the paperwork sits one click from the equipment it describes, and the record accumulates across every job. Meters, criticality and downtime live there too, and the Asset Status Board turns that history into lifetime cost, MTTF and MTTR. RapidEye reads the photo half of that record as a series rather than as a folder: what this asset looked like in March, in June, and today, which is the comparison a status board cannot make out of numbers.

MPulse integration FAQ

Does RapidEye integrate with MPulse?

Yes. RapidEye reads the photos your technicians attach to MPACT work orders and asset records, together with the asset, the location and the time, and returns a finding for each problem it sees: damage, wear, a step that was not really done, a hazard beside the repair. Nothing in MPACT is edited: work orders, tasks, assets, parts and schedules stay as your team left them.

Does MPACT hold photos on work orders?

Yes, in two places. MPulse says field photos land on the work order, and that manuals, diagrams, warranty documents and photos attach directly to the asset record. A technician closing a job logs hours, readings and photos on the record itself, so the picture arrives already tied to the asset it was taken of.

What happens to photos captured with no signal?

They sync when the device reconnects. MPulse describes an offline technician mobile app, an add-on on iOS and Android, in which work orders, readings and photos are captured fully disconnected and synced on reconnection. RapidEye reads those photos when they arrive, so a basement or a remote site is checked the same way as the shop.

Do required fields not already guarantee closeout quality?

They guarantee the fields are filled. MPulse's own framing is that required fields make closeout documentation a condition of finishing rather than a favour, which is the right design, and it is why MPACT records are unusually complete. What a required field cannot check is whether the photo attached to it shows a finished job. That is the part RapidEye reads.

Can RapidEye look at the photo history already in MPACT?

Yes, and it is the fastest way to see value. On first connection RapidEye reads the photos already sitting on your closed work orders and asset records and builds a baseline for each asset and space, so early findings include slow drift: rust that has been advancing for a year, a missing guard that nobody logged.

We run several buildings on one MPACT system. Does that work?

It is the reason to bother. MPulse says asset hierarchies and location structures span sites with location-based permissions, so every photo already carries the building and the asset it belongs to. Findings roll up the same way, and a facilities director sees which site is drifting rather than which site files the most work orders.

Other CMMS platforms RapidEye reads

Systems where the work order is the record and the field photo rides along with it.

LimbleWork orders assigned and completed from anywhere, their photos read for condition eMaintMulti-site records read to one standard across every facility UpKeepMobile work orders with photos and checklists, checked against the asset Q Ware CMMSChecklists and task verifications on school and municipal work orders Maintenance ConnectionMobile workflows and asset history read for what the numbers miss All facilities integrations

Sources

  • MPulse product pages, MPACT work order, mobile, asset and preventive maintenance documentationmpulsesoftware.com
  • MPulse learning centre, CMMS licensing and maintenance terminologympulsesoftware.com

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