ICC Soils Inspector EC common mistakes
ICC Soils Inspector EC · Understand the traps and how to avoid them.
Reading the percolation (perc) rate from a single test hole and applying it to the whole lot without averaging or accounting for the slowest hole.
Candidates treat the perc test as one number instead of recognizing that the design rate is governed by the most restrictive (slowest) acceptable test result and the number of holes required by the local code; variability across the site is the whole point of multiple borings.
What to do instead
Before the exam, memorize the rule that the design application rate is based on the slowest (highest time) acceptable perc result, and that a minimum number of test holes per area is code-specified. Practice problems where several holes give different rates and you must select the governing value.
Confusing the depth to a limiting layer (bedrock, seasonal high water table, impervious stratum) with the total usable soil depth, and placing the absorption area too deep or too shallow as a result.
Candidates conflate 'depth to restriction' with 'depth of suitable soil' and forget that separation distances (vertical separation to the limiting layer) are measured from the bottom of the infiltrative surface, not from grade.
What to do instead
Draw a quick cross-section on scratch paper for every site-evaluation item: mark grade, bottom of trench, and the limiting layer, then measure the vertical separation between the last two. Rehearse the code's minimum separation distance until it is automatic.
Classifying a soil by feel or color alone without confirming with texture-by-feel plus ribbon length and, where required, laboratory particle-size analysis.
Field texture estimation is subjective and candidates over-rely on one cue (e.g., grittiness) instead of the full procedure; color is also misread as a drainage indicator without considering mottling and redox features.
What to do instead
Practice the full ribbon test and texture-by-feel sequence on known samples until classifications are repeatable, and always cross-check color/mottling against the code's criteria for a seasonal high water table rather than treating color as definitive.
Misidentifying soil horizon boundaries and sampling or logging the wrong layer for the design decision.
Candidates log by depth alone and ignore changes in structure, consistence, and color that mark horizon boundaries, so a restrictive horizon is missed or a suitable horizon is overestimated.
What to do instead
Log horizons top-down with a hand auger or profile pit, recording boundary depth, color, texture, and structure for each layer before assigning any design value. Build a habit of describing each horizon fully before moving deeper.
Reporting field density or moisture content without verifying the test method, calibration, and that the sample is representative of the lift being tested.
Candidates focus on the number and skip the quality controls: wrong method for the soil type, uncalibrated gauge or sand cone, sample taken from a non-representative spot, or testing a lift that is too thick.
What to do instead
Before accepting any density result, confirm the method matches the soil and specification, the equipment calibration is current, the test location is random and representative, and the lift thickness is within the tested zone. State these checks explicitly in inspection notes.
Comparing field dry density to maximum dry density from a standard Proctor when the specification calls for modified Proctor, or vice versa, and declaring pass/fail on the wrong basis.
Both tests yield a 'maximum dry density' and a 'percent compaction,' so candidates plug numbers into the wrong reference curve without checking which effort the spec requires.
What to do instead
Always read the specification's required test method (standard vs. modified effort) before computing percent compaction, and label the reference maximum dry density and optimum moisture content with their method in every calculation and report.
Treating moisture content at compaction as an afterthought when the density passes but the soil is on the dry or wet side of optimum.
Candidates equate passing density with acceptable compaction and forget that moisture outside the specified range around optimum produces marginal or unstable fill even when density reads acceptable.
What to do instead
Record field moisture content alongside every density test and compare it to the specified moisture range around optimum. When density passes but moisture is out of range, flag it rather than signing off.
Applying a code requirement from memory without confirming the edition, local amendment, or jurisdiction-specific rule that governs the project.
Candidates study one edition or a generic rule set and assume it is universal, but codes are adopted with local amendments and different editions, and the inspector must apply the adopted version.
What to do instead
For each code-administration item, identify which edition and which local amendments apply, and cite the section number in your answer or report. Practice locating requirements in the adopted code rather than reciting them.
Issuing an approval or correction notice without documenting the specific code section, the observed condition, and the required corrective action.
Candidates write vague notes ('compaction not adequate') because they focus on the outcome, not the record; this makes the finding unenforceable and untraceable on reinspection.
What to do instead
Use a fixed template for every finding: code section cited, observed condition with location and measurement, required corrective action, and reinspection trigger. Practice writing findings that a third party could verify without you present.
Failing to distinguish a failed inspection from a stop-work or unsafe-condition notice, and not following the required notification and reinspection sequence.
Candidates treat all negative findings the same and skip the procedural steps (written notice, timeline, reinspection request, escalation) that the code administration process requires.
What to do instead
Memorize the decision tree: minor deficiency vs. failed inspection vs. stop-work/unsafe condition, and the required written notice and follow-up for each. Rehearse the sequence so the procedural step is as automatic as the technical finding.