For a single-site organisation of under fifty people, a roadmap is about a week of work: a baseline footprint, a costed list of reduction measures with dates and owners, and a way of checking progress each year. Cost rises with sites, suppliers to engage, and any external verification.
Four things, and an organisation that has all four has a roadmap whatever it calls the document:
Anything else in the document is presentation.
| Stage | Effort | What decides it |
|---|---|---|
| Baseline footprint | 1 to 3 days | Whether energy, travel and purchase data are already in one place |
| Options and costing | 1 to 2 days | How many measures are genuinely available: a tenant cannot replace the boiler |
| Written roadmap and board paper | 1 to 2 days | Whether trustees or a board have to approve it |
If no baseline exists, that first stage is the whole cost driver, and it is the same work described in working out a footprint without buying software.
Twelve months of energy bills, a mileage or expenses export, and a purchase ledger already grouped by category. Handing those over at the start removes most of the first stage. So does accepting a rough number in year one: precision can be added later, and a roadmap built on an approximate baseline is still a roadmap.
Buying offsets before doing the reductions. Offsets do not change any of the four things above, they cost every year, and they are the first thing a sceptical funder or journalist asks about. Reduce first, offset the remainder last, if at all.
By the job, after a look at what data exists, so the quote reflects the days actually needed rather than a package. The look itself is free.
Send me twelve months of energy bills and I will tell you whether your baseline is a one-day job or a three-day one, before you commit to anything.
DON'T PANIC
cyberspaceroad.com