The framework
What good looks like, in six stages
Ask ten organizations how a right of way vegetation program should run and you will get ten answers, most of them shaped by whoever last sold them something. This is the consortium's account of the sequence a competent program follows, written so it can be argued with.
Assess
Establish what is actually on the ground before deciding what to do about it.
- What good looks like
- Species composition, density, growth rate and proximity to the asset, recorded at a resolution that supports a decision. Access conditions and landowner constraints captured at the same time, because they determine what is executable.
- Where it usually goes wrong
- Assessment collapses into a walk-through and a total acreage. Remote sensing measures height and clearance and the species question is quietly skipped, which is the variable that drives everything downstream.
- The question to ask
- What was measured, what was modelled, and what was assumed?
Prescribe
Decide the treatment, and record why.
- What good looks like
- A prescription names the method, the timing and the reasoning — this stem, this treatment, because of this species against this clearance requirement. It is written to be read by the crew who will execute it.
- Where it usually goes wrong
- The prescription is a scope of work. It says how many acres and by when, and carries none of the reasoning, so nobody in the field can tell a good deviation from a bad one.
- The question to ask
- Would the crew know why, not just what?
Execute
Do the work, and record where it departed from the plan.
- What good looks like
- Crews carry the prescription and the authority to flag when it is wrong. Deviations are recorded as exceptions with a reason, which is what keeps the plan and the ground from silently diverging.
- Where it usually goes wrong
- Execution is measured only in acres completed. Deviations happen constantly, are invisible in the record, and surface years later as an unexplained gap between what was specified and what is standing.
- The question to ask
- How is a deviation recorded, and who sees it?
Document
Leave a record that answers questions you have not been asked yet.
- What good looks like
- For any point on the line: what was assessed, what was prescribed, what was done, when, and on whose authority. That is a decision history, and it is what a regulator, a landowner dispute or an integrity investigation will ask for.
- Where it usually goes wrong
- A work history — dates, acreage, invoices. It proves the work happened. It cannot explain why it was the right work, which is the question that actually gets asked.
- The question to ask
- Can you reconstruct a decision two years later?
Measure
Judge the program on outcomes, not on activity.
- What good looks like
- Regrowth rate against prescription, treatment durability, cost across a full cycle rather than a single season, and safety performance measured on leading signals rather than lagging counts.
- Where it usually goes wrong
- Cost per acre becomes the KPI. It is easy to collect, easy to compare, and it rewards the programs that defer cost into the next cycle rather than the ones that remove it.
- The question to ask
- Which of your measures would look worse if the program improved?
Adapt
Feed what you learned back into the next assessment.
- What good looks like
- Results change the prescription. Species that resprouted faster than expected alter the interval; a method that failed on a slope is not specified there again. The loop closes, and the program compounds.
- Where it usually goes wrong
- Each cycle restarts from the same assumptions. The knowledge sits with the crew lead who was there, and leaves when they do.
- The question to ask
- What did last cycle change about this one?
It describes principles, not products. Any number of tools and contractors can implement it well, and naming one here would defeat the purpose — a framework is only useful to a buyer if the body publishing it has nothing to sell.