ALA CLM common mistakes
ALA CLM · Understand the traps and how to avoid them.
Treating a legal-management scenario as a pure legal-ethics question and answering with the 'most ethical-sounding' option rather than the option that best serves sound firm management.
Candidates carry habits from substantive law or ethics exams, where the safest-sounding answer usually wins; CLM items instead reward the balanced management judgment (e.g., documenting a decision, escalating through the right channel, protecting both client and firm interests).
What to do instead
Before choosing, ask 'what would a competent managing partner or legal administrator actually do to run the firm well here?' and prefer options that combine process, documentation, and proportionate response over dramatic or purely moralistic ones.
Confusing the roles and authority of the managing partner, the firm administrator/CLM, and the partnership/board when answering governance scenarios.
The titles overlap in practice and candidates map them loosely, so they attribute decisions (compensation changes, policy adoption, hiring/firing) to the wrong body.
What to do instead
Build a one-page authority matrix: who decides, who recommends, who implements for each common decision type, and check every governance answer against it.
Computing profitability or billing-rate figures without correctly distinguishing direct costs, overhead, and the effect of realization and utilization.
Candidates plug numbers into a formula but skip intermediate steps (e.g., applying write-downs before computing realized rate), so they pick a distractor that reflects an earlier stage of the calculation.
What to do instead
Work the chain explicitly: standard rate → billed → collected (realization) → cost to produce (utilization and overhead) → margin; write each intermediate figure before selecting an answer.
Mishandling trust/IOLTA accounting concepts, such as commingling, timing of deposits and withdrawals, or earned-vs-unearned fee treatment.
Candidates treat trust accounting as ordinary bookkeeping and ignore the strict rules on when funds may be moved and what may be held in trust.
What to do instead
Memorize the core rules as bright lines (client funds separate, no firm operating money in trust, fees withdrawn only when earned or as agreed) and test each option against those bright lines.
Answering cash-flow or budgeting questions using accrual logic when the scenario calls for cash basis, or vice versa.
The distinction is glossed over under time pressure, and both answer types appear as plausible distractors.
What to do instead
Identify the basis stated or implied in the stem first, circle it mentally, and eliminate any option that only works under the other basis.
Selecting disciplinary or termination responses for performance problems before trying progressive, documented coaching and improvement steps.
Candidates jump to the most decisive-sounding action, but HR items usually reward the proportionate, documented sequence.
What to do instead
Default to the documented progressive path (feedback, improvement plan, review) unless the stem describes misconduct serious enough to justify immediate action.
Missing legal-compliance constraints in HR scenarios, such as protected characteristics, retaliation risk, or leave and accommodation obligations.
Candidates focus on the managerial goal (e.g., filling a role, addressing attendance) and overlook the legal overlay that makes an otherwise sensible action unlawful.
What to do instead
For every HR option, ask 'does this touch a protected status, a leave right, or could it look like retaliation?' and eliminate options that do.
Choosing workflow or staffing fixes that add capacity (hire, add technology) when the scenario's root cause is a process bottleneck or poor delegation.
Adding resources feels like the strong management move, but operations items often test diagnosing the constraint before spending.
What to do instead
Identify the bottleneck or failure point in the stem first; prefer the option that removes the constraint or fixes the process over one that simply adds people or tools.
Ignoring project-management fundamentals in operations scenarios, such as unclear scope, missing milestones, or absent responsibility assignment.
Candidates read the scenario as a people or client problem and skip the structural cause embedded in the facts.
What to do instead
Check each operations stem for scope, schedule, roles, and communication gaps, and favor options that establish those controls.
Confusing marketing with business development and client service, e.g., choosing a branding or advertising action when the scenario calls for relationship-building, cross-selling, or client feedback processes.
The terms are used interchangeably in everyday speech, so candidates pick a promotional answer for a retention or development problem.
What to do instead
Classify the goal in the stem (attract, develop, or retain) and match the tactic to it; for existing-client scenarios prefer relationship and feedback actions over promotional ones.