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
Fieldwire
Fieldwire integrationConstruction and equipment rentalField management and punch list app

AI photo review for Fieldwire

Read every photo your crews attach to a Fieldwire task and get a finding back for the damage, the unfinished work and the safety condition in the frame, pinned to the same spot on the plan.

How a Fieldwire task holds a photo

Overview

Fieldwire puts a photo in exactly the right place and then waits for someone to look at it. A task is pinned to a point on a plan sheet, numbered, categorised, assigned, dated and closed, and the photo taken inside it inherits all of that: which room, which trade, which day, which person. It is the cleanest jobsite evidence anyone produces. It is also produced faster than any project team can read it, and the usual reason to open one is a dispute that has already cost money. RapidEye reads the photos on your Fieldwire tasks as they arrive and returns a finding per issue, carrying the plan location and the task with it.

Findings land on the planEach one carries the task number and the pin, so the answer to "where" is a point on the sheet.
Every task, not the loud onesA thousand-task project gets read the same as a ten-task one. Volume is the reason, not the obstacle.
Fieldwire stays in chargeNo task created, assigned, moved or verified. No markup added. RapidEye reads and reports.

How it works with Fieldwire

Fieldwire's own help centre lists what teams use tasks for, and each of those uses puts a different kind of photo in front of us.

  • Punch items and deficiencies. A punch walk produces a pin, a sentence and a photo, and later a second photo saying it was fixed. RapidEye reads the closing photo against the opening one and says whether the thing in the first frame is actually gone from the second.
  • QA and QC observations. The photo taken to record one detail also records everything around it. A shot of a bracket carries the conduit run behind it, the fire caulk that is not there yet, the panel already scratched before handover.
  • Inspection observations. Fieldwire holds checklists on a task with initials and a date per line. The initials say the line was checked. RapidEye reads the photo attached to the same task and says what the line missed.
  • Safety issues. Housekeeping, a guardrail gap, a ladder set wrong, an extinguisher blocked. These show up constantly in the background of photos taken for other reasons, and nobody is looking for them there.
  • Work progress and as-built evidence. The photos taken to prove progress are the same photos that prove condition on the day. Read in order, per location, they become the record a claim is argued from instead of a folder someone has to go through under pressure.

A finding names the plan sheet and location, the task, the spot in the frame, the kind of issue, how serious it is, the photos it came from, and a suggested next step, and it lands in the RapidEye dashboard or a Slack channel or inbox. Nothing is written back to Fieldwire; you decide whether it becomes a new task on the plan. And photos are only the common case: 360 photos, videos captured in a task, walkthrough footage or scans of an area, a QA format you already run, all of that is a setup conversation rather than a boundary.

How to connect Fieldwire to RapidEye

  1. The Fieldwire projects to start with. Access in Fieldwire is granted per project from the project People tab, so a project you do not invite us to stays out of scope entirely.
  2. Photos on the tasks. Crews keep tapping the camera icon inside a task in the mobile app, or attaching existing photos from the Photos tab, exactly as they do now. If part of the work gets photographed outside Fieldwire, RapidEye can take those through a capture link that opens on any phone with no app to install.
  3. Invite RapidEye to the project. A Project Admin adds the user from the People tab. The modal has the details.

How a Fieldwire task holds a photo

Checked against Fieldwire's help centre, September 2026.

A task is Fieldwire's one unit of work, and the help centre is blunt that it is a catch-all: QA and QC issues, inspection observations, punch items, safety issues, RFIs and change orders, work progress, delays, coordination, and plain messaging between people on site. It is created by dropping a pin on a plan sheet, it gets a project-unique number that can never be reused or changed, and it carries a title, a category, an assignee, a location, start and end dates, cost, tags, watchers and a checklist whose lines record initials and a date.

According to Fieldwire's help centre documentation (fieldwire.com), the paperclip on a task accepts nine kinds of attachment, and the photo ones behave differently from each other in a way that matters if you are trying to read them all.

Photo or file 360 photo Existing photo Existing file Form RFI Link Google Drive Crop plan

A new photo added to a task also appears in the project's Photos tab, and deleting it from the task removes it from there too. An existing photo attached from the Photos tab does not work that way: unlinking it from the task leaves the original where it was. Photos uploaded straight to the Photos tab cannot be marked up at all until they are attached to a task, form, RFI, file or plan, which is a quiet nudge toward putting every meaningful photo on a task in the first place. Fieldwire also applies automatic tags to newly uploaded photos on projects created on or after 10 September 2025, drawn from a fixed list of 22 covering things like Drywall, HVAC, Rebar, Roof and Scaffolding.

