Speaking Practice Needs Analysis: Start With Real Communication Tasks

A speaking practice needs analysis should begin with the conversations learners must actually handle, then work backward to the language functions, conditions, and evidence those conversations require. Do not start with a platform feature list, a generic level label, or a target number of practice minutes.

The result is a short decision document: who must speak, with whom, for what outcome, under which constraints, and how the program will know the learner can do it reliably. The Council of Europe’s official Companion Volume publication record identifies its illustrative descriptor framework, but a descriptor is a reference point, not a ready-made curriculum for a particular workplace, university, or public service.

Define the communication task before the course

“Improve speaking” is too broad to design or evaluate. “Explain a delayed shipment to a customer, check understanding, and agree a next action in a five-minute call” is actionable. It identifies an interlocutor, purpose, channel, time pressure, and visible result.

Interview learners, their managers or teachers, and people who receive the communication. Ask for recent examples, including conversations that went wrong. Observe the task when privacy and policy allow. Collect artifacts such as call outlines, meeting agendas, or public-facing service scripts without copying confidential information into a learning system.

For each task, record:

Field	Useful question	Example
Outcome	What must be different when the exchange ends?	The caller understands the delay and accepts a new date
Interlocutor	Who participates and what can they reasonably know?	A frustrated customer unfamiliar with internal terms
Mode	Is it live, recorded, in person, or audio-only?	Live audio call
Pressure	What makes the task difficult?	Interruptions, numbers, and an unexpected objection
Language action	What must the learner do with language?	Explain, clarify, acknowledge, propose, confirm
Evidence	What would count as competent performance?	Key facts accurate; repair succeeds; next action confirmed

This task-first approach also prevents a common procurement error: equating access to a speaking tool with a completed learning outcome.

Use three evidence layers

A defensible analysis separates evidence into three layers.

1. Reported need: what participants say they need. This reveals confidence, perceived barriers, and motivation, but self-report alone may miss work that has become habitual.
2. Observed task: what communication actually requires. Observation may expose turn-taking, repair, register, or terminology that a survey never names.
3. Performance sample: what learners can currently do in a representative simulation. Use more than one prompt so familiarity with a single scenario does not masquerade as transferable ability.

The CEFR Companion Volume offers illustrative descriptors across communicative activities, but local users still need to select and adapt them to their purpose. That makes descriptors helpful when turning needs into learning targets, while the local task analysis supplies the context a general framework cannot know.

Convert a task into a practice specification

Take one priority task and write a one-page specification:

Task: Give a concise project update in an international stand-up.

Successful result: colleagues understand progress, the current blocker, and the requested decision.

Conditions: video call, up to ninety seconds, one follow-up question, mixed proficiency among listeners.

Language resources: sequencing, approximate quantities, cause and effect, diplomatic disagreement, and clarification.

Interaction resources: signal completion, invite a question, notice misunderstanding, and repair it.

Practice sequence: first rehearse the update; then add an unpredictable question; then change the audience and blocker; finally perform after a delay without the original notes.

Evidence: two trained reviewers use a short task rubric; the learner succeeds on two different versions, not merely the rehearsed version.

The distinction between long-turn production and co-constructed interaction matters here. A fluent monologue does not prove the learner can respond when another speaker interrupts or asks for precision. Use the comparison in Synchronous vs Asynchronous Speaking Practice to choose conditions that match the target.

Prioritise instead of collecting an endless wish list

Score each candidate task on four dimensions from one to three:

• frequency: how often learners face it;
• consequence: what happens if communication fails;
• current gap: how far present performance is from the required result;
• trainability: whether practice and feedback can plausibly improve it within the program.

Multiply frequency, consequence, and current gap, then use trainability as a decision check rather than a mathematical promise. A rare safety-critical task may still outrank a frequent low-consequence exchange. Document that judgment.

After prioritising, connect each task to a measurement plan. How to Measure Learner Speaking Time helps distinguish opportunity from active speech, while Oral Language Outcome Measures helps match the metric to the claim. Those are separate questions: participation data cannot establish communicative competence.

Make the deliverable usable

Keep the final analysis short enough to govern decisions. A practical package contains:

• a population and context statement;
• five to eight ranked communication tasks;
• task cards using the fields above;
• a baseline sampling plan;
• accessibility, privacy, and recording constraints;
• target outcomes and review dates;
• unresolved assumptions and an owner for each one.

Revisit the analysis when roles, channels, or learner populations change. A program designed around scheduled presentations may become misaligned if the real work shifts to rapid customer calls.

Commercial disclosure

LinguaLive sells AI-supported speaking practice and offers an education pathway. That commercial interest makes task-first analysis especially important: the needs document should be usable even if an institution selects another provider. A product demonstration, vendor score, or usage dashboard is not evidence that the institution’s priority communication tasks have been met.

Limitations

Needs analysis is context-specific and partly judgment-based. CEFR resources can help describe performance, but they do not validate a local course, certify an individual from one sample, or replace occupational standards. Observation can alter behaviour, and stakeholder interviews can overrepresent people with more authority.

For regulated work, disability accommodation, safeguarding, employment decisions, immigration, clinical care, or other high-stakes uses, involve qualified local specialists and the affected community. Do not collect authentic recordings or confidential work artifacts unless there is a documented lawful, ethical, and secure process.

Frequently asked questions

How many tasks should a speaking needs analysis include?

Start with five to eight priority tasks for one population. A longer inventory can exist in the background, but a small ranked set produces clearer practice and measurement decisions.

Can a CEFR level replace the task analysis?

No. A level can provide shared reference language, while the task analysis identifies the actual audience, purpose, pressure, and acceptable result in the local context.

Should learner confidence be measured?

Yes, as a separate outcome. Confidence can affect participation and matters to learners, but it should not be treated as proof that a communication task was completed accurately or appropriately.

Sources and editorial review

This guide was checked against its primary official or academic reference on 29 July 2026. Language usage can vary by region, relationship, and situation. Review the primary source.