11.5 Use Diagnostics After a Failed Attempt

What the result tells you-and what it does not

NCEES reports the FS outcome as pass or fail. It does not publish a fixed raw passing percentage, and it does not give you a numeric score. That means a failing result should never be interpreted by inventing a target like "I was only three questions short." You cannot know that, and guessing wastes energy. What you do receive on a failing attempt is a diagnostic report broken out by the knowledge areas-it tells you, in relative terms, which areas were strong and which were weak. That breakdown is the actionable signal.

Treat the diagnostic as a map of where to spend the next cycle, weighted against the question ranges you already know:

A weakness in a large-pool area is worth more retake hours than the same-magnitude weakness in a small-pool area, because more questions ride on it.

Re-attack each weak domain with its highest-yield fact

The fastest way to convert a diagnostic into points is to re-study the single most-tested fact in each flagged area first, then broaden. Use this domain-by-domain high-yield recap as your re-entry point:

• Applied Math / Statistics: Standard deviation and error propagation. Random errors combine in quadrature (root-sum-of-squares); the standard deviation of the mean shrinks as 1/sqrt(n). Know mean vs. median vs. mode and the normal-distribution 68-95-99.7 idea.
• Surveying Processes / field: GNSS method selection and OPUS. Static for high-accuracy control, RTK/real-time networks for production; OPUS returns NAD83 and the orthometric height via the current geoid model. Differential leveling closure error is checked against a published tolerance.
• Survey Computations: Latitude/departure closure. Latitude = L cos(bearing), departure = L sin(bearing); a closed traverse must have sum of latitudes = 0 and sum of departures = 0, and the Compass (Bowditch) Rule distributes misclosure proportional to leg length.
• Surveying Principles / geodesy: SPCS scale factor and the geoid. State Plane uses Lambert (E-W zones) or Transverse Mercator (N-S zones); grid distance = ground distance x combined factor (scale x elevation). Orthometric height H = ellipsoid height h minus geoid height N.
• Boundary Law: Order of controlling elements / priority of calls (senior rights, then written intentions, then unwritten rights). Calls priority: natural monuments > artificial monuments > metes/courses-and-distances > area, with monuments controlling over measurements.
• Mapping / GIS: Contour rules and map-projection trade-offs. Contours never cross; they V upstream in valleys; a 1:24,000 USGS quad has a defined ground-distance-per-inch. GIS distinguishes raster vs. vector and projected vs. geographic coordinate systems.
• Business / ethics: Negligence and standard of care. A surveyor owes the professional standard of care; breach causing damages is negligence (errors-and-omissions). Stamping/sealing implies responsible charge.

Pair the diagnostic with your own evidence

The by-area diagnostic tells you where, but not why. Cross-reference it with two of your own records to find the true cause:

1. Your error log (see Section 11.6) classifies misses by cause-knowledge gap, units, sign/quadrant, wrong-domain assumption, or careless error. If the diagnostic says "weak computations" but your log shows the misses were nearly all angle-mode or units slips, the fix is a calculator routine, not relearning curves.
2. Your timed-practice data. If you ran out of time and left the last 10 items as blind guesses, a "weak" area may really be a pacing failure (Section 11.4), not a content gap.

Then build a measurable weekly plan: name the two largest-pool weak areas, set a question target per area, and re-test with a timed mini-exam. Avoid the trap of re-studying what you already know well because it feels productive-spend the cycle on the high-pool, high-cause-rate gaps. A retake plan that says "do more problems" is weak; one that says "close my boundary-priority-of-calls gap and my radian-mode slips, 30 timed items each, by Friday" is one you can actually execute and verify.

Sequence the retake cycle and re-test

A structured retake cycle beats an open-ended one. Sequence it so the highest-leverage work comes first and verification is built in:

1. Weeks 1-2: largest-pool gaps. Attack the weak high-count areas the diagnostic flagged-usually boundary law and/or computations-starting from each domain's highest-yield fact (Section 11.5 recap). These hours return the most points.
2. Weeks 3-4: mid-tier and quick wins. Refresh mapping/geodesy, then drill the cheap recall points in business and statistics.
3. Final week: timed mini-exams and error-log review. Re-test under exam timing, confirm weak areas have moved to 'solid,' and rehearse the pre-answer checklist (Section 11.6).

The goal of the retake cycle is not simply to study more-it is to study differently, guided by evidence you did not have the first time. The diagnostic plus your own error log and timed data form a feedback loop: each week you should be able to point to a specific gap you closed and verify it with a timed re-test. A candidate who treats a failed attempt as data rather than defeat converts a setback into the most efficient study cycle of the whole effort.