An observation network that looks beyond project boundaries

The options

The order shown is not a ranking of preference.

1. Option 1

   Observation along project boundaries

   Strengthens responses to changes around facilities and project-level records, but leaves less comparative data across projects and for unused subsurface.

2. Option 2

   Joint observation linking the zones

   Helps compare changes across different uses and zones, but lowers observation density around individual facilities and costs money for access agreements.

3. Option 3

   Baseline observation of unused subsurface

   Leaves pre-development comparative data for users who will enter later, but delays reinforcing monitoring around operating projects.

The situation as it stands

If the procurement deadline passes, each operator will buy its own equipment first, the observation standards will diverge, and the chance to secure a baseline before operations begin will shrink.

The Haedam Underground Shared Zone, a fictional local zone operated by the fictional Subsurface Sharing Cooperative

1. Premise 1Synthetic premise: aquifer facilities, a geothermal project, and an underground storage project want to procure a joint observation network. Existing records are concentrated within each project's boundary, and there is no common baseline for comparing reported changes received from outside the boundaries.
2. Premise 2Synthetic premise: the joint budget cannot observe every candidate site at the same density. The investment committee can commit only to installation and maintenance costs within the cooperative's zone, and observing outside the zone requires a separate access agreement with the adjacent cooperative.
3. Premise 3Synthetic premise: the operating operators want to detect anomalies around their facilities quickly, while adjacent communities ask for changes between the zones to be observed first. Prospective users of subsurface that has not yet been used worry that without pre-development records they may be left holding liability later.

Where it holdsApprove the spatial scope of the observation network to be installed with the cooperative's joint budget and the cost-maintenance commitments.

What can be lost

• Operating operators: if observation around their facilities is inadequate, responses to anomalies will be delayed and disputes over liability unrelated to the cause will generate costs.
• Adjacent communities: if changes outside the boundary are not recorded, it will be hard to obtain evidence to claim losses to their living foundations.
• Future subsurface users: without pre-development data, they cannot distinguish the effects of existing use from the effects of new use, and may lose access opportunities or funding.

What is still unknown

1. Unknown 1It has not been confirmed whether a reported change is the effect of a particular project, a combination of multiple uses, or a fluctuation unrelated to any project.
2. Unknown 2It is unknown how much of the change extending beyond the zone the current candidate observation points will capture.
3. Unknown 3Whether maintenance payments and the interpretation of records will continue after a project ends or the cooperative withdraws has not been settled.

Signals to decide again

• The cooperative's observation lab cross-checks every month whether reported changes outside the boundary and the scope of observation are diverging, and reports to the investment re-review.
• An independent data steward checks each quarter whether the share of records that cannot be compared under common standards is rising.
• The cooperative's accounting audit checks every half year whether withdrawals or closures leave gaps in the maintenance cost commitments.