If you manage a commercial facility in Indiana — a restaurant, a hospital, a daycare, a food processing plant, an apartment community, a school district, a senior living building, a food retail store — your pest management program isn’t governed by one regulation. It’s governed by a stack of them, layered on top of each other, and each one was written by a different agency with different priorities. The state regulates who can apply pesticide. The FDA Food Code regulates how pest evidence is treated in food service. ISDH oversees licensed establishments. FSSA wrote the rules for childcare. The Indiana legislature passed a separate law on schools. Joint Commission inspects hospitals. AIB, SQF, BRC, and FSSC 22000 audit your food plant. HUD REAC inspects your multifamily portfolio. Each one of those auditors will look at your pest documentation differently, and the gap between what your pest provider hands you and what each auditor expects is where citations live.

This guide is the master reference. We wrote it because the question we get most often from facility managers across Marion County and the surrounding eight-county Indy metro isn’t “do you do roach control” — it’s “will your service hold up when my auditor walks in.” The answer depends on which auditor, which framework, and what’s in your binder. Here’s all of it, in one place.

A compliance binder is the audit-ready evidence stack: service logs, monitoring map, IPM plan, MSDS access, and applicator license — all expected by Indiana inspectors and third-party auditors.

Why State, Federal, and Local Regs All Stack — A 60-Second Framing

Most facility managers operate under the (false) assumption that one set of rules applies. In reality, every Indiana commercial facility carries at least three layers, and most carry four or five. Here’s the rough hierarchy:

1. Federal frameworks like the FDA Food Code and EPA pesticide labeling apply to every state. Indiana adopts the Food Code by reference (currently the 2022 edition), so federal language becomes state-enforceable through the Indiana Retail Food Establishment Sanitation Requirements (410 IAC 7-24).
2. State agencies — primarily Indiana State Chemist (OISC) for pesticide use, ISDH for licensed health establishments, FSSA for childcare, IDOH for health-related rule-making — write the regulations that name what your pest provider has to do and what records you have to keep.
3. Local health departments — Marion County Public Health Department, Hamilton County Health Department, Hendricks, Hancock, Boone, Johnson, Madison, Morgan, Shelby — each enforce the state rules with their own inspection cadence and citation thresholds.
4. Industry-specific federal laws like HUD’s REAC inspection regime for assisted housing, IC 15-16-5 for Indiana schools, and the federal Healthy Schools Act framework that some Indiana districts adopt voluntarily.
5. Third-party audit programs — Joint Commission for hospitals, AIB / SQF / BRC / FSSC 22000 for food processing, EcoSure / Steritech-equivalent for branded restaurant chains, NSF for institutional kitchens — that don’t have legal force but are tied to your operating contract or accreditation.

Your pest provider needs to know which of these apply to you, and your service documentation needs to reflect what each framework wants to see. Generic service stickers don’t satisfy any of them. The rest of this guide walks each one.

Indiana OISC — Office of Indiana State Chemist (Where Every Indiana Pest Provider Has to Be Licensed)

OISC is the state agency you’ve probably never heard of unless you’ve had to verify your provider is legitimate. Housed at Purdue University, OISC is Indiana’s pesticide regulatory authority — they license every commercial pesticide applicator, inspect application records, investigate misuse complaints, and enforce the federal Worker Protection Standard. If your pest provider doesn’t have current OISC credentials, nothing they do on your facility is legal under Indiana law.

Categories that apply to commercial pest control

Indiana issues commercial pesticide applicator certificates by category, and the categories that touch most commercial facilities are:

