Panel 04 · Field guide

How to read a long horizon

A field guide for the moment after a decision is made, when the work of keeping it moving begins. It is written for planners, keepers and anyone who will inherit a plan they did not write.

Read the sections in order the first time. After that, use the contents to return to the part you need.

Section 1

Slow variables change under fast news

Some things change quickly and make headlines. Others change slowly and rarely make news at all. Soil, groundwater, the growth of trees, the settling of made ground, the condition of a foundation, and the wording of a written agreement all belong to the second group.

Slow variables are easy to ignore because nothing about them demands attention this week. A plan that tracks only the fast variables will be surprised by the slow ones, and the surprise usually arrives after the people who could have acted have left.

When you start a review, list the slow variables that the decision touches. For each one, write down how you would notice a change, and who is responsible for looking.

Section 2

Design for the second owner

The first owner knows why a thing was built. The second owner only has the thing. Many of the questions that matter for a long-lived asset are asked by whoever inherits it, and by then the original authors can no longer answer them.

Ask what the second owner will need to know, and what they will be unable to ask you. Then write those answers down in the place they will look first, which is usually the asset itself: a plate, a label, a file beside the drawing, or an entry in the deed.

A useful test is to imagine the handover happening on a bad day, with no time to read a long document. What would the new owner need in the first ten minutes?

Section 3

Separate a signal from a single event

One bad season, one flood, or one failed part is an event. A signal is a pattern that repeats over time and across places. Treating every event as a trend leads to rushed decisions, and ignoring repeated small events leads to slow failures.

Before you look at new evidence, write down what would change your mind. If you cannot say what a result would mean, the result cannot teach you anything. Keep that note with the reading so the next reviewer can see what was expected.

Plans are rarely wrong all at once. More often a set of small observations, each easy to dismiss, points the same way for years. The guide asks you to keep those observations in one place.

Section 4

Write the stop rules in advance

A stop rule states the condition under which a plan should pause, change course, or be abandoned. It is written before the work starts, when people are calm and the costs are still hypothetical.

Good stop rules name an observable condition, a person who checks it, and the action that follows. A rule that says "if things go badly, reconsider" is not a stop rule. A rule that says "if the intake level falls below the line marked on the design, the keeper calls the review group within the week" can be followed.

Put stop rules inside the plan, not in a separate memo. Plans get read when something goes wrong. Memos do not.

Section 5

Keep records that survive their keepers

A record survives when it can be found, opened, and understood by someone who was not there. That requires three things: a second copy in a different place, a format that does not depend on one program or one account, and a plain index that says what each file is.

• Keep at least two copies in locations with different risks, such as a different flood plain or a different owner.
• Prefer formats that a person can read with common tools. Store a printed or plain-text version of anything that matters.
• Keep the index beside the files, not inside a system that might be closed.
• Name a second custodian and write down how they will be told they hold the record.