Ask a property manager what the garage earns and you will usually get a monthly number that has not changed in two years. Ask how many spaces are occupied on a Tuesday and the answer is a shrug, because nobody counts. Parking is the one part of a commercial building that is simultaneously a revenue line, an amenity, a tenant negotiation and a source of weekly complaints, and it is usually run on a spreadsheet and a gate.

Parking management software for a commercial building gets pitched as a way to sell more spaces. The more useful framing is that it turns an unmeasured asset into a managed one, and the selling follows from that.

The spreadsheet works until three things happen

It works while the garage is full and stable. It breaks on expansion, on churn, and on visitors.

A tenant expands from twelve spaces to twenty and wants them adjacent, which means somebody has to know where the free ones are. A monthly parker leaves mid-month and the space sits empty until the next renewal cycle because nothing surfaces it. A tenant's client arrives at nine in the morning for a meeting nobody told the desk about.

Each of those is a small failure. Together they are the reason garages run below what they could collect, without anyone being able to say by how much.

Three products, not one

Most buildings sell parking three ways and manage it as though it were one thing.

Monthly is a subscription with a lease-like relationship: a start date, an end date, a rate, a person, sometimes a plate. Reserved is monthly with a specific stall attached, which sounds trivial and is the source of most disputes. Transient is a day pass or a visitor space, which is where the tenant experience lives and where the revenue leaks.

They have different lifecycles and want different handling. A system that treats a day pass like a monthly account creates work; a system that treats a monthly account like a day pass loses money.

The garage is the only amenity in the building that bills every month, and in most buildings it is the least instrumented thing in the portfolio.

Visitor parking is a tenant experience problem wearing a revenue costume

The nine o'clock arrival is the test. A tenant's client shows up, the barrier does not know them, the desk is on the phone, and the client circles the block for eleven minutes before finding a public garage two streets away.

The building lost a small transaction. The tenant lost something bigger, and they will remember it at renewal in a way that never appears in an operating report.

The fix is not complicated: let the tenant issue the visitor pass themselves, in advance, the same way they pre-register a guest for the lobby. It costs the building nothing and removes the entire failure mode.

What good parking management looks like

One inventory with real status. Total, assigned, available and reserved, current enough to answer an expansion question on the phone.
Accounts follow the lease. A tenant's parking starts and stops with their term, and expansions do not require someone to rebuild a tab.
Tenants issue their own visitor passes. Ahead of time, within a limit the building sets.
Billing happens once, in one place. Card, invoice or lease charge, decided at the point of sale instead of reconciled monthly from a paper log.
The barrier knows what the system knows. Otherwise every change is entered twice, and the second entry is the one that gets skipped.

The number that changes the conversation

Utilisation against inventory, read monthly. Not revenue on its own, which hides everything.

Two garages can bill the same amount while one is at ninety per cent occupancy with a waiting list and the other is at sixty with three tenants over-allocated and hoarding spaces they do not use. The first one should raise rates. The second one has spaces to sell today and does not know it.

Over-allocation is the most common finding and the most awkward one, because reclaiming unused spaces from a tenant is a conversation nobody wants. It is a much easier conversation with a utilisation number attached.

Enforcement, and who has to do it

Every parking policy is only as real as its enforcement, and enforcement in a commercial building is uncomfortable work performed by people who would rather not do it.

A car in a reserved stall means a tenant with a contract is standing in the garage at 8:50 with nowhere to go. The response has to be immediate to matter, which means whoever is on site needs to know instantly whose stall it is and who to call, not fifteen minutes later after a phone call to whoever keeps the sheet.

The system's job is to remove the lookup. Plate to account, account to contact, contact to phone, in one screen. Whether you tow, warn or shrug is a policy decision for the building. Not being able to answer the question at all is a software decision, and it is the one worth fixing.

Rates are a leasing decision

Parking rates get set once and then live forever, usually below market, because nobody owns them. They belong in the same review as rent, since they are frequently traded in negotiation and just as frequently given away without being priced.

The practical habit is to review parking whenever a lease is reviewed. What is included, what is charged, what the market rate is now, and whether the allocation matches the tenant's actual headcount instead of the headcount they had when they signed.

EV charging is now part of this

Charging stalls introduce a scarcity problem the rest of the garage does not have. A charger occupied for nine hours by a car that finished charging in two is a stall out of service, and the resulting complaints arrive at the property manager instead of the driver.

Buildings handle this with time limits, session-based pricing, or reservation windows. Which one you pick matters less than picking one before the third complaint, because the default, an unmanaged charger, converts an amenity you paid for into a recurring annoyance.

Where the garage meets the rest of the building

Parking is where a lot of building systems have to agree. Lease data says who is entitled to what. The access system decides whether the barrier opens. Billing needs to collect. The tenant wants to do all of it from the same place they book a conference room.

Running that as four disconnected systems is what produces the spreadsheet in the first place. Somebody has to be the person who reconciles them, and that person is always the property manager.

Where BuildingHub fits

Short-term and monthly parking run in Amenity Hub alongside bookable space and memberships, so a visitor pass is issued by the tenant the same way a room is booked, accounts follow the lease term, and billing happens at the point of sale through Stripe instead of in a monthly reconciliation. Amano McGann integration connects the gate, and because Security Hub sits in the same platform, the credential and the parking entitlement do not have to be maintained twice.

Parking as a revenue line, not a headache