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
Arthur Online
Arthur Online integrationLong-term residentialProperty management system

AI inspections for Arthur Online

RapidEye reads the images sitting on your Arthur tasks, subtasks and work orders, and returns a finding for every problem in them, tied to the unit and the tenancy.

How an Arthur task carries photos

Overview

An Arthur task is a wrapper for the job, not a judgement on the property. Arthur describes a task as the thing that holds everything needed to complete the job at hand, with subtasks as the checklist inside it and a work order as the worksheet handed to a contractor. Images ride along at every one of those levels, and once the work order is signed off nobody opens them again. RapidEye reads those images, alongside the property, unit or tenancy each one belongs to, and returns a finding for every problem visible in them, whether or not it is the problem the task was raised for.

Read at every levelTask images, subtask images from the companion app, and work order images all land in the same read.
The whole frame, not the complaintThe tenant photographed a leaking trap. The same shot holds a swollen carcass and a stained ceiling below.
Arthur keeps the recordNo task, subtask, work order, sign-off or tenancy is written to. RapidEye reads and reports.

How it works with Arthur Online

Arthur already routes four kinds of people through one record, and each of them leaves a different kind of image behind. The checks follow that split.

  • Issues raised in the Occupant App. Arthur has the tenant pick an issue type, write a description and attach images before the issue reaches you. That photo is usually the earliest picture of the problem and the only one taken before anyone touched it. RapidEye reads it whole: the damp patch the tenant named, and the blown seal, the missing detector and the mould line behind it that they did not.
  • Inspection tasks on the companion app. Arthur's recipe for inspections is a task type called Inspection with a subtask list behind it, images added as you go. RapidEye reads the images against the subtask they were added under, so a subtask that says the boiler cupboard was checked is either supported by its picture or contradicted by it.
  • Work orders and sign-off. A completed job waits in Awaiting Sign-off until you set it to Completed. RapidEye reads the contractor's images before you do that, so the sign-off is a decision about the work rather than a formality about the paperwork.
  • Voids between tenancies. The unit is empty, someone cleans it, someone says it is ready for viewings. RapidEye names what was skipped: the oven, the window tracks, the sealant, the marks on the trim.
  • Furnished lets and inventory. Arthur keeps an inventory record against a property. RapidEye reads what is in the pictures against what was in them last time, and names the white good, the key, the remote or the piece of furniture that is no longer there.

A finding is one problem: the unit, the room, the spot, what kind of issue it is, how serious it looks, the earlier photo of the same spot beside the current one with both dates, and a suggested next step. Findings land in the RapidEye dashboard, and in an inbox or a Slack channel for whoever on your team wants them. Nothing is written back to Arthur, so you decide whether the finding becomes a task, a work order, or a note against the deposit. Examples on this page are the common ones, not the boundary: if your team documents with video walkthroughs, 3D scans, or an inspection format of your own, that is something we set up with you.

How to connect Arthur Online to RapidEye

  1. An Arthur account with your portfolio on it. Properties and units set up the way you already run them, so every image RapidEye reads arrives with a property, unit or tenancy attached. Single-unit properties managed at unit level, as Arthur suggests, work exactly the same.
  2. Decide where the images come from. Images already attached to tasks and work orders are read as they are. For check-in, check-out and void photos that never reach a task, RapidEye sends a capture link that opens on any phone, nothing to install, a fixed set of angles per room, lights on.
  3. Add RapidEye as a person. Arthur invites team members through Contacts, then People, then Add a New Person. The Connect modal on this page has the name and address to use.

How an Arthur task carries photos

Checked against Arthur Online's help centre, September 2026.

Arthur Online is a UK property management platform for letting agents, self-managing landlords, student housing and social housing, and its distinguishing move is a separate mobile app for each kind of person in the chain: occupant, property manager, contractor and property owner. According to Arthur Online's help centre documentation (arthuronline.co.uk), a task is created by a manager, by a tenant raising an issue, automatically when a trigger fires, or by the scheduler, and it can sit against a property, a unit, a tenancy, or nothing at all. Images enter the record at three nested levels.

Level 1

