4.3 Basic Communication and Interpersonal Language

Communication as a Tested Competency

Basic Communication is one of the core CASAS content areas, present across STEPS (for ESL learners) and woven into GOALS reading. It measures the everyday interactional English an adult uses to get things done with other people: greeting and introducing, making and responding to requests, clarifying when something is unclear, giving and following directions and instructions, using the telephone and taking messages, and observing social courtesy. Unlike a document item that points at a printed value, a communication item asks: what is the right thing to say or do in this exchange?

The master skill is reading or hearing the communicative function before choosing. A line of dialogue or a notice performs a function - a greeting, an apology, a request, an offer, a complaint, an instruction, a thank-you - and the correct response is the one that fits that function.

Match the function to the response

The trap answer is grammatical English that responds to a different function - replying to a thank-you as if it were a question, or answering an apology with a fact about the weather. Name the function, then pick the matching move.

Clarification: the right move when information is missing

A large share of Basic Communication items test clarification language - what to say when you did not catch or understand something. The communicatively correct response to missing information is to ask for it, not to guess. Useful clarification moves include: Could you repeat that? Could you speak more slowly? What does that word mean? How do you spell it? Do you mean...? In an item where a speaker gives a phone number too fast, the appropriate next line is "Could you say the number again, please?" - not an invented number and not silence. CASAS rewards the response that repairs the conversation.

Telephone and message tasks

Telephone items - spoken on Listening STEPS or printed as a phone-message form on reading - ask you to capture and use specific information accurately:

• Who called (caller's name and sometimes the company).
• The callback number.
• The time of the call.
• The reason for the call.
• The requested action (call back, come in, bring a document).

A written While-You-Were-Out message slip is a labeled form: read the label beside each blank exactly as you would on any other form, and do not place the callback number in the time field. A common item asks what the message taker should do next, and the answer is the requested action, not a background detail.

Following and giving directions

Direction items - getting to a place, operating a machine, completing a multi-step procedure - turn on sequence words: first, next, then, after, before, finally, turn, go, until, when. The correct answer follows the steps in the exact order given; the trap answer reorders, skips, or adds a step. "Turn left at the light, then go two blocks, and the clinic is on the right" cannot be satisfied by an answer that turns right or stops at the first block. On before and after items, the order flips: "Sign the form before you give it to the clerk" makes signing the first action, not the second.

Giving directions is tested too: an item may ask which sentence correctly tells someone how to reach a location, and the right choice uses clear sequence words and matches the map or description provided.

Worked example: a clarification dialogue

A Listening or reading dialogue runs: Speaker A says, "Your appointment is on Thursday at two fifteen." Speaker B did not hear the time clearly. The question asks for B's best response. The communicatively correct answer is "I'm sorry, could you repeat the time?" - a clarification move. Wrong choices include guessing a time ("So, three o'clock?" when no such time was said), saying "Thank you, goodbye" (ending the call without the needed information), or changing the subject. The principle: when a needed detail is missing, the right move is to ask for it clearly, which is exactly the real-life skill Basic Communication measures.

Register and politeness

Basic Communication also tests register - matching politeness to the situation. A request to a supervisor or an official uses a polite form ("Could you please...?") rather than a blunt command ("Give me..."). Items may offer two responses that carry the same information but differ in courtesy; in a workplace or service setting, the polite, complete response is the supported answer.

Greetings, introductions, and small talk

Lower-level Basic Communication items test the openings and closings of conversation: greetings ("Good morning", "How are you?"), introductions ("This is my coworker, Sam"), and leave-taking ("Have a nice day"). The tested skill is matching the time and setting to the right phrase - "Good evening" fits the evening, and a formal introduction fits a new contact. A common item pairs a greeting with the appropriate reply: "How are you?" expects "Fine, thank you - and you?", not a detailed health report. The trap answer is a real English sentence that breaks the routine social script the situation expects.

Understanding indirect language

Functional communication often hides the real meaning behind a polite or indirect form, and higher-level items test whether a learner hears the intent. "Would you mind closing the window?" is a request, not a yes/no question about minding, so the cooperative reply is "Not at all" followed by closing it, or "Sure." "It's a little cold in here" can function as an indirect request to close a window or turn up the heat. CASAS rewards the response that answers the intended function rather than the literal surface, because that is the comprehension a real conversation requires.

Workplace and service interactions

Many Basic Communication items sit in work and service settings: asking a supervisor for time off, reporting a problem to a manager, ordering or returning an item, checking in at an appointment, or asking a coworker for help.

Each has an expected exchange, and the answer is the response that is both accurate and appropriately polite. Reporting a broken machine to a supervisor, for example, is best done with a clear statement of the problem and a request for what to do next, not with a vague complaint or an apology. The through-line for this whole area is simple: identify the function, respond appropriately, ask to clarify when something is unclear, and keep the steps and details in the exact order they were given.