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
CompanyCam
CompanyCam integrationConstruction and equipment rentalJobsite photo documentation

AI inspections for CompanyCam

Every Photo on your CompanyCam Projects gets read, not just the ones somebody opened, and comes back as a finding tied to the Project, the date and the frame.

What a CompanyCam Photo carries

Overview

A CompanyCam Project is a complete visual record of a job, and completeness is exactly what makes it too big to read. Crews shoot as they work, every Photo lands on the right Project with a timestamp and a geotag, and the Timeline fills up over the life of the job. A year later that Project holds thousands of frames, most of which nobody has opened since the day they were taken. RapidEye reads them: all of them, on the Projects you choose, and returns one finding per issue with the Project, the date, the spot in the frame and the Photo it came from.

Every frame, not a sampleThe shots taken for the record get read the same as the ones taken to show somebody. That is where the missed work hides.
Dated evidence, already stampedTimestamps and geotags are on the Photos already. A finding carries both frames and both dates, which is what a claim argument runs on.
CompanyCam stays the recordNo Photo moved, no Tag added, no Project touched. RapidEye reads and reports back.

How it works with CompanyCam

CompanyCam already organises the job the way a reviewer would want it organised, by Project, by location, by date, so the checks follow that structure rather than fighting it.

  • The Project Timeline. The chronological view of a job is also a change log of the site. Two shots of the same wall three weeks apart come back paired, with what moved between them: a gouge in new drywall, a fixture that vanished, a slab edge chipped by a delivery.
  • Daily capture on an active Project. The photos a crew takes while working are the honest ones, because nobody is composing them. RapidEye reads what is behind the subject too: the unguarded opening, the ladder at the wrong angle, the material stacked where it should not be.
  • Punch and closeout. Project Tasks and Checklists say what still needs doing. The Photos say whether it got done. RapidEye reads the frames from the closeout visit against the frames from the punch walk and reports on the items that look unchanged.
  • Before & Afters. When a pair already exists in CompanyCam, RapidEye reads the pair as a pair and describes the difference in words a homeowner or an adjuster can follow.
  • Subcontractor work on a Project. Restricted Users and Collaborators shoot only the jobs they are on, which makes their Photos a clean per-trade record. Findings come back attributed to the Project and the User who captured the frame.
  • The back catalogue. The Projects you closed last year are still full of Photos. Reading them is how a disputed claim gets answered from a dated frame instead of from memory.

Each finding names the Project and the area, where in the frame the issue sits, the kind (damage, work not done, a missing item, a safety condition), how serious it looks, the Photos it came from with their dates, and a suggested next step. It files into the RapidEye dashboard, and can also reach Slack or an inbox. What happens next in CompanyCam is yours to decide: RapidEye writes nothing. And if the way your teams document a site looks different from any of this, video walkthroughs, 360 capture, drone imagery, scans, or an inspection format of your own, that is a setup conversation rather than a limit.

How to connect CompanyCam to RapidEye

  1. Pick the Projects. A Project Group, a division, or one job to start. Whatever is on those Projects is what gets read, and archived Projects stay out unless you ask for them.
  2. Keep shooting the way you shoot. The Photos are already there, so there is no new app for the crew and no change to the camera routine. RapidEye reads the Photo history already on the Project as well, because the earlier frames are what make a later change legible.
  3. Add RapidEye as a User. An Admin or a Manager invites Rapid Eye as a Standard User, which is the role CompanyCam documents as seeing every Project on the account without touching Users, billing or company-wide settings. The modal has the details.

What a CompanyCam Photo actually carries

Checked against CompanyCam's help centre, September 2026.

CompanyCam is built around one idea: a Photo is worthless loose and valuable in context, so the app never lets a Photo exist outside a job. According to CompanyCam's help centre documentation (companycam.com), a Project is a single job or job site, and every Photo, video, Checklist and Document for that job lives inside it. Projects are created by searching an address, dropping a map pin, or drawing a GeoFence for a larger or longitudinal site. That is the container. Here is what rides along with each frame inside it.

