# US Facility Environmental Compliance Workspace: One Source of Truth for SWPPP, SPCC, Tier II, RMP, RCRA, and Phase I ESA > A practical guide for EHS managers and environmental consultants on using Rakenne's US Facility Environmental Compliance Program workspace template to keep overlapping facility compliance documents consistent from one shared facility record. Author: map[bio:Founder linkedin:https://www.linkedin.com/in/ricardocabral/ name:Ricardo Cabral] Published: 2026-04-28 Tags: skills URL: https://rakenne.app/learn/tutorials/us-facility-environmental-program-workspace-guide/index.md Environmental compliance for a US industrial or commercial facility is rarely a single-document exercise. A manufacturing site with outdoor storage, oil tanks, hazardous chemicals, waste accumulation areas, and stormwater exposure may need a SWPPP, an SPCC plan, annual Tier II reporting, RCRA contingency planning, RMP applicability screening, and Phase I ESA records for financing or acquisition diligence. The hard part is not writing each document once. The hard part is keeping them consistent. A facility's emergency coordinator, 24-hour alternates, oil inventory, drainage map, SDS list, fire department contacts, spill-response equipment, training records, drill logs, permits, and incident history appear across multiple plans. When those plans are drafted in isolation — often by different consultants at different times — they drift. One plan lists an old plant manager. Another uses a superseded site map. The Tier II inventory does not match the SPCC oil aggregation. The RCRA contingency plan names a responder arrangement that changed two years ago. Rakenne's **US Facility Environmental Compliance Program workspace template** is designed to solve that coordination problem. Instead of treating SWPPP, SPCC, Phase I ESA, RMP, Tier II / EPCRA, and RCRA contingency planning as isolated files, the workspace starts with a shared `facility/` record. Each deliverable reads from the same profile, site-plan notes, SDS inventory, contacts, training matrix, drill log, permits register, and incident log. This guide shows how the workspace is structured, when to use it, and how an EHS manager or environmental consultant can move from facility intake to coordinated deliverables without re-entering the same facts six times. --- ## Why plain templates fall short for facility EHS programs A downloadable SWPPP or SPCC template can help you remember headings. It cannot tell you that the emergency contact table in one plan conflicts with the Tier II cover letter, or that the oil quantities in the SPCC plan no longer match the SDS inventory. | Concern | Standalone templates | Rakenne facility workspace | | --------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | **Shared facility data** | Re-entered separately in each document | Stored once under `facility/` and reused across deliverables | | **Inventory consistency** | Oil, hazardous chemical, and waste quantities can drift | SDS inventory acts as the source for SPCC, Tier II, RMP, and RCRA screening | | **Contact accuracy** | Emergency contacts copied between files manually | One contact roster feeds plans, notices, and response procedures | | **Map and site-plan reuse** | Each plan may reference a different drawing | Site-plan narrative and uploaded map references stay in one place | | **Regulatory traceability** | Generic boilerplate may omit citations | Workspace guidance anchors sections to 40 CFR 122, 112, 68, 370, 264/265, ASTM E1527-21, and related standards | | **Program continuity** | Updates depend on whoever last edited a file | Missing values are written back to shared assets before outputs are updated | The difference is structural: the workspace makes the shared facility record the canonical input. Deliverables become views of the same operating reality, not disconnected documents. --- ## The coordinated facility workflow The template is designed around two common buyer journeys. First, an **in-house EHS or facilities manager** needs a recurring program. They want the facility profile, SDS inventory, contacts, training records, permits, and incidents in one place so annual SWPPP/SPCC reviews, March 1 Tier II reporting, drill updates, and operational changes do not require starting from scratch. Second, an **environmental consultant** may be engaged for one deliverable — a SWPPP for a new industrial tenant, an SPCC plan after a tank expansion, or a Phase I ESA during acquisition. The workspace still helps because facts gathered for that single deliverable can be saved in reusable files, making the next engagement faster and more defensible. The recommended workflow has four phases: | Phase | Goal | Workspace behavior | | ---------------------------- | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | **1. Program intake** | Populate facility facts once | Complete `facility/profile.md`, `facility/sds-inventory.csv`, `facility/contacts.md`, and related assets | | **2. Applicability triage** | Decide which plans are likely required | Check stormwater exposure, oil thresholds, SDS quantities, RCRA generator status, RMP substances, and diligence context | | **3. Deliverable execution** | Draft or update one plan at a time | Use the relevant skill or workspace instructions while reading the shared assets first | | **4. Consistency review** | Prevent cross-document drift | Summarize which shared files were read or updated, outputs produced, assumptions, and adjacent obligations | --- ## Step 1: Build the shared facility record The workspace provisions a stable `facility/` folder. These files are intentionally plain Markdown or CSV so they can be read, reviewed, edited, and exported without locking your program data inside a proprietary form. | File | Purpose | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- | | `facility/profile.md` | Legal name, EPA FRS ID, NAICS/SIC, county, coordinates, ownership, operator, corporate family, employee count, and operating hours | | `facility/site-plan.md` | Drainage map notes, outfalls, oil storage, hazardous-waste accumulation areas, emergency exits, muster points, and drawing references | | `facility/sds-inventory.csv` | Chemical and oil inventory for Tier II reporting, RMP threshold checks, RCRA characterization, and SPCC oil aggregation | | `facility/contacts.md` | Emergency coordinators, 24-hour alternates, LEPC, SERC, fire department, NRC, insurer, qualified PE, and consultant contacts | | `facility/training-matrix.md` | Required courses, assigned roles, last-completed dates, and next-due dates | | `facility/drill-log.md` | SPCC drills, RCRA contingency drills, RMP tabletop exercises, findings, and corrective actions | | `facility/permits-register.md` | NPDES, RCRA EPA ID, RMP, Title V, and other permit identifiers or status notes | | `facility/incident-log.md` | Releases, near-misses, fines, corrective actions, and closure evidence | A typical intake can begin from a short conversation. {{% chat-window title="Facility intake" %}} > **You:** Set up the facility record for Great Lakes Coatings LLC in Toledo, Ohio. We manufacture industrial coatings. About 85 employees, one main production building, outdoor loading dock, four 1,000-gallon aboveground oil tanks, solvent storage, and a wastewater pretreatment permit. Our EHS manager is Dana Kim. > > **Agent:** I’ll start by updating the shared facility assets rather than drafting a plan immediately. I’ll save the organization identity and operating context in `facility/profile.md`, note the outdoor loading dock and tank farm in `facility/site-plan.md`, add Dana Kim to `facility/contacts.md`, and flag missing values I still need: EPA FRS ID, coordinates, NAICS code, receiving water/outfall details, SDS inventory, emergency alternates, and current permit numbers. > > Before we decide which deliverables apply, can you upload or paste the SDS inventory and any existing site map, SWPPP, SPCC plan, or Tier II report? {{% /chat-window %}} This matters because the agent is instructed to ask for missing values once, then write the answer back to the appropriate shared asset. The canonical facts should not be buried only inside an output document. --- ## Step 2: Triage which environmental deliverables apply Once the shared files have enough data, the workspace can help screen for likely obligations. This is not a substitute for counsel, a qualified professional engineer, or regulator review, but it gives the EHS team a structured way to reason from the same facility facts. {{% chat-window title="Applicability triage" %}} > **You:** Based on what we have, which plans should we prioritize? > > **Agent:** I’ll read `facility/profile.md`, `facility/sds-inventory.csv`, `facility/contacts.md`, `facility/site-plan.md`, and `facility/permits-register.md` before making recommendations. > > Initial triage: > > - **SPCC:** Likely applicable. Four 1,000-gallon aboveground oil tanks exceed the 1,320-gallon aggregate aboveground threshold in 40 CFR 112, subject to the reasonable-expectation-of-discharge analysis. > - **SWPPP / NPDES:** Needs review. Outdoor loading and industrial activity may require MSGP coverage depending on sector, exposure, outfalls, and receiving waters under Clean Water Act §402 / 40 CFR 122. > - **Tier II / EPCRA:** Needs SDS threshold review. I need maximum and average daily quantities in the SDS inventory to compare against 40 CFR 370 thresholds and state requirements. > - **RMP:** Needs regulated-substance threshold review under 40 CFR 68. Current solvent list is incomplete. > - **RCRA contingency plan:** Depends on generator status. If the facility is an LQG, contingency planning and quick-reference expectations become central. > - **Phase I ESA:** Event-driven. Relevant for acquisition, refinancing, lender diligence, Brownfields, or baseline environmental condition documentation under ASTM E1527-21 / 40 CFR 312. {{% /chat-window %}} The point is not to force every facility through every document. The point is to make the applicability logic visible and tied to the shared files. --- ## Step 3: Draft one deliverable without losing program context The workspace supports focused work. A consultant can still say, “I only need an SPCC plan today.” The difference is that the SPCC plan reads the same site plan, contacts, and inventory that future Tier II, RCRA, or RMP work will read. {{% chat-window title="SPCC planning" %}} > **You:** Start with the SPCC plan. We have four 1,000-gallon used-oil tanks outdoors, one 500-gallon diesel day tank indoors, and hydraulic oil totes in production. > > **Agent:** Before drafting, I’ll update `facility/sds-inventory.csv` with the oil-containing containers you listed and read the site-plan notes for drainage and secondary containment. > > SPCC applicability appears likely because aggregate aboveground oil storage exceeds 1,320 gallons. I’ll structure the plan around 40 CFR 112, including facility description, oil inventory, drainage and discharge potential, secondary containment, inspections, personnel training, spill-response procedures, five-year review, and PE certification considerations. > > I still need: tank construction details, containment capacity, nearest storm drain/outfall, inspection frequency, spill kit locations, prior discharge history, and whether a qualified PE has reviewed the site. {{% /chat-window %}} The same pattern applies to SWPPP work. Outfalls, drainage areas, exposed materials, BMPs, inspection schedules, and corrective actions should update the shared site-plan and incident records where appropriate. --- ## Step 4: Use the SDS inventory as the bridge across SPCC, Tier II, RMP, and RCRA The SDS inventory is the most important cross-document asset in the workspace. It is not just a list of chemicals. It is the bridge between multiple regulatory decisions: - SPCC oil aggregation under 40 CFR 112 - Tier II hazardous chemical reporting under EPCRA §§311–312 and 40 CFR 370 - RMP threshold quantities under Clean Air Act §112(r) and 40 CFR 68 - RCRA waste characterization and generator-status context - HazCom and SDS library alignment under 29 CFR 1910.1200 {{% output-excerpt %}} | Chemical / product | CAS | Max quantity | Location | Hazard categories | Program uses | | ------------------ | ---------- | ------------ | --------------------------------- | ------------------------ | ------------------------------------- | | Used oil | Mixture | 4,000 gal | Outdoor tank farm | Combustible liquid | SPCC aggregation, Tier II screening | | Diesel fuel | 68476-34-6 | 500 gal | Generator room | Flammable liquid | SPCC aggregation, Tier II screening | | Xylene blend | Mixture | 2,200 lb | Solvent room | Flammable, health hazard | Tier II screening, RMP review, HazCom | | Waste solvent | Mixture | 1,500 lb | Hazardous-waste accumulation area | Ignitable waste | RCRA generator-status review | {{% /output-excerpt %}} When the inventory changes, multiple documents may need review. That is exactly why the workspace keeps the inventory in `facility/sds-inventory.csv` rather than scattering quantities across plans. --- ## Step 5: Keep regulatory anchors visible The workspace instructions require plan content to be grounded in the governing authority and to cite specific references where practical. The core anchors are: | Deliverable | Primary anchors | | ------------------------- | ----------------------------------------------------------------------------------------------------------- | | **SWPPP / NPDES** | Clean Water Act §402, 40 CFR 122, applicable CGP or MSGP | | **SPCC** | 40 CFR 112, including applicability, containment, inspections, training, and certification paths | | **Phase I ESA** | ASTM E1527-21 and EPA All Appropriate Inquiries at 40 CFR 312 | | **RMP** | Clean Air Act §112(r), 40 CFR 68, Program 1/2/3 criteria, and relevant 2024 amendments | | **Tier II / EPCRA** | EPCRA §§311–312 and 40 CFR 370, including March 1 annual reporting | | **RCRA contingency plan** | 40 CFR 264.51 / 265.51 and LQG contingency-plan expectations | | **Related context** | HazCom/SDS at 29 CFR 1910.1200, HAZWOPER at 29 CFR 1910.120, Title V at 40 CFR Part 70, AHERA at 40 CFR 763 | This is especially important for consultants. A client-ready draft should distinguish facility facts, assumptions, regulatory interpretations, and sections requiring professional review — for example, PE certification for an SPCC plan or environmental professional review for a Phase I ESA. --- ## Step 6: End each deliverable with a consistency review After producing or updating a plan, the agent should summarize more than the output file. It should explain how the work affected the shared workspace. {{% chat-window title="Consistency review" %}} > **Agent:** SPCC draft complete. Here is the workspace impact summary: > > **Shared assets read:** `facility/profile.md`, `facility/site-plan.md`, `facility/sds-inventory.csv`, `facility/contacts.md`, `facility/training-matrix.md`, `facility/drill-log.md`, `facility/permits-register.md`, `facility/incident-log.md`. > > **Shared assets updated:** Added diesel day tank and hydraulic oil totes to `facility/sds-inventory.csv`; added spill-kit locations to `facility/site-plan.md`; added annual SPCC briefing to `facility/training-matrix.md`. > > **Outputs produced:** `output/spcc-plan-draft.md` and `output/spcc-open-items.md`. > > **Open items:** Confirm secondary-containment capacity; add PE contact; verify storm-drain connection to receiving water; confirm prior reportable discharges. > > **Adjacent deliverables to consider:** Tier II threshold review based on the updated inventory; SWPPP review because the outdoor tank farm and loading area may affect stormwater exposure. {{% /chat-window %}} That closing review turns each document into a program maintenance event. The workspace gets more accurate over time. --- ## Who should use this workspace Use the US Facility Environmental Compliance Program workspace when you manage or advise facilities that have overlapping environmental documents, especially: - manufacturing plants with outdoor industrial activity or stormwater exposure; - facilities with aboveground oil storage, hydraulic systems, generators, or used-oil tanks; - sites with reportable hazardous chemicals and recurring Tier II obligations; - large quantity generators or facilities approaching RCRA contingency-plan thresholds; - companies preparing for acquisition, refinancing, Brownfields diligence, or Phase I ESA review; - environmental consultants who want to reuse facility facts across repeat engagements. It is less useful for a one-time, low-complexity document where there is no recurring facility record to maintain. The template shines when the same facility facts appear in multiple compliance artifacts. --- ## Getting started Create a new project with the **US Facility Environmental Compliance Program** template and start in one of two modes: 1. **Program setup** — populate the facility profile, SDS inventory, contacts, site-plan notes, permits register, training matrix, drill log, and incident log before deciding which plans apply. 2. **Single deliverable** — focus on one document now, while still writing reusable facts back to the shared `facility/` files. If you already have prior SWPPPs, SPCC plans, Tier II reports, SDS spreadsheets, site maps, permits, or Phase I ESA reports, upload them first. The fastest path is not to start with a blank page — it is to extract the facility truth you already have, normalize it into the shared workspace, and let each deliverable cite the same source. That is the core promise of the template: one facility, one source of truth, many compliance outputs. --- Back to [Tutorials](https://rakenne.app/learn/tutorials/index.md)