AI housekeeping inspection for Track

Overview

A Track housekeeping work order is a scheduling and accounting record that happens to carry photographs. It knows the unit, the clean type or whether it is an inspection, who it is assigned to, the reservation before it and the reservation after it, the time it should take and the time it did, what it cost and whether the owner gets billed. Photos hang off it as their own resource, each with a filename, a description and the name of whoever uploaded it. Track stores them faithfully and shows them to anyone who opens the work order, which at enterprise volume is close to nobody. RapidEye reads those photos against a baseline built from the unit's own history and returns a finding per problem, with the earlier frame beside the new one.

How it works with Track

Track was built for portfolios where nobody can look at everything, and its housekeeping model shows it: work is bucketed by clean type, split across zones, assigned to staff or to outside vendors, and settled against an owner statement. Those same buckets are how the findings come back, so they land in the shape your operation already thinks in.

• By clean type. Track's clean types are named records with their own time estimate and task list, and the same list holds inspection types alongside cleaning types. A departure clean and a mid-stay service should not be judged against the same standard, and they are not. RapidEye scores the photos on each work order against what that clean type is supposed to leave behind, which is how a stripped bed on a turn reads as normal and a stripped bed on an arrival check reads as a finding.
• By zone. Housekeeping zones are how a large operator splits a market into workable areas. Findings roll up the same way, so a supervisor covering three zones sees three lists, and a pattern that belongs to one zone rather than one cleaner shows up as a pattern.
• By the exception. Track gives a work order a dedicated exception state for the moment something is wrong on site. That state depends on somebody noticing and saying so. RapidEye raises the ones nobody flagged: the cracked hob, the water mark spreading across a bedroom ceiling, the missing bar stool, on work orders that closed clean.
• By what the owner gets billed for. A Track work order can carry a cost and a flag for charging the owner. A charge that arrives with two dated photographs and a description of the damage survives the phone call that follows. A charge that arrives as a line item does not.
• By who did the work. A work order can be assigned to a user or to a vendor. Reading every one of them gives you a record per cleaner and per vendor company built out of what the camera saw rather than out of complaints, which is the only version of that record that holds up when you renegotiate.

A finding carries the unit, the room, the spot, the type of problem, a severity, the two frames, and a suggested next step. Findings go to the RapidEye dashboard by default, and to a Slack channel or an inbox if that is where your team looks. Whether it becomes a maintenance work order, an owner charge, a reopened clean or nothing at all is your call, made in Track. And photographs on a work order are the most common input rather than the only one. Operators who film walkthroughs, who hold 3D scans of their units, or who want findings scored against an inspection form they wrote themselves, get that configured with us at the start.

How to connect Track to RapidEye

1. The units and the zones to cover. Tell us which Track units are in scope and how your housekeeping zones are drawn. Large portfolios usually start with one region or one owner group and widen once the first findings land.
2. Photos on the work order. Your housekeepers already attach photos to housekeeping and maintenance work orders, and those are what RapidEye reads. Where a crew does not photograph yet, a RapidEye capture link covers them instead: any phone, no app to install, a fixed set of angles per room, taken before the work order is completed.
3. A short call to set up access. Track does not publish its user administration steps, so we walk your Track administrator through adding Rapid Eye and the email support@rapideyeinspections.com. The modal has the same detail.

Housekeepers keep working the same work orders on the same phones. Nothing about the schedule, the task list or the portal changes.

Inside a Track housekeeping work order

Checked against Track's product pages and public API documentation, September 2026.

Track's own housekeeping page names six things it gives a property care team: work order management, checklists, automated communications, reference photos attached to work orders, a housekeeping portal as the central point of contact for staff and vendors, and vendor management and billing. What that page does not show is the shape of the record underneath. According to Track's public API documentation (trackhs.com), a housekeeping work order is either a clean of a defined clean type or an inspection, it belongs to a unit or to a unit block, and it moves through seven states.

1. pendingWaiting to be scheduled or assignedThe work order exists against the unit with a due date. Nobody has picked it up.
2. not-startedAssigned and dueIt has an owner, a staff member or an outside vendor, and a time estimate attached to its clean type.
3. in-progressSomebody is in the unitThe clock is running against the estimate. Task list items get ticked, and photos start arriving on the work order.Photos attached here are read as the state the guest left behind.
4. completedThe work is declared doneCompleted carries a timestamp and the user who completed it. It is a claim about the work, made by the person who did the work.The full photo set is read and the findings for that unit follow.
5. processedSettled on the booksCost, owner charge and any linen ticket are reconciled. Track records who processed it and when.A finding here is the evidence attached to a charge.
6. exceptionSomething was wrong on siteA dedicated state for the clean that could not proceed, or that found a problem. It fires only when a person raises it.RapidEye raises the exceptions nobody typed.
7. cancelledCalled offThe work order is closed without the work happening. A reopen is available if it should not have been.

States as named in Track's public API documentation. The blue rows are where photographs exist, and the blue line under each is what RapidEye does there.

What the record holds beyond a status

The fields are the interesting part, because several of them exist precisely because condition is hard to prove after the fact.

Does Track review the housekeeping photos?

No, and it does not claim to. Track's housekeeping page describes reference photos as property photos attached to work orders, which is exactly what they are: a store, a display and an audit trail. Nothing in Track's documentation compares a photo with the last one taken of the same room, checks a photo against the task list item it belongs to, or ranks today's completed work orders by how likely they are to be wrong. At thirty units a supervisor closes that gap by driving. At three thousand, the photos are the only thing that scales, and until something reads them they are an archive rather than a control.

Track integration FAQ