When high value gets counted twice

Anyone who has redone the impact tables in an EA knows this. The first pass goes by feel: high value, high impact, whatever the project does. Then the comments ask why one is major and the next moderate, and nobody can show the method.

One case on our Try page: the impact tables for a road reconstruction. Yesper wrote the method, value and sensitivity rated apart, and redid the tables. The old tables set sensitivity equal to value, so high value counted twice: impacts overstated for 3 of 8 resources, three construction factors never rated.

The method is in the draft before the comments ask for it. The impact follows what the project does, and the stockpile nobody rated shows up in time to move it. Same for the rest of the Try page: an EA put back into tracked changes, a creek's flow after a pit expansion.

Try it yourself →