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
Raken
Raken integrationConstructionDaily reporting and field management

AI photo review for Raken daily reports

RapidEye reads the photos your crews attach to work logs, notes, checklists and observations in Raken, and returns a finding for every damage, rework and site condition issue it sees in the project Gallery.

How Raken handles photos

Overview

The Raken project Gallery is a complete record of the jobsite and a queue nobody finishes. Every photo a crew takes in the app is time and date stamped, attached to the day's report, and filed into the Gallery in date order, which is exactly what you want when a dispute lands eighteen months later. What no gallery can do is tell you which of today's four hundred frames shows a cracked slab edge, a fire extinguisher blocked by stacked material, or a wall that got closed up before the rough-in was signed off. RapidEye reads the same photos Raken already holds and returns a short list of findings against the project, so the reading gets done on the day the photo was taken rather than the week a claim is filed.

Every photo readWork log, note, attachment, checklist and observation photos, on every project you connect.
Change over timeToday's frame against the last one of the same area, so drift and damage show up as a difference.
Findings, not foldersA short list per project with the photo, the area, the severity and a next step.

How it works with Raken

Raken already decides where a photo goes. RapidEye follows that structure rather than asking anyone to file things differently, so the field workflow is untouched and the reading happens on the way through.

  • Work log photos. The crew photographs what they put in place: a pour, a hanger layout, a trench before backfill. RapidEye compares that area against the last time it appeared and flags the differences worth a look, including work that was covered before it was documented.
  • Note photos. Notes are where a foreman calls attention to something in words. RapidEye reads the photo attached to it and returns what else is in the frame, which is often the part nobody wrote down.
  • Attachments on the daily report. Deliveries, damage on arrival, equipment left overnight. A finding here names the item and the condition, which is the level of detail a rental or delivery dispute turns on.
  • Checklist and observation photos. A negative observation carries photos of the hazard; a checklist carries photos of the item being checked. RapidEye reads them as evidence and says whether the frame supports the answer given.
  • Collaborator report photos. Subcontractor reports are the ones least likely to be read closely and most likely to matter in a backcharge. They go through the same review as your own.

A finding is one issue: the project, the area, what kind of issue it is, how serious it looks, the photo with the region marked, the earlier photo of the same area, and a suggested next step. It lands in the RapidEye dashboard and, if you want, a Slack channel or an inbox for the project team. Nothing is opened, closed or edited in Raken; your supervisor decides whether a finding becomes an observation. If your standard is something else entirely, a punch list format of your own, a video walkthrough of a floor, drone or 360 capture, or a client's turnover spec, that is a setup conversation, not a limitation: RapidEye reads whatever documentation a project already produces and reports against whatever standard you hold it to.

How to connect Raken to RapidEye

  1. Pick the projects. Projects are the unit in Raken: the Gallery, the daily reports and the Safety and QC records all hang off one. The projects you pick are the scope of the integration, and you can start with one.
  2. Keep attaching photos where you already do. Photos reach the Gallery through Notes, Work Logs and Attachments on the daily report, plus checklists and observations. Crews keep the same app and the same habit. If a project needs a fixed set of angles nobody captures today, RapidEye can send a capture link that opens on any phone with no app to install.
  3. Add RapidEye as a View only user. Directory, then Employees, then add RapidEye with the View only role and assign it to those projects. The modal has the details.

How photos move through Raken

Checked against Raken's help centre, September 2026.

Raken is a mobile-first daily reporting app for construction field teams, and its photo model is unusually strict in a way that helps here: a photo cannot exist on its own. According to Raken's help centre documentation (rakenapp.com), photos appear in a project Gallery automatically when they are uploaded through one of three sections of the daily report, and the Gallery itself has no upload button by design. That means the Gallery is not a shared drive that fills with stray images, it is a consolidated view of files that are each already attached to a day, a project and a person.

NotesPhotos attached to a daily note, where a foreman flags something in words.
Work LogsPhotos attached to a work log entry, tied to the work recorded that day.
AttachmentsFiles attached directly to the daily report.
Ends up in The project Gallery

Read-only, organised by date, searchable, with full-screen view, file names and descriptions, and bulk download on the Performance Plan. Photos taken outside Raken, or not yet attached to a report, never appear here.

Raken's documentation is explicit that this is by design, and answers the obvious question directly: there is no upload button in the Gallery, so photos go in through Notes, Work Logs or Attachments and arrive in the Gallery on their own.

