CLWM common mistakes
CLWM · Understand the traps and how to avoid them.
Mapping a legal process by drawing the steps the way the firm says they should work, rather than tracing how a live matter actually moved through intake, conflict check, engagement letter, and file opening, including the detours and rework loops.
Candidates study the documented policy and treat it as the process. Exam scenarios deliberately describe a real matter that skipped a conflict check or looped back for missing client ID, and the candidate maps the ideal state instead, missing the failure point the question targets.
What to do instead
When a scenario describes an actual matter, build the map only from the events described, then mark each handoff, decision point, and rework loop explicitly. Compare that map to the stated policy as a separate step and name the gap. Practise converting narrative case descriptions into swimlane maps with a start event, decision diamonds, and an end state.
Treating triage as 'accept every matter' or 'reject anything unusual' instead of applying stated acceptance criteria such as practice area fit, matter value, deadline feasibility, and risk rating, then routing to the correct fee earner or declining with a documented reason.
Triage questions often include a sympathetic client or an urgent deadline, and candidates let urgency override the criteria. Others assume a conflict of interest is the only decline trigger and ignore capacity, scope, or uninsured risk.
What to do instead
Before answering, write out the firm's stated acceptance criteria from the scenario and score the matter against each one. If any mandatory criterion fails, the answer is decline or escalate, regardless of urgency. Distinguish 'decline' from 'refer out' and from 'accept with conditions' and check which the firm's policy permits.
Confusing version control with file naming: assuming that saving 'Contract_v3_final_FINAL.docx' is sufficient control, and failing to identify that the authoritative version must be held in the document management system with check-in/check-out, audit trail, and a single source of truth.
Candidates rely on everyday desktop habits. Exam questions test whether they know that email attachments and local copies break the chain of custody and that 'final' in a filename carries no legal or evidentiary weight.
What to do instead
Learn the components of a defensible version control regime: unique document ID, controlled repository, check-out locking, version history with author and timestamp, and a defined point at which a version becomes the executed or filed copy. In scenarios, locate where a copy left the repository and state the control that would have prevented it.
Building a legal budget by summing hourly rates times estimated hours and stopping there, omitting disbursements, counsel fees, taxes, contingency, escalation, and the phases or task codes the client's outside counsel guidelines require.
Candidates default to a simple arithmetic exercise. Exam scenarios embed billing guidelines, phase and task code requirements, and a fixed-fee or capped component that changes how the budget must be structured and reported.
What to do instead
Always decompose a budget into fees by phase and task, disbursements, third-party costs, and contingency, then apply any cap, fixed fee, or success fee stated in the scenario. Check the outside counsel guidelines in the fact pattern for required task codes, staffing mix limits, and reporting cadence before finalising the number.
Automating a broken or undocumented process: designing a workflow rule or template for a step that has no clear owner, no defined trigger, and no exception path, so the automation silently fails on the first unusual matter.
Candidates see automation as a technical exercise and focus on the rule logic. They forget that a rule encodes a decision, and an undocumented decision produces a rule that misfires or blocks legitimate matters.
What to do instead
Before designing any rule, state the trigger, the condition set, the action, the owner, and the exception or override path. Test the design against at least one edge case from the scenario, such as a matter with two clients or a missing data field, and specify how the rule behaves when a required field is empty.
Treating the practice management system and the case management system as interchangeable, and failing to distinguish the system of record for time and billing from the system of record for matter documents, tasks, and deadlines.
Vendors and firms use the terms loosely, so candidates assume one product covers both. Exam questions test whether the candidate can identify which system holds the authoritative data and how the two integrate.
What to do instead
Memorise the functional split: practice management covers time capture, billing, trust accounting, and financial reporting; case management covers matter intake records, document and email linkage, task and deadline management, and matter-level reporting. For any scenario, ask 'which system is the source of truth for this data item' and answer from that split.
Handling a confidentiality or conflict scenario by citing the general duty of confidentiality without identifying the specific obligation triggered, such as a screening requirement, an information barrier, a client consent step, or a mandatory regulatory report.
Candidates know confidentiality exists but not the operational controls that satisfy it. They give a broad ethical statement where the question wants the concrete mechanism and the order in which it must occur.
What to do instead
For each scenario, name the duty, the trigger, and the control: conflict check before engagement, need-to-know access restriction, ethical screen for a lateral hire, engagement letter scope and third-party disclosure consent, and records retention schedule. Sequence the controls in the order the scenario requires and state who must approve any exception.
Assuming that deleting a file ends the retention obligation, or that retention means keeping everything forever, rather than applying a defined retention schedule with legal hold suspension, secure disposal, and documented destruction.
Candidates conflate data minimisation with deletion on demand. Exam questions test whether they know a legal hold overrides the retention schedule and that destruction must be logged and defensible.
What to do instead
Learn the retention lifecycle: classification, scheduled retention period by matter type, legal hold that suspends destruction, review at expiry, and certified disposal with an audit record. In scenarios, check first whether a hold or foreseeable litigation applies before permitting any deletion.
Reporting a single headline metric such as billable hours or matter count as evidence of improvement, without a baseline, a target, a defined data source, and a comparison over time.
Candidates answer with the metric they can name rather than the measurement design. Exam questions ask how you would know whether a workflow change worked, and a bare number cannot answer that.
What to do instead
For any improvement question, specify the metric definition, the data source and owner, the baseline period, the target, the review cadence, and the confounders to watch. Prefer paired measures such as cycle time alongside error or rework rate, so a speed gain that increases defects is visible.
Rolling out a new workflow or system by announcing it and issuing a manual, without identifying stakeholders, assessing impact by role, planning training and piloting, or defining how feedback and resistance will be handled.
Candidates treat adoption as a communication task rather than a change programme. Exam scenarios describe fee earner resistance or a partner refusing to use the new intake form, and the candidate prescribes more training instead of addressing incentives, sponsorship, and workflow fit.
What to do instead
Structure every adoption answer around sponsor engagement, role-based impact assessment, a pilot with named champions, targeted training, feedback channels, and reinforcement through metrics and incentives. Diagnose resistance before prescribing a remedy: capability gaps need training, workflow friction needs redesign, and incentive conflicts need partner-level resolution.