7.6 Variance Requests & Permitting Determination

7.6 Variance Requests & Permitting Determination

The Conducting Compliance Review duty accounts for 12% of the REHS/RS exam (24 scored items). Five sub-tasks drive that score: conduct plan review (8 items), review HACCP plans (6 items), evaluate variance requests (2 items), determine permitting status (3 items), and verify compliance with regulations (5 items). Plan review and HACCP are covered in section 7.3, and compliance verification in 7.4. This section addresses the two administrative sub-tasks that determine whether a facility is formally authorized to deviate from code (variance) and whether it is authorized to operate at all (permitting).

Variance Requests

A variance is a written, legally binding authorization issued by the regulatory authority allowing a facility to deviate from a specific code requirement. The FDA Food Code, NSF standards, and most state codes contain specific variance provisions that allow innovation while protecting public health.

When a Variance Is Required

The FDA Food Code explicitly requires a variance (and often a HACCP plan) before a facility may use certain processes that the code otherwise restricts:

• Smoking or curing food as a method of preservation rather than for flavor enhancement.
• Using food additives or adding components such as sulfites to delay pathogen growth.
• Custom processing animals (e.g., dressing game animals in a retail facility).
• Operating a reduced oxygen packaging (ROP) method that is not otherwise permitted.
• Sprouting seeds or beans.
• Preparing food by another method determined by the regulatory authority to require a variance.
• Displaying or holding food under conditions not otherwise allowed (e.g., unpackaged time/temperature control for safety foods displayed for longer than the standard 4-hour limit).
• Using a water supply, sewage disposal system, or waste management approach that does not comply with the code.

Variance Application Requirements

A complete variance application must include:

1. Statement of the proposed deviation: Identify the specific code section from which the facility seeks relief.
2. Justification: Explain why the deviation is necessary (economic, operational, or technical reasons).
3. Proposed alternative: Describe the specific alternative method, process, or equipment that will provide an equivalent level of public health protection.
4. Supporting data: HACCP plan, scientific studies, challenge studies, process authority letters, equipment specifications, or other evidence demonstrating equivalence.
5. Monitoring and verification plan: How the facility will monitor the alternative and how the regulator will verify compliance with the variance conditions.

Variance Review Standards

The regulatory authority evaluates the request against a documented standard:

• Equivalence: Does the alternative provide the same level of public health protection as the code requirement it replaces? The applicant, not the regulator, bears the burden of proof.
• Scientific basis: Is the supporting data from a credible source (peer-reviewed study, process authority, recognized guideline)? Anecdotal claims do not meet this standard.
• Operational feasibility: Can the facility consistently implement and monitor the alternative?
• Precedent consistency: Is the decision consistent with prior variances for similar requests, or is there a documented basis for differentiation?
• Reversibility: Can the variance be revoked if the facility fails to comply with conditions?

Variance Decision Outcomes

A variance is not a permanent waiver. It must specify a review or expiration date, typically 1 to 3 years, and is non-transferable to a new owner or location.

Documentation and Appeal

The regulatory authority must document the technical basis for the variance decision in writing and provide it to the applicant. An applicant denied a variance is entitled to due process, typically a hearing before the health officer or an administrative tribunal.

Permitting Status Determination

Permitting status determination is the verification that a facility holds a valid, current operating permit covering its specific operations before an inspection proceeds. While plan review (section 7.3) precedes construction and pre-operational inspection, permitting status determination is the ongoing verification that authorization has not lapsed, been suspended, or been exceeded in scope.

What Permitting Status Verification Includes

1. Validity: Confirm the permit has not expired. Most food establishment permits are annual; some permits (e.g., body art, septic installer) are biennial. Expiration triggers immediate unpermitted operation.
2. Scope: Confirm the permit covers the operations actually being conducted. A facility permitted as a retail bakery may not operate a full restaurant without permit modification.
3. Ownership / change of operator: A permit is typically non-transferable. A change in ownership or operator requires a new permit application, plan review (if applicable), and a new pre-operational inspection.
4. Conditions: Confirm any permit conditions (e.g., 'no raw oyster service', 'limited menu only') are being met.
5. Outstanding enforcement: Confirm the permit is not under suspension or revocation order.

Common Permit Types in Environmental Health

Permitting and Inspection Workflow

The first step in any routine inspection is to verify permitting status:

1. Request the permit: Ask the person in charge to produce the posted or filed permit.
2. Verify validity: Check the expiration date and any current conditions.
3. Cross-check with operations: Confirm the facility's actual operations fall within the permit's scope.
4. Document the status: Note the permit number, issuance date, expiration date, and any conditions in the inspection report.
5. Act on discrepancies: If the permit is expired, suspended, or out of scope, follow the enforcement hierarchy in section 7.4: informal notice for first-time administrative lapses; formal notice of violation or operating permit suspension for chronic or willful non-compliance.

Interaction Between Variance and Permitting

A facility with an active variance must hold a permit that reflects the variance. The permit will typically note 'Variance approved for [specific process] on [date]; expires [date]; conditions: [list].' When the variance expires, the permit must be re-issued or amended to reflect the standard code requirement, or the variance must be renewed.

Enforcement for Permitting Violations

• Operating without a permit: A strict-liability violation in most jurisdictions. Sanctions range from civil penalties to immediate closure.
• Operating beyond permit scope: Treated as unpermitted operation for the activities outside scope.
• Expired permit: Most codes provide a grace period (often 30 days) for renewal; after the grace period, the facility is unpermitted.
• Suspended permit: Operation during a suspension period is a separate, more serious violation.

Record-Keeping

Both variance decisions and permitting determinations must be retained as public records, subject to applicable open-records laws. Records must include the application, supporting documentation, decision, technical basis, conditions, and any subsequent enforcement actions. These records support consistency in future decisions and provide the audit trail required when a decision is challenged.