Hotels and restaurants

Operations OS

The day, and the manager on duty’s one pane over all of it.

9:41

Costa Vista · Thursday

Manager on duty

Sound on · todayFreya · MOD
Past SLA
14 open across the departments
2
Overdue traces
6 due today
1
VIPs not yet in
9 VIP arrivals · 2 past ETA
4
Arrivals
7/31
Departures
9/29
In house
90
Arrivals · 31
1204 · Whitcombe · 16:00Mark arrived
1108 · Okafor · 14:45 · lateMark arrived
Property OS · 14 open · 2 past SLA — tap a row to act; Property OS records who did it, from here.
MODThe dayVIPTracesMore

The stay feed imported from the PMS morning pack, the arrivals board, traces that execute as Property OS tickets, the glitch log — and the reports section. One pane reads Property, Roster, Concierge and Training.

White-gloveMonth-to-monthFrom $400/mo

Walk Operations OS →

How it works

Operations OS in Under Two Minutes

1:39 · with captions

Walk it yourself →

Who it's for

For the Manager Who Runs Today and Reads Yesterday.

The manager on duty, the director of operations, front office and guest relations, and the F&B director. Restaurants run the reports section and the oversight without the stay feed — same product, same ladder.

  • Manager on duty

    One pane: past SLA, overdue traces, VIPs not yet in — and a Property OS ticket escalated or closed by proxy.

  • Director of operations

    The arrivals meeting with a board instead of a printout; traces that leave with a due time, and an owner when one is named.

  • Front office manager

    Arrivals by ETA with tier, occasion, allergy and recovery history; a discrepancy header that catches the two-day guest.

  • Director of F&B

    The outlet daily report in your office's own shape — covers, comps and voids by reason and by server, labor productivity from Roster OS.

  • Guest relations

    The glitch logged with its photo, root cause and recovery; the apology drafted in your voice for the desk to send.

  • Ownership

    The numbers come from the products that captured them — never re-keyed, each panel honest about what is wired.

What we build for you

Your day and your reports, built to the operation.

  • 01The reports section wired to the products you run — the daily report roll-up in the shape your F&B office already uses, comps and voids, labor productivity.
  • 02The manager's pane over your products — Property analytics, Roster shifts and labor, Concierge threads, Training compliance — with deep links into each.
  • 03Your PMS morning-pack reports mapped once, so each morning's import is one step (the Opera report text or a CSV export; a direct Mews connection is next).
  • 04Your VIP tiers, amenity standards and trace kinds, so the arrivals meeting produces tickets with due times.

Pairs withProperty OS →Operations OS decides the day; Property OS executes it. A trace created at the arrivals meeting becomes a ticket in the right department queue, with SLA and escalation, and its status flows back to the board. Each is sold standalone — no bundle price, no product-count discount.

The right screen

The Day for a Hotel. The Report for a Restaurant.

Switch the view — the same product, with the stay feed present or simply absent.

operations.harios.ai/console/day

Stay feedThe day

Add a stay Import the pack
Mon · Nov 16
17 in · 20 out
Tue · Nov 17
17 in · 18 out
Wed · Nov 18
17 in · 21 out
Today · Nov 19
31 in · 29 out
Fri · Nov 20
0 in · 20 out
Sat · Nov 21
0 in · 19 out
Sun · Nov 22
0 in · 12 out
Arrivals
31
9 VIP · 24 not in yet · 2 late
Departures
29
9 departed so far
In house tonight
90
59 stayovers · 176 guests
Occupancy
74%
122 rooms · 3 out of order · 1 no-post
Arrivals 31Stayovers 59Departures 29Rooms 4↑↓ move · Enter opens · [ ] change day
VIP 9Not in yet 24Late 2Allergy 4Occasion 7Handle with care 1No-post 0Long stay 5Children 3
RoomGuestTierETAAdl / chlNightsStatusFlags
1108GDNMarcus Okafor14:451 / 02Late
1204GDNEleanor Whitcombe +1VIP 416:002 / 04Due inALLERGYOCCASION
701PHSHana Takeda +1VIP 516:002 / 09Due inLONG STAY
414TJSIngrid Solberg +2VIP 218:302 / 15Due inREPEATCHILDREN

