What is a hotel quality assurance audit?

A hotel quality assurance (QA) audit is a structured, internal inspection a property or hotel group runs against its own brand standards, or against a franchisor's brand standards, to catch gaps before an external inspector, a guest complaint, or a lost star rating finds them first. It is GM-led or delegated to a quality or ops manager, runs on a recurring cadence, daily department checks, weekly full-property walks, monthly comprehensive reviews, and produces a score, a punch list of failed items, and, in a properly built program, a corrective action with an owner and a deadline.

This is functionally different from a brand standard audit (BSA), run by the franchisor itself. Marriott's BSA is an annual compliance review spanning five core operational areas, front desk, guest rooms and housekeeping, food and beverage, public areas, and safety and compliance, with auditors sometimes arriving unannounced and posing as regular guests, according to GoAudits' breakdown of Marriott BSA structure. High-performing Marriott properties target scores above 90%, and internal self-audits are commonly built to a 5-point cushion above the external target, because the internal program is the rehearsal, not the performance.

A few terms worth defining on first mention:

• Self-audit / internal QA audit: the property's own recurring inspection program, run by GM-ops staff, announced or unannounced internally.
• Brand standard audit (BSA): the franchisor's own compliance review (Marriott, Hilton, IHG), scheduled or surprise, scored against contractual brand requirements.
• LQA (Leading Quality Assurance): an independent third-party luxury hospitality assessment company, not a Xenia feature and not run by the hotel itself.
• Forbes Travel Guide inspection: an independent star-rating inspection, also third-party and anonymous, that produces a public rating instead of an internal score.

The eight-department spine that most brand-standard programs converge on, arrival, front desk, housekeeping and turndown, F&B/in-room dining, wellness/spa, security, and property presentation, is the correct structure for a self-audit template that later needs to reconcile against BSA, LQA, or Forbes categories. Auditors check details as granular as grout lines, mirror condition, and amenity placement in guest rooms, and a missing property certification form can trigger an automatic point deduction regardless of other performance, per GoAudits' Marriott BSA article. That level of granularity is exactly why unweighted scoring produces misleading numbers, a problem covered in the next section.

Internal self-audit vs. independent LQA vs. Forbes, the distinction the SERP gets wrong. An internal QA self-audit, an LQA assessment, and a Forbes Travel Guide inspection are three different processes, not three points on one continuum. The self-audit is run by property staff, happens frequently, and drives same-day corrective action. LQA and Forbes are external, anonymous, and infrequent, and they produce a benchmark score or a public rating rather than a punch list a GM can act on immediately.

LQA (Leading Quality Assurance) is the global market leader in luxury hotel assessment, supporting more than 70% of the luxury hotel market according to LQA's own hotel assessments page. Its program:

• Covers more than 1,000 standards across 8 departments, Food & Beverage (379 standards), Front of House (179), Housekeeping (117), Product (109), Service (up to 238), Spa & Fitness (53), Golf (49), and Transport (32), per GoAudits' LQA standards breakdown.
• Is conducted anonymously, under the guise of a regular guest, by an independent consultant who stays 1 to 3 nights on property, confirmed on LQA's own site.
• Produces quantitative scores, qualitative feedback, and an emotional-engagement rating, not a same-day punch list.
• Uses a passing score typically cited above 95%, with a recommended minimum of two assessments per year.

Forbes Travel Guide star ratings run on a parallel but separate model. Inspectors evaluate up to 900 objective criteria, confirmed by Forbes Travel Guide's own materials, during an anonymous stay that typically runs two nights and three days, sometimes longer. Service accounts for roughly 70-75% of the rating, with the remainder on facilities. No property can pay for a rating. It is earned solely through the inspection.

The internal self-audit is neither of these. It is run by the property or hotel group's own staff, not an outside assessor. It happens daily, weekly, or monthly, not once or twice a year. It is actionable in real time, a failed item creates a corrective task before the next shift, not a report delivered weeks later. And it functions as the preparation mechanism for both the BSA and any independent LQA or Forbes visit, not a replacement for either.