Project
The job the Photo belongs to. There is no loose camera roll to reconcile later, which is the whole reason crews adopt it.
Time and location
Every Photo is automatically timestamped and geotagged. A per-User camera setting can also burn the date, time and GPS coordinates into the corner of the image on mobile.
Who took it
The User, which is why CompanyCam's own documentation is firm that each person needs their own login. Activity is viewable by User.
Tags and captions
Photo Tags label the shot for later retrieval; Quick Caption adds a spoken description without typing. Both are things a person chooses to add.
Position on the site
Map this photo plots where each Photo was taken within a single Project. LiDAR mode on supported devices captures depth and measurement data alongside the image.
Its place in the job
The Project Timeline holds everything that happened on the Project in order, so the frame sits between what came before it and what came after.

Offline Mode keeps the camera working in a basement or a new build with no signal and syncs when the phone comes back, so the record does not develop holes in the places hardest to shoot.

Who can open which Photos

This matters for an integration, because a reader that cannot see a Project cannot report on it. CompanyCam documents four permission roles, and the difference between them is scope.

AdminAll Projects and features, plus billing, Users, Templates and integration settings.
ManagerAll Projects and features, Users and Templates; integration settings for select integrations.
StandardAll Projects on the account. No Users, no billing, no company-wide settings.
RestrictedOnly Projects they created or were assigned to by an Admin or Manager.

Two more kinds of access sit outside the roles: a Collaborator is invited to a single Project to view, add and comment on Photos without being a full User, and Guest Access shows a homeowner the Photos on one Project through a web link with nothing else on it. Admins and Managers are the roles that can send an invite, and Standard is the default the invite screen offers.

Does CompanyCam read the photos for problems?

It writes them up, which is a different job. CompanyCam's AI features are aimed at the paperwork: AI Documents turn a set of Photos and their descriptions into a Summary, a Daily Log, a Progress Recap or a Walkthrough Note, and AI Checklists let a crew build and complete a Checklist by voice with their hands full. Every one of those starts from Photos a person has already chosen, which is the right design for a write-up. The Photos nobody chose are a separate pile, and on a busy Project it is the larger one. RapidEye reads that pile, compares a frame against how the same place looked before, and returns only the frames with something in them. The two fit together: CompanyCam captures and documents the job, RapidEye tells you which of the frames deserves a person's eyes.

CompanyCam integration FAQ

Does RapidEye integrate with CompanyCam?

Yes. RapidEye reads the Photos on your CompanyCam Projects, along with the Project, the capture time, the geotag, the Tags and the User who took the shot, and returns a finding for each issue it sees: damage, work that was not done, a missing item, or a safety condition. Nothing in CompanyCam moves. Your Projects, Photos, Tags and Timelines stay exactly as your crews left them.

Which CompanyCam Projects does RapidEye read?

Whichever ones you point it at. Most teams start with one Project Group or one division, then widen. On first connection RapidEye also reads the Photo history already sitting on those Projects, because the earlier shots of the same wall, roof or panel are what make a later change visible.

Can RapidEye compare two Photos of the same spot from different dates?

That is the core of it. Every CompanyCam Photo carries a timestamp and a geotag, and the Project Timeline puts them in order, so two shots of the same corner taken a month apart can be lined up and read against each other. A finding names both dates and shows both frames.

Does RapidEye change anything in CompanyCam?

No. RapidEye does not move, delete, tag, caption or edit anything on a Project. CompanyCam stays the record of the job. Findings land in the RapidEye dashboard, and in a Slack channel or an inbox if you want them there, and a person decides whether a Project Task or a Checklist item follows.

We already use CompanyCam AI Documents. What does this add?

AI Documents turn Photos you have chosen into a written Summary, Daily Log, Progress Recap or Walkthrough Note, which is the write-up half of the job. RapidEye works on the other half: the Photos nobody chose. It reads every Photo on the Project, including the hundreds that were captured for the record and never opened, and reports only the frames with something in them.

What if our field team documents with video or 360 capture instead?

That works too. RapidEye reads whatever documentation a crew already produces, photos, video walkthroughs or 3D scans, and reports against the standard you set. If your capture looks different from the shape described here, tell us what it looks like and we will set it up.

Other construction software RapidEye works with

Platforms where the field team is already producing imagery of the site.

DroneDeploy Ground360 Walks and Progress Photos read against the plan, capture to capture OpenSpaceJobsite imagery read for condition, not only for coverage ProcorePhotos attached to project records read alongside the field workflow FieldwireTask photos read so rework shows up before it is billed RakenDaily report photos read for what the write-up did not mention All construction integrations

Sources

  • CompanyCam help centre, Projects, photo capture, permission roles and glossary documentationcompanycam.com
  • CompanyCam product pages, core and advanced featurescompanycam.com

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