Building America's Future, Faster
A common data standard for NEPA & permitting that unlocks interoperable systems, automated workflows, and transparent timelines for the infrastructure projects powering American progress.
Why This Matters
America needs to build—fast. Clean energy projects, grid expansion, AI infrastructure, and critical transportation networks all depend on efficient permitting. The NEPA Data Standard unlocks the speed and transparency required to build the future.
Interoperable Data
APIs across agencies enable seamless data exchange and cross-system integration
Automated Workflows
Intelligent screening, routing, and consultation processes reduce manual overhead
Digital-First Documents
Structured, reusable data replaces static PDFs for better analysis and transparency
Predictable Timelines
Real-time dashboards and milestone tracking provide clarity for all stakeholders
Four Service-Delivery Standards
Business Process Modernization
Standardize and optimize workflows using BPMN modeling to create executable, auditable processes
Workflow Automation
Automate screening, routing, and consultation processes to reduce manual overhead and human error
Digital-First Documents
Replace static PDFs with structured, machine-readable data for better analysis and transparency
Minimizing Timeline Uncertainty
Provide real-time visibility into review status and milestones for all stakeholders
Learn more in the CEQ Technology Action Plan
The Data Standard
A unified data model defining core entities, properties, and relationships for interoperable NEPA & permitting systems
Entity Relationship Overview
The standard defines six core entities that work together to create a complete picture of the NEPA review process:
Required & Suggested Properties:
- Project ID (unique identifier)
- Project Name
- Project Description
- Applicant Information
- Location (GIS coordinates)
- Project Type/Category
- Status
- Lead Agency
- Cooperating Agencies
Document Structure & Metadata
All documents must include standardized metadata for discoverability and interoperability:
{
"documentId": "DOC-2025-0001",
"documentType": "Draft Environmental Impact Statement",
"title": "Renewable Energy Project EIS",
"projectId": "PROJ-2025-0042",
"processId": "PROC-2025-0042-EIS",
"publicationDate": "2025-03-15",
"leadAgency": "Department of Energy",
"gisReferences": ["GEOM-001", "GEOM-002"],
"keywords": ["renewable energy", "wind power", "grid"],
"fileUrl": "https://example.gov/documents/DOC-2025-0001.pdf"
}Full specification available at permitting.innovation.gov/resources/data-standard
Process Modeling with BPMN
Business Process Model and Notation (BPMN) makes NEPA workflows explicit and executable, enabling rules-driven automation, parallel consultations, and timeline analytics
Why BPMN?
- Standardized notation understood across agencies and vendors
- Executable workflows that can drive automation engines
- Visual clarity for stakeholders at all technical levels
- Audit trails showing exactly what happened and when
Automation Opportunities
- Automated screening for categorical exclusions using decision rules
- Parallel consultations with multiple agencies simultaneously
- Geospatial checks against protected areas and resources
- Timeline tracking with automated notifications and escalations
Example NEPA Review Process
A simplified BPMN diagram showing how a project flows through initial screening to decision:
Process initiation and completion
Work to be performed
Decision points and branches
Order of execution
Learn More About BPMN
Ten Minimum Capabilities
The CEQ Technology Action Plan defines ten functional capabilities that agencies must implement, with a clear maturity path from foundational to leading-edge
Adopt the core entities, properties, and relationships defined in the NEPA & Permitting Data Standard
Maturity Path
Enable applicants to submit structured data once and share across agencies
Maturity Path
Use rules engines to automatically screen projects for categorical exclusions
Maturity Path
Provide transparent, machine-readable access to screening rules and thresholds
Maturity Path
Track projects, processes, and milestones in integrated case management systems
Maturity Path
Overlay project locations with protected areas, resources, and constraints
Maturity Path
Store, version, and retrieve documents with rich metadata and full-text search
Maturity Path
Collect, categorize, and analyze public comments using NLP and topic modeling
Maturity Path
Maintain complete, auditable records of all decisions and supporting materials
Maturity Path
Expose and consume APIs for cross-agency data exchange and workflow integration
Maturity Path
Implementation Timeline
The CEQ Technology Action Plan establishes a 90-day adoption window for agencies to begin implementing these capabilities. The Permitting Innovation Center provides ongoing support, prototyping, and governance to ensure successful adoption.
Adopt & begin implementing the standard
Prototype new capabilities & integrations
Governance & evolution via PIC
Implementer's Guide
Quick-start guidance for agencies and vendors adopting the NEPA & Permitting Data Standard
Cross-walk your data model
Map your existing database schema to the standard's entities and properties
Publish/consume APIs
Expose core entities via REST or GraphQL APIs; align identifiers for cross-system references
Convert to digital-first documents
Add required metadata to all documents; structure content for machine readability
Model processes in BPMN
Start with categorical exclusions and common consultations; build executable workflows
Add GIS overlays
Integrate spatial analysis tools to check projects against protected areas and resources
Track milestones & events
Implement timeline dashboards showing real-time status and upcoming deadlines
Starter Resources
For Agencies
- • Review the full data standard specification and entity definitions
- • Identify existing systems that need integration or replacement
- • Engage with the Permitting Innovation Center for technical assistance
- • Start with high-volume, repeatable processes (e.g., categorical exclusions)
For Vendors
- • Build adapters/connectors for the standard's API specifications
- • Ensure your products support the required metadata schemas
- • Implement BPMN execution engines for workflow automation
- • Provide migration tools to help agencies transition from legacy systems
Frequently Asked Questions
What if not all fields apply to my agency's processes?
The standard defines required and optional properties. Implement what's relevant; document any agency-specific extensions.
How do we handle sensitive or protected data?
Follow existing security protocols and mark sensitive fields appropriately. The standard supports access controls and redaction.
Can we extend the standard with custom fields?
Yes, but maintain compatibility with the core schema. Document extensions and share with the PIC for potential inclusion in future versions.
Resources & References
Official documentation, specifications, and learning materials
CEQ Technology Action Plan
The complete action plan outlining service-delivery standards and implementation roadmap
Data Standard Specification
Full technical specification including entities, properties, and API schemas
Document Metadata Schema
Required metadata fields for digital-first NEPA documents
E-NEPA Report to Congress
Background on the need for common data standards and interoperability
CEQ NEPA Regulations
Official NEPA regulations and agency implementing procedures
BPMN 2.0 Specification
Official OMG specification for Business Process Model and Notation
Agency NEPA Procedures
Each Federal agency has NEPA implementing procedures consistent with CEQ regulations. These procedures detail how each agency conducts environmental reviews for their specific mission areas.
View Agency Procedures
Help Build the Future of Permitting
Whether you're a federal agency, software vendor, researcher, infrastructure developer, or just someone passionate about building America's future—we want to hear from you. Every perspective matters.
Your submission helps us understand the community's interests and capabilities. We'll follow up with relevant opportunities to contribute.