Virginia Beach Food Safety Consultant
HACCP, FSMA Preventive Controls, shellfish sanitation and SQF support for Virginia Beach seafood processors, cold storage operators, specialty food makers and multi-unit hospitality groups — built around VDACS and VDH jurisdiction, and rehearsed before the inspector arrives.
Virginia Beach sits at the point where a working seafood coast, the Port of Virginia's cold chain, and a year-round hospitality economy all meet. That mix means a single city can contain a clam shucking house answering to the National Shellfish Sanitation Program, a refrigerated warehouse answering to FSMA Preventive Controls, and a 40-unit restaurant group answering to the Virginia Department of Health — each with a different inspector, a different rulebook, and a different definition of an acceptable record.
We build the food safety programs that hold up under whichever of those authorities walks through your door. That means writing HACCP and Preventive Controls plans that match what your process actually does, getting your shellstock tagging and time-to-refrigeration controls defensible, and rehearsing the audit so the first person to test your system is us, not a regulator.
What compliance costs a Virginia Beach operation before anyone organizes it
Most coastal food businesses are not short on effort. They are short on structure — the same temperature check gets recorded three times in three places, and none of the three is the one the auditor asks for.
- 21 CFR 123
- The seafood HACCP rule
- Mandatory for fish and fishery products, separate from Preventive Controls
- 90 days
- Shellstock tag retention
- Required under the NSSP Model Ordinance
- 24 hrs
- Traceability retrieval target
- What buyers and regulators increasingly expect
- 3 agencies
- Potential jurisdictions
- VDACS, VDH and FDA can all have a claim on one city block
A typical mid-sized Hampton Roads processor spends roughly this much staff time each year on food safety administration that is duplicated, hand-transcribed, or recreated from memory before an audit.
One city, three regulators, and the confusion that produces
The first question we ask a new Virginia Beach client is rarely about their process. It is about who actually inspects them — because a surprising number of operators cannot answer it cleanly, and the wrong answer produces the wrong food safety plan.
In Virginia, the Department of Agriculture and Consumer Services (VDACS) inspects most food manufacturing, processing and warehousing. The Department of Health (VDH) inspects restaurants, caterers and other food service establishments under the Virginia Food Regulations, which are built on the FDA Food Code. And the FDA sits above both, enforcing FSMA Preventive Controls and the seafood HACCP rule at 21 CFR Part 123 for facilities that ship interstate. A Virginia Beach business that processes shellfish, warehouses it cold, and also runs a retail counter can genuinely touch all three.
The practical consequence is duplicated and contradictory paperwork. We regularly find operations running a Food Code-style temperature log next to a HACCP monitoring record, tracking the same cooler, with different limits written on each. When an FDA investigator asks which document represents the actual critical limit, there is no good answer — and that gap is what turns a routine inspection into an observation on a Form 483.
The fix is not more paperwork. It is deciding, deliberately and in writing, which regulatory framework governs each part of your operation, then building one set of records that satisfies it. Everything else we do for a client in Virginia Beach follows from getting that decision right first.
Co-Founder & Chief Food Safety Officer
Led by a food safety officer who has been on both sides of the inspection
Dave Seddon leads our consulting practice and has spent his career building food safety systems that survive contact with real production schedules. That experience matters most in a market like Hampton Roads, where a plan written for a textbook facility falls apart the first time a boat lands late and the whole day's schedule compresses.
His approach is deliberately unglamorous. Start with the process flow as it genuinely runs, including the shortcuts people take when they are behind. Identify the hazards that are reasonably likely to occur in that real process. Write controls that a supervisor on a Saturday shift can actually execute and record. Then test them under pressure before an auditor does.
For Virginia Beach clients that usually means walking the floor during an actual production run rather than a scheduled tour, sitting with the people who complete the logs, and finding out where the written procedure and the real one diverge. That gap is almost always where the audit finding is waiting.
Shellfish sanitation is a separate regime, and it is unforgiving about time and tags
Virginia Beach clam and oyster operations sit under the National Shellfish Sanitation Program, administered in Virginia through the Department of Health's Division of Shellfish Safety. It is a different animal from FSMA, and operators who assume their Preventive Controls plan covers it are usually wrong.
The NSSP Model Ordinance governs the chain from growing water to the plate. Harvest areas are classified, and product may only be taken from waters approved at the time of harvest — a classification that can change after rainfall or a treatment plant event. Shellstock must carry a tag identifying the harvester, the harvest area and the date, and those tags must be retained for 90 days after the container is emptied. Time-to-refrigeration limits apply from the moment of harvest, tightening in warm months when Vibrio risk climbs.
Where operations fail is rarely the concept. It is the handoff. A tag gets separated from its lot during shucking. A truck sits at a dock and nobody logs the time. A retail buyer asks for the harvest date on a specific case and the answer takes two days to assemble from paper in three locations.
We rebuild that chain so identity survives every transfer — tag capture at receiving, lot identity carried through shucking and packing, time-and-temperature recorded at each handoff, and a retrieval process that answers a buyer's question in minutes. For dealers seeking or holding a place on the Interstate Certified Shellfish Shippers List, that discipline is the difference between keeping the listing and losing the market it opens.
The four controls that decide a shellfish inspection
Regulators and buyers rarely dispute whether you understand shellfish sanitation. They test whether you can prove it on a specific lot, on a specific day, without warning.
Four controls carry most of that weight. Harvest area classification determines whether product could lawfully be taken at all, and it changes with rainfall and treatment plant events. Shellstock tagging preserves the identity that makes every later record meaningful. Time-to-refrigeration limits govern Vibrio risk from the moment of harvest, tightening through the warm months. And tag and shipping record retention — 90 days after the container is emptied — is what lets you answer a question about a case you shipped two months ago.
When we assess a Virginia Beach dealer, we test each of these against a real lot chosen at random rather than reviewing the procedure in the abstract. That is the same method a Division of Shellfish Safety inspector will use, and it is the only way to find out whether identity actually survives every handoff in your operation.
What a defensible Part 123 plan actually contains
A seafood HACCP plan under 21 CFR Part 123 is judged on whether it addresses the hazards genuinely reasonably likely to occur in your process — not on how thick the binder is.
For Hampton Roads processors, the recurring hazards are specific. Histamine formation in scombroid species such as tuna and mahi is a decomposition hazard controlled almost entirely through temperature at receiving and in storage, which is why a 40°F receiving limit for fresh fish carries so much weight. Pathogen growth from temperature abuse runs through the whole process. Aquaculture drug residues and environmental chemical contaminants are supplier-side hazards controlled through receiving verification rather than anything you can do on the floor.
Sanitation monitoring sits alongside the plan rather than inside it, covering the eight sanitation conditions the rule requires you to monitor and record. And traceability underpins all of it: if you cannot assemble the records for a given lot quickly, every control above becomes an assertion rather than evidence.
We build the plan against your actual species and process, then verify it the way an FDA investigator would — by pulling records for a date at random and following the lot in both directions.
Where cold storage programs break, and what closes the gap
Virginia Beach's proximity to the Port of Virginia makes cold storage and refrigerated distribution a defining part of the local food economy — and a distinct compliance problem.
Temperature control is the obvious requirement, but it is not usually where operations fail. They fail on the excursion. A chiller drifts overnight, an alarm fires, someone makes a sensible decision at 2am, and nothing is written down that explains what the product experienced or why it was released. Months later a buyer asks, and there is no defensible answer.
The second failure is identity. Product moves between racks, trailers and facilities, and lot identity degrades at every transfer until a recall request cannot be answered without physically walking the warehouse. Under FSMA Section 204, that is no longer survivable: covered foods require Key Data Elements captured at each Critical Tracking Event, retrievable in a sortable electronic format within 24 hours.
We build excursion procedures that force a documented decision, and a traceability structure that carries lot identity through every movement — then we test it with a timed mock recall rather than assuming it works.
The Virginia Beach food economy, sector by sector
Virginia Beach does not have one food industry. It has several, and they fail audits for entirely different reasons. A consultant who treats them interchangeably will write a plan that fits none of them.
What follows is how we scope work across the sectors that actually operate here — from the seafood houses working the Lynnhaven and the Chesapeake, through the refrigerated warehousing that moves product across the Port of Virginia, to the specialty producers and hospitality groups that make up the visible face of the city's food economy. Each section describes the governing framework, the control that most often breaks, and what we build to close it.
The common thread is proximity. Harvest waters, processing floors, cold storage and dining rooms sit within a few miles of each other, and product routinely moves between all four inside a single day. That compresses the margin for error: a time-to-refrigeration failure on the dock becomes a cold chain problem in the warehouse and a liability on the plate. Programs written for one link in that chain rarely survive contact with the next.
The sectors that define food production in Virginia Beach
Six areas where we do the most work in Hampton Roads, and the specific control failure we most often find in each.
Seafood processing and shucking
Finfish, clam and oyster operations fall under the seafood HACCP rule at 21 CFR Part 123, which requires a hazard analysis specific to fishery products — histamine in scombroid species, natural toxins, aquaculture drug residues and pathogen growth from temperature abuse. The failure we find most often is a plan copied from a template that names hazards the facility does not have while missing the one it does. We rewrite the hazard analysis against the actual species and process, then build monitoring records a shift supervisor can complete accurately at pace.
Cold storage and port logistics
Refrigerated warehousing near the Port of Virginia operates under FSMA Preventive Controls, and for many operators the Sanitary Transportation rule as well. Temperature is the obvious control; the overlooked one is what happens during a deviation. We write excursion procedures that define the decision, the disposition and the documentation, so a chiller alarm at 2am produces a defensible record rather than a judgement call nobody wrote down.
Restaurants and hospitality groups
Food service in Virginia Beach is inspected by the Virginia Department of Health under the Virginia Food Regulations, which adopt the FDA Food Code. Multi-unit operators face a consistency problem more than a knowledge problem — one location runs a tight program and another does not. We build standardized procedures, a Certified Food Protection Manager coverage plan, and an internal self-inspection cadence that finds the issue before the health inspector does.
Specialty and value-added producers
Sauces, baked goods, roasted coffee, preserves and packaged snacks generally fall to VDACS inspection, with FSMA Preventive Controls applying above the qualified facility thresholds. Acidified foods carry an additional and frequently missed obligation: process filing and scheduled process documentation. We determine which rules genuinely apply at your volume, then build the smallest compliant program rather than the largest.
GFSI certification readiness
Retail and foodservice buyers increasingly require SQF, BRCGS or FSSC 22000 before they will place volume. These schemes demand management commitment, internal audits, verified corrective actions and a functioning food safety culture programme — evidence built over months, not assembled the week before. We run the gap assessment, close the findings in priority order, and conduct a full mock audit against the current scheme edition.
Traceability and recall readiness
FSMA Section 204 brings additional recordkeeping for foods on the Food Traceability List — which includes finfish, crustaceans, molluscan shellfish and several produce categories central to this market. Compliance requires capturing Key Data Elements at defined Critical Tracking Events and producing them in a sortable electronic format within 24 hours of an FDA request. We map your tracking events, close the capture gaps, and run a timed mock recall to prove the retrieval works.
Four operating environments, four different ways an audit is lost
Shellfish handling, seafood processing, refrigerated warehousing and multi-unit food service each answer to a different rulebook — and each fails for a reason the others never encounter.
Passing a VDH inspection through a Virginia Beach summer
Virginia Beach's hospitality sector carries a seasonal load that few other Virginia markets experience. Oceanfront volume swings enormously between February and July, and staffing turns over with it.
That pattern shapes the risk. VDH inspects food service establishments under the Virginia Food Regulations, and the recurring findings in high-turnover operations are consistent: cold holding above 41°F, inadequate date marking on ready-to-eat foods held more than 24 hours, cross-contamination during preparation, and employee health reporting that exists on paper but not in practice.
For multi-unit groups the deeper problem is variance. One location runs a disciplined program because a strong manager built one; another runs on memory. The health department finds the weak site, and the brand absorbs the consequence.
We standardize procedures across locations, build a Certified Food Protection Manager coverage plan that survives turnover, and install a self-inspection cadence using the same criteria the health inspector applies. The goal is that your worst location on your busiest week still passes — because that is the one that will be inspected.
The agencies with a claim on a Virginia Beach food business
Knowing which authority governs which part of your operation is the decision every other compliance choice depends on.
Virginia Department of Agriculture and Consumer Services (VDACS)
VDACS is the primary inspecting authority for food manufacturing, processing, packing and warehousing in Virginia. Its Office of Dairy and Foods conducts routine inspections of food establishments and enforces the state's food laws, and it carries out contract inspection work on behalf of the FDA at many facilities. For most Virginia Beach manufacturers and warehouses, VDACS is the agency that will physically walk your floor.
Virginia Department of Health (VDH)
VDH regulates food service establishments — restaurants, caterers, mobile units and institutional kitchens — under the Virginia Food Regulations, which adopt the FDA Food Code. VDH also houses the Division of Shellfish Safety, which classifies growing waters and administers the National Shellfish Sanitation Program in Virginia. For a shellfish dealer, VDH is both the sanitation authority and the gatekeeper to the Interstate Certified Shellfish Shippers List.
US Food and Drug Administration
The FDA enforces FSMA Preventive Controls, the seafood HACCP rule at 21 CFR Part 123, the Sanitary Transportation rule and FSMA Section 204 traceability. Facilities shipping interstate are subject to FDA inspection regardless of what state-level oversight they already receive, and FDA investigators issue Form 483 observations and Warning Letters. Virginia Beach's port access means a high proportion of local processors ship interstate and fall squarely in scope.
Your customers and certification bodies
In practice the most demanding auditor is often commercial rather than governmental. Retail and distribution buyers require GFSI-benchmarked certification, conduct their own supplier audits, and issue corrective action requests with commercial consequences attached. A certification body auditing you against SQF or BRCGS will examine evidence a regulator may never ask for — internal audit records, management review minutes, verified root cause analysis and documented food safety culture activity.
From uncertain to audit-ready, in a defined sequence
A structured engagement that establishes jurisdiction first, builds the program second, and proves it works before anyone official tests it.
Step 1 — Jurisdiction and gap assessment
We start by establishing which authorities actually govern each part of your operation — VDACS, VDH, FDA, or some combination — because that determines every requirement that follows. Then we walk the facility during live production, review your existing plans and records, and map what exists against what the applicable rules require. You receive a written gap register with each finding rated by regulatory and commercial risk, so the sequence of work is driven by consequence rather than convenience.
Step 2 — Hazard analysis and plan development
We rebuild the food safety plan around your real process flow. For seafood operations that means a Part 123 hazard analysis addressing the species and methods you actually handle. For manufacturers it means a Preventive Controls plan with process, allergen, sanitation and supply chain controls defined where the hazard analysis justifies them. Critical limits are set against a defensible basis, and monitoring procedures are written to be executable on a busy shift, not just technically correct.
Step 3 — Implementation and training
A plan nobody follows is a liability. We implement the program on the floor — configuring records, positioning them where the work happens, and training supervisors and operators on what they are monitoring and why it matters. Training is role-specific and documented, because both regulators and certification schemes will ask for evidence of competence, not just an attendance sheet.
Step 4 — Verification and mock audit
We test the system under audit conditions. That means records review, verification that monitoring actually happened as written, a timed mock recall to prove traceability retrieval, and a full mock audit against the relevant standard — regulatory inspection, SQF, BRCGS or FSSC 22000. Findings are documented and closed with verified corrective actions, so the first serious test of your program is one you can fail privately and fix.
Step 5 — Ongoing support and reassessment
Food safety plans require reanalysis when your process, suppliers or products change, and at minimum every three years under Preventive Controls. We provide continuing support through regulatory inspections and customer audits, refresh the hazard analysis as your operation evolves, and keep the program current with scheme edition changes and new rules such as the FSMA 204 traceability requirements.
Virginia Beach food safety consulting, answered
The questions Hampton Roads operators ask most often before starting an engagement.
Who inspects my food business in Virginia Beach?
It depends on what you do. Food manufacturing, processing, packing and warehousing generally fall to the Virginia Department of Agriculture and Consumer Services (VDACS). Restaurants, caterers and other food service establishments are inspected by the Virginia Department of Health (VDH) under the Virginia Food Regulations. Shellfish growing, harvesting and dealing is overseen by VDH's Division of Shellfish Safety under the National Shellfish Sanitation Program. On top of all of that, the FDA has jurisdiction over facilities shipping interstate and enforces FSMA Preventive Controls and the seafood HACCP rule. Many Virginia Beach businesses are subject to more than one of these at once, which is exactly why we establish jurisdiction before writing anything.
Does my seafood operation need HACCP or FSMA Preventive Controls?
Seafood processors are covered by the seafood HACCP regulation at 21 CFR Part 123 rather than the Preventive Controls rule for the seafood processing activities themselves. This is a common and consequential point of confusion. If your facility also conducts non-seafood manufacturing, those activities may separately fall under Preventive Controls, meaning you need both frameworks operating in one building. We determine which rule applies to which activity and build a single coherent program rather than two competing ones.
What does the NSSP actually require for shellstock tags?
Under the NSSP Model Ordinance, shellstock must be tagged with information identifying the harvester, the harvest area and the date of harvest, and dealers must retain those tags for 90 days after the container is emptied. Tags must stay with the product until the container is empty, and lot identity must be maintained through shucking and packing operations. In practice, most failures occur at handoffs rather than at receiving, which is where we focus when rebuilding the chain of custody.
How does FSMA 204 traceability affect Virginia Beach seafood businesses?
The FSMA Section 204 rule applies to foods on the Food Traceability List, which includes finfish, crustaceans and molluscan shellfish alongside several produce categories. Covered businesses must capture defined Key Data Elements at Critical Tracking Events such as receiving, transformation and shipping, and be able to provide those records to the FDA in a sortable electronic format within 24 hours of a request. Given the seafood concentration in Hampton Roads, this affects a large share of local processors and distributors. We map your tracking events and test the retrieval before it is ever needed.
How long does it take to get ready for an SQF or BRCGS audit?
For an operation starting without a formal system, a realistic timeline is four to eight months. The constraint is rarely writing documents — it is that certification schemes require evidence accumulated over time. You need completed internal audits, verified corrective actions, management review records and demonstrable food safety culture activity. A facility with existing HACCP or Preventive Controls foundations can often be ready in three to five months. We sequence the work so evidence starts accumulating from week one rather than after the documentation is finished.
What happens if we receive an FDA Form 483?
A Form 483 lists an investigator's observations of conditions that may violate the Food, Drug and Cosmetic Act. It is not a final agency determination, but your response matters a great deal. You should respond in writing within 15 business days with corrective actions, timelines and evidence, because a strong response can prevent escalation to a Warning Letter. We help clients investigate root cause properly, write responses that address the systemic issue rather than only the specific observation, and implement changes that hold up at the follow-up inspection.
Do you work with smaller operations, or only large processors?
We work across the range, and for small operations the first task is often determining what genuinely applies. FSMA includes qualified facility exemptions based on revenue and sales patterns, and a business below those thresholds may have substantially reduced requirements — though it still needs to document its exempt status and comply with applicable state rules. We would rather tell you that you need a modest program than sell you an oversized one.
Do you work on site in Virginia Beach?
Yes. Certain work has to happen on the floor — process flow verification, hazard analysis, environmental monitoring design and mock audits all require physically walking the operation during production. We combine on-site work in Virginia Beach and the wider Hampton Roads area with remote support for documentation development, record review and audit preparation, which keeps engagements cost-effective without losing the observation that makes the plan accurate.
Talk to a food safety expert about your Virginia Beach operation
Whether you are shucking clams on the Lynnhaven, running refrigerated warehousing near the Port of Virginia, producing specialty foods for regional retail, or managing food safety across a multi-unit hospitality group, the first step is the same: establish exactly which rules apply to you, and find out honestly where your current program stands against them.
We will walk your operation, tell you what we find, and give you a prioritized plan — whether or not you engage us to implement it.
Speak with our Expert Consultants
15–30 minutes. We map FoodReady to your process, plug in your real HACCP plan, and show you the auditor view before the call ends.