InnveraDocs
Housekeeping

Housekeeping Settings

Inspection rules, generation, service standards, checklists, sections, the shift roster, par levels and task presets — and what each one changes.

Housekeeping is a configured module: the board only has cards on it because the service standards said so, the attendant only has a checklist because a template resolved, and Auto-assign only balances because somebody rostered a shift. All of it lives under Settings → Housekeeping, described in the header as Configure standards, checklists, sections, shifts, par levels, and task presets.

Six tabs run across the top: Settings, Checklists, Sections, Shifts, Par levels and Task presets.

Permissions

Five of the six tabs need housekeeping: configure. The Shifts tab uses housekeeping: assign instead, so a shift supervisor can roster the week without being able to rewrite hotel-wide standards. Without the grant every tab still opens read-only, with You can view these settings but not change them. Ask an administrator if something needs editing.

Settings

The first tab holds the property-wide switches and the service standards matrix. Nothing saves as you type: a line at the top reads All changes saved, Unsaved changes or Fix validation errors before saving, and Save settings commits both the switches and the matrix in one go.

Inspection

Whether a supervisor signs off a clean before the room goes back on sale.

SettingEffect
Inspection requiredOn (the default), a completed clean on a vacant room becomes Clean and waits in the Inspections queue before it is Ready to sell. Off, completing a clean releases the room straight to Ready and marks the task Inspected automatically.
Spot-check sample rateThe share of completed cleans routed to inspection, 0–100%. At 100 every room is inspected; at 30, roughly three rooms in ten are and the rest release themselves. The choice is derived from the task, so it never changes on a refresh. Only editable while Inspection required is on.
Allow self-inspectionLets an attendant verify a clean they performed themselves. Off by default — the server refuses with You cannot verify a housekeeping task you performed. Turn it on only for a property too small to have a second person.

Settings that depend on another are indented under it and greyed rather than hidden, so you can always see the option exists.

Generating the day

Whether tomorrow's sheet is built automatically from your service standards.

SettingEffect
Auto-generate day sheetCreates tomorrow's tasks overnight from the standards matrix. With it off, a supervisor runs Generate day by hand from the board.
Runs atHotel-local time as HH:mm — 23:30 by default. The nightly worker fires on the hour, so a property whose time matches that hour has its next local day generated.

Auto-generate will not switch on until the property is actually ready for it. When something is missing the switch is disabled and an amber Finish these first list appears under it, drawn from:

  • Create at least one section.
  • Assign every room to a section.
  • N enabled standard(s) have no resolvable checklist template.
  • One line per uncovered cell, in the form Deluxe Double · FULL_CLEAN has no resolvable checklist template.

The first of those reasons is also shown as a banner at the top of the page, with a count of the rest.

Assigning work

How the day's rooms are spread across the attendants on shift.

SettingEffect
Auto-assignBalances unassigned rooms across published shift capacity when the day is generated. Blocked with Add at least one shift to the roster. until the Shifts tab has something in it.
Assumed shift lengthCapacity in minutes for an attendant who has no rostered hours for the day — 420 (seven hours) by default. It is what the attendant columns on the board fall back to when drawing a capacity bar.

Service rules

Extra services, and when linen can be left alone.

SettingEffect
Turndown serviceIncludes Turndown tasks on occupied stayover rooms where the standards matrix enables them. Off, no turndown is ever generated regardless of the matrix.
Green stayLets the linen change be skipped on a stayover when the guest opts in.
Skip linen afterConsecutive stayover nights before the skip applies — 1 by default. Only editable while Green stay is on.

Dirty on check-out — coming soon

The server also carries a per-property dirty on check-out switch, which decides whether a check-out immediately dirties the room and raises a departure clean. It defaults to on and has no control on this page yet, so every check-out dirties the room today.

Service standards

The matrix underneath the switches is what generation actually reads: one row per room type × task type, saying whether to raise the task, how often, how long it should take and what checklist it runs against. Empty, it says No service standards yet. Add one to tell generation what to raise, how often, and against which checklist.

ColumnMeaning
Room typeA specific room type, or Hotel default for a rule that covers every type without its own row.
Task typeFull clean, Touch-up, Deep clean, Turndown, Inspection or Maintenance.
EnabledYes / No. Generation only raises tasks from enabled rows.
Every N nightsCadence for an occupied stayover — 1 services every night.
Vacant daysCadence for a room sitting empty — a vacant refresh every N days.
Every N staysCadence counted in completed stays; this is how the deep-clean cycle is set.
Credits (min)The estimated minutes put on every task raised from this row. Capacity bars, Planned totals and the auto-assign balancer all add these up.
ChecklistThe template that resolves for this row, or Inherited when it comes from a fallback, or an amber No resolvable checklist when nothing does.