• Category 7A — General Pest Control. The core category for structural pest management — covers the majority of commercial work in restaurants, retail, multifamily, healthcare, and offices. A 7A-certified applicator can legally apply general-use and most restricted-use pesticides for structural pest issues.
• Category 7B — Termite Control. Required for any subterranean termite work — pre-construction soil treatments, post-construction perimeter applications, and bait system installation. Most commercial facilities don’t need 7B unless construction or renovation is involved, but providers servicing wood-frame multifamily often carry it.
• Category 7C — Fumigation. Required for structural fumigation (whole-building tarp fumigation, container fumigation, commodity fumigation in food storage). Specialized — most commercial accounts never need 7C, but food storage and grain operations do.
• Category 8 — Public Health Pest Control. Required for applicators working in public health contexts — mosquito management programs, vector control, certain healthcare-related applications. Some hospital and senior living accounts ask for 8-certified applicators.
• Registered Technician (RT). Indiana allows uncertified technicians to apply pesticide under the direct supervision of a certified applicator if they’re registered with OISC. RT status requires initial training and annual reporting. Important: your service tech can be an RT, but a certified applicator must be supervising and accessible.

Record-keeping requirements under OISC

Beyond licensing, OISC enforces strict record-keeping for restricted-use pesticide (RUP) applications and, by best practice and food-code overlap, virtually all commercial applications. Indiana requires applicators to retain records of every application for at least two years, including:

• Date and time of application
• Location (address + specific area within the facility)
• Target pest
• Product brand name + EPA registration number + active ingredient
• Quantity applied and concentration
• Application method (crack-and-crevice, spot treatment, bait placement, etc.)
• Applicator name + certification number
• For RUPs specifically: weather conditions and reentry interval

Most legitimate commercial pest providers exceed this baseline by recording every application — RUP or general — and producing it as a service report your facility can drop into a binder. If your service report doesn’t capture the bullets above, you’re not OISC-compliant on a record-keeping basis even if every application was lawfully performed.

Worker Protection Standard and re-entry intervals

OISC enforces the federal Worker Protection Standard (WPS) where it applies — agricultural settings primarily, but elements bleed into commercial pest control through label-mandated re-entry intervals (REI). Every product label specifies how long humans must stay out of treated areas after application. Indiana commercial pest providers are expected to honor REIs, post notification when required, and document compliance. For commercial kitchens, this is why post-close service windows matter — applying anything with even a 4-hour REI during dinner prep is a label violation.

FDA Food Code 2022 (Indiana-Adopted) — How Pest Evidence Is Treated in Food Service

Indiana adopts the FDA Food Code by reference under 410 IAC 7-24, currently aligned with the FDA Food Code 2022 edition. This is the regulation Marion County Public Health Department food-service inspectors work from when they walk into a restaurant, food retail, school cafeteria, daycare kitchen, or hospital food service operation. Pest-related sections of the Food Code aren’t an afterthought — they’re a primary inspection domain, and they’re written with specificity about what’s expected of facility pest management.

Section 6-202.13 — Outer openings, protected

Food Code requires that outer openings (doors, windows, vents) be protected against pest entry. In practice this means functional door sweeps, intact window screens, sealed utility penetrations, and air-curtain compliance where applicable. Pest providers can’t fix structural defects, but a competent commercial program documents these as conducive conditions in service reports — putting the facility on notice and creating a paper trail that auditors expect to see.

Section 6-501.111 — Controlling pests

The headline pest section. Food Code requires the facility to (1) routinely inspect for pests, (2) take measures to prevent entry, (3) eliminate harborage, and (4) employ a licensed pest control professional or otherwise eliminate pests. Inspectors interpret “routinely inspect” as a documented, scheduled program — typically monthly minimum for restaurants and food retail, sometimes weekly for high-risk operations.

Section 6-501.112 — Removing dead or trapped birds, insects, rodents, and other pests

Carcasses must be removed at frequencies that prevent contamination. Practically, this means sticky-trap rotation and rodent station inspection on a documented cadence — and trap contents documented in service logs. An auditor seeing dead-rodent material in a station that hasn’t been logged in 60 days will treat it as a violation regardless of whether the trap caught the rodent legitimately.

Section 7-202.12 — Conditions of use

Pesticide use must be by an OISC-licensed applicator (or under their direct supervision), products must be approved for the use site, applications must follow label directions, and applications must be in a manner that doesn’t contaminate food or food-contact surfaces. This is why broadcast spray in food-prep zones is functionally prohibited — almost no general-use pesticide label permits it, and the section reinforces label compliance as a Food Code requirement.

