Environmental Impact Assessment Editing and Proofreading Services

An impact assessment concludes that a project's effect on a wetland is "not significant." The community group reviewing it, and the developer who commissioned it, both accept the word at face value, but neither can find the actual threshold the assessment used to decide that this specific level of habitat loss falls below the line rather than above it. The conclusion is presented as though significance were self-evident from the data. It is not; it is a judgement made against a criterion, and the criterion is the part of the assessment that determines everything downstream of it and is nowhere in the document.

We edit what environmental consultancies and agencies produce to assess and disclose project impacts — significance determination criteria and their application, impact assessment methodology and threshold disclosures, mitigation measure and monitoring commitment documentation, and the correspondence explaining how a specific significance finding was reached. Our editors work on the word "significant" and the criterion standing behind it that the document needs to actually show.

The stated significance threshold is what an impact assessment's conclusion actually rests on, and its failure is a finding of significant or not significant presented as though it were a direct reading of the data rather than a judgement against a criterion that needs to be shown. Not significant is a conclusion; the assessment needs to show what threshold of habitat loss, population effect, or other measured impact would have crossed into significant, and where the actual project's impact falls relative to that line. We work through these so the specific threshold used for each significance determination is stated explicitly, since a reader cannot evaluate whether a judgement was reasonable without knowing what standard it was judged against, and a threshold left unstated makes the conclusion unfalsifiable; so the actual measured or predicted impact is stated in the same units as the threshold, given that a reader needs to see the two numbers next to each other to understand how close the finding actually was, rather than a conclusion that treats a narrow margin and a wide one identically; so cumulative effects with other nearby projects are addressed specifically, because a project's impact assessed in isolation can understate what the wetland actually experiences alongside other developments, and a threshold applied only to this project's individual contribution can miss a cumulative effect that matters; so mitigation measures relied upon to reach a not-significant conclusion are stated as a condition of that conclusion, given that a finding of not significant that depends on a mitigation measure being implemented is different from one requiring no mitigation at all, and this distinction needs to be visible; so monitoring commitments tied to an uncertain prediction are stated with what would trigger a review, rather than left as a general commitment to monitor; and so a stakeholder's specific question about how a significance finding was reached receives the actual threshold and calculation, not a repetition of the conclusion. Assessments written this way let a significance finding actually be checked rather than simply accepted.

Everything you send is treated in confidence, including impact data, methodology and stakeholder correspondence. We are editors rather than environmental assessors, ecologists or regulators, and we offer no view on impact significance, methodology or assessment findings. What we can do is make sure the threshold behind the conclusion is actually visible.