What is conditional visibility?

Conditional visibility is question-level branching logic on an audit template that hides or shows questions based on attributes of the location being audited or the user performing the audit. It is not a no-code form builder, and it is not AI-driven. It is deterministic branching tied to data Xenia already holds on the location record and the user profile.

Two dimensions of conditional visibility matter to multi-unit operators:

• Location-attribute branching answers "which questions apply to this store?" Drive-thru units see drive-thru questions. Patio units see patio questions. The canonical reference for that dimension is the conditional visibility explainer for location attributes.
• Auditor-role branching answers "which questions can this person answer?" A store manager auditing their own line can score line-check discipline. They should not be asked to score financial-controls questions reserved for a third-party auditor.

Both dimensions pair with nullify scoring. Conditional visibility hides irrelevant questions. Nullify scoring keeps hidden questions from tanking the score. A self-audit cannot be penalized on the 8 governance questions it never rendered.

The structural rationale comes from audit governance theory. The IIA's Three Lines Model separates first-line operational management (the store doing its own daily check), second-line oversight (the DM walk), and third-line independent assurance (the corporate or external auditor). Each line has a different accountability. Each line needs a different question set. Same standard, same template, three rendered subsets.

The C-store chains running conditional checklists for tap-system vs fuel-only sites already work with the location-attribute dimension. Auditor-role rendering is the parallel layer that sits on top of it inside the broader conditional audits collection.

Worked example, conditional visibility in action

A 90-unit chain runs one brand-standards template that carries 50 questions. The auditor's role on their profile decides which subset renders.

| Auditor role | Cadence | Questions rendered | Sample question scope |
|---|---|---|---|
| Store manager (self-audit) | Weekly | 30 daily-discipline | Line check temps, hot-hold timestamps, mat cleanliness, drive-thru window signage |
| District manager (DM walk) | Every 2 weeks | 42 (the 30 plus 12 coaching) | Above, plus training-record completeness, prior corrective-action closure, weekend staffing readiness |
| Corporate or third-party | Quarterly | 50 (all) | Above, plus license display, regulated-record completeness, financial-controls signoff, hazmat manifest |

The store manager scores on 30 questions. Their nullify-scored result is comparable across stores in their region. The DM's 42-question walk includes the same 30 the manager just answered, so the DM can verify those findings, plus 12 the manager is not expected to grade. The corporate auditor sees all 50. The dashboard rolls all three audits up against the same template ID, so the same store can be compared at the question level across auditor roles.

Restaurant worked example

Picture a 90-unit QSR with the cadence above. The store manager's weekly self-audit walks the line, checks hot-hold timestamps, looks at mat cleanliness and drive-thru signage. The biweekly DM walk includes those same 30 items (so the DM can verify against the manager's submission) plus 12 coaching items: training records on the new allergen rollout, closure verification on last cycle's corrective actions, weekend staffing readiness. The quarterly corporate audit adds 8 governance items: COGS variance signoff, license display, allergen-procedure binder, regulated-record completeness.

This cadence aligns with the multi-unit best practice SynergySuite documents in its food-safety audit guide: daily line checks, weekly manager audits, monthly corporate audits, and external health inspections one to four times a year. Bindy's retail audits guide confirms the same shape for retail: weekly self-audits, biweekly DM walks, quarterly corporate. Operators looking for cadence benchmarks by vertical can lean on the audit frequency reference.

C-store worked example

A 60-store fuel/c-store operator runs one site-standards template:

• Closing attendant self-audit (nightly). 18 daily-discipline questions: restroom cleanliness, coffee bar facing, cooler door seals, fuel-spill cleanup, end-of-day cash drop reconciled.
• Area manager walk (every 2 weeks). Those 18 plus 10 coaching items: fuel-pricing execution from the last broadcast, prior corrective-action closure on cooler equipment, training-completion check on the latest poster rollout.
• Corporate compliance walk (quarterly). 18 plus 10 plus 7 governance items: tobacco license display, ABC license display, underground-storage-tank inspection log, hazmat manifest review, fuel-pricing-policy acknowledgment record.

C-store chains with mixed formats (some stores with tap systems, some without) already run one audit and hide irrelevant questions per location group. Auditor-role rendering is the orthogonal dimension layered on top.

The named-customer anchors here are Dave's Hot Chicken, who run a self-audit-then-DM-verify cadence at scale across 321 locations, and Ace Retail Group, who run audit governance across multiple banners with the same role structure. Auditor-role conditional rendering is the architecture that makes "the same template, scored by both" possible without the duplicate-template tax.

How does conditional visibility differ from static audits?

A static audit template renders the same questions to every user, every time. Three failure modes show up immediately in multi-unit ops.

| Approach | Behavior at N/A items | Score impact | Templates required |
|---|---|---|---|
| Static audit, single template | Manager guesses or marks N/A on governance items they cannot grade | Score tanks on items the manager could not answer, or scoring is skewed by N/A handling | 1 generic template, used inconsistently across roles |
| Static audit, separate template per role | Each role gets its own template. Question IDs do not match across templates. | Scores look clean per role, but cannot be compared question by question across roles | 3 templates per audit area, drifting independently |
| Auditor-role conditional audit | Hidden questions are nullified. Each role is scored on the subset it rendered. | Each role's score reflects only the questions that role saw and can answer. | 1 template with role-based visibility rules |

The static-audit workaround the rest of the market uses, separate templates per auditor tier, is documented across the competitor SERP:

