Tier II reporting from SDS to submission

Who this guide is for

This guide is for the person who prepares or signs off on a facility's annual EPCRA Section 312 inventory report, the Tier II report (often written "tier 2 reporting"), whether that's an EHS manager, a plant engineer, or an operations lead who inherited the job. It is also useful for anyone deciding whether a facility needs to file at all.

Start with applicability. Sections 311 and 312 apply to any facility that is required to maintain Safety Data Sheets under OSHA's Hazard Communication standard for hazardous chemicals stored or used in the workplace, when those chemicals are present at or above the reporting thresholds: 10,000 pounds for hazardous chemicals, and 500 pounds or the threshold planning quantity (TPQ), whichever is lower, for extremely hazardous substances (EHSs). Retail gas stations have separate thresholds for gasoline (75,000 gallons) and diesel (100,000 gallons) stored entirely underground in compliant tanks.

Next, be clear about which period you are reporting. The Tier II report is due by March 1 each year and covers the previous calendar year, so the report due March 1, 2027 covers January 1 through December 31, 2026. Quantities are based on the maximum amount present at any one time during that year, and the form also asks for the average daily amount and the number of days the chemical was on-site.

Work through a Tier II reporting checklist alongside this guide so each item has an owner and a completion record before the March 1 deadline.

Stage 1: Set up the facility

Everything starts with the facility itself: address, contacts, and the state it operates in. This should be a one-time setup that everything downstream inherits automatically, not something you reconstruct for every reporting cycle.

Stage 2: Verify state-specific requirements

The federal EPCRA baseline is only the floor. Many states layer their own filing portals, fees, additional data fields, or lead agencies on top of it. A real end-to-end platform verifies what your specific state requires for that facility (which portal, which agency, which format) rather than assuming a single national process applies everywhere.

Start from the official sources: EPA's state Tier II procedures directory (linked in the report section below) points to each state's program, and our summary of Tier II requirements by state collects the portal, recipients and state-specific rules in one place. Record the date you checked, because portals and fee rules change. For example, Minnesota accepts electronic Tier II data only through its Tier II Manager software and charges a per-facility Tier II processing fee under Minn. R. 7507.0500: details another state's process would not tell you.

Stage 3: Build the SDS library, with extraction

Every Safety Data Sheet that enters your facility needs to land somewhere centralized. In a lot of operations, this stage is genuinely just a shared drive folder or an email inbox, which means SDS files get lost, duplicated, or go out of date without anyone noticing.

End-to-end starts with a single library (every SDS, searchable and centralized) combined with AI SDS extraction that auto-indexes each sheet as it's uploaded: CAS number, hazard classification, physical state, pulled directly from the document instead of typed in by hand.

Stage 4: Manage inventory and auto-calculate thresholds

Once you have structured data, it needs to live somewhere that reflects reality in real time, not just at year-end. That means tracking quantities per facility and running automatic threshold calculations against your 302, 311, and Tier II obligations continuously, not once a year when someone finally sits down to do the math.

The comparison itself is simple once the inputs are right: take the maximum amount of each chemical present at any one time, summed across every storage location on the same day, and compare it with the federal threshold that applies. For EHSs in mixtures, add the EHS component in every mixture (concentration × mixture weight) to all other quantities of that EHS on-site. Our guide on how to calculate reporting thresholds works through the rules, including the 1% (0.1% for carcinogens) mixture cut-off for hazardous chemicals.

Keeping inventory current through the year is what makes this stage quick. Whether you use a spreadsheet with disciplined monthly counts or chemical inventory software that records quantities by building and room, the goal is the same: a record of receipts, use and transfers you can trust when you pull the reporting-year maximum.

Stage 5: Get notified before deadlines arrive

Even accurate, current data doesn't help if nobody remembers the deadline. Real end-to-end compliance includes calendar-based notifications tied to what a specific facility actually owes: a heads-up that a 302, 311, or Tier II report is coming due for that facility, generated from your real data rather than a generic seasonal reminder.

Not every EPCRA deadline is annual. Section 302 notification to the SERC and LEPC is due within 60 days after a facility first has an EHS at or above its TPQ, and a Section 311 SDS or chemical-list submission is due within three months after a chemical first triggers the OSHA requirement at or above threshold. Changes to the facility emergency coordinator details must be reported to the LEPC within 30 days.

Stage 6: Generate the report, in a usable format

The report should be a natural output of everything upstream, not a separate task built from scratch. Look for output in .t2s format, which allows straightforward import into Tier2 Submit, E-Plan, and similar systems, rather than a static PDF you have to manually re-key elsewhere.

EPA's free Tier2 Submit software is one way to prepare an electronic Tier II and generate a .t2s file; EPA advises checking with your state to find out whether it accepts Tier2 Submit files. Whatever tool produces the file, a person should review the draft before it is certified.

What a finished Tier II report contains: an annotated example

Before anyone certifies the report, walk through it section by section. The example below follows the data elements on EPA's Tier II form; your state's version may use different labels or add fields.

Once certified, the report goes through your state's submission route: a state portal, an accepted electronic file, or in some states a state-specific paper form. Confirm in your state's official instructions who must receive it (the SERC, the LEPC and the local fire department are the federal recipients) and whether one upload reaches all of them. Then save the submission confirmation, the certified copy and the calculation records together; that file is your proof if the filing is ever questioned.

Stage 7: Submit it, or have it submitted for you

This is the stage most platforms leave out entirely, and it's the one that actually makes a solution end-to-end rather than end-to-almost-end. Generating a correctly formatted report still leaves you to log into a state portal, upload it, and route it to the right recipients: the SERC, the LEPC, and the local fire department.

A genuinely end-to-end platform offers to close that gap: submitting the completed report directly to SERC, LEPC, and fire department on your behalf, so the last mile isn't left to you.

Even when a service submits for you, the owner/operator or an authorized representative still certifies the report, and the facility remains responsible for the accuracy of the data. Submission help also depends on the route each state accepts, so confirm per state and per facility what will be submitted, to whom, and what proof you will receive.

Official requirement versus optional assistance

It helps to separate what EPCRA and your state require from the help a tool or service can give. The requirements are the same whichever way you work; the assistance only changes who does the work and how much of it is manual.

If you want one system to carry the data through every stage, NeoTech's Tier II reporting software covers facility setup, the SDS library with AI extraction, inventory with threshold calculations, deadline reminders and .t2s/PDF output, with an optional managed submission service. You still review the data and certify the report.

The test for "end-to-end," in one question

Ask a vendor: "If I upload a new SDS today, what has to happen, and who has to do it, before that chemical is correctly reflected in a report that's actually been filed?"

If the honest answer stops at "you generate the report and file it yourself," that's a compliance tool (a good one, potentially), but not end-to-end. True end-to-end means the chain runs all the way through submission, with a human only needed to review and approve, not to manually complete each stage.

Why this matters more than it sounds

Every manual handoff in that chain is a place where errors get introduced: a mistyped CAS number, an outdated quantity, a missed deadline, a report generated but never actually filed. The value of true end-to-end automation isn't just time saved; it's fewer places where a small gap becomes a missed filing you don't find out about until an audit or a penalty notice.

Official source

The federal requirements described in this article are established under the Emergency Planning and Community Right-to-Know Act (EPCRA). Always verify current state-specific rules with your SERC.

Applicability, thresholds and the March 1 deadline come from EPA's EPCRA Sections 311 and 312 page and 40 CFR part 370; Section 302 deadlines come from 40 CFR part 355.