REA vs HEA: what's actually different in mitigation accounting

Aerial view of a patchwork of green and gold farm fields divided by tree-lined hedgerows under a cloudy sky.

Anyone who's sat through an NRDA scoping call has heard both terms thrown around like they're interchangeable. They're not, and mixing them up in a draft restoration plan is a good way to get a redline from the trustees.

HEA measures habitat, REA measures services

Habitat equivalency analysis runs on a simple premise: injury and restoration get expressed in the same currency, discounted service-acre-years of habitat. You estimate how much a resource was degraded, for how long, and then size a restoration project that delivers an equivalent number of service-acre-years back. HEA is the default in cases involving wetlands, submerged aquatic vegetation, or other habitat-based injuries where the loss ties to a specific acreage and recovery curve.

Resource equivalency analysis is the broader family HEA sits inside. HEA assumes the injured resource and the replacement resource are basically the same kind of thing, marsh for marsh, oyster reef for oyster reef. REA gets used when you're scaling across different resource types, or when the metric isn't acreage at all. It might be fish production, recreational user-days, or some other service metric that doesn't map cleanly onto a habitat footprint. Practitioners also use the term REA for cases where the scaling math is identical to HEA but the unit being equated has changed.

Where the line gets blurry in practice

In a lot of trustee council documents, "HEA" is used as shorthand for the whole equivalency analysis family, REA included, because HEA was the version NOAA formalized first and the name stuck. That's part of why searches for a clean distinction keep landing on circular definitions. The practical test: if the restoration plan scales to acres of comparable habitat, you're doing HEA. If it scales to a different service metric, or you're converting across resource types (lost fish production translated into acres of created spawning habitat, say), you're in REA territory and need to justify that conversion factor in the plan itself.

Why the model matters less than the acreage inputs

Both frameworks run on debits and credits against a baseline. Debits come from the documented injury. Credits come from the restoration action, sized by projected habitat quality and acreage over time. Whichever framework the trustees apply, you still need a defensible number for existing patch size, connectivity between habitat blocks, and edge-to-interior ratio at the proposed restoration site, because those feed straight into the quality multiplier on the credit side.

That's the part that chews up budget early. Most teams either send a crew to walk the parcel and delineate by hand, or they commission a bespoke ecology survey before anyone's confirmed the site is even a viable candidate. If three of your five shortlisted sites get dropped once the trustees see the restoration plan, that's a wasted survey cost on parcels that were never going anywhere.

A land cover classification run against the study area, paired with a connectivity metrics table, gets you patch size and edge density figures fast enough to rank candidate sites before committing to ground-truthing any single one. Habitat Suitability builds that layer and table from annual high-resolution imagery, enough to screen sites and sketch a corridor concept ahead of the survey that eventually has to back up the equivalency analysis numbers.

The short version

HEA scales restoration to match habitat-for-habitat injury. REA is the umbrella term, used when the resource being replaced isn't a one-to-one habitat match, or when the service metric itself differs. Trustees will tell you which one applies to your case. Your job is making sure the site you propose can actually carry the credits the model says it needs.

If you're still narrowing down which parcels are worth that level of scrutiny, pulling fragmentation metrics for a few candidates before committing to fieldwork can save a round of surveys on sites that don't pencil out.