| Attribute | Internal Self-Audit (GM-ops) | LQA Assessment | Forbes Travel Guide Inspection |
|---|---|---|---|
| Who runs it | Property or hotel group staff | Independent LQA consultant | Anonymous Forbes inspector |
| Frequency | Daily to monthly, recurring | 1-2x per year | Annual re-rating cycle |
| Announced | Internally known, often unannounced within the property | Anonymous, guise of a regular guest | Anonymous guest-experience stay |
| Standards count | Property or brand defined, typically 100-300 items | 1,000+ across 8 departments | Up to 900 objective criteria |
| Output | Score plus corrective action list, actionable same-day | Benchmark report, qualitative and emotional scoring | Public star rating |
| Purpose | Catch gaps before they're found externally | Benchmark against the luxury segment | Market-facing quality signal |

Xenia does not perform the independent LQA assessment or the Forbes inspection. Xenia runs the internal self-audit program that prepares a property for those external evaluations. Its QA audit templates map to LQA's and Forbes' department structure so GM-ops teams can rehearse against the same categories an outside inspector will use, but the score a property gets in Xenia is not an LQA score or a Forbes rating, and no claim to the contrary would be accurate.

How does GM-ops quality assurance work in Xenia?

GM-ops quality assurance works in Xenia as a weighted-scoring audit program with room-type conditional logic and corrective actions that close inside the same record as the audit, not a checklist-only exercise that stops at data collection.

The relevant capabilities:

• Weighted scoring with color-coded thresholds: critical items (life-safety, security, ADA) get high point values, cosmetic items get low point values, and pass/fail thresholds drive corrective action automatically. This is the exact feature Dave's Hot Chicken switched to Xenia from RizePoint for in the restaurant vertical, at 321 locations, and the hospitality application is structurally identical.
• Conditional visibility (room-type variant): room types, king, suite, accessible, drive different inspection question sets without manual template duplication.
• Nullify (N/A) scoring: a property without a pool isn't scored against pool inspection items. A standard room isn't scored against accessible-room-only requirements.
• Follow-up questions with required image capture: a room inspection failure, stained linen, broken fixture, can trigger a required follow-up question ("what did you find?") and a required photo, capturing evidence at the moment of failure.
• End-to-end corrective action workflows: a QA audit failure creates a corrective task, assigns an owner, sets a deadline, and escalates to the housekeeping director or GM if not closed, closing the loop that checklist-only tools leave manual. A maintenance-flagged item, a broken exit sign, a failed HVAC unit, routes the same way a guest request routes from front desk to maintenance to closure.
• Custom dashboards on issues, not just completion percentage: a multi-property ops leader sees which properties have overdue corrective actions and which are trending toward repeat failures, not just a completion percentage. This matches how ops directors actually want to look at the data. A 50-property portfolio doesn't need another completion-percentage view. It needs to see what's coming up as a problem before it becomes one.

A GM-ops workflow example (illustrative product pattern, no invented customer): A 400-key property runs a weekly GM-ops QA audit across the eight department categories. The security section flags a malfunctioning emergency exit sign, a critical item at maximum weight. The audit auto-generates a corrective task assigned to the chief engineer with a same-day deadline. If it's not closed by end of shift, the task escalates to the GM. Meanwhile, a suite room fails a cosmetic item, a slightly worn armchair, logged at minor weight and batched into next week's maintenance run instead of triggering an escalation. The QA score for the week reflects that difference instead of hiding it. This is the hospitality paper-digitization pattern: the property replaced a paper punch-list clipboard walk with a tablet-based, photo-proof audit, without needing to replace its property management system.

A few honest boundaries worth stating plainly. Xenia is not a PMS replacement, it complements Cloudbeds, Mews, and Opera rather than competing with them. Xenia does not run the independent LQA assessment or the Forbes inspection described earlier. And Xenia's signature-capture feature is compliance evidence, not a legally binding e-signature. There is no published, named hospitality customer case study yet, which is why the workflow above is described as a generic product pattern rather than attributed to a specific property.

How do weighted scoring and room-type conditional logic make QA scores honest?

Weighted scoring assigns higher point values to life-safety and brand-critical failures, a broken smoke detector, a security lapse, than to cosmetic issues, a slightly misaligned picture frame, so a hotel's QA score reflects what actually matters instead of averaging critical and cosmetic items into a meaningless blended percentage. Room-type conditional logic shows different inspection questions for king rooms, suites, and accessible rooms from a single audit template, so a standard king room is never scored against ADA grab-bar requirements it doesn't have.

