What is conditional visibility?

Conditional visibility is the audit-template feature that shows or hides question groups at runtime based on metadata on the location record or the auditor's prior answers. In a franchise tier audit, the metadata field is franchisee tier, and the audit a corporate unit sees, the audit a franchisee sees, and the audit a licensee sees are all rendered from one master template with different branches firing.

The underlying problem it solves is template sprawl. Without conditional logic, a franchisor running corporate, franchisee, and licensee tiers ends up maintaining three separate audit templates (or six, once you split by store format), and any change to brand standards forces a parallel edit in every template. Conditional visibility consolidates that into one template with rules, change the question once, every tier sees the change, no parallel maintenance.

Conditional visibility lets you ask different questions at different locations without penalizing stores for N/A items, the "patios vs. no-patios" problem solved. One audit template handles 100+ format variations. The pattern is documented in SafetyCulture's logic-fields reference for any prior-answer trigger, and it pairs naturally with nullify scoring, the rule that hidden question groups don't deduct from the audit score. Without nullify scoring, a 60-question Seasoned-operator audit would post a 30% score because 140 hidden questions read as zero. With it, a Seasoned audit and a New-operator audit can both score 100% off the same template. For background on the full audit framework these features sit inside, see the Xenia conditional audits hub and the weighted audit scoring with critical-item thresholds primer.

Worked example, conditional visibility in action

Picture an 80-unit QSR system with three tiers on the location record: 22 corporate-owned, 48 franchisee, and 10 licensee (small-format airport and stadium kiosks). The franchisor maintains one master template with 200 questions across nine groups, food safety, line check, opening procedures, brand-mark placement, drive-thru speed, patio cleanliness, training-completion verification, POS configuration, and active-promo execution. Conditional rules render a different effective audit per tier:

| Audit attribute | Corporate unit (Seasoned, 92% last score) | Franchisee unit (New, 60 days open) | Licensee kiosk |
|---|---|---|---|
| Question count rendered | 55 (exception audit) | 180 (full foundation audit) | 38 (limited-format audit) |
| Cadence | Quarterly | Weekly during 0-90, bi-weekly through month 6 | Monthly |
| Major-item scoring weight | 5 points | 3 points (coaching tier) | 5 points |
| Critical-item SLA | 24h, photo, GM closes | 24h, photo, GM + franchisor field manager notified | 24h, photo, licensee operator + corporate notified |
| Hidden groups | Foundation drills, POS configuration, training verification | None | Drive-thru, patio, full-line back-of-house |

The rule logic on the template reads roughly like this:

| Tier | Trigger condition | Question groups shown | Question groups hidden |
|---|---|---|---|
| Corporate | Last audit score 90 percent or higher | Food safety, line check, active promo, prior weak items | Foundation drills, POS config, training verification |
| Franchisee | First 4 months open | All question groups | None |
| Licensee | Kiosk store format | Food safety, brand mark, active promo, kiosk-specific block | Drive-thru, patio, full back-of-house |

Pull the rendered audits across all 80 stores into a rollup and the dashboard reflects what each tier actually does, not what the template thinks every location should be doing. A licensee kiosk that aces its 38 questions posts a 100% score the same way a corporate unit acing 55 exception questions does. Both numbers are honest. A location without a patio doesn't get dinged on patio cleanliness. A unit without a fryer doesn't fail on fryer temp logs. For a sibling pattern that branches on physical store format instead of franchisee tier, see the patio vs. no-patio conditional audit walkthrough; for cadence triggered by season or weather, see seasonal conditions conditional audits. Per GoAudits' franchisee monitoring research, 19.3% of franchisees now run multiple locations, which means tier logic isn't just "corporate vs. franchisee" anymore; it has to handle multi-unit franchisee operators with mixed-maturity portfolios under one entity.

How does conditional visibility differ from static audits?

Static audits ask every question at every store at the same cadence; conditional audits branch the question set, the cadence, and the scoring weights off location metadata. The difference shows up in three places: how N/A items behave, how the score reads, and how many templates the franchisor maintains.

| Attribute | Static audit | Conditional audit (Xenia) |
|---|---|---|
| Behavior at N/A items | Question shown anyway, often marked "N/A", sometimes still deducts | Question hidden at render time; nullify scoring removes it from the denominator |
| Score impact at format mismatch | Underscores stores missing irrelevant equipment | Score reflects only what the location is supposed to do |
| Templates required for 3 tiers × 4 formats | Up to 12 parallel templates | One master template with conditional rules |
| Update cycle when brand standards change | Edit each template; reconcile drift | Edit once; every tier inherits |
| Auditor experience | Same form regardless of tier | Form length and depth match the audit's purpose |

