The card machine, the till, the bookings and the cameras all run on one connection that nobody owns, with a password that has not changed since the venue opened. What breaks first, and the hour that makes it survivable.

On a Saturday at eleven the card machine stops. Then the till is slow. Then somebody says the bookings screen will not load. Somebody else unplugs the box behind the bar and plugs it back in, and eight minutes later everything works again and nobody ever finds out what happened.

That box is holding the venue's takings, its bookings, its recordings and its phones, and it has never once appeared on anybody's list of things the business depends on.

What is actually riding on it

Almost every venue underestimates this, because the connection was installed for one thing and quietly acquired nine more.

The card machine

⇒ On most modern terminals, card payments go over the same connection as everything else. ⚠️ When it degrades, the machine does not say "the network is slow" — it says declined, or it says nothing for forty seconds.

⇒ When the Card Machine Goes Down

The till

⚠️ Cloud tills stop taking orders. Local tills keep working but stop syncing, which is worse in a specific way: nobody notices until the end of the night, when two devices disagree about what was sold.

⇒ The Till That's Always Short

The bookings

⇒ The screen the door is working from, the confirmations going out, the changes somebody made an hour ago. ⭕ A booking system that cannot be reached is a paper list that is now out of date.

⇒ The Booking Nobody Confirmed

The cameras

⚠️ Many recorders are reachable over the network and some upload off-site. A connection problem can mean the week you most want footage is the week it was not being written.

⇒ The Cameras Nobody Watches

And the phone

⇒ Where the line is carried over the internet rather than a copper pair, the phone is on the list too — and nobody thinks of the phone as a network device.

⇒ The Phone Is Your Booking System, Whether You Built One Or Not

The one thing nobody planned for

Guest Wi-Fi and business Wi-Fi are usually the same connection with two names, and on a busy Saturday one of them is doing something the other cannot afford.

Two hundred phones is a real load

⚠️ Not because people are downloading much. Because two hundred devices reconnecting, roaming between access points and retrying is work, and consumer equipment does it badly.

The upload is the narrow part

⇒ Guests posting video use the direction that most connections have least of. ⭕ Your card machine and your till need almost nothing — but they need it immediately, and they are queued behind somebody's upload.

⇒ The Photographs Guests Take

Which is why it fails at the worst hour

⚠️ The connection is fine all week and fails at eleven on Saturday. That is not a coincidence and it is not bad luck — it is the only hour when the load is real.

Why nobody owns it

It was installed once, by somebody who left

⇒ A contractor, or a member of staff who was good with computers. ⚠️ Nobody has the login for the router, and this is discovered on the night it matters.

⇒ The Keys You Cannot Account For

It works, right up until it does not

⭕ There is no gradual warning. A connection is either fine or it is the reason your Saturday went wrong, so it never earns a place on a maintenance list.

And the fix is always the same, so nobody investigates

⚠️ Turning it off and on again works often enough to prevent anybody ever asking why. ⇒ A problem with a reliable workaround is a problem that never gets solved.

What to write down

One page, kept where the night manager can reach it. This is most of the value of this whole subject.

Who the provider is and what the account number is

⇒ Sounds obvious. ⚠️ Most venues cannot answer this at midnight, which means they cannot report a fault either.

Where the equipment physically is

The incoming line ／ the router ／ the switch ／ each access point

⭕ Including the ones in the ceiling that nobody has seen. You cannot restart what you cannot find.

The login for the router

⇒ Written down, in the same place as everything else that matters. Not on a laptop belonging to somebody who no longer works here.

And what to try, in order

⚠️ Not a manual. Three lines: restart this box, then that one, wait two minutes, then call this number.

⇒ The Person Everyone Asks First

Trading when it is down

The plan matters more than the prevention, because outages are not entirely within your control.

Know whether the card machine has a fallback

⭕ Some terminals can take payments offline and settle later. ⚠️ Whether yours can, and what the limits are, is a question for your provider — and the answer belongs on the page above, decided in advance.

Know how you take an order

⇒ Paper, and somebody who has done it before. A team that has never worked without the screen will lose an hour discovering how.

⇒ The Run Of Show For A Busy Night

Know what you tell guests

⚠️ Silence at the bar reads as chaos. ⭕ One sentence, said the same way by everybody, turns an outage into an inconvenience.

⇒ The Complaint That Never Reached You

And know what you reconcile afterwards

⇒ Whatever was taken by hand has to reach the same record as everything else, that night.

⇒ The Cash-Up That Takes An Hour

The separation that solves most of this

The single most useful change is not faster internet. It is keeping the two jobs apart.

Guests on their own network

⭕ Most business routers can do this, and it stops two hundred phones competing with your card machine.

The things that take money on the wire

⚠️ Where a cable is possible, use it. A card machine or till on a cable is a category of problem that stops existing.

And know which is which

⇒ Somebody should be able to say, in one sentence, what the till is connected to. If nobody can, the separation does not exist even if somebody set it up once.

The guest side, which is a different question

Guest Wi-Fi has its own considerations that are not about reliability at all.

It is a service, and it is judged

⇒ A password that does not work, or a page that never loads, is a small bad experience at the start of the night. ⭕ If you offer it, it should work.

What you collect from it is a legal question

⛔ If your guest network asks for an email address, a phone number, or a social login, you are collecting personal data, and what you may do with it is not an operational decision.

⭕ Ask your solicitor before, not after. ⚠️ A Wi-Fi sign-up that quietly builds a marketing list is exactly the kind of thing that is looked at closely.

⇒ The Messages Your Venue Sends

And what happens on it may not be your problem, but it is your name

⇒ Whether you are expected to filter or log anything varies by country and sometimes by licence. Ask once, decide once, write it down.

What good looks like

The midnight test

Ask the night manager who to call if the internet fails. ⇒ A name and a number means you have a plan. A pause means you have a router.

The separation test

Ask what the card machine is connected to. ⚠️ If the answer is the same network the guests are on, you know why Saturdays are like that.

The offline test

Working     — the team has taken orders without the screen, and knows how
Not working — it has never happened, so it will happen for the first time on a busy night

Three to hold

1  The connection is not an amenity — the takings, the bookings and the cameras ride on it
2  It fails at eleven on Saturday because that is the only hour the load is real
3  The plan for trading without it is worth more than a faster connection

Where the record has to sit

The provider, the account, where the equipment is, who to call, and what to do while it is down belong with the operating records rather than in somebody's memory. So does what actually happened on the nights it failed — without that, every outage is the first one, and the same eight minutes are spent finding the same box behind the bar.

⇒ The Report You Open Every Monday

The Wi-Fi Everything Depends On