NCQLP LC common mistakes
NCQLP LC · Understand the traps and how to avoid them.
Treating the LC exam as a pure lighting-design test and answering from aesthetic intuition rather than from the published illuminance, uniformity, and power-density criteria that the multiple-choice items actually probe.
Most candidates come from design practice where judgment and client preference drive decisions, so they default to 'what looks best' instead of the numeric target or recommended practice the item is testing.
What to do instead
Before answering any quantitative item, identify which published criterion it maps to (recommended maintained illuminance for the task, max/min or avg/min uniformity, or lighting power density allowance) and answer from that value first, then sanity-check against design intuition. Build a one-page cheat sheet of the criteria you keep missing and review it weekly.
Confusing maintained illuminance with initial illuminance and ignoring the light loss factor when selecting or evaluating a design.
Candidates compute the 'as-installed' value from lamp lumens and fixture count and stop there, forgetting that the criterion is a maintained value that accounts for lumen depreciation, dirt, and ambient temperature effects.
What to do instead
Whenever a calculation item appears, write out the formula with the light loss factor explicitly and state whether the answer is initial or maintained. Practice converting between the two using typical LLF values so the distinction becomes automatic.
Mixing up the inverse-square law and cosine law conditions, applying them at short distances or to extended sources where they do not hold.
These formulas are memorized as plug-and-chug, so candidates apply them to any point-source-looking problem without checking whether the distance is at least about five times the source dimension or whether the surface is perpendicular.
What to do instead
For every point-calculation item, first state the assumptions (point source, distance >> source size, incidence angle). If the assumptions fail, reject the inverse-square approach and reason qualitatively or with the appropriate extended-source method. Work through a set of problems where the correct move is to say the formula does not apply.
Selecting luminaires by wattage or lamp type alone without checking photometric distribution, cutoff classification, and glare control relative to the task and mounting height.
Product familiarity and price drive real-world specification, so candidates skip the photometric file and answer from brand or lamp-family habits.
What to do instead
Practice reading a luminaire's photometric summary: distribution type, cutoff/classification, spacing-to-mounting-height ratio, and glare rating. For each item, ask what the distribution must do for the stated task and mounting condition before choosing a fixture.
Ignoring the interaction between color rendering, correlated color temperature, and the task when evaluating a lighting scheme.
Candidates treat CRI and CCT as cosmetic preferences rather than as performance criteria tied to task type, and they overlook that high CCT does not mean high CRI.
What to do instead
Memorize the ranges that matter (for example, high CRI for color-critical tasks, appropriate CCT for the setting) and practice items where two options are both 'white light' but only one meets the rendering requirement. Always check CRI and CCT as separate attributes.
Calculating lighting power density from connected load of all fixtures without applying the correct space-by-space or whole-building method and the associated allowances and exceptions.
Candidates remember one LPD method and apply it everywhere, and they miss that some spaces use area-category allowances while others use a whole-building budget, and that certain loads are exempt.
What to do instead
For each compliance item, state the method being used and the space category before computing. Keep a short table of common space categories and their allowances, plus a list of exempt loads, and drill problems that hinge on choosing the right method rather than on arithmetic.
Treating controls as an afterthought and failing to match control strategy (occupancy sensing, daylight harvesting, dimming, scheduling) to the space use and code requirement.
Controls are often delegated in practice, so candidates know the vocabulary but not which strategy is mandatory or effective for a given space type and fenestration condition.
What to do instead
Build a matrix of space type versus required and recommended control strategies, and practice items that ask which control is required or which one is ineffective. Include daylight-responsive and occupancy-based requirements and their typical exemptions.
Skipping units and dimensional analysis, then picking an answer that is off by a factor of ten or by a square-foot versus square-meter conversion.
Items mix lux and footcandles, watts and kilowatts, and square feet and square meters, and candidates under time pressure compute in whichever unit comes to mind.
What to do instead
Write the unit next to every number as you compute and carry it through. Memorize the key conversions (1 fc ≈ 10.76 lux, 1 W/ft² ≈ 10.76 W/m²) and do a final magnitude check: does the answer make physical sense for the space described?
Reading only the last sentence of a scenario item and missing the qualifier ('except', 'least appropriate', 'most cost-effective') that determines the correct option.
Stem length and time pressure push candidates to skim, and scenario items are written so that the qualifier, not the technical content, separates the best answer from the plausible one.
What to do instead
Underline or mentally flag the operative qualifier before evaluating options. Practice a set of items where several options are technically true and only one satisfies the qualifier, so you learn to answer the question asked rather than the one you expected.
Managing time poorly by over-investing in calculation items and then rushing the conceptual and code items at the end.
Calculation items feel productive and candidates want certainty, so they re-derive numbers repeatedly while short factual items go unanswered or are guessed in the final minutes.
What to do instead
Do a first pass answering every item you can resolve in under a minute, flag calculations, and return to them with a fixed per-item time budget. If a calculation exceeds the budget, estimate the magnitude, eliminate implausible options, and move on.