What it is
Plain description. What gets installed, changed or done.
Mechanism
Why it works, physically. If we cannot state the mechanism, we do not understand the solution well enough to sell it.
Expected effect
| Metric | Expected change | Range | Tier | Basis |
|---|---|---|---|---|
State ranges, not single numbers. State which of resilience or sustainability (or both) this serves — see principle 8.
Preconditions
When does this apply? Site characteristics, existing systems, climate conditions, occupancy patterns required for it to work.
When it does NOT apply
Equally important, and more useful to a reader. Conditions under which this is the wrong answer.
Cost
| Item | Range | Notes |
|---|---|---|
| Capital cost | ||
| Installation | ||
| Annual running cost | ||
| Annual maintenance | ||
| Expected lifespan | ||
| Replacement / end of life |
Cost recorded with the same rigour as benefit — principle 7.
Regulatory position
Permits required, codes engaged, grants available, restrictions. With a date, because this changes.
Local availability
Can this be bought and installed in Mallorca, by whom, with what lead time? A solution with no local installer is a research topic, not an offer.
Side effects and interactions
What else does this change? Other flows affected, maintenance burden introduced, failure modes created, dependencies added.
Failure modes
How does it break, how would we notice, what does it cost to fix?
Measurement plan
How we would verify this on a real site: which metrics, baseline duration, verification duration, confounders to normalise for. Links to metric definitions.
Evidence status
What we actually have: modelled, vendor-claimed, published-literature, measured elsewhere, measured by us. Be exact.
Sites where deployed
| Site | Date | Result | Case study |
|---|---|---|---|