Six booking systems is a reporting problem, not a software problem

Here is a conversation we have had, in some form, with almost every agency that calls us.

A council member asks how much revenue the city earned from its own buildings last quarter, and whether the recreation center covers its operating cost. It is a reasonable question. It takes three weeks to answer, the answer is assembled from four exports and a spreadsheet, and the person who assembles it does not entirely trust it.

Why nobody has fixed it

The instinct is to describe this as a technology problem, but it usually is not. Parks has a reservation package bought years ago that does what parks needs. The library runs room booking on a catalog add-on that library staff are happy with. The clerk keeps chambers in Outlook, which is completely adequate for chambers. Fields are allocated in a spreadsheet each spring by somebody who is genuinely good at it.

Every one of those systems works for the department that chose it. That is the trap. There is no burning platform, no department in crisis, no obvious failure to point at in a budget request. The cost is distributed and invisible, which means it never quite reaches the top of anybody's list.

The four costs, named

Re-keying

A request arrives as a PDF by email, or a phone call, or a walk-in at one of three counters, or a web form into a shared inbox. Somebody types it into a system. If it needs an approval it may get typed into a second one. If it takes payment it may get typed into a third. Nobody counts the hours because they are spread across four job descriptions.

Status calls

A resident who cannot see where their application has got to phones to ask. That call takes longer than the application did, and it happens because the applicant has no visibility, not because they are impatient. Self-service does not reduce calls because residents prefer computers. It reduces calls because the answer becomes visible.

Compliance drift

Certificates of insurance expire mid-season. Damage deposits get refunded from memory. Background screening for a coach lapses. In a fragmented setup nobody owns the calendar of expiries, so risk management finds out after the incident rather than before it.

Fee schedule drift

This is the one agencies underestimate. When four teams apply a fee schedule by hand, four slightly different interpretations emerge. Somebody rounds. Somebody applies the resident rate on the basis of a mailing address rather than the jurisdiction boundary. Somebody has not noticed that council adopted a new schedule in October. None of it is misconduct and all of it shows up as revenue leakage.

What consolidation actually buys

Not a better calendar. Three things that only exist once everything is on one platform.

• Conflicts found across departments. A maintenance closure blocks a rental, a program and an internal booking at once. Two staff in two buildings cannot double-book one room.
• One customer record. A household that books a pavilion, registers a child for camp and holds a membership is one record, so eligibility, waivers and insurance carry forward instead of being re-collected.
• One number. Utilization and revenue by rate class against direct cost, for the whole portfolio, including internal and no-charge use. That last part matters: a utilization number that excludes internal use is wrong, and it is usually wrong in the direction that gets a building closed.

How to make the case without a crisis

Since there is no burning platform, the business case has to be built from something else. Three things work.

1. The compliance date. ADA Title II requires WCAG 2.1 Level AA conformance for the pages residents use, by April 26, 2027 for entities of 50,000 or more and April 26, 2028 for smaller entities and every special district. Four vendors means four conformance problems. One portal means one.
2. The cost recovery question. Ask your finance director whether they could produce a defensible cost of service study for facilities today. The answer is usually no, and it is usually the argument that lands.
3. One department, properly. Do not propose replacing six systems. Propose the highest-volume business area, integrated with finance from day one, and let it become the reference point inside your own organization. Every subsequent phase is then an extension of something colleagues already use.

That last point is the one we push hardest with agencies, sometimes against our own short-term interest. A four-week single-business-area go-live that works beats an eight-month portfolio replacement that stalls in month five.