17.2 Miss-Log Diagnostics by Domain

Why a Miss Log Works

An 80-question WRE mock produces far too much information to review from memory. Without a structured log, candidates reread topics they already enjoy or redo only the items they missed — and they overlook two decisive patterns: slow correct answers and repeated process failures. A correct but 18-minute pump problem can matter more than one wrong groundwater item, because in a locked ~4.25-hour session that 18 minutes is stolen from three other questions you could have banked.

The log must be short enough to maintain and specific enough to change behavior. Reject vague notes like "study hydraulics." Write the actionable version: "Used Hazen-Williams when Darcy-Weisbach was required because the problem supplied a friction factor and asked for SI headloss." That sentence names the trigger, the wrong choice, and the correct method — it is a repair, not a complaint.

Diagnostic Columns

A correct answer still belongs in the log if it was guessed, slow, or required repeated searches. These are often the best final-week wins, because the candidate already holds partial understanding and only needs a faster, cleaner workflow.

Domain Patterns to Watch

Hydrology

Hydrology misses usually start before any arithmetic — choosing the wrong rainfall quantity. Track whether the failure was annual exceedance probability versus return period, an intensity-duration-frequency (IDF) lookup, time of concentration, NRCS curve-number runoff depth, unit-hydrograph timing, or reservoir routing storage. If most misses occur at classification, the repair is problem identification, not more calculation drills.

Hydraulics

Separate closed conduit from open channel. Closed conduit errors involve energy-equation terms, headloss-model selection (Darcy-Weisbach versus Hazen-Williams), the pump operating point, or confusing pressure with the hydraulic grade line. Open channel errors involve normal depth, critical depth, specific energy, culvert inlet-versus-outlet control, gutter spread, or Manning unit constants (1.49 USCS, 1.0 SI). If both show unit slips, build one shared unit workflow instead of two topic drills.

Water Quality, Drinking Water, and Wastewater

These three share mass-balance logic. Log whether the missed step was a load conversion, flow weighting, detention time, solids loading, disinfection CT (concentration x time), alkalinity/hardness, sludge volume, or process selection. The classic trap: applying a concentration-removal fraction when the question asks for load removal and the flow changes between points.

Sitework, Soils, Materials, and Prioritization

Sitework and geotechnical-adjacent questions are easy to underestimate because they look less WRE-specific, yet sitework carries the largest range (9-14). Track earthwork quantities and shrink/swell, compaction (Proctor), boring-log interpretation, slope stability, temporary erosion and sediment controls, OSHA 29 CFR 1926 Subpart P excavation/trench rules, retaining-wall pressures, and horizontal/vertical curve geometry. These are highly repairable because the workflows are procedural.

After the mock, compute accuracy by domain and tag each with a priority label:

1. Red — high-range domain below 60 percent, or repeated setup errors.
2. Yellow — low-range domain below 60 percent, or high-range domain at 60-70 percent.
3. Green — above 70 percent with no repeating process issue.
4. Blue — correct but slow; needs timing drills, not content review.

Then pick no more than three repairs for the next study block, each measurable: solve 12 mixed mass-balance problems, build a one-page unit ladder from cfs to MGD to lb/day, or redo six culvert and energy-grade-line problems closed-solution. For April-2027-and-later candidates, add a standards/source column to log slow navigation in OSHA, FHWA HDS-5/HEC-14, USACE EM 1110-2-1902, UFC dewatering, and Ten States standards.

Turning the Log Into a Study Schedule

A miss log is only useful if it converts into hours on the calendar. After tagging every entry Red, Yellow, Green, or Blue, count entries per cause across the whole mock, not per domain. A candidate who sees seven "unit" causes, four "setup" causes, and two "concept" causes should spend the bulk of the next block on a single unit-and-setup workflow, because that one fix removes errors scattered across hydrology, hydraulics, water quality, and wastewater simultaneously. This cause-first rollup is what separates an engineering diagnostic from a topic-by-topic reread.

Weight the schedule by points at risk, defined as the domain question range multiplied by the error rate. A domain like sitework at 9-14 questions with a 50 percent error rate puts roughly five to seven points at risk — more than any single calculation topic — so it earns the first study slot even though it feels less technical than pump hydraulics. Re-run a fresh mixed mock no sooner than 48 hours after the repair block so the fix has time to consolidate, and compare the new miss log against the old one.

If the same cause label reappears at the same frequency, the repair was reading rather than active problem-solving; switch to timed, closed-solution drills. If the cause label drops but a new one rises, that is healthy progress: you fixed the binding constraint and surfaced the next one, which is exactly how the final two weeks should feel.