We use essential cookies to make our site work. With your consent, we may also use non-essential cookies to improve user experience, personalize content, and analyze website traffic. For these reasons, we may share your site usage data with our analytics partners. By clicking “Accept,” you agree to our website's cookie use as described in our Cookie Policy. You can change your cookie settings at any time by clicking “Preferences.”
For developers, applicants, environmental consultants

The full toolset. And the publishing surface for the council and community views.

HRA, BACT, NSR significance, Title V applicability, generator fleet configuration, zone-of-impact mapping, scenario modeling, AI agent assist, and a shared workspace with the reviewing agency. The same workspace publishes the Community Impact Brief, council briefing, and community dashboard your project produces.

Read the developer brief

Workspace

A unified workspace for the permit application

A single project workspace where the air permit, the HRA, the BACT analysis, the generator fleet config, and the public-engagement surface live together. Built for environmental consultants, applicants, and project managers who currently juggle six tools to assemble a single filing.

What this means for your team

  • One project workspace replaces a stack of spreadsheets and modeling tools
  • Multi-user access for the applicant team, the consultant, and reviewing agencies
  • Permit-level audit trail captures every input change for the record

HRA

Health Risk Assessment, mapped

A full HRA built on EPA AirToxScreen and California OEHHA methods. Cancer risk, chronic non-cancer hazard index, acute hazard index. Mapped to the modeled receptor grid so you can see exactly where the modeled risk lands. Inputs and assumptions are logged for the record.

What this means for your team

  • Cancer and non-cancer hazard outputs at every modeled receptor
  • Methodology citations on every step so the analysis holds up at the agency
  • Comparable across alternative scenarios for the conditions conversation

BACT

BACT analysis, with the case-law and precedent record

Best Available Control Technology analysis structured against the actual agency precedent for your project type and pollutant. Pulls the technology-cost effectiveness comparison, the energy and environmental impacts evaluation, and the prior agency determinations into a single defensible memo.

What this means for your team

  • Top-down BACT memo assembled from your project inputs
  • Comparable agency determinations referenced and cited
  • Cost-effectiveness analysis ($/ton) computed against the cost basis

NSR

NSR significance and Title V applicability checks

New Source Review significance thresholds and Title V applicability triggers, computed from the live emissions inventory. The view highlights which thresholds your project crosses, what permit category that pulls you into, and what the modeled headroom looks like before each trigger.

What this means for your team

  • Automatic NSR significance threshold checks per pollutant
  • Title V major-source applicability evaluation against current inventory
  • Headroom analysis so you can see how close the project sits to each trigger

Generator Fleet

Generator fleet configuration at the unit level

Configure dozens to hundreds of backup generators per project at the unit level. EPA Tier 2, Tier 3, or Tier 4 emission factors. Site-specific runtime assumptions for testing and outage events. Annual emission totals roll up automatically into the inventory and the HRA.

What this means for your team

  • Unit-level fleet configuration with the correct EPA emission factors
  • Runtime hour assumptions per scenario, audited in the inventory
  • Roll-up totals feed the HRA, BACT, and NSR analyses

Zone of Impact

Zone-of-impact mapping with sensitive receptor overlay

Air dispersion modeling across the project footprint, mapped against schools, hospitals, daycare centers, residential blocks, and other sensitive receptors. The view makes the spatial distribution of the impact obvious to a non-technical reader so the public hearing can focus on conditions, not on whether the impact is real.

What this means for your team

  • Dispersion modeling outputs mapped to the receptor grid
  • Sensitive receptor overlay flags schools, hospitals, daycares, and homes
  • Side-by-side comparison across alternative permit conditions

Simulation Lab

Simulation Lab for scenario modeling

Rerun the entire underlying model against alternative inputs. Different generator fleet sizes, different runtime caps, different water sourcing plans, different stack heights. Each run carries forward into the HRA, the zone-of-impact, and the NSR analysis. The lab is what makes the conditions conversation specific instead of theoretical.

What this means for your team

  • Side-by-side comparison of multiple permit scenarios
  • Each scenario propagates into HRA, zone-of-impact, and NSR outputs
  • Designed for the conditions negotiation, not for the desk-top exercise