Two things happen to a photo automatically. Time and date stamps are added to every photo and video captured in Raken, and watermarks can carry the company logo, the project name and GPS coordinates. Separately, on the Performance Plan, AI Photo Tagging analyses photos taken inside the app and applies descriptive tags such as concrete, rebar or equipment, which you can then search by in the Gallery; Raken notes those tags are Gallery-only today and are not surfaced in daily reports or the activity feed, that photos imported from a camera roll are not tagged automatically, and that you can add, rename or remove any tag yourself.

Can Raken tell you whether a photo shows a problem?

That is not what tagging is for. Tags answer "where is the photo of the rebar", which is the hard part of finding one image among tens of thousands, and Raken's marketing pages put the volume it has handled at more than 130 million jobsite photos. What no tag can carry is judgment: whether this bay looks different from last Tuesday, whether the guardrail in the corner of the frame is missing a mid-rail, whether the finish on the left is the third time that wall has been patched. Raken's own quality pages describe the same intent from the other direction, that photos and video give stakeholders the closest thing to walking the site themselves, which only pays off if someone is actually looking. RapidEye is the someone. It reads the frames that were already captured and returns the handful worth a supervisor's attention.

Observations already have the shape of a finding

Where an issue does get raised in Raken, it lands in a well-formed record, and it is worth knowing the fields because a RapidEye finding is written to slot into them.

The Raken observation record
TypePositive for something done correctly, or negative for a hazard, risk or quality issue, then a type and sub type.
PrioritySet on the record when it is raised.LowMediumHighCritical
StatusDefaults to Open and moves through the workflow as the fix progresses.OpenIn progressResolvedClosed
LocationSelected from the project locations, when they are configured.
Assignee and due dateThe person responsible for resolving it, who is notified, and the deadline.
AttachmentsPhotos or files added as evidence, from the web app or straight from the camera on mobile.

Observations sit under Safety and QC on a project, can be submitted on their own or as part of a checklist, and require the Performance Plan; administrators can see them across every project from the company level. RapidEye does not write into this record. It gives your supervisor a finding specific enough to raise one in a few seconds, with the photo already attached to the day it came from.

Raken integration FAQ

Does RapidEye integrate with Raken?

Yes. RapidEye reads the photos and videos your crews attach to work logs, notes, attachments, checklists and observations in Raken, along with the project, the date and who submitted them, and returns a finding per issue: damage, rework, a housekeeping or access problem, or a safety condition, with the photo it came from. Your daily reports, observations and project settings in Raken are not changed.

Where do photos live in Raken?

In the project Gallery. Raken's help centre documentation explains that photos reach the Gallery only by being uploaded through Notes, Work Logs or Attachments on a daily report, and that the Gallery itself is a read-only consolidated view with no upload button. RapidEye reads that same set of photos.

How is this different from Raken's AI photo tagging?

Tagging tells you what is in a photo so you can find it. Raken applies descriptive tags such as concrete, rebar or equipment to photos taken inside the app, which is what makes a gallery of thousands searchable. RapidEye answers a different question: whether what is in the photo is a problem, and how this frame compares to the same area last week.

Does RapidEye create observations or close them in Raken?

No. Raken stays the record of the day. Observations keep their own workflow of Open, In Progress, Resolved and Closed, with the priority, assignee and due date your team sets. RapidEye reports what it finds and your supervisor decides whether it becomes an observation.

We run subcontractors on collaborator reports. Are those photos read too?

Yes, once the collaborator reports are indexed into the project. Subcontractor photos are usually the ones nobody scrolls, and they are also the ones a backcharge conversation later depends on, so they are worth reading.

What does a finding look like?

One issue per finding: the project, the area, the kind of issue, how serious it looks, the photo it was found in with the region marked, the earlier photo of the same area for comparison, and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for the project team if you want it there.

Other construction platforms RapidEye reads

Systems that hold the same thing Raken does: photographic evidence of a jobsite, captured by whoever was standing there.

ProcorePhotos on daily logs, inspections and incidents across the project record. FieldwireTask photos pinned to a location on the plan, punch list to closeout. CompanyCamEvery photo location and time stamped, organised by project. OpenSpace360 walkthrough capture mapped to the floor plan, read frame by frame. HammerTechSite inspection and safety observation photos on enterprise projects. All construction integrations

Sources

  • Raken help centre, project gallery, photo and attachment documentationhelp.rakenapp.com
  • Raken help centre, safety and quality control documentation covering observations and checklistshelp.rakenapp.com
  • Raken help centre, directory documentation covering employees, roles and permissionshelp.rakenapp.com
  • Raken product pages for daily reports, photo documentation and quality managementrakenapp.com

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