The other half of a task is its status, and Fieldwire's statuses are a ladder rather than a set of labels. Every status, default or custom, is one of three types, and a task cannot skip a rung on the way up.

Open type

Where a task starts. On the default set this is Priority 1, 2 or 3, and a new task lands on Priority 2.

Admin, Member, Follower
Tracked type

Work reported done. Fieldwire records the date a task entered this type, which is what makes it filterable and reportable later.

Admin, Member, Follower
Verified type

Someone with authority agreed. Also dated, and verified tasks archive after a period set in the project settings.

Project Admins only

A project on the higher tiers can rename these, recolour them and add up to twenty of its own, mapped onto the same three types with their own permissions, which is how a punch workflow ends up reading Pre-Punch, Defect, In-Progress, Approved by Sub, Approved by GC. Three statuses can never be deleted: Open, Completed and Verified.

Does Fieldwire check what is in the photo?

It labels it, which is a different job. The automatic tagging picks from those 22 tags so a photo can be found again, and the help centre is clear that tags are for grouping and filtering. Nothing in Fieldwire's documentation describes anything that reads a photo for condition, compares it to the same location a month earlier, or contradicts the person who moved the task to Completed. That is the honest position, and it is the right one for a field management tool: Fieldwire's job is to make the record, and it makes an unusually good one, pinned and numbered and dated. Two-step verification is the closest the platform comes to a second opinion, and it is still a human opinion, formed from the same photo, usually on a phone, usually later. Reading the photos is what RapidEye adds on top of a record that is already better than most.

Fieldwire integration FAQ

Does RapidEye integrate with Fieldwire?

Yes. RapidEye reads the photos in your Fieldwire project, the task each one is attached to, the plan sheet and location it is pinned to, the category and the person who added it, and returns a finding per issue: damage, work that is not finished, a missing item, or a safety condition. Tasks, statuses, plans, markups and the Photos tab are not changed.

Does Fieldwire already check what is in a task photo?

It labels them. Fieldwire's help centre describes automatic AI photo tagging that applies tags from a fixed list of 22, such as Drywall, HVAC, Rebar and Scaffolding, to photos on projects created on or after 10 September 2025, so a photo can be found later. A tag says what the photo is of. RapidEye says what is wrong in it.

Can RapidEye check a task somebody already marked Completed?

That is the point of it. Fieldwire runs a two-step verification: all permission levels can mark a task Completed, and only Project Admins can move it to Verified. Verifying is a person deciding, usually from a photo on a phone, often days later. RapidEye reads the same photos before the admin gets there and says which tasks deserve a walk.

Will RapidEye create, assign or close tasks in Fieldwire?

No. Fieldwire stays in charge of the work: the tasks, the plan pins, the statuses, the checklists and the reports are all untouched. RapidEye reads and reports, and your team decides whether a finding becomes a new task.

Our subs already photograph everything. Is that not enough?

Photographing everything is what creates the problem. A project can carry over a thousand tasks with photos on most of them, and the reason to open one is almost always a dispute that has already happened. Reading them as they arrive is the difference between evidence you can find later and evidence that told you something at the time.

Does it work on a project that uses custom task statuses?

Yes. Fieldwire lets a project define up to twenty statuses, each mapped to Open, Tracked or Verified, with its own name, colour and permission. RapidEye reads whichever status a photo's task was in when the photo landed, so a finding on a task sitting in your own Pre-Punch or Approved by Sub status is reported against that status.

Other jobsite software RapidEye works with

Platforms that hold the same jobsite photos Fieldwire does, filed a different way.

ProcoreObservations, punch and inspection photos read across the project RakenThe photos attached to the daily report, read the day they land CompanyCamLocation and time stamped project photos, checked for condition OpenSpace360 walkthrough capture, read for what changed between passes BluebeamMarkup-driven punch, with the photo evidence behind it read All construction and equipment rental integrations

Sources

  • Fieldwire help centre, tasks, photos, task statuses and project permissions documentationfieldwire.com
  • Fieldwire product pages, punch list and construction management softwarefieldwire.com

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