Task Arthur's own words: the task acts as a wrapper for everything required to complete the job. It carries a task type, which Arthur describes as behaving like a folder, and a sharing setting that decides which tenants can see it: everyone in the building for a property-level task, the unit's current tenants for a unit-level one, that tenancy's tenants for a tenancy-level one.
SubtasksCompanion app The checklist inside the task, added by hand or automatically from a template on creation. Arthur's inspection guidance is to make a task type called Inspection, hang subtasks off it for the parts of the property to review, then work it on the companion app: tap a subtask to mark it completed, add images as you go, view them from the summary.
Work orderContractor app Arthur calls a work order the digital equivalent of a worksheet given to a contractor. It can be added to a task, to an expiring certificate, to a property, unit or tenancy, automatically by a trigger, or through the scheduler. Title, description and work order service are mandatory; images and documents are optional. From an inspection on the companion app you can raise one and share the images you just took onto it.

Who can see the images on a work order

This is the part most operators get wrong, and Arthur documents it plainly. Sharing is set by preferences and by tick boxes on the work order itself, including whether documents and images are copied from the related task and whether they are shared with the contractor at all.

WhoWhat Arthur says they see
ContractorAll of the work order information, and any media on it when share documents and images with contractors is ticked. Tenant contact details can be hidden with a separate setting.
Property ownerCan view and approve work orders, but not the contractor's details or contact details.
TenantOnly the contractor allocated to the job and the documents that were deliberately shared.

The other settings on the same panel are worth knowing because they change what a picture is worth: marking a job an emergency adds a banner the contractor and owner see and nothing else, requiring a quote holds the job until you accept one, and access details from the access management module are shared with the assigned contractor only when you say so.

Does Arthur Online inspect the photos it collects?

No, and it does not claim to. Arthur's help centre describes attaching images to an issue, adding them under a subtask on the companion app, copying them onto a work order, and sharing them with a contractor. Every one of those articles is about moving the image from one person to another. None of them describes anything reading it. A completed subtask means somebody tapped a subtask, which is a statement about the visit rather than about the room, and once a work order goes from Awaiting Sign-off to Completed the images stop being looked at entirely. Arthur is also candid about the edge of its own scope: its inspection guidance recommends specialised inventory software for tenancy check-in and check-out, which is exactly where a long-term rental deposit argument is won or lost. RapidEye is the layer that reads what Arthur collected, sets a photo of a spot beside the earlier photo of the same spot with both dates, and hands your team a finding instead of a folder.

Arthur Online integration FAQ

Does RapidEye integrate with Arthur Online?

Yes. RapidEye reads the images attached to your Arthur tasks, subtasks and work orders, along with the property, unit or tenancy each one sits on, and returns a finding for every problem it can see in them. Your tasks, work orders, sign-off flow and tenancy records in Arthur are not changed.

Does Arthur Online check whether an inspection photo is any good?

No. Arthur's help centre describes uploading images against a subtask on the companion app and sharing them onto a work order, and describes marking a subtask completed by tapping it. Nothing in that flow reads the image. A completed subtask means somebody tapped it, which is a statement about the visit and not about the room. RapidEye reads the image and says whether the two agree.

Can RapidEye compare check-in and check-out photos for a deposit case?

Yes. RapidEye holds the earlier image of the same spot and puts it beside the later one with both dates on the pair, so a deduction argument starts from two pictures rather than a memory. Arthur's own guidance points check-in and check-out work at specialised inventory software, and RapidEye works alongside whichever one you use.

What about the photos tenants send through the Occupant App?

Those are read too. Arthur says a tenant chooses an issue type, adds a description and attaches images when raising an issue, which usually makes the tenant photo the earliest picture of the problem. RapidEye reads the whole frame, not just the thing the tenant named.

Do contractors have to change anything?

No. They carry on accepting jobs and completing them in the Contractor App as they do now. If a contractor works over email instead, a RapidEye capture link opens on any phone with nothing to install.

Will RapidEye create or close anything in Arthur Online?

No. Arthur stays the system of record for the property, the tenancy, the task and the work order. RapidEye reads and reports, and the manager decides whether a work order gets raised or a sign-off waits.

Other lettings and residential platforms RapidEye works with

Systems that, like Arthur, put the job and the tenancy in one record and leave the photos unread.

ReapitProperty management and the Reapit Go mobile app, read for condition FixfloReactive repair reports read before the job is even allocated GoodlordEnd of tenancy evidence set against the start of it AltoLettings progression photos read across every tenancy Re-LeasedProperty operations media read building by building All long-term residential integrations

Sources

  • Arthur Online help centre, tasks, work orders, companion app and permissions documentationarthuronline.co.uk
  • Arthur Online product pages, task, workflow and stakeholder managementarthuronline.co.uk

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