Field tools · Case studies and failures

What actually happened.

A library of successes is a sales brochure. A library of failures is a teacher. These are composite patterns — not reports of specific named projects — with the lesson that changed the next build.

Back to tools
Composite examples. These patterns combine common failures; they are not a report of a particular household or project. Use them to ask what could fail here, then document your own build with the template below.

The failure library

Six patterns worth recognising

Each entry follows the same shape: what happened, why, what changed, and the lesson that transfers.

Water · well

The well that silted

What happened
A hand-dug well produced cloudy water after the first season and then yielded less each month. The bottom had filled with fine sand and the screen was buried.
Why
The water-bearing sand was not surrounded by a graded gravel pack, and the well was pumped hard during development. Fines migrated into the screen and the sump.
What changed
The well was cleaned, a proper gravel pack and screen were installed, and development was done slowly until the water cleared. A pump rate was agreed.

Lesson: a screen without a matched gravel pack is a filter that clogs. Develop gently, and write down the sustainable pumping rate.

Building · roof

The roof that leaked at the wall

What happened
The roof covering was sound, but water ran down the junction between the roof and the masonry wall during driving rain. The plaster inside stained and the wall stayed damp.
Why
There was no flashing or drained gap at the wall; the render bridged the roof and capillary action pulled water inward.
What changed
A lead-free flashing and a drained air gap were formed, the render was cut back, and the wall was allowed to dry before repair.

Lesson: most roof leaks are at the details — wall junctions, valleys, penetrations and eaves — not in the middle of the field.

Food · cellar

The cellar that warmed

What happened
Roots stored well in the first cold months, then sprouted and rotted in late winter. The cellar smelled sweet and the walls were wet.
Why
The vent was blocked to keep the cellar “warm”, and the door was left open to the heated house. Condensation and higher temperature woke the roots.
What changed
The vents were reopened, the door kept closed, the store inspected weekly, and the crop sorted before storage. A thermometer and humidity meter were hung inside.

Lesson: a cellar is a climate, not a cupboard. Ventilate, measure, and remove the first rotten root immediately.

Food · preservation

The jar that looked fine

What happened
A batch of low-acid vegetables was processed in a boiling-water bath. The jars sealed and looked normal; one lid later bulged and the contents fizzed.
Why
Boiling water does not kill botulinum spores in low-acid food. The sealed, anaerobic jar was the ideal environment for them.
What changed
The batch was discarded, the recipe replaced with a tested pressure-canned one, and the gauge checked. The household switched to fermentation for the rest of the crop.

Lesson: “it sealed” is not “it is safe”. Low-acid canning needs a tested pressure process; when in doubt, throw it out.

Community · tools

The tool nobody owned

What happened
A shared concrete mixer was borrowed repeatedly, returned dirty and eventually left outside with a cracked drum. Nobody felt responsible.
Why
There was no named caretaker, no check-out record and no rule for cleaning or repair.
What changed
The asset was entered in the register with a caretaker and a back-up, a check-out board was hung in the workshop, and a repair fund was agreed.

Lesson: a shared tool needs an owner, a home, a return date and a repair plan. Otherwise it is an abandoned tool with a queue.

Health · emergency

The emergency that took two hours

What happened
A child was badly cut. The household had a first-aid kit, but no one knew the nearest clinic’s night entrance or who had a working vehicle.
Why
The emergency plan existed only as an intention. No contacts were written down and no drill had been run.
What changed
An emergency card was posted in the kitchen, a route and backup vehicle were agreed, and a first-aid drill was held. The kit was restocked.

Lesson: first aid is a chain of skills, contacts and transport. The kit is only one link.

Land · boundary

The boundary that moved

What happened
A hedge was planted “on the line” from memory. A decade later it had spread, the neighbour disputed the line, and the original corner marker could not be found.
Why
No survey was checked, no corner coordinates were recorded, and the hedge was planted on the boundary rather than inside it. The living edge became the de facto line.
What changed
A surveyor re-established the line, new corner markers and coordinates were recorded, a written agreement was signed, and the hedge was cut back and replanted inside the legal line.

Lesson: survey first, plant inside the line, and record the corner markers. A hedge is evidence of occupation, not proof of title. See living boundaries.

Water · cistern

The cistern that floated

What happened
An underground tank was installed in late summer. In the wet season the empty tank lifted a few centimetres, cracked its inlet pipe and allowed muddy groundwater in.
Why
The base was below the wet-season water table, the tank was not anchored, and the backfill was not designed for saturated ground.
What changed
The tank was replaced with an above-ground tank. The new design used the test-pit water level, a structural base and a maintenance plan.

Lesson: measure the wet-season water table, design for buoyancy when empty, and compare underground with above-ground before digging. See underground cisterns.

Document your own

Case-study template

Write one page after a build, a failure or a season. Keep it with the plans and the maintenance register.

Copy these fields into the notebook.
FieldPrompt
ContextPlace, climate, soil, water, household size, skills available, budget.
DesignWhat was built, with what materials and dimensions? Include a sketch.
Cost and labourMaterials, transport, tools, person-days, cash and in-kind contributions.
TimelineWhen it started, what slowed it down, when it was finished or abandoned.
FailureWhat went wrong, when, and how it was noticed. Keep the evidence.
CauseDesign, material, workmanship, weather, use, maintenance or social cause — be specific.
FixWhat was changed, what it cost, and whether it held.
Transferable lessonOne sentence someone else can use without repeating the whole story.
EvidencePhotos, receipts, test results, dates, names of advisers.

The short form

Failure log

Not every failure needs a case study. A one-line log still prevents the same mistake twice.

Copy into the maintenance book.
DateAsset / taskWhat failedCauseFix / change
—————
—————
—————

Link the lesson to the relevant guide — water, preservation, building, governance — and add the asset to the maintenance register.