What is conditional visibility?

Conditional visibility is the audit feature that shows or hides questions based on a location attribute or a prior answer. A drive-thru-only store sees the drive-thru section. A dine-in-only store sees the lobby section. A combo store sees both. The auditor never wastes time skipping irrelevant questions, and the score reflects what the location actually does.

The feature pairs with nullify scoring, which makes hidden questions count for nothing. Without nullify, a hidden question still pulls the denominator down and produces false negatives. With it, a drive-thru-only unit and a dine-in-only unit can both score 100% on the same brand standard. See the deeper write-up on conditional audits for multi-format operators and on how nullify scoring pairs with conditional visibility to stop N/A items from tanking the score.

QSR operators care because format variation is the defining audit problem of 2026. Chick-fil-A's Elevated Drive-Thru has no dining room. Taco Bell Defy runs four lanes with no lobby. McDonald's still anchors the dine-in plus drive-thru combo. Wingstop opened the ghost-kitchen wave, then rebalanced to physical stores. A single audit template that branches is the only way to score apples-to-apples across the four formats. Xenia's conditional logic engine handles question-level branching natively, where Zenput requires parallel forms per format and SafetyCulture asks the operator to build the logic by hand.

Same audit template for 100 franchises, but units with drive-thrus see drive-thru questions, units with patios see patio questions, units with espresso bars see espresso bar questions. That is the operator promise. The competitor gap is what makes it a migration trigger, covered in the worked example next.

Worked example, conditional visibility in action

A 150-unit QSR chain runs three formats. Drive-thru only. Dine-in only. Combo stores with both. The audit template carries 38 questions. The format gate on the location record fires the right branch.

| Store profile | Condition on location record | Question groups shown | Question groups hidden |
|---|---|---|---|
| Drive-thru only | Service format is drive-thru only | Order board cleanliness, headset audio, drive-thru timing, window service, car-corral cleanliness | Lobby cleanliness, dining-room turn time, condiment station |
| Dine-in only | Service format is dine-in only | Lobby cleanliness, dining-room turn time, condiment station, self-order kiosk, restrooms | Order board cleanliness, headset audio, drive-thru timing, window service |
| Combo store | Service format is drive-thru plus dine-in | All drive-thru questions plus all dine-in questions | None at the format layer |
| Ghost kitchen | Service format is delivery only | Courier hand-off zone, tablet status, bag-sealing protocol, order-staging shelf labeling | Lobby, drive-thru, customer-facing service |

Drive-thru-only stores see 22 questions. Dine-in-only stores see 24 questions. Combo stores see all 38. The food-safety, hand-wash, and labor-compliance questions sit on the trunk of the template above the gate, so every store answers them. The format-specific questions appear automatically based on the store profile.

The 2025 Intouch Insight Drive-Thru Study, based on 165 mystery shops per brand across 13 chains, anchors the drive-thru question set. Total service time averaged 4 minutes 15 seconds, up 10 seconds year over year. Clear speaker systems cut wait times by 54 seconds. Eliminating order repetition saved another 1 minute 25 seconds (Intouch Insight 2025 Drive-Thru Study). A drive-thru audit that captures three pulls (greet time, OEPE, total service time) and scores headset clarity is the operational layer behind those benchmarks.

The dine-in branch surfaces a different question set. Lobby cleanliness, dining-room turn time, condiment-station hygiene, restrooms with an hourly cleaning-log signature, and self-order kiosk status. The cleaning audit checklist from SafetyCulture's restaurant library catalogs the same surface, but the operator-grade version pairs it with a corrective task on every fail. Pair this section with the patio vs no-patio conditional audit pattern for the seating-format twin of this problem, and with weighted audit scoring with critical-item thresholds for the scoring layer that sits underneath.

How does conditional visibility differ from static audits?

A static audit asks every question of every store. A conditional audit branches by store profile and surfaces only the relevant subset. The difference compounds at scale.

| Attribute | Static audit | Conditional audit |
|---|---|---|
| Approach | One form, every question fires at every store | One form, branches at the question level based on location attributes or prior answers |
| Behavior at N/A items | Auditor marks N/A, manually skips the section, or leaves it blank | Section auto-hides. Auditor never sees the question |
| Score impact | N/A items can still hurt the denominator unless the platform supports nullify | Hidden questions are excluded from the score, every store can hit 100% on the brand standard |
| Template count required | Three to four parallel forms per format variation | One form for the entire portfolio |

A 150-unit chain on a static-audit platform maintains three audits (drive-thru only, dine-in only, combo) and a fourth for ghost kitchens. Every brand standard change has to be applied four times. Every score report has to be reconciled across four data sets. The DM walking 12 stores in a region is comparing four different denominators.

