LARE Section 3 common mistakes
LARE Section 3 · Understand the traps and how to avoid them.
Treating Section 1 (project and construction management) as pure vocabulary recall - memorizing definitions of delivery methods, contracts, and scheduling terms without ever practicing the calculations those terms imply.
Section 1 reads like a glossary, so candidates skim it and assume recognition equals competence. In reality the scored items ask you to apply concepts: compute a critical path, adjust a schedule for weather days, or reason about which party bears risk under a given contract form. Recognition memory collapses under application questions.
What to do instead
For every Section 1 concept, write one worked numeric or scenario problem and solve it. Build a one-page risk-allocation matrix mapping contract types to who owns design errors, cost overruns, and delay. Practice CPM forward/backward passes by hand until float calculations are automatic.
Answering construction-administration questions from the perspective of the designer's preference rather than the contractual role defined in the scenario.
Candidates bring real office habits - 'I'd just tell the contractor to fix it' - into questions that hinge on formal roles like owner's representative, construction manager, or architect-of-record. The exam tests whether you know who is authorized to act, not what seems practical.
What to do instead
Before answering, explicitly label the roles in the prompt and ask 'what does this role owe under this delivery method?' Drill the difference between observation, inspection, and supervision, and between substantial completion, beneficial occupancy, and final acceptance. Write a short role-obligation table and review it before every practice set.
Skipping the inventory and analysis phase in Section 2 and jumping straight to a design idea when a site-planning prompt presents a program and constraints.
Designers are trained to generate solutions quickly, and the exam's scenario format rewards candidates who demonstrate a documented process. Candidates who jump to a concept miss the scored reasoning about site data, opportunities and constraints, and program fit.
What to do instead
Practice a fixed written sequence for every site-planning scenario: inventory the given data, list opportunities and constraints, state program requirements, then evaluate alternatives against them. Time yourself doing this in outline form so the habit becomes automatic under exam pressure.
Confusing the intent of a graphic or spatial standard with its exact dimensional threshold - for example, treating a recommended slope or a typical dimension as a hard requirement, or vice versa.
Section 2 draws on accessibility, grading, and site-engineering conventions where some numbers are mandatory and others are guidelines. Candidates who memorize one number for a concept misapply it when a question asks about a different condition, such as a ramp versus a walkway or a swale versus a pipe.
What to do instead
Build a comparison table for each dimensional family: element, mandatory minimum or maximum, recommended range, and the condition that changes it. Rehearse the 'when does the number change' question for each entry rather than memorizing a single figure.
Reading Section 3 (design and construction documentation) questions as drafting-production questions and ignoring the coordination and liability dimensions of the same drawing set.
Candidates associate documentation with CAD and sheet production, but the scored content centers on what a drawing must communicate, who relies on it, and how errors propagate through specifications, details, and general notes. That conceptual layer is what trips people up.
What to do instead
For each document type - plan, section, detail, schedule, specification, general note - write what decision it controls and what happens downstream if it is wrong or missing. Practice spotting coordination gaps in described drawing sets, such as a dimension that conflicts with a schedule entry.
Treating specifications and drawings as interchangeable sources of truth instead of knowing which governs in a conflict and how the two documents divide responsibility.
In practice, teams often work from whichever document is handy. Exam items deliberately place a drawing note against a specification clause to test whether you know the precedence rules and the division of scope between them.
What to do instead
Memorize the standard precedence hierarchy and the general principle that specifications govern quality of materials and workmanship while drawings govern quantity, location, and dimension - then test yourself with conflict scenarios. Write three conflict examples and resolve each using the hierarchy.
Memorizing plant lists by name without linking species to the site conditions and design functions that justify their selection in Section 4.
Section 4 tests planting and ecosystem reasoning - why a species fits a moisture regime, a soil pH, a maintenance budget, or a design intent. Name-only recall fails when the question asks for the best choice under stated constraints.
What to do instead
For each plant you study, record a profile: light, moisture, soil pH, mature size, maintenance level, native or invasive status, and a design function such as screening, canopy, or erosion control. Practice selecting from a short list against a stated site brief rather than recalling a single correct name.
Answering grading and drainage questions by eye - choosing the option that 'looks like it drains' instead of computing elevations, slopes, and flow direction from the given numbers.
Grading feels intuitive to experienced designers, and the exam supplies enough numbers that an eyeball answer is often plausible but wrong. Candidates who don't compute miss the one option that actually satisfies the required slope or drainage path.
What to do instead
Force the arithmetic on every grading item: convert slope percentages to rise over run, check flow direction against spot elevations, and verify that proposed grades meet minimums. Do ten short calculation drills per study session until the conversion is reflexive.
Managing time uniformly across all four sections instead of budgeting by question difficulty and section weighting, so a slow Section 4 calculation consumes time needed for straightforward Section 1 items.
The sections feel equally important, and candidates often grind on the hardest item they encounter rather than marking it and moving on. This is a strategy failure, not a knowledge failure, but it costs scored points.
What to do instead
Set a per-question time budget before the exam and rehearse it in full-length timed practice. Adopt a mark-and-return rule: if an item exceeds roughly twice the average budget, flag it and continue. Track your flag rate and accuracy by section to find where you habitually over-invest.
Studying each domain in isolation and never practicing mixed sets that require switching between management, site analysis, documentation, and planting reasoning within one sitting.
Domain-by-domain study builds depth but not cognitive flexibility. The real exam interleaves content, and candidates who only drill single-domain blocks underperform when a question requires combining, say, a documentation detail with a site-engineering constraint.
What to do instead
After building domain depth, shift the majority of remaining study time to mixed practice sets with randomized domain order. After each set, categorize every miss by domain and by error type - knowledge gap, misread, or calculation slip - and target the dominant category.