The static-audit pattern is what most franchise systems used before conditional logic became standard. It's still the default in tools that lack per-location branching, and it's the gap that drove operators away from older platforms. For the side-by-side on the displacement target, see the Xenia vs. Zenput comparison; for the scoring half of the equation, see weighted audit scoring explained. Per Operandio's franchise audit research, operators replacing flat checklists with branched workflows cut compliance paperwork from 20 hours per week to 3, a 7x reclaim that only materializes when the audit stops being uniform across tiers.

How to set up conditional visibility in Xenia

Tier-conditional audits in Xenia are a configuration project, not a software project. A multi-unit franchisor on the platform can ship a working tier-conditional model in roughly 30 days. The working sequence:

1. Define the tier matrix on the location record. Add franchisee tier (corporate, franchisee, licensee), franchisee maturity (New 0-90, Ramping 3-12 mo, Seasoned), last audit score, store format, and risk flags as fields on every location. The matrix is the source of truth for every conditional rule downstream.
2. Build the master audit template once. All question groups live on a single template, food safety, line check, opening procedures, brand-mark placement, drive-thru, patio, training verification, POS configuration, active promo. Conditional rules decide which groups render per audit run.
3. Wire the show/hide rules per group. For each question group, set who sees it in plain English. An exception-style group shows for corporate and franchisee units classified Seasoned with a last audit score of 90 percent or higher. Foundation drills show only for units in their first 90 days. The drive-thru speed block shows only for units with a drive-thru on file. The platform handles the field-matching internally; the operator describes the rule, not the syntax.
4. Wire the scoring weights per tier. Critical items hold at 10 points across every tier (food safety and life safety don't get a coaching discount). Major items run at 5 points for Seasoned operators and 3 points for New operators. Minor items suppress entirely on the Seasoned-quarterly exception audit and re-enable when score drops below 90%.
5. Wire the corrective-action SLAs. Severity × tier maps to due-date offset and notification list. Critical = 24 hours and photo verification at every tier. Major = 72 hours for New, 7 days for Standard, 14 days for Seasoned-High. Minor = 14 to 30 days, sometimes logged-only for the top tier.
6. Schedule the cadence engine, then publish. New = weekly, Ramping = bi-weekly, Seasoned-Standard = monthly, Seasoned-High = quarterly, Underperformer = bi-weekly intensive. Risk-event triggers (health-dept finding, complaint cluster, GM change) override the standing cadence with a 7-day spot audit on the affected risk area.

The pitfall every operator hits: tiering the audit without automating the cadence. If a human is manually deciding each week which stores get which audit, the system collapses by month four. The tier classification has to be a property of the location record, and the cadence has to fire off it without human gating. For the corrective-action half of the loop, read the corrective action SLA framework, that's the cross-cluster piece that turns audit findings into closed work.

Where do operators see results?

Tier-conditional audits move the numbers franchisor leadership reports to the executive committee, auditor hours, audit scores, corrective-action closure rate, and field-manager throughput. The named outcomes:

• Tacala Companies (largest Taco Bell franchisee, 350+ units): per the Crunchtime / Zenput Tacala case study, a 6% lift in brand audit scores since 2020 and tens of thousands in paper-checklist savings after replacing uniform checklists with branched ops-execution workflows.
• Aggregate platform results (Crunchtime / Zenput operations execution): operators on a branched-audit platform report a 20% improvement in audit scores, a 24% reduction in compliance issues, 5+ hours per week reclaimed per store employee, and 8+ hours per week reclaimed per field manager.
• Corrective-action closure: per the Xenia Brand Standards Audit Guide, automated tier-routed corrective-action workflows close more than 85% of findings inside 14 days, versus less than 40% inside 30 days when follow-up runs on manual email. Audit failure leads to an automatic corrective task, tracked to resolution, with escalation if not addressed by deadline. Most platforms collect audit data; few drive it to closure.
• Xenia customer base: Dave's Hot Chicken, Refuel, Huck's, H&S Energy, and Ace Retail Group are named multi-unit operators running conditional-audit and ops-execution patterns on Xenia. Refuel and Huck's are the c-store reference cases; Ace Retail Group is the multi-banner retail reference, with each banner mapped to its own tier on the location hierarchy.

The legal posture matters too. Per the FTC Franchise Rule Compliance Guide and the FTC's deep dive on the FDD, franchisors have broad latitude to set audit cadence as long as the tier definitions are documented in the operations manual (Item 14) and applied consistently. Critical food-safety findings still need to align with FDA Food Code imminent-health-hazard expectations, which is why every tier holds the same 24-hour critical SLA. Tier logic varies cadence and depth; it never varies the contractual remedy. For a sibling explainer on the audit framework that anchors all of this, see the conditional audits overview.