Let's talk
operations

One hoarding, two clients, the same month

Every media owner has had this call. A client rings to confirm the Gangapur Road site for next month, you say yes, and somewhere in the back of your mind a small alarm goes off. You check. It was held for somebody else in March. You said yes to both.

Nobody talks about this one, because it feels like carelessness. It usually isn’t.

The hold that was never confirmed

Here is the actual sequence, and it is the same one almost every time.

A client asks you to hold a face. You do — in your head, in a diary, in a message thread. He says he’ll confirm by Friday. Friday passes. He doesn’t confirm and he doesn’t release it either, because releasing it costs him nothing and he might still want it.

Meanwhile a second client asks for the same month. You either turn him away for a booking that never materialises, or you take him and hope the first one has gone quiet for good.

Both outcomes cost money. The first is a lost sale you will never see recorded anywhere. The second is the phone call.

Why a diary cannot solve it

The information exists. It just lives somewhere only one person can reach.

A booking diary is a record of what was decided, not a system that answers a question. When your salesman is with a client and needs to know whether the College Road face is free in November, he cannot consult a notebook in your drawer. He rings you. If you don’t pick up, he guesses — and a guess is exactly how a face gets sold twice.

The problem gets worse with scale in a way that is not linear. Fifteen structures with two faces each is thirty sellable things across twelve months: three hundred and sixty face-months to keep straight, most of them in one person’s head.

What actually fixes it

One calendar the whole business reads. Not one person’s calendar shared on request — one record that the salesman, the office and you are all looking at, at the same moment. The moment two people can see the same answer, the guess disappears.

Availability worked out, not typed in. A free-or-booked column that somebody maintains by hand is wrong within a week, and it is wrong precisely when it is busiest. Availability should be what is left over after the confirmed bookings — derived, so it cannot drift.

Holds with an expiry date. This is the important one. A hold is not a booking, and it should not behave like one forever. Give it a date. When the date passes, the face opens again by itself and appears in your available inventory. That converts “he never confirmed and I never chased” from a silent loss into something that surfaces on its own.

A record of who held it and when. When the awkward call does come, the difference between “I have it here — you asked on the 3rd and it lapsed on the 10th” and “I don’t have that written down” is the whole conversation.

The part that is not a software problem

None of the above stops you saying yes to two people. It only stops you doing it by accident. Discipline about confirming holds is still yours. What a system removes is the class of error where everyone acted reasonably on the information they had, and the information was wrong.

In Sazinga AdBoard availability is derived from live bookings on one shared calendar, so the same face cannot be sold twice, and a hold carries an expiry that releases the site when it passes. It is one of several failures that running an outdoor media operation produces when the inventory only exists in one person’s memory.

Related: how many days did your sites sit empty, which is the same problem seen from the other side — inventory you had and did not sell. If you are weighing up tools for this, what billboard management software actually needs to do sets out how to test a system for exactly this before you pay for it.

Working on something like this?

We build this kind of software, and we staff the teams that do.

Get in touch