• SafetyCulture / iAuditor controls access at the template level (Conduct / Edit / View, per the SafetyCulture access-rules docs). To get auditor-role differentiation, operators duplicate the template per tier and lose comparability between roles for the same store.
• FranchiseSoft explicitly markets two flows: "select a self-audit, conducted by the franchisee on their own business, or a corporate audit, that can be scheduled for a corporate staff member" (FranchiseSoft Franchisee Audit & Compliance Software). Two flows, two templates, two scores.
• GoAudits and BrandWide feed self-audit and corporate audit into a shared dashboard but require separate template setup per the GoAudits franchisee monitoring guide.
• Zenput (Crunchtime) is checklist-and-form-driven without question-level branching by auditor role. Conditional visibility was a documented Zenput migration driver for Graham Enterprise.
• RizePoint sells conditional logic as an expensive add-on and uses penalty-based scoring that punishes N/A items, exactly the failure mode auditor-role rendering plus nullify scoring resolves.

The cost of the duplicate-template workaround is concrete. A 90-unit operator with five audit areas (food safety, brand standards, fuel or site, regulated records, training) maintaining three role-tier copies is running 15 templates instead of 5. When standards change, that is three sets of edits per area. The reports do not reconcile by question, so question-level coaching across roles for the same store is impossible.

This is the conditional visibility value prop in compressed form: same audit template across all 90 units, hidden questions do not penalize, and the underlying question IDs stay constant so DM walks and self-audits compare cleanly. Built for multi-format chains and the audit-role variation those chains already deal with on the floor.

How to set up conditional visibility in Xenia

Five steps. Step 4 emits HowTo JSON-LD against this list.

1. Define the auditor-role hierarchy on the Xenia user record. Three default roles cover most multi-unit ops. Store Manager handles the self-audit. District Manager handles the DM walk. Corporate Compliance or Third-Party handles governance. Set the role on each user's profile so the template can branch on it.
2. Build the master template with every question in one place. For a brand-standards template, that is the full 50 questions: 30 daily-discipline, 12 coaching-and-verification, 8 governance. Group by section (line check, cleanliness, training records, governance) for readability, but keep them in one template.
3. Apply role-based visibility on each question. Daily-discipline questions: visible to Store Manager, District Manager, and Corporate. Coaching-and-verification: visible to District Manager and Corporate. Governance: visible to Corporate only.
4. Enable nullify scoring for hidden questions. This is the pairing feature that keeps the audit fair when questions are hidden. A self-audit is scored against the 30 questions the Store Manager saw, not penalized against the 20 they never rendered.
5. Schedule the audit with the appropriate auditor role. Weekly self-audit, biweekly DM walk, quarterly corporate audit. The auditor's role on their profile drives which questions render at audit time. The dashboard rolls all three up against the same template ID, so scores compare cleanly across roles for the same store.

Optional sixth step: route corrective actions differently per auditor role using conditional response routing. A self-audit failure on a critical line item escalates to the DM. A DM-walk failure on a governance item escalates to corporate compliance.

Where do operators see results?

The dashboard view is the closing argument. Three operator-results scenarios make it concrete.

Restaurant ops director, Monday morning rollup

A regional VP of ops opens her Monday dashboard. The "Brand Standards by Auditor Role" widget shows three views for the same 90-unit chain. Self-audit completion and score by store comes up first: 87 of 90 stores completed last week's self-audit, average 91% on the 30-question subset, three stores flagged. Next view: DM walk score versus self-audit score for the same store over the last 14 days. Twelve stores walked. Nine show DM scores within 3 points of the self-audit, healthy calibration. Three show the DM walk more than 10 points below the self-audit, calibration drift, the manager is over-scoring and the DM needs to coach. Third view: open corrective actions from corporate audits over the last 90 days. Eight governance items still open across five stores, license display backlog leading the list.

The DM-walk-versus-self-audit comparison view is only possible because both audits target the same template against the same store. With separate templates per auditor tier, this comparison view does not exist. Dashboards on issues, not just completion percentage, are the differentiator: the view shows where the next failure is forming, not just whether yesterday's tasks got done.

C-store area manager, biweekly walk prep

A C-store area manager opens her tablet before Tuesday's round of walks. The pre-walk view shows the last self-audit per store with photos and timestamps from the closing attendant. Her walk template renders the 18 self-audit questions (so she can verify the closing attendant's findings) plus the 10 coaching items: training-record check on the new allergen poster rollout, prior CAP closure on cooler equipment, fuel-pricing-policy acknowledgment evidence. Her walk takes 40 minutes per store instead of 75, because she is not re-asking what is already in the system.

Franchise compliance officer, quarterly governance review

A franchise compliance officer (primary persona for this page) prepares the quarterly governance review. The corporate-audit-role rendering surfaces the 8 governance questions per store: license display, regulated-record completeness, financial-controls signoff, hazmat manifest. The rollup shows pass-rate by question across all 90 units, ranked by risk. The 42 daily-discipline and coaching questions she does not grade are not rendered for the corporate audit walk, so her tablet is not cluttered with items the franchisee already self-reported.

The migration story behind this design is Graham Enterprise, who migrated from Zenput to Xenia on the conditional visibility and facilities workflow drivers. Zenput's audit logic could not handle the question-by-question branching their multi-format c-store operation needed. Dave's Hot Chicken, at 321 locations, run the same self-audit-then-DM-verify cadence at scale. Their primary migration drivers from RizePoint were weighted scoring and Bluetooth thermometers (covered in the weighted scoring explainer), but the auditor-role pattern is part of the same operating architecture. Ace Retail Group apply the same role pattern across multiple banners after their migration from Bindy. None of these customers have a published customer story page yet, so they are named here without a profile link.