A blank cadence cell shows — and means that trigger is unused, not zero.

Checklist resolution runs in three steps, and the matrix shows you the outcome rather than the rule: the template pinned on the standard if it is still active, otherwise an active template for the same task type scoped to that room type, otherwise the active hotel-wide template for that task type. A row that resolves nothing is highlighted amber and blocks auto-generate.

Add or edit a standard

Open the dialog

Click Add standard, or Edit on a row. The dialog explains the rules: Cadence fields accept blank (unused) or whole numbers ≥ 1. One standard per room type and clean type.

Scope it

Pick a Room type — or Hotel default — and a Clean type. Picking a clean type on a new standard re-seeds its cadence and credits with sensible openers: Full clean every 1 night at 30 minutes, Touch-up every 1 night or 2 vacant days at 15, Turndown every 1 night at 15, Deep clean every 5 stays at 90, Inspection at 10 and Maintenance at 15, all with no other cadence set. Choosing a pair that already exists is refused with This room type already has a standard for that clean type. Edit it in the matrix instead.

Set cadence, credits and checklist

Enabled controls whether generation raises tasks from it. Fill the cadence fields that apply, set Credits (min), and optionally pin a Checklist — leave it blank and the row says Inherits Departure clean, or warns No active full clean checklist when nothing would resolve.

Save

Add standard / Save standard stages the row; Save settings at the top of the page writes it. Room type and clean type are fixed once created — add a new standard if either needs to change.

Remove asks Delete this service standard? — Generation will stop raising tasks from it, and its cadence and credit minutes are lost. This cannot be undone. Existing tasks already raised from it are untouched.

Checklists

A checklist template is a list of things an attendant must do in a room. Templates are listed on the left with an Active or Inactive badge and a line reading Full clean · All room types · v3; the panel on the right edits the one you select.

New creates an empty template from three fields — Name (Departure clean), Clean type and Room type (or all room types). Creates an empty template. Add its items once it opens.

On the template itself you can rename it in place, toggle Active, Duplicate for room type (pick a room type from the dropdown to make a scoped copy), and Delete template — which warns that Service standards that reference it will show a coverage warning until you point them at another template.

Add item appends a row called New checklist item and focuses it. Each item has:

FieldEffect
LabelWhat the attendant reads — What should the attendant do?
AreaOptional grouping, such as Bathroom.
WeightIts share of the inspection score, shown live beside the box as 12% of score.
MandatoryThe attendant cannot complete the room until this item has a result. The server refuses with Cannot complete: N mandatory checklist item(s) are not done.
Photo requiredThe attendant must attach at least one photo, unless they mark the item N/A. Refused with Cannot complete: N checklist item(s) require a photo.

Items reorder by dragging, or Move up / Move down in the row menu; Delete item warns that Tasks generated from now on will no longer include it. Two previews at the foot of the panel show the same list twice — What the attendant does and What it scores on — so you can see the consequence of a weight before anyone is standing in a bathroom.

Templates are snapshotted onto the task

The checklist is copied onto a task the first time an attendant presses Start — and only then; resuming never re-copies it. Editing a template therefore changes tasks started from now on, and never rewrites a room somebody has already worked. A task started before its template had items has no checklist at all and completes without one.

Sections

Sections are the floors or zones you group rooms into: Floor/zone labels, room assignment, and display order for the board and assignment sheets. They drive the board's Section grouping, the section column on assignment sheets and printed sheets, the Preferred section on a shift, and the auto-generate gate.

A line at the top keeps the score — 42 of 56 rooms are assigned to a section — the remaining 14 can block auto-generate.

Add section takes three fields:

FieldNotes
Section nameShown on the board — North Wing.
CodeShort ID on printed sheets; unique per property — NW.
Floor / zoneFree text label, optional — 1–2.

Rows reorder by dragging or the Move up / Move down menu, and the order is what the board and the sheets use. Edits stage locally: a Save button appears on a changed row, and Save changes at the top writes every dirty row.

To change which rooms a section holds, click Reassign rooms. The picker warns Saving replaces every room in this section — it sends the whole list, so a section you open and save with nothing staged is emptied. Add rooms by searching name or floor, or add a whole floor at once with the Floor 3 buttons; a room already held by another section cannot be taken without removing it there. Cancel reassignment drops the staged list and leaves the server's assignment alone.

Delete asks Delete "North Wing"? Rooms will be unassigned from this section.

Shifts