The stay feed — the day as the morning pack describes it, each arrival with its tier and flags.

  1. 01

    The day, from the morning pack

    Arrivals, departures, in-house, out-of-order by reason — imported each morning from the reports your PMS already produces. A direct Mews connection is next.

  2. 02

    Every arrival, with its flags

    Tier, occasion, allergy and long stay on each arrival; who is not in yet and who is late, counted at the top.

  3. 03

    The outlet daily report, in your shape

    Covers, net revenue, comps and voids by reason and by server, labor when the export carries it — assembled from the POS export and signed off by the manager on duty.

The day rail

Five Moments in One Day.

From the arrivals meeting to the night close, the day runs through one place — and nothing is re-keyed. Each panel of the manager's pane states plainly whether a product is live, not wired, or not entitled. No fabricated number, ever.

  1. 09:00
    Arrivals meeting

    The board replaces the printout. Every VIP, occasion and allergy from the morning pack; traces leave with a due time.

  2. 11:00
    Checkout wave

    Departures marked as they leave, open folios flagged, rooms handed to Housekeeping on the same screen.

  3. 15:00
    Arrivals

    The suite's ready-by time passes with its ticket still open — the manager's pane shows who has it — and the amenity trace comes back from Property OS as done.

  4. 19:30
    Service

    A guest glitch logged with its recovery; the apology drafted in your voice for the desk to send.

  5. 23:30
    Night close

    The outlet daily report signed off, the MOD report written, the daily sheet printed for tomorrow’s 09:00 meeting.

One hotel day, five moments in it. The stay feed is imported once a day from the PMS morning pack; a live two-way connection (Mews first) is next.
Costa Vista — a fictional luxury property created by HARIOS; all names, operations, and data are invented.

What's inside

For the Day.

The stay feed, imported — not re-keyed
Arrivals, departures, in-house, no-post rooms, out-of-order by reason, forecast — a column map learned once, idempotent re-imports, a manual add for the walk-in.
The arrivals meeting, with a board
Arrivals by ETA with tier chips, occasions, allergies and recovery history; per-department briefs generated from the feed.
Traces with a due time and a done-state
Pushed into the right Property OS queue with an absolute due time, and the owner’s name when there is one; status comes back to the board.
The glitch log and the daily sheet
Situation, solution, compensation and approval, a photo, a root cause — and the hotel daily sheet printed and exported from the same data.
The manager's pane
Queue health from Property OS, staffing from Roster OS, guest-thread signal from Concierge OS, compliance from Training OS — one pane that updates on its own.
The reports section
The outlet daily report, hotel-wide F&B totals, comps and voids by server and approver, forecast versus actual, labor productivity, the printable daily pack.
Restaurants run it without the stay feed
The reports section and the oversight over Roster OS and Training OS, with the arrivals board simply absent. Same product, same ladder.
Honest about what is wired
Each panel states plainly whether a product is live, not wired, or not entitled. No fabricated number, ever.

Before you sign

The Questions an Operator Asks.

Does it read our PMS?

The morning pack, today — the Opera report text or a CSV export, mapped once so each morning's import is one step. A live, two-way Mews connection is next, and this page will say so when it is.

Does it read our POS?

The outlet daily report reads the POS export file today and assembles it in your F&B office's shape. A live POS connection is still ahead.

Can the manager act from the pane?

On Property OS tickets, yes — escalate or close, by proxy; the manager's name and “via Operations OS” land on the ticket's timeline in Property OS. Every other row opens the product that owns it.

What about a restaurant with no PMS?

Operations OS is then the reports section and the oversight over Roster OS and Training OS; the arrivals board is simply absent.

Month-to-month from day one. No early-termination fee, 30-day notice, full data portability, white-glove onboarding.

The first call

Start with a Conversation.

  1. 1Thirty minutes with the person who builds your instance — not a sales rep.
  2. 2Your property mapped against the platform: departments, service periods, voice, compliance.
  3. 3A decision together. If it is a yes, your instance goes live in as little as 72 hours.

sales@harios.aisupport@harios.ai