Register Waitlist

Module

Front Desk

The daily operational surface — the room rack, arrivals and departures, folios and billing, and the policies deciding when a stay may start and end.

Register Waitlist →Read the docs →

What it is

Front Desk is where a stay is created, moved, billed and closed. It runs on the property's business date rather than the wall clock, so the arrivals list, the departures list and a night's postings all agree on which day they belong to. Every action a receptionist takes — check in, check out, post a charge, take a payment, open a group's master folio — is the same operation the API exposes.

01

The room rack

One row per room, one column per night, and a bar for every stay occupying one. Room type groups the rows, so a run of free deluxe rooms is something you see rather than something you compute. Blocking a room out of service happens on the same grid.

The Room Rack in Nerve: one row per room, grouped by type, with coloured bars spanning the nights each room is taken across a July date range.
Every room and every night in one grid — the view the desk actually works from.
02

Arrivals and departures, on the business date

Both lists are driven by the property's business date rather than the reader's clock, which is what keeps them stable across a night audit and across timezones. A walk-in is the same screen: it creates the reservation and the in-house stay in one step.

The Arrivals and Check-in screen in Nerve. A business date governs the list; one arrival is due, marked Ready, with a Check in button beside it and a Walk-in button for guests with no reservation.
Arrivals are driven by the property's business date, not by the clock on the desk.
03

The readiness gate

This is the check-in dialog twice. A clean room opens straight to a deposit field with the Check in button available. A dirty one raises a banner naming the problem and holds the button behind an explicit readiness override. It is a policy the desk can consciously override — not a hard stop, and never a silent pass.

Nerve's check-in dialog for a room that is ready. It reads “201 · clean”, offers an optional deposit with a payment method, and the Check in button is available.
Room clean: check in, open the folio, take the deposit.
The same check-in dialog in Nerve when the room is not ready. A red banner says the room is not ready for check-in and the room line reads “201 · dirty · not ready”; check-in needs the readiness override ticked.
Room dirty: the same dialog blocks, and says exactly why.
04

Folios, payments and group billing

Charges post to an open folio line by line, each tagged with its charge kind, and a folio cannot be settled and invoiced while a balance stands. A group gets a master folio with a billing split set per stay, and a total row reconciling the master against the guests.

A guest folio in Nerve with an outstanding balance itemised as a room charge and tax for night one. “Post charge” adds a line; “Settle and invoice” is greyed out while the balance stands.
A folio settles when it is settled — the button is not available before then.
05

Stay-time policies, three levels deep

Check-in and check-out clock times are set as a hotel default, overridden per room category, and overridden again per rate plan — the narrowest wins. A non-refundable rate that includes a late check-out is a policy row, not a note in a comment field.

The Stay-Time Policies screen in Nerve: a hotel default of check-in 14:00, check-out 11:00 and a 30-minute turnaround, an empty room-category level, and a rate-plan override that moves check-out to 12:00.
Three levels of check-in and check-out times, with the narrowest one winning.
What it means for an agent

An agent works the desk through those operations and that permission model: read the arrivals for a business date, check a reservation in, post a charge to an open folio, take a payment against it. It hits the readiness block the receptionist hits, and it cannot settle a folio that still carries a balance. Refunds and adjustments sit behind step-up re-authentication, so the operations that matter keep a human in them.

Go deeper

Every screen above is documented, operation by operation, against the shipped product.

Front Desk documentation →

Register Waitlist →Start from your property type →

Wondering whether this is for a property your size?

← All features