Blog

It’s February. Your automatic waterer is a block of ice, the coop floor is standing water, and you’re hauling 50-pound feed bags through a doorway that’s three inches too narrow for a wheelbarrow.

This didn’t happen because you’re bad at building. It happened because the free plan you found online was designed for a flat lot in Texas, not a sloped yard in Oregon with 40 inches of annual rain.

The Three Mistakes Almost Everyone Makes

1. Ignoring drainage. The most common failure. A coop placed without accounting for slope, runoff, and seasonal water movement will flood. In the PNW, that means a mud pit from November through March — and sick birds.

2. Building for the wrong climate. Plans designed for Texas or Georgia don’t account for the PNW’s freeze-thaw cycles, sustained wet conditions, and low winter light. Your watering system, ventilation, and insulation approach all need to match the climate you’re actually in.

3. Designing for aesthetics instead of workflow. That cute coop with the charming proportions? The feed room door is too narrow for a wheelbarrow. The nesting boxes are at the wrong height for daily egg collection. The roosts are hard to clean. After six months, you hate it.

What Actually Matters for PNW Coops

• Siting: Elevate the coop above grade with proper drainage. Observe where water pools on your property in winter before you pick a location.
• Orientation: Prevailing winter winds in the Willamette Valley come from the south/southwest. Face the coop to minimize wind-driven rain through ventilation openings.
• Water system: If you’re running an automatic waterer, bury the supply line below frost depth (18 inches in the Willamette Valley). Insulate or heat-tape the riser.
• Ventilation vs. drafts: The PNW needs more ventilation than you think (to manage moisture) but zero drafts at roost height. High vents, low roosts.
• Feed storage: Dry, rodent-proof, accessible without entering the coop. Positioned so you can move feed bags from vehicle to storage to coop without backtracking.

None of this is complicated. It’s just specific — and the free plans don’t account for your site. That’s the gap: freely available information doesn’t adapt itself to your slope, your climate, your constraints.

Sometimes the difference between a mud pit and a working coop is an afternoon with someone who knows which questions to ask about your specific site.

A friend wanted to enlarge an exterior window. Her general contractor said she needed a structural engineer — standard practice, defensible, and expensive. I showed her the codebook table that covered her exact situation, walked her through the prescriptive path, and she submitted the permit herself. One afternoon instead of several thousand dollars.

The building department approved it because it followed their own code. No stamp required — just someone who knew where to look and how to read it.

When You Need an Engineer — And When You Don’t

The building code isn’t a black box. It’s written to be used without an engineer for most common situations. The prescriptive path — tables of standard sizes, spans, and capacities — covers the vast majority of residential construction. An engineer is required when you step outside those tables: unusual loading, non-standard materials, complex structural configurations.

The skill isn’t knowing the tables by heart. It’s knowing which table applies to your situation and how to read it. Headers, beams, joists, rafters, footings — there’s a table for nearly everything in a standard residential project. The IRC (International Residential Code) is designed so that a competent builder can construct a house using only prescriptive tables, without ever hiring an engineer.

The Approach

1. Identify the element. What are you building? A header over a window opening is different from a beam supporting a floor load.
2. Determine the loading condition. What’s above it? Roof only? Roof plus floor? Ground snow load in your area?
3. Find the right table. The IRC is organized by building component. Headers are in Chapter 6 (Wall Construction). Joists and rafters are in Chapter 8 (Roof-Ceiling Construction).
4. Read across the row. Most tables are formatted: given this span and this loading, use this size member. Sometimes there are footnotes about specific conditions — read them.
5. Present it to the building department. Write down the table reference, the span, the load, and the specified size. The building official can verify it against their own codebook in 30 seconds.

This isn’t a loophole. It’s how the code is designed to work. The prescriptive path exists precisely so homeowners and builders don’t need an engineer for every header, every footing, every beam.

If you’re ever unsure — and this matters — hire the engineer. The cost of being wrong exceeds the cost of being certain. But if your situation fits neatly within a prescriptive table, you may not need to. Learning to tell the difference is worth a thousand dollars an hour.

Here’s something most property owners learn the hard way: your land doesn’t care about your project boundaries. The water off your barn roof doesn’t stop at your chicken coop just because you planned them in different years. The slope you ignored when you built the garden is the same slope draining into your feed storage. The access road you put in last spring is now a channel sending winter runoff straight into your paddock.

Your property is a system of systems. Water, structures, animals, energy — each runs on its own rules, but they don’t exist in a vacuum. When they clash, you’re the one paying.

The Problem With Piecemeal Planning

Most homesteads and rural properties are built one project at a time — and that’s fine. You can’t do everything at once. The problem isn’t phasing. The problem is phasing without a framework.

When each new project is designed in isolation, you get: a chicken coop that catches all the runoff from the barn, a garden that sits in the one spot on the property where frost settles hardest, a rainwater tank sized by guesswork instead of catchment calculations, and fencing that blocks the movement patterns you’ll need for rotational grazing later.

None of these are disastrous on their own. Together, they’re death by a thousand paper cuts — and every fix costs more than doing it right the first time.

How to Think About It

Before you build anything else, trace the connections. Ask yourself:

• Where does water go on this property — in every season?
• What moves across this land daily? (You, animals, equipment, feed)
• What infrastructure do you already have that a new system should connect to?
• What future project will this current one either enable or block?

You don’t need a full master plan to get this right. You need someone who can look at your specific site and trace the connections before you break ground. That’s the difference between building it wrong once and building it right the first time.

This is the first in a series on property systems thinking. Next: how to sequence infrastructure on a new property — what to build first and what can wait.