Use this guide as a decision-training plan rather than a glossary. Work through the sections in order: master the greywater/blackwater distinction, compare system types before studying any single one, practice interpreting site data, then trace the two worked scenarios to see where plausible reasoning fails and what a better justification sounds like. Finish by building your own paper design from the exercise prompt and scoring it against the rubric. Repeat the exercise with different soil and slope assumptions until your justifications hold up without notes.
Greywater and Blackwater: Why the Source Distinction Drives Every Later Decision
Greywater is wastewater from bathtubs, showers, bathroom sinks, and clothes washers; blackwater comes from toilets and commonly includes kitchen sinks. Every downstream choice—treatment level, irrigation method, and where water may be applied—depends on which stream you are handling.
Greywater carries soap residues, lint, hair, skin oils, and small amounts of organic matter, and it degrades quickly: if stored without oxygen, it turns septic and develops odor within a short time. That is why sound greywater designs deliver water promptly to soil and mulch rather than holding it. Blackwater carries a far heavier pathogen and solids load and requires full treatment. Naming these characteristics precisely matters, because a core skill worth drilling is matching a water source's contamination profile to a handling method.
Apply the distinction by tracing misclassification. Compare a washing machine discharging rinse water with a kitchen sink discharging food particles and grease: the second stream contains solids that clog fine filters and load mulch basins far faster. A candidate who treats 'all household wastewater' as one category cannot explain why the two need different handling. Practice stating, for each fixture in a building, which stream it produces and one design consequence that follows from it.
Comparing System Types Before You Study Any Single One in Depth
Study greywater systems comparatively: laundry-to-landscape, branched-drain gravity distribution, pumped pressurized distribution, and pre-treatment options such as mulch basins or constructed wetlands. Each solves a different combination of elevation, flow, and filtration problems.
A comparative frame helps you avoid a learning error worth naming: mastering one system's parts list and then forcing it onto every site. A laundry-to-landscape setup uses the washer's pump, needs no surge tank, and serves only laundry water. A branched-drain system relies on consistent gravity fall from a collection point, so it lives or dies by slope. A pumped pressurized system buys flexibility on flat or uphill sites but adds electrical components and maintenance obligations. These trade-offs are the core decision content of the field.
Use the table below as a study scaffold: cover the right-hand columns, name a system, and reconstruct its typical source, movement mechanism, and fitting site condition from memory. Then reverse the drill—given a site condition, list which systems fit and which are excluded, and say why in one sentence. Fluency in both directions is what lets you justify a selection rather than merely identify one.
| System type | Typical water source | How water moves | Key design consideration | Best-fitting site condition |
|---|---|---|---|---|
| Laundry-to-landscape | Clothes washer only | Washer pump pushes water through hose to outlets | Filter at the drum exit; outlets placed so water does not pool | Laundry located near or above the irrigated area |
| Branched drain (gravity) | Showers, tubs, bathroom sinks, washer | Piped network with splitting valves; water flows downhill to outlets | Consistent slope and correct pipe sizing to avoid air locks and uneven splitting | Reliable fall from the collection point to the landscape |
| Pumped pressurized distribution | Any greywater collected in a tank | Pump delivers water through smaller lines on demand or timed cycles | Surge tank sizing, pump maintenance access, backflow and electrical considerations | Flat sites, uphill planting areas, or long distances |
| Mulch-basin disposal | Any greywater outlet | Water discharges into a sunken basin filled with coarse mulch | Basin capacity and infiltration rate; mulch replenishment schedule | Almost all systems; the standard soil-interface method |
| Pre-treatment stage (e.g., constructed wetland or media filter) | Greywater needing extra solids reduction | Water passes through planted or media-filled cell before reuse | Added space, complexity, and upkeep versus benefit gained | Higher-load sources or reuse goals requiring cleaner effluent |
Site Assessment: Turning Soil, Slope, and Fixture Data into a Design Basis
Assessment means converting observations—soil texture, slope, water table hints, fixture inventory, available irrigation area—into three design inputs: estimated flow, allowable loading per discharge point, and feasible distribution method.
Learn the named concepts precisely. Soil texture (sand, loam, clay proportions) governs infiltration: water enters sandy soil quickly and clay slowly, so identical flows produce very different ponding behavior. Hydraulic loading is the flow assigned to each discharge point; the assessment's job is keeping loading within what the soil and mulch can absorb between discharges. Surge capacity absorbs a shower or tub release arriving faster than soil can drink it. Slope determines whether gravity distribution is even possible and where water will naturally travel.
Interpretation practice matters more than collecting data. Given a fixture inventory, estimate flow by reasoning about use patterns rather than memorizing a single figure, and state your assumptions. Given a soil described as 'dense, sticky when wet, water puddles for hours,' translate that to slow infiltration before you touch any layout. A defensible assessment names each observation, states the design conclusion it forces, and flags what remains unknown—such as seasonal high water table—which becomes a verification item rather than a guess.
Worked Scenario 1: A Branched-Drain Recommendation the Soil Rejects
This paper scenario shows how a correct system type with incorrect loading still fails. The plausible mistake is sizing discharge points from fixture counts while ignoring soil infiltration; the better decision resizes loading to what the soil can absorb.
Paper setup (all numbers are illustrative for this exercise only): a single-bathroom cabin with a shower, bathroom sink, and washer produces roughly 90 gallons on a busy day. The yard behind the cabin slopes gently away, and the soil is described as heavy clay. A proposed design uses a branched drain splitting flow into three mulch basins, reasoning that three basins 'match' the three fixtures. With clay infiltration assumed very slow, 30 gallons per basin per day will not soak in between uses, so basins pond, turn anaerobic, and smell.
The better decision keeps the branched-drain concept—which fits the slope and source—but adds basins or larger basins, spreading flow so each receives a load the clay can absorb over the day, and it documents that assumption as a verification item on site. Why it matters: the failure mode here is not a wrong component but a wrong translation of soil data into loading. Practice writing the correction as a justification: observation, conclusion, revised design, and the specific field check that would confirm or refute it.
Worked Scenario 2: The Maintenance-Access Mistake During Installation Sequencing
This paper scenario shows an installation-stage error: a correctly designed laundry-to-landscape setup buried with its filter and valve inaccessible. The better decision sequences work so every component needing service stays reachable for its whole life.
Paper setup: a laundry-to-landscape line runs from the washer through a lint filter and a diverter valve, then outdoors to four outlets. The installer, working quickly, buries the filter and valve behind a fixed wall panel to tidy the utility area. Design-wise nothing is wrong; installation-wise the system is now unservable, because the filter must be cleaned regularly and the diverter must be switched so the washer can send water to the sewer when needed—such as when washing diapers or harsh chemicals.
The better decision places the filter and diverter in an accessible location with clear labeling, and verifies switch operation before closing any surfaces. Why it matters: greywater systems can fail quietly—by clogging, ponding, or being abandoned—when routine tasks cannot be performed. Generalize the lesson into a sequencing habit: for every component you install, ask what periodic action it requires, who performs it, and what physical access that action needs. If your sketch cannot answer those three questions, the installation plan is incomplete regardless of how correct the pipe routing looks.
Procedures and Documentation: Sketches, Checklists, and the Maintenance Handoff
Documentation translates a build into a usable record: an as-built sketch, a component list, an assumed-design-basis note, and a maintenance schedule. These artifacts are how an installation stays understandable after the installer leaves.
Practice producing the four artifacts from a paper design. The as-built sketch shows pipe routes, basin locations, filter and valve positions, and slopes as actually installed, not as first drawn. The component list names each part with its function. The design-basis note records the assumptions that shaped the design—the estimated flow, the soil interpretation, the loading per basin—so a future reader knows what the system was built to handle. The maintenance schedule assigns each task a frequency and an owner.
Then trace a handoff: imagine a homeowner reading your packet one year later to diagnose reduced flow. Your sketch lets them locate the filter; your design-basis note tells them whether slow drainage is new behavior or expected on this soil; your schedule shows whether cleaning is overdue. Weak documentation fails exactly there. Self-check by handing your packet to someone else and asking them to answer three questions from it alone: where is each component, what should it be doing, and what task is due now. Any question they cannot answer marks a gap in your documentation practice.
A Paper Design Exercise, a Self-Check Rubric, and an Adaptable Prep Sequence
Build a complete paper design for a hypothetical site, score it against the rubric below, then repeat with changed assumptions. Readiness means justifying every decision aloud—selection, layout, loading, and maintenance—without notes.
Exercise: draw a site plot with these assumed conditions (illustrative only)—a two-bathroom house, washer on the ground floor, yard sloping down and away, soil described as medium loam, and a vegetable bed plus ornamental shrubs as irrigation targets. Produce a system-type selection with a one-paragraph justification, a labeled sketch showing collection, distribution, and discharge points, a loading estimate per discharge point with stated assumptions, and a maintenance schedule. Note which landscape areas you excluded and why, since application-location reasoning is part of the design basis.
Adaptable sequence: spend early sessions on the source distinction and the comparison table; move to assessment translation drills using written soil and slope descriptions; then run this exercise three times, changing one variable each round—clay instead of loam, no slope, or a distant planting area—and observe how your design must change. Close each round by rewriting your justifications more tightly. The sequence works because each repetition isolates one design variable, teaching you which site facts actually drive which decisions.
- Rubric checkpoint 1 — Source reasoning: every fixture is classified correctly, and each classification is tied to a stated design consequence.
- Rubric checkpoint 2 — System fit: the selected system matches the slope and elevation facts, and at least one rejected system is named with a reason.
- Rubric checkpoint 3 — Loading logic: flow estimates state their assumptions, and loading per discharge point is linked explicitly to the soil description.
- Rubric checkpoint 4 — Serviceability: filter, valves, and any tank are shown with access, and each has a listed maintenance task.
- Rubric checkpoint 5 — Unknowns flagged: at least two verification items (such as confirming soil behavior on site) are written into the design basis rather than assumed away.