Operations
Open one screen and the day is already on it
Arrivals to check in, departures to settle, balances to collect, rooms to turn over, activities to prepare. The Control Deck reads them off the property's live state and puts them in the order they need doing, and clicking one either finishes it or opens the screen that does.
Checking a guest in from the day's task row, on the demo property, Auberge du Lac Tranquille in Mont-Tremblant. Nothing between those clicks is a page load.
How it works
Today, generated rather than summarised
Nothing here is a static widget. Each item exists because something on the property is in a state that needs a person.
The day arrives as a task list
Arrivals to check in, departures to check out, balances to collect, rooms to clean, activities to settle. Clicking a task either completes it outright or opens the exact screen that does.
Start walks the shift
One guest at a time, with the folio, the balance and the next action already chosen. The operator is never asked to remember which screen a task lives on.
Routine work shows up the morning it is due
Nobody keeps the list. Each routine has its own cycle and its own window, and the deck opens it at the right moment: the cleaning list every morning before arrivals start, last month's manager report on the first, once the month has genuinely closed, and only through the second business day, the rate review once a year on the anniversary of the day you opened. Clearing one records the period it belonged to, so it stays gone until the next cycle comes around, and one nobody got to ages out when its window closes rather than sitting there as a red number.
One routine only appears when the property is nearly full
When tonight is 70 percent full or better, a different kind of task turns up. Look at next week and your free nights are scattered: one night open in one unit, two in another, a Wednesday somewhere else, and nobody books a single midweek night on its own. The deck offers to move a few of next week's bookings between units of the same kind, so those loose nights collect together and whole units come free for three and four nights in a row, which is a stay somebody will actually book. Guests keep the rate they booked and only the unit number changes. It shows you what it would do before it does anything, and if it would not open up a longer stretch it says so rather than moving people for nothing. It is gone the next morning, because it was only ever about this week.
A greyed-out button tells you what would turn it on
Open a reservation with no card on file and Check in is not clickable. Underneath it the screen says check-in unlocks once a guarantee is on file, and beside that are the three things that count as one: hold a card, take a deposit, or charge the company account. You are never left clicking a dead control and guessing where in the system the missing piece lives. Where a rule is the property's rather than the software's, the override is listed too: on departure morning with a balance outstanding, check out without settling is right there, marked as an override.
Money actions from the list, or through the folio: you choose
A task row does the thing itself, check in, check out, settle, with the same confirmation the folio would ask for. A property setting, on by default, decides whether money actions run straight from the list or open the folio first.
Two clicks to any screen, or type its name
Every screen is one click in the side menu and every tab on it is the second. Or press Ctrl K from anywhere and type: a guest's name, a room, a confirmation or folio number, or the name of the screen you want.
The day is drawn on the property's own clock
Above the list, the operating day runs on a real time axis: the check-out deadline, the turnover window, the hour check-in opens, each phase as wide as it actually is on your clock and the current one draining as the hour passes. The countdown runs to the next real milestone, and the light beside it takes its colour from money actually at risk rather than from a threshold somebody picked.
The greeting at the top is written for the hour, the weather and the board
The headline greets whoever opened the deck, and it is chosen by the hour, the weather and how heavy the board looks. A full night reads "Full house tonight", a fogged-in morning reads "Fog on the lake", a day with nothing on the board reads "Quiet one - enjoy it". It uses your name when it is greeting you and leaves it out when it is remarking on the weather, because a name pinned to an observation is what makes software sound synthetic. It holds one line for a whole part of the day rather than reshuffling while you watch it, and it never puts a number up there: the numbers belong to the list underneath, where somebody has to act on them.
Why it matters
The real cost of a system is training, and nobody prices it
A seasonal property that hires eight people when it opens and loses them when it closes pays that training cost every year, and it cannot afford software that takes two weeks to learn.
Productive on the first shift
New staff do not need to know the system's map. The software tells them what to do rather than waiting for them to remember.
Guidance where a first-timer would stall
Plain-language tips on the fields nobody knows on day one: lodging tax, fiscal year start, remittance basis, deposit percentage, cleaning time assumptions, minimum stay.
The operations a new hire has not found yet
The real gap for a new hire is not the screen in front of them, it is the operations nobody thought to mention. Cardinal keeps that list, thirty of them across the front desk, money, rooms and rates, daily operations and the faster routes, and marks off the ones this property has already done. What stays visible is what nobody has found yet: moving a guest to another room from a right-click, booking a stay by dragging across the dates on the board, splitting a folio so the incidentals go on a different card from the room. Nobody reads a manual for those. The list belongs to the property rather than to one browser, so the second desk sees the same one, and the titles it hands out along the way are the ones a real house uses, from New Arrival to Innkeeper.
Two desks see the same thing, with no refresh
Multi-desk realtime. A check-out in one browser updates the other without a refresh. With more than one person working, that is a correctness requirement rather than a convenience.
New employees are productive on their first shift, because the software tells them what to do rather than waiting for them to remember.
Architecture
One load, then instant
The perceived slowness of legacy hospitality software is architectural, not a hosting problem. Those systems are multi-page apps where every click is a full page load.
A single application load
Moving from the calendar to a folio to housekeeping to the manager report does not reload the page, re-authenticate, or fetch a new document.
Each screen arrives the first time you open it
The first load is the shell and the stores it needs, about 230 KB gzipped, and each screen's code arrives the first time you open it. The entire product, every screen and every report, is about 570 KB gzipped. Measured on the shipped build in August 2026.
Data loads once and stays live
Data is held client-side and kept current by a realtime channel, so screens render from memory instead of re-fetching. That is why navigation feels instant.
It matters most on a rural connection
On a property with a mediocre link at the desk, the difference between a state change and a page load is a check-in that takes ten seconds instead of two minutes.
Every click in Cardinal is a state change, not a page load.
Questions
Asked and answered
How long does it take to train someone?
The system generates the day's work and walks staff through it one guest at a time, so the first shift is productive. There is contextual guidance on every field a first-timer would not know, and the software surfaces its own capabilities as staff encounter them rather than requiring a training manual.
What if I do not know what a field means?
Every field a first-timer cannot be expected to know carries a small (i), right beside the field, with a plain-language note: what a lodging tax applies to, what a minimum stay does to a rate, what a scheduling model is for an activity. The note is written for somebody who has never run a property, and it is the same voice in configuration, at the folio and in the manager's reports.
Why does it feel faster than the system I use now?
Because it loads once. Cardinal is a single application: moving from the calendar to a folio to housekeeping to a report changes what is on screen rather than fetching a new page, so there is no sign-in again and no wait between steps. Older systems in this category are built a page at a time, which is the architecture an operator is describing when they say their system is slow. It shows up hardest on a rural connection.
Can two people use it at the same time?
Yes, and they see each other's work. A check-out on one computer updates the other without a refresh. With more than one person on the desk that is a correctness requirement, not a convenience.
How long does it take to get set up?
Enter your property address and the province, tax table and timezone configure themselves. Then add your room types and rates. A single-rate property is fully operational after the rooms section. Rate plans and bulk rate tools are optional and labelled as such.
Next
Read this next
Rooms and reservations
The booking and its bill on one screen, with guards that stop the mistakes that cost money.
Housekeeping and assignment
Priority derived from movements, a staffing forecast, and room assignment that spreads wear.
Reporting and insights
Today's numbers, a forecast that separates what is booked from what is modelled, and insights that open the screen that fixes them.
See it running
Watch a day run before you talk to anyone.
Six real screens from a working property, in the order the day happens. Open it now and go at your own pace.