AI inspections for Tango

Overview

Tango Maintenance is a routing and accountability system, and the photo on the job is documentation it holds rather than something it interprets. A location raises a service request, a facilities manager validates and classifies it, the routing matrix picks the right internal team or vendor by trade, market and SLA, the work order goes out, and someone eventually closes it. Along the way field teams share photos and vendors upload their documentation into the portal, so a picture of every one of your locations is arriving in Tango continuously. RapidEye reads it: the images on the request and the work order, plus the location, the trade, the asset and the dates, returned as one finding per issue with the earlier photo of the same spot beside it.

How it works with Tango

Tango's maintenance lifecycle produces images at three different moments, and each one answers a different question. RapidEye reads all three, because a single photo is a claim and a pair of them is evidence.

• The request photo. Someone at the location reports the problem and attaches what they can see. RapidEye reads it against what that spot looked like on the last job there, which is often the difference between a fair claim and a store manager escalating a scuff that has been there for a year.
• The completion photo. The job is done and someone photographs it. RapidEye compares it to the request frame and reports the repair that is only cosmetically finished, the debris left behind, the adjacent damage created while fixing the first thing.
• Scheduled maintenance. Recurring work generates work orders automatically, so the same equipment is photographed by whoever attended that quarter. Across three visits a compressor's surroundings, a roof drain or a floor finish reads as drift rather than as a sudden failure.
• Vendor work in the portal. Vendors complete work orders and their associated documentation inside your system. Their photos read on exactly the same terms as your own team's, which is the reason for having them in one place.
• Condition, not just completion. Because Tango holds work order history per asset, findings can sit against that history: this is the fourth time this location has reported the same thing, and here is what the photos looked like each time.

A finding names the location, the work order and the asset, where in the frame the problem is, what kind it is, how serious it looks, both photographs, and a suggested next step. It lands in the RapidEye dashboard and, if you want, a Slack channel or an inbox for the facilities team. Tango stays the system of action; you choose what the finding becomes there. And if your inputs are not job photos at all, a walkthrough video from a district manager, a 3D scan of a store, a brand-standards format your team wrote itself, tell us: RapidEye reads whatever documentation you already collect, against whatever standard you care about, and we set that up with you.

How to connect Tango to RapidEye

1. The locations and trades to start with. A Tango Maintenance account with the locations you operate. Tell us which sites to begin with and which trades matter most to you, since a routing matrix that sends plumbing one way and refrigeration another produces two very different photo streams.
2. The photos already on the job. Field teams share photos from any location and vendors complete work orders with their documentation in the portal, so the images are already there and nobody changes their routine. Where a job closes with no image, a RapidEye capture link supplies one from any phone, with nothing to install.
3. The invite. Your Tango administrator adds RapidEye as a user on the account. The details are in the Connect Tango box, and we take the rest from there.

Where the photos sit in a Tango work order

Checked against Tango's product and blog documentation, September 2026.

Tango is a Dallas-based suite covering the location lifecycle for multi-site occupiers, from real estate and lease accounting through capital projects into facility maintenance, and Tango Maintenance is the part that runs the day-to-day. According to Tango's own product documentation (tangoanalytics.com), it covers service request submission from a mobile-friendly interface, a centralised call centre that classifies issues and issues tickets, request validation against asset history and landlord or tenant responsibilities, an issue routing matrix that picks a vendor by issue type, SLA and cost parameters, one-to-many work order creation with SLA enforcement, vendor selection and dispatch, scheduled maintenance that generates work orders as needed, and invoicing with approval chains. That is a serious piece of operational machinery, and the chain it runs is documented step by step.

1. Someone raises a service requestAnyone with access can create one, from the location, on a mobile-friendly interface, with pictures and documents attached.
2. A facilities manager validates and classifies itReviewing asset history and responsibilities so the job is routed correctly and unnecessary repairs are avoided.
3. A vendor is selectedFrom your supplier database, or by preferred-supplier rules that can differ market to market for the same trade.
4. The work order is created and dispatchedWith a priority and an acceptance window; if the vendor does not accept in time, the job returns to the unassigned pool.
5. The vendor accepts or declinesVendors under contract can have work auto-accepted on their behalf and are notified to review and schedule it.
6. The vendor does the workField teams submit updates and share photos from any location; vendors complete the work order and its checklists and documentation in the portal.
7. The facilities manager closes it outValidating the work and the rate, from an office, for a location nobody from head office has stood in.
8. The invoice is submitted and approvedCoded, split across assets, and pushed through the approval chain with a digital audit trail.

Every one of those steps is about getting the work to the right person, on the right terms, at the right price, and Tango is unusually good at it. The images enter at steps one and six and are still sitting there at step seven, when the only question that matters is whether the thing is actually fixed.

Does anything read the photo before the job is closed?

Not in the way close-out needs. Tango's pages describe field teams sharing photos and communicating with stakeholders from anywhere, vendors with limited access completing work orders and their associated checklists and documentation, and every record staying inside the system so it can support workflows and feed reports. All of that is about holding the evidence and keeping it where it belongs, which is exactly right. None of it describes anything opening the image and saying what it contains.

So validating the work at step seven is done on a rate, a description and a trust relationship, and the picture is available but unread. That is not a gap in the software, it is a gap in the day: a portfolio of a few hundred locations closes more work orders in a week than one facilities team can visually review in a month, and the ones worth reviewing look identical to the rest until somebody opens them. RapidEye opens all of them. Tango has already done the difficult half, which is getting a dated photograph of a specific location and asset, taken by the person who did the work, filed against the work order they were paid for.

Tango integration FAQ