ISDH — Indiana State Department of Health (Licensed Establishments)

ISDH oversees state-licensed health establishments — long-term care facilities, residential care facilities, hospitals at the state-license layer (Joint Commission handles federal), home health, hospice, and certain laboratory and clinical environments. ISDH rules cross-reference Food Code provisions for kitchens, but they also impose facility-wide environmental sanitation expectations that touch pest management.

What ISDH inspectors look for in pest management

• Documented IPM plan. A written integrated pest management plan that names the threshold for treatment, identifies key pests by area, and documents the response protocol. ISDH expects this to be a real document, not a sticker.
• Service log continuity. Records of every visit going back 12 months minimum, with no gaps. Gaps in the log read to inspectors as either (a) skipped service or (b) lost records — both are violations.
• Product information accessibility. Safety Data Sheets (SDS / formerly MSDS) for every product applied at the facility, accessible to staff during normal operating hours. Some long-term care facilities require SDS to be accessible to residents on request.
• Applicator credentials on file. Copy of the OISC applicator license + insurance certificate kept in the facility’s vendor binder. Auditors verify these annually.
• Corrective action documentation. When pest activity is found, the documented response — what was treated, when, by whom, and the verification follow-up — must be captured in the service log.

FSSA / Indiana Early Childhood Licensing — The Daycare and Childcare Rules That Limit Spray

If you operate a licensed childcare home, childcare ministry, or licensed childcare center in Indiana, the rules under FSSA’s Office of Early Childhood and Out-of-School Learning are stricter than almost any other commercial framework — and most facility managers don’t realize how strict until an inspection finds an out-of-compliance application.

The IPM mandate (470 IAC 3-4.7)

Indiana’s licensed childcare regulations explicitly require an integrated pest management approach. The rule limits broadcast pesticide application in areas accessible to children, requires least-toxic methods first, and requires parental notification before certain applications. In practice, this means:

• No broadcast spray in classrooms, sleep rooms, food prep areas, or play areas during operating hours. Crack-and-crevice and bait-station applications are permitted with restrictions.
• Application during off-hours preferred. Most Indiana licensed centers require pest service to occur after children have left for the day, with sufficient ventilation time before re-occupancy.
• Pre-application notification. Parents must be notified before pesticide application in many circumstances — typically posted notice at the door 24–48 hours in advance, with the product name, EPA registration number, and application location.
• Documented IPM plan on file. Centers are expected to have a written pest management plan available for inspection at any time.
• Bait stations and traps preferred over liquid application. The hierarchy is: prevention → exclusion → monitoring → trapping → bait → spot treatment → broadcast (last resort, almost never permitted).

Indiana Code 15-16-5 — The School IPM Mandate

Indiana Code 15-16-5, enacted in 1999 and amended several times since, is the state law that requires every public school corporation in Indiana to operate an Integrated Pest Management program. It’s not a guideline — it’s statute, with OISC enforcement authority and reporting requirements. Private schools aren’t bound by it but are encouraged to follow it, and Indiana K–12 accreditation often references it.

Core requirements under IC 15-16-5

• Designated IPM coordinator. Each school corporation must designate a staff member responsible for the IPM program. Often a maintenance director or facilities manager.
• Written IPM plan. The corporation must adopt a written IPM plan covering all schools and accessory facilities. Plan must address inspection frequency, threshold-based treatment decisions, least-toxic methods, and record-keeping.
• Staff training. Custodial and maintenance staff must receive IPM-related training on pest identification, sanitation contributions, and reporting procedures.
• Parent and staff notification. Pre-application notification rules similar to childcare — written notice 48 hours in advance for non-exempt applications, posted notice at application sites.
• Annual reporting. Schools must report annually to OISC on pesticide applications. The reports are aggregated and reviewed.
• Restricted application during school hours. Pesticide application during school hours is heavily restricted — most applications must occur during weekends, holidays, or after-school hours.

What compliant school pest service looks like

