Somewhere in your building there is a clipboard. It holds a route somebody walks, a set of boxes somebody ticks, and a signature at the bottom. When the route is finished the clipboard goes into a drawer, and the information on it stops existing in any way that can be searched, counted or acted on.

That is the honest starting point for building inspection software for property management. The inspections are usually already happening. What is missing is the part where they turn into a record and, more importantly, into work.

An inspection that ends in a drawer is a cost

It costs the porter's hour, and it returns nothing except the reassurance that the walk happened. The value of a route is the early signal: the belt starting to fray, the door closer that no longer latches, the ceiling tile with a stain that was not there in June.

Signal only has value if it reaches somebody who can act, in a form they can act on. A tick in a box does not do that. A finding attached to a location, with a photo and a work order behind it, does.

Routes are the unit, not checklists

Buildings that make this work think in routes instead of forms. A route has a sequence, a rhythm and a person: lobby and ground floor at eight, mechanical rooms at ten, restrooms four times a day, roof and drains weekly.

The sequence matters more than it looks. A route ordered by geography gets walked; a route ordered by asset category makes the porter cross the building six times and gets cut short by week three. Design the route the way somebody would walk it, or design a route nobody completes.

The measure of an inspection programme is how many findings turned into work orders, because that is the only step where a walk becomes a repair.

What good inspections look like

The route lives on a phone. Not on paper that gets transcribed later, because transcription is where detail and enthusiasm both die.
A finding becomes a work order in one tap. If reporting a problem means leaving the route and writing an email, the route becomes an exercise in ticking boxes.
Photos should be the default. A picture of a stained tile settles in one second what three sentences argue about for a week.
Location is structured. Floor, room, asset. Free text means you cannot ask the obvious question later, which is whether this is the same spot as last time.
Completion is evidence. Who walked it, when, what they found. That is the artefact an insurer, a buyer or a regulator asks for.

The adoption question nobody asks in the demo

The person who will use this every day is often not in the room when it is bought, and they have a phone with cracked glass, gloves on, and forty minutes to walk a route before something else needs them.

That constrains the design more than any feature list. Big targets. Works with one hand. Survives a basement with no signal and syncs later. Does not log you out between floors. A route that takes eleven taps per item will be completed in the van at the end of the shift from memory, which produces a record that is worse than paper because it looks authoritative.

If you are evaluating tools, put the phone in the hands of whoever walks the route and watch them do one floor. That single test predicts adoption better than the rest of the evaluation combined.

Compliance rounds are a different animal

Life-safety inspections carry a date, a standard and a consequence: fire doors, extinguishers, emergency lighting, sprinkler valves, exit signage. These are not judgement calls and they are not optional, and the record is as important as the work.

The practical distinction worth building into the process is between rounds that generate insight and rounds that generate evidence. Insight rounds can flex. Evidence rounds cannot, and their outputs need to be exportable in the shape whoever asks expects, which is usually a date-stamped list with a name against it.

The photo problem, and how it goes wrong

Photographs are the most valuable thing a route produces and the fastest way to create an unusable archive. Ten thousand images with no location, no asset and no finding attached are indistinguishable from no images at all.

The fix is boring. Every photo attaches to a finding, every finding attaches to a location or an asset, and nothing is uploaded on its own. Once that holds, the archive becomes a before-and-after record you can put in front of a contractor who says the damage was already there.

Frequency is a decision you should revisit

Most inspection frequencies were set once, by someone who has left, based on the building as it was then. Occupancy changes, use changes, equipment ages.

The review takes an hour twice a year: for each route, what did it find last period? Routes that consistently find nothing are candidates for stretching. Routes that consistently find something are telling you either that the interval is too long or that an underlying condition needs capital instead of more walking.

Who walks the route

In-house staff know what normal looks like in your building, which is most of the skill. A contractor walking a route for the first time will miss the thing that is subtly wrong and catch the thing that is obviously wrong, which is the reverse of what you want from a preventive programme.

Where third parties do add real value is in specialist compliance rounds with a certificate at the end, and in an annual pass by fresh eyes precisely because they have not stopped seeing the corridor everyone walks past.

Where inspections meet the lease

Two inspection types sit on the boundary between operations and leasing, and they are the ones most often improvised.

Move-out condition reports decide whether a restoration obligation gets enforced or written off. Done with photographs against a structured checklist, they are a negotiating position. Done from memory a week later, they are an argument you lose.

Suite readiness before a new tenant takes occupancy is the other. A twenty-minute walk with a defined list catches the five small things that otherwise become the new tenant's first five work orders, which is the worst possible introduction to how the building runs.

What this is worth

Do not model it as labour saving; the walking still happens. Model it as three things: fewer failures that arrive without warning, a defensible record when somebody asks, and a shorter argument with vendors and insurers because the evidence exists.

The one number worth watching is the conversion rate from findings to work orders. If a hundred routes produce four work orders, your team is ticking boxes. If they produce sixty, some of them trivial, the programme is doing its job and you should leave it alone.

Where BuildingHub fits

Rounds and inspections run inside Operations Hub, on a phone, with findings that become work orders without leaving the route and photos that attach to the asset instead of to somebody's camera roll. Because preventive maintenance lives in the same place, a finding on a route and a scheduled service on the same equipment appear against one record. Related: schedules that survive staff turnover.

Inspections: turning a clipboard route into a record