ADULT ESL/ELL INTERMEDIATE • PRESENTATIONAL COMMUNICATION (SPEAKING & WRITING)

Explaining Needs with Details — I can explain a need or problem clearly and provide relevant details in common situations (work, services, health).

Master the language structures and strategies for clearly communicating needs in professional, service, and medical contexts.

Historical Context & Motivation

The ability to explain needs and problems clearly is one of the most practically important skills in any language, yet it has only recently received focused attention in language pedagogy. For much of the twentieth century, communicative competence — the capacity to use language effectively in real social situations — was not the primary goal of language teaching. Grammar-translation methods dominated classrooms, and students could conjugate verbs flawlessly but struggled to explain a toothache to a dentist or request a deadline extension from a supervisor. The shift toward functional language use reflects decades of research showing that learners need not just linguistic knowledge but pragmatic skill — the ability to deploy the right words, in the right order, with the right level of detail, for a specific communicative purpose.

1972
Hymes Defines Communicative Competence
Dell Hymes argued that knowing a language means more than knowing grammar rules — it means knowing when, where, and how to use language appropriately in social contexts. This concept laid the foundation for teaching language as a tool for real-world communication.
1983
Canale & Swain's Framework
Canale and Swain expanded communicative competence into four components: grammatical, sociolinguistic, discourse, and strategic competence. Their model highlighted that explaining needs requires all four components working together.
2001
CEFR Published
The Common European Framework of Reference for Languages introduced 'can-do' descriptors, explicitly identifying the ability to explain problems and needs as a B1-level skill. This standardized how proficiency in functional tasks is measured worldwide.
2012
ACTFL Proficiency Guidelines Updated
The American Council on the Teaching of Foreign Languages refined its proficiency scale, emphasizing that intermediate speakers can 'handle successfully a variety of uncomplicated communicative tasks in straightforward social situations,' including explaining needs at work, in services, and in health care.

This trajectory reveals a critical insight: language learning is not merely about mastering vocabulary lists or grammar charts. It is about developing the ability to organize information strategically so that a listener or reader can understand your situation and help you. How do you structure a clear explanation? What details are relevant, and which are distracting? What language patterns signal urgency, politeness, or specificity? These are the questions this lesson addresses.

Core Principles of Explaining Needs

Effectively explaining a need or problem in English requires more than stringing together correct sentences. It demands a structured approach rooted in several key principles that govern how information is selected, organized, and delivered. Whether you are speaking to a manager about a workplace issue, calling a repair service about a broken appliance, or describing symptoms to a doctor, the same foundational framework applies. Understanding these principles allows you to adapt your communication to any situation with confidence and precision.

1

State the Need First

Begin with a clear topic statement that identifies the problem or request. English communication favors a direct approach: the listener should know what you need within the first sentence or two. For example, 'I need to report a problem with my internet service' is more effective than beginning with background details.
2

Provide Relevant Details

After stating the need, supply specific, relevant information that helps the listener understand the situation. Use the journalist's framework — who, what, when, where, why, and how — to ensure completeness. Relevance is key: a doctor needs to know when your pain started, not what you ate for breakfast (unless it's related).
3

Use Appropriate Register

Register refers to the level of formality in your language. Speaking to a supervisor requires different vocabulary and sentence structures than chatting with a coworker. Markers of formality include modal verbs ('could,' 'would'), indirect requests, and polite openings such as 'I was wondering if…'
4

Signal Urgency and Importance

English offers specific urgency markers — words and phrases that tell the listener how quickly action is needed. Phrases like 'as soon as possible,' 'this is urgent,' or 'I need immediate assistance' calibrate the listener's response. Conversely, 'when you get a chance' signals low urgency.
5

Request a Specific Outcome