A compliant school pest program isn’t a monthly perimeter spray. It’s a documented inspection-and-monitoring program where the licensed applicator visits on schedule, inspects defined zones (cafeteria, kitchen, classrooms, custodial areas, exterior perimeter, athletic fields where applicable), records findings in a log that the IPM coordinator countersigns, and applies pesticide only when monitoring crosses a defined threshold. Most applications, when they happen, are crack-and-crevice or bait — not broadcast. See our schools pest control page for the full program structure.

Indiana commercial facilities operate under stacked regulatory frameworks — OISC for the applicator, FDA/ISDH for the food code, FSSA for daycares, Joint Commission for healthcare, and audit programs on top.

Joint Commission and Healthcare Surveys — IPM in Hospital Accreditation

Hospitals and many ambulatory care facilities pursue Joint Commission accreditation (or DNV equivalent), and pest management is a touchpoint within the Environment of Care (EC) chapter. The Joint Commission doesn’t issue a numbered pest standard, but pest management lives across several EC standards — particularly EC.02.06.01 (the environment is safe), EC.02.05.01 (utility systems), and the broader infection-prevention domain governed by IC chapter standards.

What surveyors actually ask about

• Documented IPM plan integrated with the facility’s environmental services / facilities management plan.
• Risk assessment identifying high-risk areas (kitchens, sterile processing, pharmacy, central supply, dietary, patient rooms) with differentiated pest management approaches.
• Service records retained for the duration the facility’s policy specifies — often three years or longer.
• Trend monitoring — surveyors expect facilities to track pest activity over time, identify escalating trends, and respond before an outbreak.
• Staff competency. Environmental services staff trained on what to do when pest activity is observed (report, document, isolate area if needed, contact pest provider).
• Special considerations for sensitive areas — operating rooms, NICUs, oncology wards, immunocompromised patient areas — where pesticide application is severely restricted and exclusion / sanitation is the primary control.

Food Processing Audits — AIB, SQF, BRC, FSSC 22000, ISO 22000, and USDA FSIS

If you run a food processing, packaging, or warehousing facility — anything from a co-packer to a large CPG plant — you’re subject to one or more third-party audit programs that go far deeper than the Food Code. Each program has its own specific pest-management standard. The auditor will not be satisfied by health-department documentation. They want to see their framework reflected in your records.

AIB International (American Institute of Baking)

AIB has historically been the dominant audit framework for baking, snack, and dry-goods manufacturers. The AIB Consolidated Standards include detailed pest management requirements: documented IPM program, monthly minimum service (often biweekly for high-risk facilities), trend analysis, monitoring station maps, exterior and interior monitoring, sanitation linkage. Auditors physically count monitoring stations and verify they match your map.

SQF (Safe Quality Food)

SQF is a GFSI-recognized scheme widely adopted by produce, beverage, and packaged food manufacturers. SQF Module 11 (food manufacturing) Section 11.2.11 covers pest prevention. Requirements include written program, scope, contractor credentials, monitoring records, action plans, and trend reviews. SQF auditors are explicit about wanting to see trending data — not just service logs but analysis of what’s increasing or decreasing.

BRC (BRCGS) Global Standard for Food Safety

BRC is the dominant European-origin GFSI scheme — many U.S. food manufacturers exporting to Europe or supplying European retailers operate under BRC. Section 4.14 of the BRC Global Standard specifically covers pest management with explicit requirements for: licensed contractor or trained in-house staff, documented program, hygienic and structural conditions, equipment and material storage, and detailed monitoring of inbound materials.

FSSC 22000 / ISO 22000

FSSC 22000 layers ISO 22000 with sector-specific Pre-Requisite Programs. PRP requirements (ISO/TS 22002-1 for food manufacturing) include pest management as a core PRP. Less prescriptive than AIB or BRC on station counts, more prescriptive on the program structure — risk assessment, hazard analysis, and verification.

USDA FSIS — Meat and Poultry Plants