A conditional audit collapses the maintenance to one template. The brand standard change is made once. The data lands in one place. The DM compares scores on the same basis across formats. Zenput supports basic branching (build different checklists by location type or daypart), but the form-capped pricing punishes the exact operator pattern that conditional logic is supposed to consolidate. The Xenia vs Zenput honest comparison walks through the displacement math in detail. SafetyCulture offers logic fields with up to 40 nested conditions, but the operator engineers the workflow and the corrective-action closure lives in a separate tool.

The wedge is the bundle: question-level branching plus native work orders plus frontline comms plus corrective-action workflows in one platform.

How to set up conditional visibility in Xenia

The setup is the same pattern every operator follows, regardless of vertical. The numbered steps below assume the QSR drive-thru vs dine-in use case, but the same logic applies to a c-store with tap systems or a hotel with pool versus no-pool properties.

1. Define the gate on the location record. Add a format attribute (drive-thru only, dine-in only, combo, ghost kitchen) to every store profile. The attribute is the single source of truth that drives every branch downstream.
2. Build the audit template once. Add the trunk questions that fire at every store: food safety, hand-wash, labor compliance, opening readiness. Place them above the gate.
3. Group the branched questions by format. Create a drive-thru section (order board, headset audio, lane timing, window service), a dine-in section (lobby, dining-room turn time, condiment station, restrooms), and a ghost-kitchen section (courier hand-off, tablet status, bag sealing).
4. Apply the conditional rule to each section. Tie the drive-thru section to "service format equals drive-thru only or combo." Tie the dine-in section to "service format equals dine-in only or combo." Tie the ghost-kitchen section to "service format equals delivery only."
5. Turn on nullify scoring. Hidden questions count for zero in the score denominator. A drive-thru-only store and a dine-in-only store can both hit 100% on the same brand standard.
6. Wire the corrective-action workflow. A failed question fires a follow-up that captures what went wrong, requires a photo of the corrective action, and assigns the task to the store manager with a deadline. The escalation routes to the DM at 24 hours if the task is not closed.

The setup runs in an afternoon for an existing brand-standard SOP. Operators who already have a SOP PDF can upload it to the AI Template Agent and get the conditional structure generated automatically, which compresses franchise rollout from weeks to days. The follow-up question and photo capture pattern is documented in the broader conditional audits overview and in the Bluetooth thermometer setup guide for restaurants pairing automatic temp logging with the same conditional pattern.

Where do operators see results?

The clearest QSR result is Dave's Hot Chicken. The chain scaled from a single LA parking-lot pop-up to more than 300 locations globally by late 2025, with Roark Capital taking a majority stake at a reported $1B valuation in June 2025 (CNBC, Roark Capital invests in Dave's Hot Chicken, Restaurant Technology News). Systemwide sales for 2025 are projected around $1.2B. CEO Bill Phelps has guided to a 4,000-unit long-term ceiling across mall, dine-in, drive-thru, and international formats.

Dave's migrated from RizePoint, and the migration drivers were specific: weighted scoring (critical food-safety items at 10 points, cosmetic items at 1), Bluetooth thermometer integration across every walk-in and hot-hold and line station, and corrective-action workflows that close with a deadline and escalation. The format expansion from urban dine-in to combo stores to nontraditional mall locations made the conditional structure essential as the audit template had to flex per format without breaking the score. Trigger follow-up questions and required image capture based on answers: if the temp is out of range, the audit captures what went wrong and a photo of the corrective action. Audit branches at the question level. Evidence is captured at the moment of failure, not after.

The displacement opening for Zenput's installed base follows the same architecture. YATCO migrated from Zenput to Xenia for conditional visibility and the facilities workflow that Zenput's checklists-only architecture does not cover. Graham Enterprise migrated from Zenput to Xenia in the C-store vertical with the same pattern. The migration thesis is consistent: a multi-format operator hits the form-cap pricing wall and the parallel-form maintenance burden, and the move to a single conditional template plus native work orders plus comms is the consolidation play. The full positioning lives on the Xenia vs Zenput honest comparison.

For multi-unit QSRs evaluating the pattern, the restaurant task management hub collects the operator-side workflows: weighted scoring, conditional logic, Bluetooth thermometers, corrective actions, and the daily ops checklists that sit underneath. The category-level guidance on audit frequency by vertical anchors the cadence question (daily shift checks, weekly zone deep-dives, monthly internal audits, quarterly food-safety) that any conditional template has to support. For the National Restaurant Association's industry framing, the NRA State of the Industry covers the operating context that makes audit consolidation a margin lever.