ASCP DLM common mistakes
ASCP DLM · Understand the traps and how to avoid them.
When an item asks what a newly appointed laboratory manager should do first, the candidate selects the technical option (review the procedure manual, re-audit QC records) instead of the option that establishes expectations with staff and stakeholders.
Most candidates were promoted off the bench and have years of reinforced technical decision-making; the technical option feels safest and most defensible when an item is worded ambiguously.
What to do instead
Before reading the options, underline the role noun and the action verb in the stem. Delete any option a bench technologist could carry out without managerial authority, then from the remainder choose the one that builds capability in others, gathers input before acting, or aligns the laboratory with organizational goals.
Classifying a cost by its label instead of its behaviour - for example calling the salary of a second technologist who is added only after volume crosses a threshold a variable cost, or treating depreciation on an already-owned analyzer as a cash operating expense.
Cost behaviour is studied once and rarely reapplied; candidates memorize the fixed-versus-variable definitions but never test them against step-fixed, semi-variable, allocated, and non-cash items.
What to do instead
Build a one-page decision table with columns for fixed, step-fixed, variable, semi-variable, and separate rows for direct/indirect and capital/operating. Classify 20 real items from your own laboratory (reagents, pipette tips, analyzer lease, depreciation, supervisor salary, proficiency testing fees) and justify each against the definition until the sort becomes automatic.
Applying fully allocated fixed overhead when costing an additional test or a discounted outreach contract, and therefore concluding the work should be declined even though the incremental revenue exceeds the incremental cost.
Internal cost reports display only fully loaded cost per test, so the allocated figure is the only number the candidate has ever seen and it is applied to short-run decisions where it is not relevant.
What to do instead
For any short-run or incremental decision, list only the costs that change with the decision (reagents, supplies, direct labor, courier) and exclude sunk and allocated costs. Drill four problem types until the logic is fixed: make-or-buy, accept-or-reject a discounted contract, break-even volume, and payback period.
Choosing the wrong improvement tool for the task - running an FMEA to investigate an adverse event that has already occurred, or building a cause-and-effect diagram when the item asks which of several problems should be attacked first.
All the tools are taught together in one quality chapter, so candidates pattern-match on keywords ('failure', 'cause', 'problem') rather than on whether the task is prospective or retrospective, ranking or diagnosing.
What to do instead
Memorize a purpose-to-tool map: FMEA is prospective, run before a failure; RCA is retrospective, run after an event; Pareto ranks and prioritizes known problems; fishbone generates candidate causes; control charts separate special from common cause; PDSA tests a change. Read the stem for tense (will fail versus has failed) and for the decision requested (rank, explain, test, or monitor).
Selecting the harshest disciplinary option offered for a first, minor, or clearly system-driven performance problem - terminating a technologist who followed a confusing procedure, or issuing a written warning with no documented prior coaching.
Candidates reason backward from the bad outcome rather than from the behaviour and its intent, and they usually see only the endpoint of disciplinary cases, never the earlier rungs of the ladder.
What to do instead
Apply a just-culture triage before answering: human error means console the individual and fix the system; at-risk behaviour means coach and remove the incentive; reckless behaviour means sanction. Then match the response to the organization's progressive discipline sequence and confirm the chosen option includes documentation and consistency with how similar cases were handled.
Computing productivity with the wrong denominator - dividing tests by total paid FTEs when the item specifies worked FTEs, or failing to subtract vacation, holiday, and sick time before comparing the result to a benchmark.
Payroll reports paid hours and many stems deliberately supply both figures to tempt the shortcut; candidates also skip the unit conversion between hours and FTEs.
What to do instead
Write the formula before touching the numbers: worked FTE = paid FTE minus benefit-time FTE; tests per FTE = tests in the period divided by worked FTE (2,080 hours per FTE-year). Circle in the stem whether it says paid, worked, or productive hours, and carry the units through each step of the arithmetic.
Rejecting an analytical run because a single control result fell just outside 2 SD, and on a later item failing to reject when six or more consecutive points sit on one side of the mean.
The 1-2s warning rule is the one candidates see flagged daily in the LIS, so it feels like a rejection, while the multi-rule logic and the shift and trend counts are memorized once and never revisited.
What to do instead
Build a two-column card - warning rules (1-2s) versus rejection rules (1-3s, 2-2s, R-4s, 4-1s, 10x) - and note whether each detects random or systematic error. Then work ten plotted control scenarios and state aloud 'warning' or 'reject' before checking the answer.
Attributing a requirement to the wrong authority - citing OSHA for personnel qualification and competency assessment, or stating that CAP determines a test's complexity category and the minimum personnel requirements that apply to it.
Compliance content is absorbed on the job as one blended list of 'rules', and overlapping layers (CLIA as the federal floor, with CAP, state, and accreditor requirements stacked on top) are rarely separated in the candidate's mind.
What to do instead
Sort requirements into a matrix by source before answering: CLIA (test complexity, personnel minimums, proficiency testing, facility administration), CAP (accreditation standards, stricter QC), OSHA (bloodborne pathogens, chemical hygiene, tuberculosis), HIPAA (privacy and security), and state licensure. For every practice item, name the governing authority first, then evaluate the options against it.
Calling an analyzer connection bidirectional when only results travel from the analyzer to the LIS, and using 'verification' and 'validation' interchangeably when the item concerns software, interfaces, or a new method.
Candidates work with one interface every day and never see the direction of message flow, and the two assessment terms are used loosely in vendor documentation and in everyday laboratory speech.
What to do instead
For any stem describing an interface, draw the arrows (orders in, results out) and label it unidirectional or bidirectional before reading the options. Hold the definitions fixed: verification confirms that specified requirements are met with an expected result known in advance; validation confirms that the intended use is met end-to-end under real operating conditions.
Placing an external condition in the internal half of a SWOT - recording 'a new reference laboratory opened ten miles away' as a weakness, or 'our fast turnaround time' as an opportunity.
The four boxes are memorized as a slogan rather than as two axes (internal versus external, helpful versus harmful), so candidates sort entries by whether they sound good or bad.
What to do instead
Run every candidate entry through two questions: is it inside our control or outside it, and is it helpful or harmful? Internal-helpful is a strength, internal-harmful a weakness, external-helpful an opportunity, external-harmful a threat. Then attach a strategic action to each entry, since many items ask what should follow the analysis rather than how to classify it.