compliance-timeline

You can forecast NEPA timelines by executing the estimation script with a fire ID, pathway, and optional start date. The skill outputs milestones, comment periods, and consultation details for single or multiple concurrent pathways.

The best way to plan ESA and NHPA consultations is to include them when generating a NEPA timeline. The skill anticipates formal and informal consultations across agencies to keep environmental review projects on schedule.

Yes, you can generate schedules for single or multiple concurrent NEPA pathways and adjust for different start dates. This allows you to compare timeline outcomes and dependencies across different regulatory scenarios.

Yes, the timeline estimation outputs a reasoning chain suitable for integration with the Python estimation script. This provides transparency in how milestones, comment periods, and consultation dates are calculated.

To generate a NEPA compliance timeline, you need a fire ID, a selected pathway (CE, EA, or EIS), and an optional start date. These inputs drive the scheduling logic for milestones and agency consultations.

You should use a CE timeline for actions with minimal environmental impact and an EIS schedule for actions significantly affecting the environment. The skill estimates distinct milestones and dependencies for each NEPA pathway.