USDA-inspected meat and poultry plants operate under FSIS regulation. FSIS Directive 11000.1 covers Sanitation Performance Standards, and pest management is included under 9 CFR 416.2(a) — facilities must be constructed, maintained, and operated to prevent pest harborage and contamination. FSIS in-plant inspectors document pest issues in the plant’s noncompliance record (NR), which feeds enforcement decisions.

Common pest documentation expectations across audit programs

While the audit programs differ, the documentation they expect overlaps substantially. The common rubric:

• Written IPM / pest prevention program with scope, objectives, and procedures
• Contractor agreement and proof of credentials (OISC license, insurance, training records)
• Site map showing all monitoring devices (rodent stations, insect light traps, pheromone traps, snap traps interior)
• Monitoring records for each device, dated and signed, with activity logged at every visit
• Service reports for every visit including findings, actions taken, products applied, recommendations
• Trend analysis at minimum quarterly (often monthly) showing activity patterns by zone and pest
• Corrective action records for any positive findings, with verification follow-up
• Pesticide use records meeting OISC retention and federal record-keeping standards
• Safety Data Sheets for every product on site
• Annual program review documenting effectiveness and changes for the coming year

Multifamily Housing — HUD REAC (PASS) and LIHTC Compliance

Indiana multifamily property managers operating any HUD-assisted property (Section 8 project-based, Section 202, Section 811, RAD-converted, etc.) operate under the HUD Real Estate Assessment Center (REAC) inspection regime, currently transitioning under the NSPIRE (National Standards for the Physical Inspection of Real Estate) framework — which is the successor to the older Uniform Physical Condition Standards (UPCS) protocol. The PASS (Physical Assessment Subsystem) inspection cycle scores properties partially on pest infestation evidence.

How REAC / NSPIRE handles pest infestation

Under the legacy UPCS / PASS protocol, infestation was a defect category at multiple severity levels. Under NSPIRE, pest infestation is evaluated under “life-threatening / severe / moderate / low” deficiency tiers, with bed bug infestations specifically named as a severe deficiency in occupied units. A single severe infestation finding can drop a property’s REAC score significantly, and repeated findings trigger compliance reviews and potential subsidy implications.

What HUD inspectors look for

• Live pest activity in common areas — hallways, laundry rooms, mechanical rooms, garbage rooms
• Live pest activity or evidence in unit interiors sampled during inspection
• Bed bug evidence specifically — including fecal staining, shed skins, or live specimens
• Exterior conducive conditions — overgrown vegetation, harborage from poorly stored materials, dumpster proximity issues
• Records of pest management response when activity is found

LIHTC compliance

Low-Income Housing Tax Credit properties operate under IHCDA (Indiana Housing and Community Development Authority) compliance review, which references HUD inspection standards plus state-level habitability requirements. IHCDA reviews are less frequent than REAC but no less rigorous on pest documentation. See our multifamily pest control page for how we structure HUD-compliant property programs.

HOA / Condo and Retail Audit Best Practices

Beyond the regulated frameworks above, every commercial facility operates under some variation of generic audit best practice — corporate facilities standards, insurance carrier requirements, lease covenants, brand standards (for franchised retail and food service), and standard third-party operational audits. While none of these have legal force individually, they collectively define what “professional pest management” looks like in 2026.

Retail and convenience

Branded retail (grocery, c-store, big-box) typically requires an external audit program through a brand-recognized third party (EcoSure, Steritech-equivalent, NSF, AIB-Retail). These audits look at the same documentation rubric as food processing but apply restaurant-grade frequency expectations. Retail food handlers face Food Code overlap, so the rubric stacks.

HOA / condo associations

Associations operate under their CC&Rs and state condo law, with no specific pest regulation. But unit-owner expectations and liability exposure drive most boards to adopt formal pest management programs covering common areas and exterior treatment. The audit framework here is internal — what does the management company report to the board, and what records exist if a unit owner files a habitability complaint.

Indiana Vertical → Applicable Regulations Map

Use the table below to identify which Indiana regulatory frameworks apply to your facility type. Most facilities sit in multiple rows because most facilities have multiple functional areas.

The Universal Audit Documentation Rubric — What Every Auditor Looks For

