Every Swiss campsite owes the same nightly debt to the statistics office: HESTA, the accommodation-statistics report. And on most sites, someone still pays it by hand — usually on a Sunday evening, usually from a stack of paper check-in cards.
Let’s break down where that hour actually goes, and why it doesn’t need to exist.
What HESTA actually requires
HESTA collects overnight-stay data per establishment: number of guests, nationality breakdown, arrivals and departures, nights stayed. It feeds cantonal and federal tourism statistics, and reporting is mandatory for accommodation providers above the size threshold.
The data it wants is data you already collect at check-in. That is the key insight — HESTA is not asking for anything new. It is asking you to re-type what you already have into a different form.
Where the hour goes
We timed the manual process across a dozen sites. The hour breaks down roughly like this:
- ~15 min gathering the week’s check-in cards and cross-checking against the booking calendar.
- ~25 min typing each guest’s nationality, party size and nights into the portal.
- ~10 min reconciling mismatches — a departure that was never recorded, a walk-in that never got a card.
- ~10 min fixing the one transposed number that makes the totals not add up.
None of that is skilled work. All of it is error-prone.
The hidden cost: errors, not minutes
The minutes are annoying. The errors are expensive. A miskeyed nationality or a missed departure doesn’t just misreport statistics — it quietly corrupts your own occupancy and revenue numbers, because the same guest record feeds both. When your HESTA figures and your bank deposits disagree, you have no idea which one to trust.
Manual reporting doesn’t just cost an hour. It costs confidence in every number downstream.
What “one click” actually means
Automation works because the report is a view of data you captured at check-in, not a separate dataset. When a guest checks in — online or at reception — their party size, nationality and stay dates are already structured. The system compiles the HESTA submission from that, on the nightly schedule the canton expects, and files it.
There is no re-typing, because there is no second dataset. The “click” is really just you confirming a report that assembled itself.
What to check before you trust it
If you move to automated HESTA filing, verify three things once, then stop worrying:
- Nationality capture happens at check-in for every guest, including walk-ins.
- Departures are recorded — an open-ended stay breaks the nightly count.
- Your canton’s format is the one being submitted; a few cantons have quirks.
Get those right and the Sunday-evening ritual simply ends.
The takeaway
HESTA is not extra work — it is a re-entry of work you already did. The fix isn’t a faster way to type it in; it’s to stop typing it in at all. Capture the data cleanly once, at check-in, and the report is a by-product instead of a chore.