If you're responsible for EPCRA Tier II reporting at even one facility, you already know the stakes: a missed March 1 deadline, a misclassified chemical, or a filing sent to the wrong portal can mean penalties, audits, and a lot of unpaid overtime. The right software doesn't just generate a form. It should catch problems before they become violations, and ideally handle the parts you'd rather not do by hand at all. Here's what actually separates a good EPCRA reporting platform from a spreadsheet with extra steps.
1. Does it start with your facilities, or just a form?
Multi-step compliance starts before any chemical data enters the system, with the facility itself. Software worth using should let you set up each facility as its own record (address, contacts, applicable state) and apply the right rules to it automatically from that point forward, rather than treating every filing as a blank slate.
2. Does it verify state-specific requirements, or just the federal minimum?
The federal EPCRA baseline is only the floor. Many states layer their own filing portals, fees, extra data fields, or lead agencies on top of it. Software that only knows the generic federal Tier II form will leave you researching your state's specific requirements manually, every year.
Look for a platform that actively verifies state-by-state requirements, confirming which portal you're filing through, which agency receives it, and what your state specifically requires, rather than assuming one national process fits every facility.
3. Does it manage your SDS library, or just your Tier II form?
A lot of "Tier II software" is really just a form generator, and you still have to manually read every Safety Data Sheet, pull out the hazard classes and CAS numbers, and type them in yourself. That's the same manual work you were doing before, just in a nicer interface.
Look for software with a real SDS library, searchable and centralized, with AI-based extraction that automatically indexes each sheet: hazard class, CAS number, and the other fields you need, pulled directly from the document instead of typed in by hand. This is often the biggest time sink in Tier II prep, and it's also where many classification errors start.
Extraction shouldn't replace human review. Ask how the software shows its confidence in each extracted field, which fields it flags for a person to check, and how a reviewer's correction is recorded.
4. Does it manage inventory and calculate thresholds for you?
Tier II reporting requires the maximum quantity of each chemical present at any point during the year, not an average, and not just what happens to be on-site when someone gets around to counting. Software that only lets you enter numbers once a year, at filing time, puts the burden back on you to have tracked those maximums manually all along.
Better platforms track inventory continuously and run auto-calculation against your reporting thresholds, so you know where you stand relative to 302, 311, and Tier II obligations without doing the math yourself every time inventory changes.
5. Does it tell you when deadlines are coming, or leave that to you?
Even accurate data doesn't help if nobody remembers the deadline. Look for calendar-based deadline notifications tied to what a facility actually owes: a heads-up when a 302, 311, or Tier II report is coming due for a specific facility, not a generic "reporting season is near" reminder that applies to everyone equally.
6. Does it generate reports in a format you can actually use?
Once thresholds and inventory are set, the platform should generate the report itself, and in a format your downstream system accepts. Look specifically for .t2s format output, which can be imported into Tier2 Submit, E-Plan and other systems that accept it, instead of a generic PDF you have to manually re-enter elsewhere. Acceptance varies: EPA advises contacting your state to find out whether it accepts Tier2 Submit files, so confirm your state's format before treating any output as ready to file.
7. Will it actually file the report for you?
This is the real dividing line between "reporting software" and an end-to-end solution. Some platforms stop at generating the report and leave submission to you: logging into a state portal, uploading the file, confirming receipt. Ask directly: can the vendor submit the report on your behalf (to the SERC, LEPC, and fire department) or do you still have to do that part yourself?
A platform that offers submission as a service, not just report generation, is the difference between a tool that helps you file and one that actually closes the loop.
8. Can you see the total cost before you sign?
Compare total cost, not the headline subscription: facility count, SDS volume, onboarding, data migration, training, support and any filing service. Ask each vendor to mark every item as included, an optional extra or quote-dependent, and get it in writing. Our EPCRA software pricing guide has a worksheet for this. For NeoTech, current monthly plans are published on the NeoTech pricing page, with a 30-day free trial and no credit card required.
A short checklist before you sign anything
If a platform can answer "yes" to all eight, it's a genuine end-to-end solution. If it stops at report generation, you're still doing the last, and most deadline-sensitive, mile yourself.
- Does it support facility-level setup with state-specific rule application?
- Does it actively verify state-by-state EPCRA requirements, not just the federal baseline?
- Does it extract structured SDS data automatically, or just store the PDF?
- Does it track live inventory and auto-calculate thresholds?
- Does it send deadline notifications tied to actual facility obligations (302/311/Tier II)?
- Does it generate reports in .t2s format for import into Tier2 Submit or E-Plan, where your state accepts it?
- Can the vendor submit the report to SERC, LEPC, and fire department for you?
- Can I see the total cost (subscription, onboarding, migration and any filing service) in writing?
A demo scorecard: make vendors show, not tell
Take this scorecard into every demo and score only what you see demonstrated, ideally on your own data or the test dataset below. A feature described on a slide or promised for a future release scores zero until it's shown working.
| Criterion | Task to demonstrate | Evidence to capture | Score (0–2) | Notes |
|---|---|---|---|---|
| State output support | Produce the output file your state accepts for a test facility | Exported file name and format; where the state rule came from | 0 / 1 / 2 | |
| Mixtures and EHS | Total an EHS present in a mixture and as a pure product | Calculation showing concentration × mixture weight, plus the total | 0 / 1 / 2 | |
| Imports | Import the test dataset from a spreadsheet | Time taken, rejected rows and the error messages shown | 0 / 1 / 2 | |
| Units | Convert a quantity recorded in gallons to pounds | Conversion basis (density) and where it came from | 0 / 1 / 2 | |
| SDS extraction and review | Extract fields from one of your SDSs and correct one | Confidence shown per field; who corrected it and when | 0 / 1 / 2 | |
| Permissions | Show what a preparer can edit vs. what a reviewer approves | Role settings screen; a blocked edit attempt | 0 / 1 / 2 | |
| Review controls | Route a draft report for approval before submission | Approval record with name and date | 0 / 1 / 2 | |
| Records | Show the history of a changed quantity and the prior year's report | Audit trail entry; retrieved prior filing | 0 / 1 / 2 | |
| Deadlines | Show the reminder for a facility's next Tier II due date | Reminder owner and escalation path | 0 / 1 / 2 | |
| Support | Ask who answers a question in late February, and how fast | Written support terms | 0 / 1 / 2 | |
| Total cost | Price your facility count, modules and services | Written quote marking included, extra and quote-dependent items | 0 / 1 / 2 |
Use the same scorecard, dataset and facility count for every vendor so the scores are comparable.
If you're also weighing a free form-preparation tool, run the same dataset and scorecard through it, and count the steps your team would do by hand. Our comparison of free versus paid Tier II software walks through that alternative workflow.
Bring your own test dataset
A vendor's sample facility is built to demo well. A small dataset with known answers shows whether the software gets the tricky cases right. Copy the fictional rows below into a spreadsheet (or swap in your own products with the same characteristics), work out the expected results yourself first, and ask the vendor to load it.
| Product (fictional) | Composition / identifier | Quantity as recorded | Location(s) | What it tests | Expected result |
|---|---|---|---|---|---|
| Solvent Blend SB-20 | Mixture: 10% Component X (stands in for a listed EHS), 90% non-EHS | 2,400 lb maximum | Paint shop | EHS in a mixture | Contributes 240 lb of Component X (10% × 2,400 lb) |
| Component X, pure | Same EHS as in SB-20 | 300 lb maximum | Warehouse B | Aggregation across products | 540 lb total (240 + 300), at least 500 lb, so reportable whatever its TPQ |
| Hydraulic Oil HO-46 | Single product; SDS density 7.3 lb/gal | 1,450 gal maximum | Maintenance | Unit conversion | 10,585 lb (1,450 × 7.3), at least 10,000 lb, so reportable |
| Caustic Cleaner CC-5 | Single product | 4,200 lb + 3,900 lb + 2,500 lb on the same peak day | Building 1, Building 2, tank yard | Multi-location totals | 10,600 lb combined, reportable; each location listed |
| Coating CT-9 | Mixture: Component Y at 0.8%, not a carcinogen per SDS | 5,000 lb maximum | Paint shop | De minimis concentration | Component Y need not be counted (1% or less); 5,000 lb mixture below 10,000 lb |
| De-icer DI-1 | Single product | 11,000 lb peak in January; 3,000 lb average | Yard | Maximum vs. average | Reportable on the 11,000 lb maximum; average and days on-site recorded |
Fictional data using federal thresholds only (10,000 lb; for an EHS, 500 lb or its TPQ, whichever is lower). Assumes every product requires an SDS under OSHA. Your state may set different thresholds, so check its instructions.
- Load the dataset in front of us. Which rows were rejected or flagged, and why?
- Show the Component X total and where the 10% concentration came from.
- Change Hydraulic Oil HO-46's density. Does the threshold result update, and is the change logged?
- Show Caustic Cleaner CC-5's three storage locations in the report output.
- Explain why Coating CT-9's Component Y is or isn't counted, and where that rule lives in the software.
- Show that De-icer DI-1 is assessed on its maximum, and where average daily amount and days on-site are entered.
- Import the same file again. Do we get duplicates?
- Export the output for our state and tell us which parts of this demo are in the plan you'd quote us.
Ask for the exported file or screenshots for each answer and attach them to your scorecard. If a vendor can only answer a question verbally, record it as a claim to verify, not as a demonstrated capability.
NeoTech evaluation example
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.
SourceEPA Tier II Forms and InstructionsRegulatory statements in this article were checked against the official sources linked above on .