The weekly roster — Attendant hours, breaks, availability, and preferred section for auto-assign capacity, one week at a time. This is the tab that makes Auto-assign possible, and its capacity figures are the bars you see on the board's attendant columns.

A week strip runs along the top with each day's shift count, available count and capacity, the current week's range and arrows to move between weeks. Week capacity is displayed as both a readable total and raw minutes. Select a day to edit it.

Attendants not yet rostered for the selected day appear as Add Maria Santos buttons; clicking one adds a Morning shift of 08:00–16:00. The table then lists:

ColumnMeaning
AttendantWho is working.
ShiftMorning, Evening, Night or Split shift.
SectionTheir preferred section, or None.
HoursStart and end, property-local.
BreakThe fixed unpaid break.
CapacityHours minus break — what auto-assign divides by.
AvailabilityWorking, or an amber Away with the reason beside it.

The pencil icon opens Shift details, which holds every editable field: Shift, Preferred section (A preference, not a restriction. Auto-assign still places work elsewhere when this section is covered.), Start, End, Break (min), Working this day, and Why are they away? when that switch is off. An unavailable attendant's hours are excluded from the day's capacity but the row stays on the roster, so the reason is on the record.

Copy this day to empty days fills every other day of the week that has no shifts yet, leaving days you have already rostered alone (Every other day of this week already has shifts. if there is nothing to do). Changes stage per day: Save roster writes one day, Save 3 days writes them in calendar order, and Discard changes throws the lot away. The week arrows are disabled while anything is unsaved — Save or discard your changes before moving to another week.

The break is fixed at 30 minutes

The roster save cannot carry a break per shift, so every saved shift takes the server's fixed 30-minute break and the Break (min) field is read-only. It is shown rather than hidden because it is the reason capacity is short of the hours: Every shift takes a fixed 30 min break, so this counts as 7 h 30 min of capacity. Hours that leave no capacity once the break comes off are flagged as you type.

Overnight shifts are handled — an end time at or before the start wraps past midnight rather than counting as zero.

Par levels

Room type × item × purpose × quantity matrix for linen, amenities, minibar, and cleaning supplies. A par level says what an attendant should expect to find and replace in a room of that type. It is not a stock balance: Stores owns physical on-hand quantities and the item catalogue, and a note at the top of the tab links both.

Pick a Room type, then edit its rows:

ColumnNotes
ItemChosen from the active Stores catalogue.
PurposeLINEN, AMENITY, MINIBAR or CLEANING.
QuantityHow many the room should have.

Add item offers everything in the catalogue not already on the list; the bin icon removes a row. Save par levels replaces the whole set for that room type in one write — a row you delete is gone once you save.

What par levels change: the consumption sheet an attendant fills in shows the expected figure against what they record (12 expected · 2 over), and the projection on Stores → Demand multiplies par levels by the day's planned tasks to say what the store will need. Items missing from the list simply have no expectation attached.

Task presets

Reusable one-off jobs — a preset pre-fills type, priority, estimate, notes and checklist when raising a task. They are what the Preset dropdown offers in the board's Create task dialog. Empty, the tab suggests the point of them: Presets save re-typing the same ad-hoc job — "descale kettle", "restock minibar" — and their estimate feeds the auto-assign balancer.

Add preset takes:

FieldNotes
NameWhat appears in the dropdown — Descale kettle.
Room typeA specific type, or all room types. Fixed after creation.
Task typeThe housekeeping task type raised. Fixed after creation.
PriorityLow, Normal, High or Urgent.
Estimated minutesThe credits put on the task. The estimate also feeds the auto-assign balancer, so keep it honest.
Checklist templateOptional; attached to tasks raised from the preset.
Default notesOptional; copied onto every task raised from this preset.
ActiveInactive presets stay configured but are hidden when raising a task.

Each preset lists as its name, a priority chip, and a summary line — Full clean · 30 min · All room types · Departure clean. Edit changes everything except the room type and task type; Delete removes it. Anything a preset filled in on a task can still be changed in the create dialog — whatever you type afterwards wins.

Getting a property ready

In order, for a property starting from nothing:

  1. Sections — create them and assign every room, or auto-generate stays blocked.
  2. Checklists — at least one active template per task type you intend to raise, hotel-wide so it can be inherited.
  3. Settings → Service standards — a row per room type and task type with a cadence, credits and a resolving checklist.
  4. Shifts — roster the week, or auto-assign stays blocked.
  5. Settings → Hotel settings — decide inspection, then switch on auto-generate and auto-assign, which are now unblocked.
  6. Par levels and Task presets — optional, and easiest to add once the day is running.

On this page