From vocabulary practice to purposeful use: a complete language lesson sequence

Give the phrase set a clear destination

Start by deciding what pupils must accomplish at the end. A useful final instruction is:

Agree one plan that stays within the budget and includes something each person wants to do. Be ready to explain one compromise.

Now work backwards. If a phrase will not help pupils understand the context, make a proposal or negotiate the decision, leave it out of this lesson. In Praktikal, use a text block and one licensed image or gallery to introduce the city, activities and prices. Add a single closed check so you can see whether pupils found the details they will need later.

Practise only what the pair task requires

Use two or three short Praktikal questions rather than a long exercise set:

• Pairing: join phrase openings and endings.
• Ordering: rebuild one useful sentence pattern.
• Fill-gap: choose the phrase that makes a proposal or response complete.

These supported closed questions can be graded automatically and reviewed in the results view. That makes them suitable for a quick checkpoint, not proof that the language is retained or ready for spontaneous use.

Decide what support will remain visible in the pair task. A pupil who still needs a full model may keep it; another may work from keywords. The product holds both stages in the same reusable lesson, but the support-removal decision is yours.

Collect a proposal before anyone speaks

Give every pupil two or three quiet minutes to prepare. Ask for a brief proposal with four parts: activity, time, cost and reason. A short free-text question in Praktikal can collect that written preparation. It is for teacher review, not automatic assessment of open language.

Scan the live answers and progress. Look for one pattern that should change your next move: perhaps pupils can state a preference but cannot give a reason, or they have ignored the budget. Clarify that one issue without projecting identifiable work. Response visibility matters only when it informs what you do next.

Put the decision between pupils, not between pupil and device

Give partners different preference cards and keep the shared budget visible. Pupils propose, disagree, ask a follow-up question and agree one plan face to face. Praktikal can display the task, city image and phrase prompt, but it does not capture, recognise, transcribe or score the speech.

Listen for use of the selected phrases and whether the pair is actually resolving the constraint. A submitted plan can show the decision they reached; it cannot show the quality of the conversation.

Turn the class pattern into one useful piece of feedback

After the exchange, ask each pair to submit its agreed plan or answer one closed question about the common issue you noticed. Use Praktikal's results view to choose a feedback focus. Keep it narrow enough for pupils to act on immediately: one missing reason, one word-order pattern or one way to disagree politely. Teachers can review responses and give feedback during or after the lesson.

Do not let the results screen become a speaking score. It contains written or closed-task evidence only.

Change one thing for the second attempt

Ask pupils to revise their written proposal or repeat the in-room exchange with one changed constraint: a smaller budget, a closed venue or a new preference. Remove one support only if the first attempt gives you a reason to do so.

End with a tiny reflection: “What did you change, and why?” The second artefact makes the response to feedback visible; it does not prove a lasting improvement.

Make it workable for your class

• Keep generated or decorative city imagery out; use licensed, accurate material and useful alt text.
• Supply text alternatives for information carried by images.
• Offer a non-spoken route where needed without presenting it as a lower-value task.
• If pupils work asynchronously, use the input, practice, proposal and written revision stages; do not pretend the pair conversation happened online.
• Use automatic grading only on the supported closed checks.