A closer look at how a shift actually runs on Altoreva Ops
Altoreva Ops is the core platform — the system a whole property runs a shift on. The home page covers the what and the why. This page goes deeper: the four pillars in detail, the smart dispatch and everything else the platform handles, and how a single request moves from raised to resolved, all in a web app that runs in the browser on the devices your staff already carry. Everything described here runs today, and there's more on the roadmap beyond it.
Action calls
Every request, whether a guest need, a repair, a delivery or a follow-up, becomes a structured action call: coded, time-stamped, and owned by someone. Not a radio message that evaporates, not a note that gets lost at shift change.
A library of hundreds of action codes spanning every department, built from years inside working hotels, not invented for a demo, and you can add your own.
Every call has an owner and a clock, so "someone's on it" is a fact you can see, not a hope.
Departments, locations, codes and timing are configurable to the way your property already runs.
The same problem on three rooms goes in with one save: add the other rooms under More rooms and each gets its own call, its own owner and its own clock.
When a closed job comes back — the drain still slow, the stain still there — a manager sends it out again with a reason, linked to the original. A Redos report shows how often it happens, and to whose work.
Escalation & recovery
Most guest complaints start as a small issue that stalled. Altoreva watches the clock on every open call and escalates automatically when one stalls, so problems surface to the right person while they're still fixable.
Escalation rules run on their own. Nobody has to remember to chase.
Each department's escalation path reflects how your team is actually structured.
When something does go wrong, the follow-up is tracked to resolution, not left to goodwill.
Preventive maintenance
Equipment fails on the worst possible night. Altoreva schedules the upkeep that prevents it, using real measurements rather than just calendar dates to flag when something is drifting out of range.
Recurring maintenance tasks per asset, assigned and tracked like any other action call.
Readings logged during rounds trigger alerts when values fall outside the expected range.
An action code can lead to a PM checklist. A call on that code shows a button to run the PM on its room, and finishing the PM closes the call.
Every asset carries its service record: useful at budget time, invaluable at 11pm.
Inspections
The standard a guest experiences is set room by room, shift by shift. Inspections make that standard something you measure rather than assume — most often on guest rooms, but the same engine runs a check on any space your property cares about.
Checklists follow your property's own standard, scored by weight so a stained duvet doesn't count the same as a crooked lampshade, and the items you can't let slide are marked critical.
Anything that misses the standard is logged and routed immediately, with no separate follow-up list, and the person whose work it was hears about it on the channel they chose.
A fail opens a linked re-inspection that carries the passes forward, so nobody re-walks a room they already cleared — and first-pass rate stays a separate number from eventual pass rate.
An action code can link to an inspection checklist. A call on that code shows a button to inspect its room, and finishing the inspection closes the call.
Recurring misses show up in the record, so training and staffing decisions rest on evidence.
Smart dispatch, so the right person gets it
A call is only useful if it reaches someone who can act on it. Altoreva Ops routes each one to a person who's actually on shift and available, balances the load across the team, and moves it on every screen the instant anyone touches it.
Auto-dispatch sends each call to an available person on the right team and balances the workload, instead of the same name catching everything.
A live read of who's available, on a break, or signed out, so dispatch works off reality rather than the printed schedule.
The work that happens every day or every week is set up once and appears on the board on its own, so routine upkeep never depends on someone remembering.
Claim or close a call and it changes on every screen at once, with time-to-breach clocks counting on the ones running late. Group it by department, area, zone, status, priority or assignee, whichever way the shift is thinking.
The rest of the work a property runs on
The four pillars carry the day-to-day. These fill in the operational gaps that usually live in a binder, a spare-key drawer, or a spreadsheet nobody updates.
When a fix needs a part or a vendor, the action call becomes a tracked work order: parked with a reason, owned, and back on the board the moment it's ready to close. A manager can correct one while it's still open. Nothing sits "waiting on parts" out of sight.
The associate going home writes what the next shift needs to know, by department. Whoever comes on gets one line for each department with something waiting, and opening the note is the acknowledgment — there's no button to forget, and the receipt is per person, so a supervisor covering two departments still owes both. A handover note isn't assigned to anyone, so before one posts Altoreva reads it, and if it leaves work someone still has to do, asks This sounds like a job: make it an action call instead, or post it anyway.
A working record of who's staying: stays, arrivals, preferences, the calls raised during their visit, and the VIP classifications your property defines for itself. Duplicates are caught and merged rather than multiplying. It deliberately stops short of regulated data — no passport or government ID, no card details, no full date of birth.
Not everything gets called in. The guest mentions it at checkout, the associate fixed it on the spot, the comment card turns up weeks later. Log it after the fact against the same code library, record what was done to put it right and what it cost, and it counts in the record like anything else.
Track what's on the shelf with a scannable QR label on every item and bin, printed on label sheets or Brother 24 mm tape. Stock is counted per storeroom, with transfers between them, movements are logged as they happen, and low-stock alerts reach the right person before you run out mid-shift.
Log guest requests — dining, spa, transport, shows — with the vendor from your vendor list, time, and party size, and carry each one from pending to confirmed. Your own amenities book here too: grills, courts, hospitality rooms, by the time slot, with a waitlist when a slot is full and the day's bookings at a glance. A booking can raise its own action calls, so the grill is clean before the next party arrives.
One list of the restaurants, tour operators, drivers, spas, suppliers and contractors your property calls, so every shift finds the same number in the same place. Each vendor keeps its phones and emails, tappable to call or write, its menus and rate sheets, and every reservation booked with it. Rename it once and every booking shows the new name, and two entries for the same place merge into one.
Log what staff find and what guests say they lost, with their photos if they have them. Save either one and Altoreva shows the possible matches, with the reason each one matches, so the two lists actually get compared. Then release the item to a named claimant who signs for it, instead of a drawer at the front desk and a shift-lead's memory. Altoreva Security upgrades this with full chain of custody.
The things that stay true across many shifts — the pool is closed, the fire panel is being tested Thursday — go up once and keep surfacing in the app, instead of scrolling off a chronological feed the way a handover note is supposed to.
Every call ever raised on a room, in one place. The guest in 412 says the AC has "always" been like this — now you can see whether they're right, and what was done about it last time.
The outdoor operation, off the clipboard
A resort runs a second operation outside, and it tends to run on a clipboard at the towel hut and a guess about who's under which palapa. For properties with a pool or a beach, both are part of Altoreva Ops, on the same rooms and the same staff list as everything else.
Towels go out against a room number, and the keypad only accepts a room that exists, so a mistyped room never makes it onto the sheet. A guest whose room isn't ready yet can take them under their name, and the room is added when they come back. Returns, swaps and where the towels went are logged as they happen.
The hut counts its shelf at opening and logs each delivery, and one button places an action call for more before the shelf runs dry. The desk can look up any room and see what's still out, and the hut sheet can arrive by email on a schedule. When an attendant records towels left in a guest room, a pickup call for that room can open on its own, under the action code your property picks.
A board of who's on each numbered spot, whether it's a palapa, a cabana or anything else your property numbers, by room or as a non-guest, and one board can cover more than one kind, palapas and umbrellas together. A room holds one spot at a time: save it on a second and you're asked to clear the first. Narrow the board with filter chips, and look back at any earlier day to settle who was where.
When belongings sit on a spot nobody is using, Items removed photographs them before anyone moves them and logs them straight to lost & found. Those photos can't be deleted.
The parts you only notice when they're missing
Reporting, reach, languages, and getting your existing history into the system in the first place. None of it is what you'd buy the software for, and all of it is what makes the software stick.
Not a wall of charts. The numbers that matter this morning, plus a needs-attention list: what's running late, what's coming due, and which follow-ups are still owed.
Volumes and response times, service delivery times, where the time goes — waiting, working or blocked — who signed in and when they took a break, redos, top action calls and top associates, PM, inspections, warranty expiry, work orders, amenity use. Filter by several people, departments or zones at once, read it on a phone, and export to Excel, CSV or PDF. Put one on a schedule with just the columns you want and it's delivered by email to the crew positions and named people who need it, so the morning review is waiting in the inbox instead of built by hand.
The people who need to know are reached in-app, by email, and by push, and a staff member on a timed break has theirs held and replayed when they're back, so nothing is missed and nobody is buzzed on their break. When an email address starts bouncing, Altoreva stops sending to it, tells the person in the app, and shows their admin the address to fix.
The interface runs in English, Dutch, and Spanish today, each person in their own, with more languages on the way. It goes further than the buttons: a manager can write an action code or an inspection task in each language, and every notification and scheduled report resolves in the recipient's language, not the sender's.
The housekeeper writes the remark in Papiamento, and the engineer reading it doesn't have to guess. Translate on any remark puts it into the languages your property chooses, from ten including Haitian Creole and Polish, and keeps the original beside it, so nothing is lost in the rewrite.
Onboarding isn't a blank database. We import your locations, assets, staff, PM schedules with their last-service dates, inspection checklists and stock, and your archive from the system you're leaving stays searchable inside Altoreva rather than in a spreadsheet nobody opens.
More than two dozen short staff guides live inside Altoreva, one per screen, in English and Spanish, written for the person actually doing the job. Press ? on any screen and its guide opens. New staff learn where they work instead of from a PDF nobody sent them.
A REST API lets the systems a property already runs raise action calls, follow them, and close them out — accept, complete, cancel or add a remark, through the same state machine your staff work in. Altoreva sits alongside your PMS instead of asking anyone to abandon it, and we set the integration up with your vendor rather than handing them a key and wishing them luck.
From "someone should look at that" to done
An issue is logged as an action call: coded, time-stamped, owned.
It goes straight to the right department and the right person.
If it stalls, it moves up automatically, before the guest notices.
Tracked to completion, with a record the whole property can see.
Built to work where your wifi doesn't
Hotel buildings are hard on wifi: concrete stairwells, basements, laundry rooms, the far end of the third floor. Most software just stops working there. The preventive-maintenance worklist doesn't: claim your jobs on wifi, and they ride onto your phone for the shift. Out in a mechanical room you work them exactly as normal, and everything syncs the moment you're back in coverage.
Offline is built area by area rather than app-wide, and that's deliberate. Coordination work like the call board is meant to stay online — claiming a job has to tell the rest of the team right away, which is the one thing an offline copy can't do.
It runs today in the browser on the devices you already have. New staff are working in minutes.
Claim a job on wifi and its checklist loads onto the phone, marked Available offline. In the dead zones you tick tasks, type readings, add notes and photos, exactly as normal.
Work saved offline waits in an out-tray and empties itself the moment you're back in coverage. No send button, no re-entry, no lost updates.
Coordination — the call board, claiming a job — is live by design and always will be: it has to reach the rest of the team the moment it happens, which is the one thing a device on its own can't do.
Three optional modules, licensed separately, on the same login
Each switches on for a property that needs it and stays off for one that doesn't. None is a second system: same board, same permissions, same record.
Incident reports with signature capture, key and visitor control, GPS-verified guard patrols, a barred register, a security shift log, and an upgraded lost & found with chain of custody.
See Altoreva Security →Guest reviews from popular review sites, collected nightly and read for recurring themes and staff mentions, with a button to raise an action call from any one of them, and your own guest survey results alongside.
See Altoreva Reviews →Direct messages and groups inside Altoreva, on your own staff list, with replies, reactions, photos and read receipts, private direct messages, and messages kept only as long as your property agrees.
See Altoreva Chat →Every property gets on-site onboarding
Software like this fails at rollout more often than at evaluation. So someone from Altoreva comes to your property rather than sending a login and a link: your rooms, staff and departments loaded in, each person mapped to the departments they actually work in, QR and NFC tags configured and registered on site, and your team trained in person in your own conference room. Housekeeping and maintenance included, not just the managers who sat in on the demo.
Ready to put it on your property?
Tell us how your property runs today and we'll get Altoreva Ops set up around it, your data included.