Treat the six depth areas as concept pairs with decisions attached. Total float protects the finish date while free float protects successor start dates, and float on a path is shared, not additive across its activities. Shrinkage converts bank cut into compacted fill using the shrink factor itself, never its inverse, while swell converts bank into loose haul volume. One takeoff error moves direct cost, duration-driven indirects, and unit prices differently. Schedule updates require a full re-pass because consumed float changes the critical path. Self-check with the pass-drill rubric and unit-state labeling before trusting any practice result.
The Selection Problem: Six Depth Areas, Each Hiding a Contrast Pair
Each NCEES construction depth area pairs a calculation with a site decision. Study every concept as a pair of near-neighbors — total versus free float, bank versus compacted volume — and rehearse which decision each number triggers.
The exam is computer-based with year-round appointments at Pearson VUE test centers, and the reference handbook is available on screen, so memorization is not the bottleneck. The difficulty lives in selection: a scenario names a field condition, and two or three handbook formulas fit the words equally well. Build a distinctions list by area — for example, shrinkage converts bank material to compacted fill while swell converts bank material to loose haul volume — one sentence per contrast, written in your own words.
Rehearse both directions of each pair. Compute forward: given quantities and a factor, decide whether the site imports or exports material. Then compute backward: given a decision such as procuring a borrow source, identify which quantity and which conversion produced it. For every solved item, write one wrong-branch sentence: if the neighboring formula had been used, the plan would have said the opposite. Log the branch you took, not just the final answer, and re-test logged branches after a week. Scenario sets like the free practice questions on this site supply the wording this method needs.
Total Float Versus Free Float: Whose Dates Does a Slip Actually Move?
Total float measures slack against the project finish; free float measures slack against the next activity's early start. Float on a shared path is spent once, so summed activity floats overstate the slack a schedule actually holds.
Build the distinction with a small network. Path P holds activity C (4 days) then D (3 days); parallel path Q holds F (8 days) then G (5 days); both paths feed the final activity E (6 days). E's early start is day 13, controlled by Q, so the project finishes day 19. Working backward, C and D each carry 6 days of total float. The tempting mistake at the planning table: adding those two numbers and reporting 12 days of combined slack.
Those 6 days belong to path P, not to each activity, and can be spent once. If C's crew and D's crew each consume their full 6, P finishes day 19, E starts at 19 instead of 13, and the project ends day 25 — a 6-day delay the '12 days' reading made look harmless. Free float separates them: C has zero, so any slip moves D's early start; D holds all 6. Recompute float after every update, because consumed days change what remains.
| Term | Definition | What it protects | Scenario wording that signals it |
|---|---|---|---|
| Total float | Late finish minus early finish (LF − EF) | The contract completion date | "Can the project absorb this delay?" |
| Free float | Earliest successor start minus early finish | Successor crews' planned early dates | "Will the next trade arrive on schedule?" |
| Shared path float | Float on a controlling path, usable once by any activity on it | The path, not each activity individually | "Two sequential tasks both claim this slack." |
Shrinkage and Swell: Converting Volumes in the Correct Direction
Shrinkage converts bank cut into compacted fill; swell converts bank rock into loose haul volume. Label every quantity with its unit state — bank, loose, or compacted — before multiplying, and convert only across that stated boundary.
Run the scenario that exposes the direction problem. A roadway section requires 10,500 CCY of compacted embankment, and the design cut yields 12,000 BCY with 20 percent shrinkage. The compacted yield of the cut is 12,000 × 0.80 = 9,600 CCY, leaving a 900 CCY deficit, so borrow of 900 ÷ 0.80 = 1,125 BCY must be hauled in. The tempting wrong branch is multiplying by 1.2 instead: 14,400 CCY of 'yield,' which reads as a 3,900 CCY surplus and points the plan in the opposite direction.
The two answers drive genuinely different site actions: a borrow source, haul-in traffic, and procurement cost on one side; a waste or disposal area, haul-out, and different pay items on the other. The mass-haul balance and every quantity line downstream inherit the error. The reliable habit is graphical: above each multiplication sign, write the conversion arrow — BCY to CCY here, BCY to LCY for swell. If you cannot state which direction the arrow runs, stop; the answer will be wrong in kind, not merely in magnitude.
One Quantity Error, Three Different Cost Consequences
A takeoff is geometric; a cost estimate layers production rates, prices, and indirects on top of it. The same quantity error lands differently in direct cost, in duration-driven indirect cost, and in unit prices — three fixes for three lines.
Distinguish the three layers before practicing numbers. Direct cost is quantity times crew and equipment production; indirect cost is duration-driven — supervision, mobilization, general conditions accrue per day; a unit price spreads cost plus margin over the quantity. Trace one understated excavation quantity: direct cost is low because the quantity is low; planned duration also shrinks, so indirects are understated a second, independent time; and the unit price, computed as cost divided by quantity, carries yet another blend of the two errors. A takeoff mistake never stays in one line.
This is why 'wrong quantity' and 'wrong production rate' are different diagnoses demanding different corrections: re-measure the work in the first case, re-rate the crew in the second. Practice the trace in both directions. Take a quantity from an earthwork scenario and name every cost line it touches. Then, given a unit price that looks low against a scenario's crew rates, ask what quantity or production assumption would produce that number — and which measurement would confirm it. That reversal trains the estimating judgment the topic is actually about.
After a Schedule Update, Patched Dates Hide the New Critical Path
A baseline is a completed network; an update is that network with actual dates behind a data date and remaining durations ahead. Recompute the full pass on remaining work — float and the critical path both change after updates.
The working distinction is between a baseline, which is a finished forward and backward pass, and a status update, in which completed and in-progress activities carry actual dates while remaining work is re-estimated. Patching only the delayed activity's start date is the tempting shortcut, and it conceals the real effect: consumed float disappears, so a path that once carried generous float can become near-critical or critical without any single dramatic slip. The update's job is to reveal that shift, and only a full re-pass of remaining work does so.
Drill this with a self-check rubric. Draw a seven-activity network with two merge points, complete a full pass, then push one mid-chain activity three days and redo the entire pass from the data date. Score yourself against these observations:
- Every early start equals the latest early finish among its predecessors — no carried-over baseline dates anywhere.
- Every late finish equals the earliest late start among its successors in the backward pass.
- The critical path shows zero total float at every step, including after the update.
- At each merge point, confirm which predecessor controls the early start — float on the other branch shrank by the delay.
- Expected observation: the delayed activity's remaining float drops toward zero and a previously float-rich parallel path becomes near-critical. If you noticed only the delayed activity, the pass was patched, not rebuilt.
Failing a Test: Fixing the Process Versus Judging the Lot
Production quality control adjusts the process — batching, moisture conditioning, gradation — before material is placed. Acceptance testing judges a delivered or placed lot against the specification, triggering accept, retest, or rework decisions.
Trace the distinction with a compaction result. A field density test below specification has at least three candidate causes: moisture off target, a lift placed too thick, or insufficient compactive effort. A production-side response changes the process — adjust moisture conditioning or placement practice so the next material is right at the source. An acceptance-side response judges the represented lot: recompact and retest the failing area before it is covered. The measured number is identical; the decision tree differs depending on whether the process or the lot is the thing under review.
Concrete shows the same fork with higher stakes. Low strength cylinders invite two separate inquiries: production records — batching proportions and water content — versus sampling, handling, and curing of the specimens themselves. The remedy differs accordingly: a process correction for future production, or further evaluation of the in-place work for the lot already placed. In practice, write both answers before choosing: "process decision: ..." and "lot decision: ..." Forcing the two sentences keeps a process problem from being answered with a lot disposition, or the reverse.
Temporary Structures: Construction Load Cases and the Final Stretch Plan
Formwork and shoring carry construction loads that differ from in-service design: fresh concrete pressure, crew and equipment loads, wind on temporary works. Study load paths and their qualitative drivers, then close preparation with a fixed sequence.
The concepts to separate are the load sources and their sensitivity. Lateral pressure of fresh concrete rises with rate of placement and falls as concrete sets, with full liquid head as the simplest bounding case; formwork design combines the weight of concrete and forms with live construction loads and environmental effects on the temporary condition. Reason on paper: given a scenario that increases the placement rate, state which way the pressure moves and which member picks up the change. You are training load-path reasoning and vocabulary — forming, shoring, resisting — not field procedures, which belong to qualified supervision in practice.
Close with a sequence you can adapt to the time you have, and finish by scoring yourself on readiness rather than on predicted results:
- Map the on-screen handbook's layout for all six depth areas until each lookup is a physical habit rather than a search under pressure.
- Write the distinctions list — two contrast pairs per area — and rehearse the wrong-branch sentence for each.
- Rotate timed scenario sets across areas, one area per session, drawing on question banks such as this site's free practice page.
- Keep an error log keyed to the branch taken, and re-test logged errors one week later.
- Readiness checks: a full forward and backward pass with float read, unaided; unit states labeled before any earthwork arithmetic; both the process and lot response stated for a failing test; and an error log showing no repeated wrong branch across two consecutive sessions. These are learning milestones, not score predictions.
- One administrative note: registration, scheduling, and current exam policies are set by NCEES at ncees.org.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.