A casa
It happens once.
So it has to work.
Most software can afford a bad afternoon. An event cannot. This page is the honest answer to the question every host eventually asks: what happens on the night if something goes wrong — with the venue, with the internet, or with us.
- Works with no signal
- Printed fallback
- Pessoas, não linhas
What happens if Evorrah is down during my event?
Your event continues. The door scanner keeps working with no internet at all — it queues every arrival on the device and syncs when signal returns — and every event can print a recovery pack: a door list that needs no network, no app and no Evorrah. If we disappeared entirely on the night, somebody at the door with that sheet still runs the room.
01
The venue with no signal.
Cellars, marquees, castles, ballrooms below street level — the places people hold the events worth designing for are frequently the places with no bars of signal. A check-in system that assumes connectivity is a system that fails precisely where it is needed.
The door scanner is built for that. It installs as a service worker, so it opens and runs from the device itself. Scans are held in an on-device queue and reconciled when the connection comes back. A guest who arrives during an outage is admitted immediately, not asked to wait.
It also refuses to guess. If a lookup fails, the screen says the lookup failed — it does not show a green tick it cannot justify, and it does not show a stale head count without saying that the count is stale.
Sem
The usual arrangement
One tablet, one connection, one point of failure. When the signal drops the queue stops, and the fallback is a spreadsheet somebody has to find, print and interpret at the door — usually a list of rows, which is not the same as a list of people.
Com a Evorrah
How this works
The scanner runs offline by design and queues arrivals locally. Alongside it, every event can print a recovery pack that opens with no network, no CDN and no font to download — and it lists people, not rows, so a family of four appears as four names a doorman can tick.
02
Why "people, not rows" is the whole difference.
One line in a guest list can be a household of four — a primary guest, a named plus-one, two children. A door sheet printed straight from those lines hands the person on the door 180 entries for a 400-person wedding, and no way to admit the other 220.
The recovery pack expands households into individual names before it prints, using the same counting logic the rest of the system uses. That matters for a reason beyond convenience: a door list that disagrees with the head count is how a room ends up over its fire code.
What to do on the day, in order.
Print the recovery pack the week before
It is a single document from your portal. Put it in the folder that goes to the venue. If you never open it, you have lost one sheet of paper.
Open the door scanner before guests arrive
Opening it once while you still have signal lets it cache everything it needs to run without any.
If a code will not scan, search the name
Every guest can be found and admitted by name. The QR is the fast path, never the only path.
If everything fails, use the paper
The pack has every name, every household and every table. The evening does not depend on us being available.
Straight answers.
What if a guest loses their QR code?
What if somebody arrives who is not on the list?
What if my files are wrong at the printer?
Who answers at 6pm on a Saturday?
Is there a phone number?
What we will not claim. We do not publish an uptime percentage, because a number measured over a year tells you nothing about your one night. What we can tell you is the design principle: every part of the event-day path is built so that the evening survives us being unavailable. That is a stronger promise than a figure, and it is one you can check by printing the pack and reading it.
Planning something that cannot go wrong?
Tell us the venue and the guest count, and we will tell you plainly what to expect on the night.
Fale com a casa