LCA Office Administration & Customer Care common mistakes
LCA Office Administration & Customer Care · Understand the traps and how to avoid them.
Treating 'confidential' as a single label instead of classifying records by sensitivity level, so personal client data, internal memos, and public notices are all handled the same way and the candidate cannot justify why one document is locked and another is shared.
Candidates memorise the word 'confidentiality' from policy summaries but never practise applying a classification scheme to concrete documents. Scenario questions then feel ambiguous because the candidate has no decision rule to fall back on.
What to do instead
Before the exam, build a three-tier table (public / internal / restricted) and write one example document per tier plus the correct storage, sharing, and disposal action for each. In scenario questions, name the tier first, then choose the action that matches it, and reject options that skip the classification step.
Answering confidentiality scenarios by choosing 'disclose everything to be transparent' or 'refuse everything to be safe' rather than the narrow, purpose-limited disclosure the situation actually requires.
Under time pressure the two extremes read as decisive and simple. Candidates avoid the middle option because it usually contains a qualifying clause ('only the minimum necessary to the named recipient') that takes longer to read.
What to do instead
Learn the minimum-necessary principle and apply it as a filter: for each option ask 'who needs this, for what purpose, and is this the smallest disclosure that achieves it?' Practise rewriting extreme answers into qualified ones so the qualified phrasing starts to look like the correct answer rather than a trick.
Calculating appointment or meeting times across time zones or daylight-saving boundaries by adding or subtracting whole hours from the wrong reference point, producing a slot that is off by one hour.
Candidates anchor on their own local time and convert once, forgetting that the counterpart's offset may itself change on a different date, or they convert in the wrong direction (adding when they should subtract).
What to do instead
Always convert to a single reference frame such as UTC first, note whether either location is in a DST transition on that date, then convert out. Work two or three dated examples by hand, including one that crosses a DST change, and check the result by converting back to the original zone.
Double-booking a resource (room, equipment, or a manager's calendar) because the candidate checks only the attendee list or only the room, not both against the proposed slot.
Scheduling questions often present a tidy attendee list that looks complete, and candidates stop verifying once one constraint appears satisfied. Resource conflicts are buried in a second constraint they never check.
What to do instead
Adopt a fixed checklist for every scheduling item: attendees, room, equipment, travel or buffer time, and recurring commitments. Apply it in order and write a one-line note per item so a missed constraint becomes visible before answering.
Recording data exactly as spoken or written in the source without applying the organisation's formatting standard, so dates, phone numbers, names, and addresses are entered inconsistently and fail validation.
Candidates equate accurate entry with faithful copying and do not realise that standardisation is part of the accuracy requirement. They also skip the validation message and assume the field accepted the value.
What to do instead
Memorise the common field standards (ISO-style dates, digit grouping, surname/first-name order, postal format) and treat them as part of the task. In questions, look for the option that both preserves the true value and conforms to the stated format; reject options that are faithful but non-standard.
Failing to verify a change before propagating it, so a corrected client address or contact number is updated in one system but the candidate confirms the old value to a caller or mails to the previous address.
Candidates treat the first record they see as authoritative and do not ask which system is the system of record. Verification feels like an extra step rather than the core of the task.
What to do instead
Learn to identify the system of record for each data type and the sequence: confirm identity, read from the authoritative source, update all dependent records, then read back. In questions, prefer options that include a read-back or cross-check over ones that act on a single source.
Responding to a complaint by defending the organisation or explaining the policy first, instead of acknowledging the customer's experience and confirming the specific outcome they need.
Candidates associate professionalism with policy knowledge, so they reach for the rule. Empathy statements feel soft or insincere and get skipped under exam pressure.
What to do instead
Use a fixed service sequence: acknowledge, clarify the specific issue, state what you can do and when, confirm agreement, then follow up. Practise turning policy-first answers into acknowledge-first answers, and in options prefer the one that both recognises the impact and commits to a concrete next step.
Escalating every difficult customer contact immediately, or conversely promising an outcome the candidate has no authority to deliver, instead of recognising the boundary of their role.
Candidates are unsure where their authority ends, so they pick the safest-sounding option (escalate) or the most helpful-sounding one (promise). Both avoid the harder judgement of what is actually within scope.
What to do instead
Write out a simple authority matrix: what you can decide alone, what needs approval, and what must be escalated with a warm handover. In scenarios, choose the option that resolves what is in scope and escalates the remainder with context, rather than one that does neither or overreaches.
Writing minutes or a confirmation email that records opinions, side comments, or the candidate's own summary as if they were decisions, and omitting the owner and deadline for each action.
Candidates transcribe rather than structure. Without a template in mind, they capture the flow of discussion and lose the distinction between what was said and what was agreed.
What to do instead
Use a minutes template with fixed sections: attendees, decisions, actions (owner, action, due date), and items deferred. Before answering, scan for the decision and the action list; reject options that attribute decisions to individuals who only expressed a view or that leave actions unassigned.
Choosing a communication channel or tone by habit (email for everything, or informal phrasing in a formal context) rather than by audience, urgency, sensitivity, and record-keeping need.
Candidates separate 'communication skills' from 'office tools' and answer each domain in isolation, so they never apply a channel-selection rule when a question mixes both.
What to do instead
Build a short channel-selection rule: sensitive or disciplinary matters go to a private, documented channel; urgent operational issues go to a live channel with a written follow-up; routine information goes to standard correspondence. For tone, identify the audience and purpose first, then choose the register that matches, and check that the option preserves a record where one is needed.