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. See the deeper write-up on conditional visibility for multi-format operators and 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's 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 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.

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. 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 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.

**

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 plus a fourth for ghost kitchens. Every brand standard change has to be applied four times. A conditional audit collapses the maintenance to one template. Zenput supports basic branching, but the form-capped pricing punishes the exact operator pattern conditional logic is supposed to consolidate. 

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 full positioning lives on the Xenia vs Zenput comparison.

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

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.
2. Build the audit template once. Add the trunk questions that fire at every store: food safety, hand-wash, labor compliance, opening readiness.
3. Group the branched questions by format. Drive-thru section (order board, headset audio, lane timing, window service), dine-in section (lobby, dining-room turn time, condiment station, restrooms), ghost-kitchen section (courier hand-off, tablet status, bag sealing).
4. Apply the conditional rule to each section. Tie each section to its matching service-format condition.
5. Turn on nullify scoring. Hidden questions count for zero in the score denominator.
6. Wire the corrective-action workflow. A failed question fires a follow-up that captures what went wrong, requires a photo, and assigns the task to the store manager with a deadline. Escalation routes to the DM at 24 hours if not closed.

The setup runs in an afternoon for an existing brand-standard SOP. Operators with a paper SOP can upload the PDF and generate the conditional structure automatically. The follow-up question and photo capture pattern is documented in the Bluetooth thermometer setup guide for restaurants.

Where do operators see results?

The pattern shows up wherever a chain runs more than one physical format under one brand standard. A drive-thru-heavy QSR brand expanding into mall and nontraditional locations hits this immediately: a mall kiosk doesn't have a drive-thru lane, a combo store has both, and a single static checklist either bloats with irrelevant questions or misses format-specific ones entirely.

The same gate-and-branch logic applies outside restaurants too. A c-store running tap systems at some locations and not others, or a hotel chain with pool versus no-pool properties, hits the identical wall.

For multi-unit QSRs evaluating the pattern, see QSC audits explained for how the audit, scoring, and corrective-action loop works for quality, service, and cleanliness, and audit frequency by vertical for the cadence question any conditional template has to support.