A generic checklist tool scores a stained bed linen item the same as a missing artwork alignment item, both "fail," both worth one point. This is the exact failure mode Dave's Hot Chicken hit with RizePoint's flat scoring in the restaurant vertical, where a missing patio chair scored identically to a temperature violation, and the same pattern shows up in hospitality: a property can post an 88% score that's either "one broken smoke detector" or "eleven scuffed baseboards," numbers that should never look the same to a GM deciding where to send the maintenance team first.

How weighted scoring should work for hotel GM-ops:

• Critical items (life-safety, security, ADA compliance failures): highest point value, immediate corrective action trigger.
• Major items (brand-defining guest-experience failures: broken HVAC, missing required amenities): mid-tier weight, 24-48 hour corrective window.
• Minor or cosmetic items (scuffs, misaligned decor): low weight, batched into routine maintenance rather than triggering escalation.

Sanitation and bedding compliance are critical items in a hotel QA program. Decor presentation is minor. That tiered weighting structure recurs across brand-standard audit content, but no competitor content pairs it with room-type conditional logic in the same workflow, which is where the structural advantage sits.

Room-type conditional visibility is the hospitality version of the "patios vs. no-patios" problem restaurants deal with. Conditional visibility is the audit feature that shows different inspection questions at different locations, or in this case different room types, without penalizing a room for items it was never supposed to have. A property with king rooms, suites, and ADA-accessible rooms cannot run one flat inspection template without either missing suite-specific items, an in-room kitchenette, sofa bed condition, or incorrectly failing standard rooms on accessible-room requirements, grab bar height, roll-in shower clearance, they don't have.

• King room inspection surfaces standard bedding, minibar, and desk-area questions.
• Suite inspection adds the additional living-area, kitchenette, and sofa-bed questions the king template doesn't need.
• Accessible room inspection adds ADA-specific grab-bar, clearance, and signage questions that don't apply, and shouldn't be scored, at a standard king room.

One audit template, three room-type variants, no manual duplication. Nullify scoring means N/A items don't count against the score, so a standard king room never fails on an accessible-room item it was never built to have. This pattern is documented in depth in the hotel room-type conditional audit guide, the cluster piece this concept connects to directly. It pairs with the deep clean schedule and cadence that many properties build their room-type inspection cycle around.

A common mistake is building three separate audit templates, king, suite, accessible, to avoid false negatives. That triples the maintenance burden every time a brand standard changes, since three templates now need three separate updates instead of one. Conditional visibility solves this with one template and room-attribute-based branching. This is the room-type variant of a differentiator Xenia applies across verticals: room types drive different inspection question sets without manual template duplication, the same underlying mechanic that lets restaurant chains show drive-thru questions only at drive-thru units.

How does Xenia compare to hotel-only tools?

Xenia compares to hotel-only tools by trading some hotel-housekeeping-specific depth for multi-vertical scope, weighted scoring, and corrective action closure that neither Flexkeeping nor the generic audit platforms currently match.

Flexkeeping is the closest hotel-housekeeping-specific competitor. Per Flexkeeping's own housekeeping product page and HotelTechReport's Flexkeeping profile, Flexkeeping specializes in real-time housekeeper location tracking, automated cleaning schedules tied to stay duration and rate type, room inspections with customizable checklists, linen and amenity management, and auto-translation into 240+ languages. It was voted #2 Housekeeping Software provider in the 2026 HotelTechAwards, with pricing starting around $2 per room per month plus a one-time setup fee, according to SelectHub's pricing aggregation.

GoAudits and SafetyCulture currently own much of the "hotel QA audit" and "LQA checklist" search results, but neither demonstrates weighted scoring with critical-vs-cosmetic point differentiation baked into the audit engine, both describe generic checklists and completion tracking rather than point-value branching tied to escalation. Neither shows room-type conditional logic. Both present flat templates. And while GoAudits describes facilitating the assignment of corrective actions, the audit trail and the closure trail are not shown as the same record with automatic escalation.