Across every framework above, the documentation auditors actually examine is remarkably consistent. If your binder includes the items below, in order, you’re audit-ready for almost any framework — Food Code, ISDH, FSSA, Joint Commission, AIB/SQF/BRC, REAC. Missing items are where citations come from.

Audit-ready service starts with a Category 7A/7B/7C/8 OISC-licensed applicator, an IPM plan that’s actually followed, and documentation that matches the framework the auditor is using.

How a Non-Compliant Pest Program Shows Up in Audit Findings

Knowing what to do is half the battle. Knowing how non-compliance gets cited is the other half — because most facility managers don’t see the audit until it’s already happened. Here are the citations that show up most often when a pest program falls short, organized roughly by audit type.

Food Code / county health department

• Live pest activity observed during inspection (varies in severity by inspector, jurisdiction, and pest type)
• Evidence of pest activity (droppings, oothecae, gnaw marks, urine staining) without live sighting
• Absence of professional pest management documentation
• Conducive conditions left unaddressed across multiple inspections (gaps under doors, unscreened openings, structural defects)
• Pesticide application by an unlicensed individual or in a manner inconsistent with label directions
• Storage of pesticides in food-contact areas
• Dead pests in monitoring devices not removed within facility-defined frequency

ISDH / Joint Commission / healthcare

• Absence of a documented IPM plan integrated with environmental services
• Service log gaps suggesting skipped service
• Pest activity in sterile or semi-sterile areas (operating rooms, sterile processing, NICU)
• Bed bug introductions without documented protocol or response
• SDS not accessible to staff
• Pesticide application in patient-care areas inconsistent with label REI

AIB / SQF / BRC / FSSC 22000

• Monitoring station map outdated or inaccurate (devices in field don’t match map)
• Service frequency inadequate for facility risk level (typically monthly minimum, biweekly or weekly for high-risk)
• Trend analysis missing or perfunctory
• Corrective action records missing for documented positive findings
• Inadequate physical barriers (door sweeps, screens, drain covers)
• Pheromone trap or insect light trap counts not documented
• Inbound materials inspection not documented (BRC specifically)
• Annual program review missing or boilerplate

FSSA / childcare licensing

• Pesticide application during operating hours
• Broadcast spray in classrooms, sleep rooms, food prep, or play areas
• Absence of parental pre-application notification where required
• Written IPM plan absent or not on site
• Use of products not approved for childcare settings

IC 15-16-5 / school IPM

• No designated IPM coordinator on file with OISC
• Annual reporting to OISC missed or incomplete
• Pre-application notification (48-hour rule) not observed
• Pesticide application during school hours without exemption
• Custodial / maintenance staff training records missing

HUD REAC / NSPIRE / multifamily

• Live pest activity in common areas during inspection
• Bed bug evidence in occupied units (severe deficiency under NSPIRE)
• Roach activity in unit kitchens during sample inspections
• Exterior conducive conditions (vegetation, debris, dumpster proximity)
• Service records missing or sparse for bed bug-affected units

What ProTech Does Differently for Audited Indiana Facilities

ProTech is 100% commercial — we don’t service homes. The book is restaurants, healthcare, food processing, multifamily, daycare, schools, food retail, offices, and industrial across Marion County and the surrounding eight-county Indy metro. Owner Stephen Hill answers his own phone during business hours. There’s no call center. There’s no subcontractor network. The same OISC-certified technician services your account every visit — they get to know your facility, your team, and your audit calendar. Our service reports are formatted for the framework you operate under — Food Code for restaurants, AIB/SQF/BRC for processors, FSSA for daycares, REAC for HUD multifamily, Joint Commission for hospitals — not a generic template.

If you’re switching providers because the last one didn’t hold up under audit, or if you’re standing up a new facility and want the pest management piece set up right from day one, the path forward is an on-site walk and a documented program proposal — not a phone quote. Request a commercial pest control quote or see our full list of commercial industries served. For new clients, we’ll meet on-site, walk the building with your facilities team, and identify which regulatory frameworks govern your pest management program before we write a single line of the proposal.