EnviGlobe

EnviGlobe expertise guide

Air Dispersion Modelling for Industrial Projects

How source data, meteorology, receptors and model choices support defensible air-quality decisions.

Air quality monitoring beside an Egyptian industrial complex
Illustrative image only; it does not depict the actual project.

Air dispersion modelling estimates how emissions from defined sources may affect ambient concentrations at receptors. Its value depends on representative emissions, terrain and building treatment, meteorology, background concentrations and transparent model evaluation.

Decision in brief

Use modelling to test a specific permit, design or risk question; do not treat colorful contour maps as the conclusion.

Who should use this guide, and what decision does it support?

Industrial developers, designers, permitting teams and operators evaluating stacks, process emissions or cumulative air quality.

Before work begins, agree the question the assessment or review must answer and who will rely on the result. A design decision, lender report and regulatory submission need different levels of detail. Defining the use case early prevents teams from collecting large amounts of information that do not change the decision.

A practical implementation sequence

  1. Define pollutants, averaging periods, scenarios and receptors.

    Set the purpose, boundary and decision timetable in writing. Name the people who will supply information and approve the result, and record any legal, lender or client framework that changes the scope.

  2. Quality-check stack, process and fugitive-emission inputs.

    Build a source register before analysis begins. Check dates, units, ownership and completeness so later calculations and findings use consistent information rather than convenient but incompatible files.

  3. Select representative meteorology, terrain and building data.

    Test important claims against more than one form of evidence where practical. Site observation, interviews, measurements and operating records often reveal whether a documented control is actually used.

  4. Configure and run justified operating and sensitivity scenarios.

    Evaluate significance against the agreed decision criteria and show assumptions or sensitivity clearly. Separate observed facts, calculations, professional judgement and information that remains unavailable.

  5. Interpret results with background, uncertainty and mitigation options.

    Turn the result into an implementable output. Assign owners, deadlines, resources, monitoring indicators and objective closure evidence, then retain the approved version for future review.

Air quality monitoring near industrial infrastructure in Egypt
Illustrative image only; it does not depict the actual project.

Data and evidence required

The conclusion becomes more reliable when boundaries, data sources, responsibilities and quality checks are documented from the start. Possessing a file is not enough: record its period, unit, owner, review method and any adjustment made.

  • Source coordinates, heights, flows and temperatures
  • Emission rates and operating scenarios
  • Meteorological and surface-characteristic data
  • Terrain, buildings and receptor grids
  • Background monitoring and model files

Maintain a simple evidence register that connects each finding to its source, identifies unavailable information and explains how uncertainty was handled. This reduces review time and makes the conclusion easier to update when design, operations or requirements change.

How management should use the result

A decision-ready output distinguishes issues that prevent a decision, actions that must close before a defined milestone and improvements that can be managed through operations. Every action should have an owner, date, resources and objective closure criterion instead of a general instruction to “comply with requirements”.

Put a short executive answer first, with the analysis and evidence underneath. Management, finance, legal and technical readers can then use the level they need while the full reasoning remains traceable and reviewable.

Common mistakes to avoid

  • Using maximum emissions with inconsistent operating assumptions
  • Ignoring building downwash or complex terrain
  • Selecting weather data for convenience alone
  • Reporting contours without receptor tables and limitations

A recurring mistake is to confuse a completed report with effective implementation. Quality is demonstrated when the output informs a decision, changes a control or closes a gap with evidence—not by page count or table density.

Frequently asked practical questions

When should the work begin?

Start before design freeze, financing approval or a submission deadline. Early work gives teams time to resolve missing data and change options at lower cost.

Is a document review sufficient?

Not for most material assignments. Documents show the intended system; interviews, site observation and operating records test whether controls work in practice.

How should incomplete data be handled?

Record the gap and its effect, use a conservative estimate where justified and define how better data will be obtained. Do not hide uncertainty inside a final number that appears more precise than the evidence supports.

What makes an output reviewable?

Clear boundaries, traceable sources, retained versions, disclosed assumptions, internal review and an identified approval owner.

Checklist before sign-off

  • Input units and coordinates are verified
  • Scenarios match realistic operations
  • Model and options are justified
  • Background and cumulative effects are addressed
  • Files allow independent reproduction

This checklist does not replace project-specific legal or contractual advice. Confirm the applicable framework for every assignment and obtain appropriate advice where exposure is material.

Official references

Related guides

Need to apply this to your project?

Discuss the requirements and next practical decision with the EnviGlobe team.

Request a consultation