EIA Tool

Consulting teams in Nepal prepare BES, IEE, and EIA reports under the Environment Protection Act and Regulations. The report follows a fixed list of chapters. The content changes by sector, and several people usually write one document.

The work gets stuck when chapter ownership is unclear, and when field notes have to become the kind of writing the report expects without losing that order. The people who use the tool are the firms that draft and assemble the report.

We built a licensed workspace with Goma Engineering Consultation. A team signs in, chooses BES, IEE, or EIA, and opens the report contents. Each person works on the chapters assigned to them.

A section is a form, with a sample beside it so the writer can see the shape it should take. Generate writes that section into a shared Google Doc. The lead assigns chapters and can see how much of the license has been used. Each generation counts against that license.

The report stays in Google Docs, where the team already finishes and shares it. The forms keep every section tied to the contents. A free chat box and an in-app document editor stayed out of the first version.

This version covers chapters 1 to 4 of the energy, water, and irrigation transmission-line template. Later chapters are outlined. Review sign-off, government submission, and payments are outside this version.

React runs the report screens. Express and MongoDB handle accounts, licenses, and chapter assignment. OpenAI writes each section from the form. Google Docs holds the shared report. Email is used to sign people in.

Clients can run a team on one report: pick the assessment type, follow the contents, fill the sections, and generate text into a Google Doc. Leads assign chapters and watch usage.

What is live covers the opening chapters of an energy, water, and irrigation transmission-line report.