AI space inspections for HqO

Overview

HqO knows who is in the building, what they booked and when they badged in. It does not know what the eleventh floor restroom looked like at nine that morning. A building is the core organizational unit in HqO, tenants group the users inside it, and Resource Booking holds every bookable space with a photo and a capacity. That structure is exactly what a finding needs in order to be addressed to someone. RapidEye reads it, reads the photos your building team, cleaners and engineers take on their walks along with any attached to service requests, and returns a finding per issue: the space, the kind of problem, a severity, the before and after photos and a suggested action.

How it works with HqO

An office building has two kinds of space, and they fail differently. The spaces a tenant pays for get complained about; the spaces everybody shares get walked past. The checks follow that split.

• Common areas on the morning walk. Lobby, elevator lobbies, restrooms, stairwells, loading dock. The engineer already walks them. Photographed on the way, they become a dated record of the building's condition rather than a memory, and RapidEye flags what changed since yesterday.
• Bookable resources between reservations. HqO's resource list holds a photo and a capacity for every meeting room, wellness space and shared resource. RapidEye compares the room after a booking against the room at the start of the day: chairs not reset, a whiteboard not cleaned, a stain that was not there, a monitor cable gone.
• Photos on service requests. HqO documents optional photo attachments on a tenant's service request. That photo is the tenant's version of the problem and it is usually the only visual record the ticket ever gets. RapidEye reads it, classifies it, and remembers it the next time that space appears.
• Tenant suites at move-in and move-out. A tenant is a company occupying space, with lease data tracked at the tenant level. A photographed walk at handover and another at exit is what a contested restoration argument runs on, and RapidEye lines up the two.
• Cleaning that was contracted and cleaning that happened. The nightly vendor works to a scope. Photographed spaces let you check the scope against the room instead of against the invoice.
• Across a portfolio. HqO can show a dashboard across all buildings in a portfolio. Findings aggregate the same way, so an asset manager sees which building is drifting rather than which one has the loudest tenant.

Each finding names the space, the type of problem, a severity, the photos it came from and a suggested next step. The RapidEye dashboard holds every finding, with Slack or email routing for the property team as an option. The property team decides whether a finding becomes a service request. Photos are the common input but not the only one: video walkthroughs and 3D scans read the same way, and the standard a space is measured against is the one your brand or your building sets. If your input or your use case is not in the list above, ask us; that is a setup conversation, not a limitation.

How to connect HqO to RapidEye

1. Choose the buildings and the spaces. Which buildings in HqO, and which spaces inside them: lobbies, restrooms, amenity floors, and the resources listed in Resource Booking. A building is the core organizational unit in HqO, so everything else hangs off that one choice.
2. Point us at the photos. The walks your building team already does, the attachments tenants add to service requests, or a RapidEye capture link that opens on any phone with no app to install and asks for a fixed set of angles per space.
3. Add RapidEye as a user. HqO Admin, CRM, Users, Add users, assigned to the buildings you chose. The modal has the details. Your engineers and cleaners keep working exactly the way they do now.

Where a photo lives in an HqO building

Checked against HqO's help centre, September 2026.

HqO is a workplace experience platform for commercial real estate, and its documentation is unusually clear about how the pieces stack. According to HqO's help centre documentation (hqo.com), a building is the core organizational unit, every piece of content and every user is associated with one or more buildings, tenants are the companies that occupy space and are the primary grouping for users, and an experience channel is the branded app or web interface those users actually see. Property teams work in HqO Admin, whose sections run CRM, Leasing, Experience, Operations, Commerce, Files, Intelligence, App Configuration and Settings. The layers below are where an image can exist inside all of that, and what each one is good for.

Read down that stack and the shape of the gap is clear, and it is not a shortcoming of the platform: every layer is doing its own job well. Requests capture what a tenant reports. Resource cards sell a room. Partner systems dispatch and close. Building systems watch the equipment. None of them is designed to hold a running visual record of what a space looks like day to day, because that has never been anybody's job. RapidEye is that layer, and it hangs off the structure HqO already maintains.

What HqO Admin can already tell you each morning

Quite a lot, and it is worth naming because it sets the boundary. The My HqO dashboard is documented as a real-time operational view with widgets for reach and new users, thirty-day communication performance, today's badge-in traffic report, a summary of visitor check-ins and resource booking totals, upcoming events with registration progress, scheduled outreach, and a timestamped recent activity feed filterable by access, surveys, RSVPs and visitors. Resource Booking adds its own colour-coded state on the calendar.

Every one of those is a measure of activity: who came in, who booked what, who opened the message. Occupancy is not condition. A floor can badge in three hundred people and still have a restroom nobody has restocked since Friday, and the dashboard reads the same either way. What the integration adds is the missing column, produced from photographs rather than from anyone's attestation.

Does HqO hold building inspection records?

Not as a documented module. HqO's own help centre describes buildings, tenants, users, audiences and experience channels as the core concepts, and its admin sections cover CRM, leasing, experience, operations, commerce, files, intelligence and app configuration. Inspections are not among them, and where work orders are involved HqO states plainly that administration stays in the partner platform. So the honest answer for an operator asking whether they can run condition inspections in HqO is that HqO is the front door and the record of the relationship, and the condition record is a thing you add. That is the integration.

HqO integration FAQ