| Attribute | Xenia | Flexkeeping | GoAudits / SafetyCulture (checklist tools) |
|---|---|---|---|
| Scope | Multi-vertical ops platform (hotel plus facilities, audits, comms) | Hotel-housekeeping-specific | Horizontal audit and inspection tool |
| Weighted scoring | Critical vs. cosmetic point values with escalation thresholds | Limited, checklist-based, not point-weighted | Generic scoring, not vertical-tuned for hospitality |
| Room-type conditional logic | One template branches by room attribute | Not positioned as an audit-conditional-logic feature | Not a native feature |
| Corrective action closure | Automatic task, deadline, escalation, same record as the audit | Task assignment exists, closure workflow is lighter | Manual follow-up in a separate view, often disconnected from the audit |
| Facilities / work orders | Native | Limited to housekeeping and maintenance coordination | Not present |
| Pricing model | Flat per-location | Roughly $2 per room per month plus setup fee | Per-seat or subscription-tier, varies |

Flexkeeping's housekeeper location tracking and stay-duration-based auto-scheduling are hotel-specific depth Xenia does not claim to match feature-for-feature. Flexkeeping is purpose-built for the housekeeping department alone. Xenia's wedge is scope: a 400-key property running GM-ops QA across front desk, F&B, security, and property presentation, not housekeeping in isolation, needs one system that spans departments and still keeps its facilities and CMMS tooling in place alongside it. That's a multi-vertical fit, not a hotel-only positioning, and it's worth checking against the same weighted audit scoring model that applies across Xenia's other audit clusters, since the underlying scoring mechanic doesn't change by vertical.

Where do operators see results?

Operators see results in this pattern by replacing paper punch-list clipboard walks and spreadsheet-tracked corrective actions with tablet-based, photo-proof QA audits, while keeping their existing PMS and any existing facilities or CMMS tooling in place. There is no published named hospitality customer case study for Xenia today, so this section describes the applicable product pattern rather than attributing it to a specific property.

What changes in that pattern:

• The GM-ops QA walk moves from a paper clipboard to a tablet, with photo evidence attached at the point of failure instead of written up after the fact.
• The audit score stops being a single blended percentage and starts reflecting weighted severity. A critical failure and eleven cosmetic items no longer look identical on the dashboard.
• The corrective action and the audit finding live in the same record, so a GM or regional ops director can see not just what failed, but whether it's been fixed, by whom, and by when.
• Multi-property hotel groups get a portfolio rollup view, location hierarchy plus scoped permissions, so a regional VP sees flagged items across properties without needing separate spreadsheets per GM. A property GM sees their property. Regional sees every property under them. One account, different scopes, no separate spreadsheets to reconcile.

For hotel groups evaluating this shift at the portfolio level, the broader hotel housekeeping and room operations hub covers the full set of GM-ops and housekeeping-director workflows this QA program connects to, and the hotel maintenance and multi-property hospitality operations hub covers the operational pattern at the industry level. The audit management hub covers the horizontal weighted-scoring and corrective-action mechanics this hospitality application draws from. The American Hotel & Lodging Association resource center is a useful outside reference point for brand-standard and housekeeping benchmarking data that GM-ops programs often calibrate against.

How to set up a hotel QA audit in Xenia

1. Map the department structure. Build the audit template around the eight-category spine, arrival, front desk, housekeeping/turndown, F&B and in-room dining, spa and wellness, security, property presentation, mirroring the categories an LQA or Forbes inspector would also evaluate.
2. Assign point weights. Set critical items (life-safety, security, ADA) at the highest weight, major guest-experience items at mid-weight, and cosmetic items at the lowest weight.
3. Build room-type conditional logic. Configure the template so king, suite, and accessible room types each surface only the questions relevant to that room type, and nullify irrelevant items so they don't penalize the score.
4. Set the passing threshold and escalation rule. Configure what score triggers a "needs attention" flag, and what corrective action deadline applies per weight tier, same-day for critical, 24-48 hours for major, next cycle for minor.
5. Attach photo requirements to failure paths. Configure follow-up questions and required image capture for any failed item, so evidence is captured at the moment of the failure, not reconstructed later.
6. Assign the audit cadence. Daily or shift-based for front desk and housekeeping, weekly for full-property walks, monthly for the comprehensive review, matching the frequency structure that both Marriott's BSA-prep guidance and LQA-prep guidance recommend.
7. Roll out to the property or portfolio. For multi-property hotel groups, apply the location hierarchy so each GM sees their property while regional ops sees the full portfolio rollup.
8. Review the dashboard, not just the completion percentage. Configure the dashboard view around open corrective actions and flagged critical items first, completion percentage second, matching the pattern operators actually want when they're checking for what's about to become a problem.