Cost of Delay

Cost-of-delay analysis tied to your project economics

Quantify the economic cost of an extended entitlement timeline against the cost of independent analysis up front. Construction schedule risk, financing carry, equipment escalation, ratepayer effects. Designed to keep the timeline conversation honest with the applicant team and the council in the same room.

What this means for your team

  • Project-economics view of the entitlement timeline
  • Comparable to alternative permit conditions, not just yes versus delay
  • Useful in financing conversations as much as the council briefing

Agency Workflow

Agency-applicant shared workflow

A shared workspace for the reviewing agency and the applicant. Document filings, modeling inputs, completeness checks, and review comments all sit on the same record. The agency receives a complete record on day one. Reviewer back-and-forth drops because iteration happens before submittal, not in the deficiency letter.

What this means for your team

  • Single record for the applicant team, the consultant, and the agency
  • Completeness checks before submittal reduce deficiency letters
  • Audit trail on every input change is preserved for the agency record

AI Agents

AI agents to draft, summarize, and check the technical record

A multi-agent workspace that drafts narrative sections of the application, summarizes long documents, runs cross-checks against agency precedent, and flags gaps in the inventory. Designed as an assistant for the consultant team, with full human oversight on every output.

What this means for your team

  • Draft narrative sections informed by the live inventory
  • Summarize long agency comments and prior precedent in seconds
  • Cross-check the application for missing or inconsistent inputs

Publishing

Publishing surface for the Impact Brief, council, and community views

The same project data drives a council briefing pack, a Community Impact Brief, and a public-facing community dashboard. As the applicant, you control what is published and when. As the consultant, you stop maintaining a parallel set of public communications, because the publishing surface is built into the workspace.

What this means for your team

  • One configuration produces the Impact Brief, council briefing, and community dashboard
  • Control which data publishes and when each release goes live
  • No parallel set of public communications to maintain by hand

Impact Brief

Community Impact Brief for the questions the public will ask

A public-facing briefing view that helps applicants prepare for the hearing room without turning transparency into a sales pitch. It shows known benefits, workforce and education metrics, health and safety context, utility and water questions, noise concerns, and open data questions that may need additional inputs or optional study.

What this means for your team

  • Show known benefits and commitments without burying the unanswered questions
  • Identify where additional detail is available if the project team provides inputs
  • Preview the public conversation forming around the project before it reaches the hearing

Publish

One toggle, one public landing page

When the applicant or consultant is ready, the project workspace publishes to a public-facing landing page at a clean public URL. The page renders the Impact Brief, Health, Environmental, Trust and Sources tabs from sanitized data. The publish flag is per-permit and can be turned off at any time. A tenant-level kill switch suppresses all publishing if your organization is not ready to share publicly.

What this means for your team

  • Per-permit publish and unpublish from inside the project workspace
  • Server-side data sanitization so internal-only fields never leak to the public view
  • Tenant-level kill switch (allowPublicSharing) suppresses publishing for the whole org

What your project produces

Your filing also produces the Impact Brief, council briefing, and community dashboard.

The same project data that drives your HRA, BACT, and NSR analysis also generates a regulator-grade briefing for the council, a public-friendly Community Impact Brief, and a public-facing dashboard for the community. You configure once. The audience-specific views publish from the same source of truth, so no party reads a different version.

What your council will read

The officials view

The briefing pack, complete record, scenario comparison, and constituent dashboard your filing produces for the council and planning staff.

View features
What your community will see

The community view

The public dashboard, project forum, sentiment monitor, and commitment tracker that publishes alongside the application.

View features
Independence as an asset

You fund the analysis. Everyone reads the same scoreboard.

The applicant pays for the work. The methods are published EPA AirToxScreen and California OEHHA. No party can quietly alter the numbers. Communities now distinguish between PR-funded data and independent analysis. Funding independence once, transparently, is designed to do for community trust what no communications budget can.

Read the developer brief: timelines, post-approval risk, business model

See LSARS on a real project.

Bring an active permit. We will load it and walk you through the consultant workspace, the council briefing, and the community dashboard end to end.