CLTC common mistakes
CLTC · Understand the traps and how to avoid them.
Treating every ticket product as the same admission item and quoting one general price instead of the specific pass type the scenario names (single-day, multi-day, child, senior, group).
Candidates skim the scenario and answer from a remembered headline price, so the pass tier, date, and eligibility conditions in the question are ignored.
What to do instead
Before answering, write down the four facts the scenario gives: pass type, number of guests, date or season, and any eligibility condition. Match the price or rule to those four facts, not to the product you remember best.
Confusing the season pass itself with the add-ons and benefits bundled with it, such as parking, guest passes, or discounts, and counting them as separate purchases.
Marketing language blends the pass and its perks, so candidates assume every benefit is a standalone charge or, conversely, assume every perk is included in the base pass.
What to do instead
Build a two-column list in your head: what the pass includes and what is charged separately. Answer only from the included column unless the scenario explicitly asks about an add-on purchase.
Mishandling date-based pricing and blackout dates, quoting the standard rate for a scenario that falls on a peak day or inside a blackout window.
Candidates memorize a single price point and do not check the calendar detail embedded in the scenario.
What to do instead
Scan every scenario for a date, holiday, or weekday/weekend cue and re-check the pricing tier before selecting an answer. If no date is given, choose the answer that states the price depends on the visit date.
Answering show or event questions with the general park schedule rather than the specific showtime, seating rule, or access requirement named in the scenario.
The show domain overlaps with general admission knowledge, so candidates default to what they know about park hours.
What to do instead
For any show question, isolate the three variables: showtime, seating or reservation requirement, and whether separate admission applies. Answer from those three, and treat park hours as irrelevant unless the question asks about them.
Assuming special events are included with admission when the scenario describes a separately ticketed event, or the reverse.
Both models exist across the venue's calendar, and candidates apply the rule from one event to another without checking the event name in the question.
What to do instead
Memorize the event names that require a separate ticket as a short list, and when an unfamiliar event appears, choose the answer that tells the guest to confirm ticketing before arrival rather than guessing inclusion.
Giving donation or giving-program answers that describe a general charitable intent without naming the specific program, eligible recipient, or matching condition in the scenario.
Donation questions feel soft, so candidates answer with a plausible sentiment instead of the program mechanics the question is testing.
What to do instead
Treat each giving question as a mechanics question: identify the program name, the eligibility rule, and the match or minimum threshold. If any of those is missing from your answer, the answer is incomplete.
Mixing up the direction of a matching gift or the timing rule, for example stating that the employer match happens automatically or that a pledge counts before it is fulfilled.
Matching and pledge mechanics are similar in wording but differ in who initiates the match and when funds are recognized.
What to do instead
For every giving scenario, state who initiates, who confirms, and when the gift is counted. If you cannot fill all three slots, re-read the scenario before answering.
Answering engagement or contact questions with a generic 'check the website' response instead of the specific channel, team, or escalation path the scenario requires.
Candidates fall back on safe-sounding advice when they are unsure which department owns the issue.
What to do instead
Learn the routing map: which team owns ticketing, which owns events, which owns donations, and which owns accessibility or lost-and-found. Answer with the named owner and the channel, not a general referral.
Confusing venue logistics such as parking, entry gates, accessibility entrances, and re-entry rules, and giving directions that apply to a different gate or lot.
Venue details are numerous and visually similar, so candidates remember that a rule exists but attach it to the wrong location.
What to do instead
Pair each venue rule with its location in a single mental sentence, for example the gate name plus the rule. When a scenario names a location, retrieve the rule tied to that location only.
Leaving a contact-information question with a partial answer, such as a phone number without hours, or hours without the department that handles the request.
Candidates stop at the first correct-seeming detail and do not check whether the question asked for more than one element.
What to do instead
After drafting an answer, count the elements the question asked for and confirm each one appears. Contact answers should include the channel, the owning department, and availability where the scenario implies it.