Conclude by stating what action you expect or what resolution you are seeking. This transforms a complaint into a constructive request. Instead of simply describing a problem, add: 'Could you send a technician by Friday?' or 'I'd like to schedule a follow-up appointment.'
KEY TAKEAWAY
Think of explaining a need like filing a report: you start with a headline (what's the problem?), then provide supporting evidence (relevant details like time, place, severity), and finally state the desired outcome (what should happen next). Just as a well-organized research paper guides the reader from thesis to evidence to conclusion, a well-structured explanation of a need guides the listener from understanding the situation to knowing how to help.

The Need-Explanation Framework Visualized

The following diagram illustrates the S-D-O framework (Statement – Details – Outcome) that structures effective need explanations across all contexts. Each stage builds on the previous one, guiding the listener from initial awareness of the problem through the relevant specifics to a clear understanding of what action is expected. Notice how the framework applies universally, whether you are at work, accessing a service, or visiting a healthcare provider.

The S-D-O framework (Statement – Details – Outcome) provides a universal structure for explaining needs. The top row shows the three stages, while the bottom row demonstrates how the same framework applies across work, service, and health contexts.

As the diagram shows, the framework is not rigid but adaptable. In a workplace context, the details emphasize deadlines, responsibilities, and project-specific information. In a service context, they center on technical specifications, timelines of malfunction, and account information. In a health context, details focus on symptoms, duration, severity, and relevant medical history. The consistent three-part structure ensures that regardless of context, your explanation moves the listener efficiently from understanding the problem to knowing how to respond.

Language Structures for Explaining Needs

Certain grammatical structures and vocabulary patterns recur whenever English speakers explain needs or problems. Mastering these patterns gives you a linguistic toolkit that you can deploy flexibly across situations. This section examines four essential categories of language structures: opening statements, detail-providing structures, urgency markers, and outcome requests. Each category includes both formal and informal variations so you can adjust your register to fit the situation.

Opening Statements: Naming the Need

Opening statement patterns by register
FunctionFormal RegisterInformal Register
Stating a problemI would like to report a problem with…I'm having trouble with…
Requesting helpI am writing to request assistance regarding…I need some help with…
Explaining a situationI wanted to bring to your attention that…So here's what happened…
Making a complaintI am concerned about…I'm not happy with…

Detail-Providing Structures

Once you have stated your need, you must elaborate with precise details. Several grammatical structures are particularly useful here. Time clauses anchor events in a timeline: 'This started on Monday,' 'It has been happening since last week,' or 'The problem occurs every time I try to log in.' Descriptive adjectives and adverbs characterize the severity or quality of the problem: 'The pain is sharp and constant,' 'The noise is extremely loud,' or 'The software crashes intermittently.' Present perfect tense connects a past event to the present moment: 'I have been waiting for three days' implies the wait is still ongoing. Conditional structures clarify cause and effect: 'When I press the button, nothing happens' or 'If I take the medication at night, I feel dizzy in the morning.'

Urgency Markers and Outcome Requests

The final components of your explanation involve signaling how quickly you need help and specifying what you want to happen. Urgency markers range from high urgency ('This is an emergency,' 'I need immediate assistance') to moderate urgency ('As soon as possible,' 'At your earliest convenience') to low urgency ('When you get a chance,' 'There's no rush, but…'). Outcome requests use modal verbs to calibrate politeness: 'Could you…?' and 'Would it be possible to…?' are more polite than 'Can you…?' which is itself more polite than the imperative 'Send me…' Understanding this politeness gradient allows you to make requests that are both clear and socially appropriate.

💡 Register Tip
A useful rule of thumb: the more distance between you and the listener (in terms of power, familiarity, or formality of the setting), the more indirect your language should be. Compare 'Fix this' (direct, informal) → 'Can you fix this?' (polite) → 'Would it be possible to have this repaired?' (very formal). All three communicate the same need, but at different registers.

Context-Specific Language: Work, Services, Health

While the S-D-O framework provides a universal structure, each context demands its own domain-specific vocabulary and conventions. A workplace email about a project delay uses different vocabulary than a phone call to a plumber, which in turn differs from a conversation with a physician. This section provides detailed breakdowns of the language patterns most commonly needed in each of the three target contexts, along with a visual reference showing how vocabulary clusters differ across domains.

This vocabulary map organizes essential nouns, verbs, and phrases for each of the three target contexts. Note how register expectations differ: workplace communication tends toward semi-formal or formal language, service interactions use a neutral to semi-formal register, and health communication ranges from neutral to formal depending on the provider.

Beyond vocabulary, each context has its own conversational conventions. In workplace settings, it is common to begin emails with a brief context-setting phrase ('I'm writing regarding the Q3 report…') before stating the need. In service interactions, you are often asked to provide identifying information early — your account number, order number, or address — so have this ready before you begin explaining the problem. In health contexts, doctors and nurses frequently guide the conversation with questions, but being prepared to describe the onset, location, duration, character, and severity of symptoms using precise language significantly improves the quality of care you receive.

Worked Example: Explaining a Health Problem to a Doctor

Let us walk through a complete example of explaining a health concern to a doctor, applying the S-D-O framework and the language structures discussed above. Imagine you have been experiencing persistent headaches and want to communicate this effectively during a medical appointment.

Explaining Persistent Headaches to a Doctor
1
Step 1 — State the Need (S)Begin with a clear, direct statement of your primary concern. Avoid beginning with unrelated background. A strong opening might be: 'Doctor, I've been having severe headaches for the past two weeks, and I'm concerned because they seem to be getting worse.' This sentence accomplishes three things: it names the symptom (headaches), provides a timeframe (two weeks), and signals the reason for concern (worsening). Notice the use of the present perfect progressive ('I've been having') to indicate an ongoing condition.
Opening statement established: symptom + timeframe + concern.
2
Step 2 — Provide Relevant Details (D)Now provide the details the doctor needs using the OLDCARTS framework commonly used in medical contexts: Onset, Location, Duration, Character, Aggravating factors, Relieving factors, Timing, Severity. You might say: 'The headaches started about two weeks ago. The pain is mostly on the right side of my head, behind my eye. Each headache lasts about three to four hours. The pain feels like a throbbing or pulsing sensation. It gets worse when I look at screens for a long time, and it improves slightly when I lie down in a dark room. The headaches tend to happen in the afternoon. On a scale of one to ten, I would rate the pain at about seven.' Each sentence targets a specific piece of information the doctor needs.
Eight categories of detail covered: onset, location, duration, character, aggravating, relieving, timing, severity.
3
Step 3 — Add Background InformationInclude relevant medical history and any actions already taken: 'I've tried taking ibuprofen, but it only helps a little. I don't have a history of migraines, and I'm not currently taking any prescription medications. I do drink about three cups of coffee per day, and my work requires me to use a computer for eight hours or more.' This provides context without overwhelming the listener with irrelevant information.
Relevant background provided: self-treatment, medical history, lifestyle factors.
4
Step 4 — Request a Specific Outcome (O)Close by expressing what you hope will happen: 'I was hoping you could help me figure out what's causing these headaches. Would it make sense to run some tests, or is there a medication you would recommend trying first?' This outcome request is polite (using 'I was hoping' and 'Would it make sense'), collaborative (inviting the doctor's expertise), and specific (mentioning tests or medication as possible next steps).
Polite, specific outcome request: diagnosis + treatment options requested.
Why This Works
This explanation succeeds because it is organized (following S-D-O), specific (using precise vocabulary like 'throbbing,' 'right side,' 'behind my eye'), complete (covering all OLDCARTS categories), and actionable (ending with a clear request). The doctor can now make informed decisions without needing to ask many follow-up questions.

Effective vs. Ineffective Need Explanations

Understanding what makes a need explanation effective requires examining common pitfalls alongside best practices. The following table contrasts weak and strong examples across the three target contexts, highlighting specific linguistic choices that make the difference between confusion and clarity.

Comparing ineffective and effective need explanations across contexts
Context❌ Ineffective Explanation✅ Effective ExplanationWhy It's Better
Work"I can't finish my work. There's too much.""I won't be able to meet the Friday deadline for the market analysis because the sales data wasn't available until yesterday. Could I have until next Tuesday?"Names the task, explains the cause, specifies an alternative timeline
Services"My phone doesn't work. Fix it.""I purchased this phone three weeks ago and the screen has started flickering when I open apps. It's still under warranty. Could I get a replacement or have it repaired?"Provides purchase date, describes the problem precisely, mentions warranty, offers two outcomes
Health"My stomach hurts. I feel bad.""I've had a sharp pain in my lower abdomen for three days. It gets worse after eating, especially greasy food. I haven't had a fever, but I've felt nauseous twice. Could we check if it might be related to my gallbladder?"Specifies location, duration, triggers, additional symptoms, and suggests a diagnostic direction
KEY TAKEAWAY
The difference between a weak and a strong need explanation is analogous to the difference between a vague search query and a precise one. Searching for 'my computer is broken' returns millions of unhelpful results; searching for 'MacBook Pro 2023 screen flickers when opening Safari after latest update' leads directly to a solution. Similarly, specificity is the single most powerful tool for transforming a confusing complaint into an actionable request. When you add precise details about time, location, severity, cause, and desired outcome, you dramatically increase the likelihood of getting the help you need.

Connecting to Advanced Communication Skills

The ability to explain needs with details at the intermediate level forms the foundation for more advanced communication tasks. As you progress toward upper-intermediate and advanced proficiency, the skills practiced here evolve into more complex discourse abilities. The following table shows how each component of the S-D-O framework maps onto higher-level communication tasks that you will encounter in academic, professional, and civic contexts.

How intermediate need-explanation skills connect to advanced proficiency
Intermediate Skill (This Lesson)Advanced ApplicationExample Context
Stating a need directly (S)Writing a thesis statement or proposal abstractAcademic writing, grant proposals
Providing relevant details (D)Building evidence-based arguments with supporting dataResearch papers, legal briefs, policy reports
Using appropriate registerCode-switching across genres and audiencesConference presentations vs. public outreach
Signaling urgencyPersuasive rhetoric and call-to-action framingAdvocacy campaigns, persuasive essays
Requesting an outcome (O)Negotiating terms and proposing solutions collaborativelyBusiness negotiations, diplomatic communication

Notice that the fundamental logic — state your position, support it with evidence, and drive toward an outcome — remains constant across proficiency levels. What changes is the complexity of the content, the sophistication of the language, and the degree of nuance required. By mastering the S-D-O framework now, you are building a transferable skill set that will serve you in virtually every communicative context you will encounter in your academic and professional life. Advanced speakers do not abandon these strategies; they elaborate on them, embedding them within longer, more complex discourse structures.

Practice Problems

The following five problems progress from conceptual understanding to critical application. For each, think carefully about how to apply the S-D-O framework, choose appropriate register, and include relevant details. Write or speak your answers in complete sentences.

PROBLEM 1CONCEPTUAL
What are the three stages of the S-D-O framework, and why is it important to state the need before providing details? Explain using your own words.
PROBLEM 2BASIC APPLICATION
Rewrite the following ineffective workplace email into an effective one using the S-D-O framework: 'Hi, I have a problem. The printer is broken and I really need it. Can someone help?'
PROBLEM 3INTERMEDIATE
You call your internet service provider because your internet has been unreliable for the past week. Write a complete spoken script (6–8 sentences) that uses the S-D-O framework, includes at least four specific details, uses appropriate register for a customer service call, and includes one urgency marker.
PROBLEM 4APPLIED
You are a new employee and need to email your supervisor to explain that you need a schedule change for the next three weeks because you have a recurring medical appointment every Wednesday afternoon. Write the complete email, paying careful attention to register, tone, and the balance between providing enough detail and respecting your own privacy.
PROBLEM 5CRITICAL THINKING
Consider this scenario: You visit a doctor with two separate health concerns — chronic knee pain and recent insomnia. How would you structure your explanation to address both issues effectively in a single appointment? What risks arise from either combining or separating the two issues, and how does the S-D-O framework help you manage complexity? Write a reflective analysis (8–10 sentences) and then draft the opening portion of what you would say to the doctor.

Lesson Summary

This lesson introduced the S-D-O framework (Statement – Details – Outcome) as a universal structure for explaining needs and problems in English. At the Statement stage, you name the problem directly so the listener immediately understands the topic. At the Details stage, you supply relevant information — who, what, when, where, why, and how — using precise vocabulary, present perfect tense for ongoing conditions, descriptive adjectives for severity, and conditional structures for cause-and-effect relationships. At the Outcome stage, you request a specific action using modal verbs calibrated to the appropriate level of politeness.

Across all three target contexts — work, services, and health — the framework remains the same, but the domain-specific vocabulary and register shift to match the expectations of each setting. The key to effective communication is specificity: precise details about time, location, severity, and cause transform vague complaints into clear, actionable requests that enable the listener to help you efficiently. These intermediate-level skills form the foundation for advanced academic and professional communication, including thesis writing, formal proposals, and negotiation.

Varsity Tutors • Adult ESL/ELL Intermediate • Explaining Needs with Details