Spoken presentations and interviews in HSC English Studies
“Students plan, rehearse and deliver spoken texts such as presentations and interviews, adapting voice and structure for audience and purpose”
A spoken text is planned like writing but delivered like a performance: plan two or three points for a clear audience and purpose, structure them as open, body (each point with an example) and close, and control delivery through pace, pausing, volume, eye contact and cue cards rather than a full script. A listener cannot reread, so signposting and repetition matter more than in writing; rehearsal is essential because delivery is a skill built only through practice. The same skills, in a more formal register, prepare you for a job interview.
Jump to a section
Think about the difference between a text message and a phone call to the same friend. In the text you can write a sentence, delete it, rewrite it, and send it only when it says exactly what you mean. On the phone call, the words come out once, live, and your friend cannot scroll back up to reread what you said a minute ago - so you naturally slow down, repeat the important bit, and say "anyway, the main thing is..." to keep them with you. A spoken presentation or a job interview works exactly like that phone call, not like the text message. You still have to plan WHAT you are going to say, just like planning an essay, but you then have to say it in a way built for listening: shorter sentences, clear signposts like "first" and "finally," a bit of repetition, and delivery choices (how fast you talk, how loud, whether you look up) that a page of writing simply does not need. Learn to plan like a writer but perform like a speaker, and both a class presentation and a job interview become much less scary.
What this dot point is asking
A lot of real-world English is spoken, not written: a presentation to a class, a talk at a community meeting, a job interview, a phone call to a service. This dot point asks you to plan, rehearse and deliver spoken texts and to adapt your voice and structure for your audience and purpose. Spoken English is its own skill, with its own techniques and its own ways of losing marks. A speech that reads well on paper can fall flat when delivered, and a relaxed chat can fail an interview. Your task is to learn how speaking works, practise it deliberately, and be able to explain in writing (for a portfolio task or Section III response) WHY spoken and written texts demand different choices.
The answer
A good spoken text is planned like a written one but delivered like a performance. The content matters, but so does HOW you say it: your pace, your volume, your pauses and your eye contact. The audience cannot reread you, so clarity and signposting matter even more than they do in writing.
Speaking is not writing read aloud
The most common misunderstanding is treating a presentation as an essay read out loud. Spoken English needs:
- Shorter sentences, so the listener can follow without losing the thread.
- Signposting words ("First", "The main thing is", "Finally") so the listener always knows where they are.
- Repetition of key points, because a listener cannot scroll back.
- A natural, spoken rhythm, not dense written phrasing.
Plan your content fully, but write it in the way you would actually say it, not the way you would type it.
The one-line test examiners look for: could this sentence be understood on a SINGLE hearing, with no rereading? If a sentence needs to be read twice to make sense on the page, it will fail completely when spoken aloud once. Shorter sentences, explicit signposting ("first", "my main point is", "to finish") and deliberate repetition of the key message all exist to pass this test; a written essay does not need any of them in the same way, because a reader can always look back.
Structure for a presentation
A reliable, general-purpose shape works for almost any spoken presentation, whatever the topic or prescribed text it draws on:
- Open: greet the audience and tell them what your talk will cover.
- Body: two or three clear points, each with a specific example.
- Close: restate the main message and end on a strong final line.
Telling the audience your structure at the start ("I'll cover three things") helps them follow and helps you stay on track.
Delivery you can control
You cannot change being nervous, but you CAN control a few things that make a real difference to how a talk lands:
- Pace: slow down. Nervous speakers rush. A pause is not a mistake; it gives the audience time to absorb a point.
- Volume: speak up enough to be heard at the back of the room.
- Eye contact: look at the audience, not only at your notes.
- Notes: use cue cards with key words, not a full script you read word for word.
Rehearsal is where this is built. Practise aloud, time yourself, and run it in front of one other person if you can. The dot point says "rehearse" for a reason: delivery improves enormously with practice, and only with practice.
Interviews: a high-stakes spoken text
A job interview is a spoken text with unusually high stakes and a single, formal audience. Prepare answers to likely questions (your strengths, why you want the role, a time you solved a problem) but do not memorise them stiffly. Speak clearly, give specific examples rather than vague claims, and ask one question of your own at the end to show genuine interest. The register is formal and polite but warm. This is the speaking side of the job-application skills the module also teaches in writing, and the comparison below is exactly the kind of thing a Section III response might ask you to explain.
Task (generic, works for any presentation topic). Deliver a two-minute talk to your class on a skill you learned outside school, then be ready to explain your spoken choices if asked in a portfolio reflection or Section III response.
Model opening and close (hypothetical student example, written the way it would actually be SAID aloud).
"Today I want to tell you about three things a part-time job taught me: managing my time, talking to customers, and handling mistakes. First, time management. [pause] When I started, I was always late for my shift because I underestimated the bus trip - now I plan fifteen minutes extra, every time. Second, talking to customers. [pause] I learned to listen first and solve the problem second, not the other way around. Third, handling mistakes. [pause] I once gave a customer the wrong change, and the important thing wasn't the mistake, it was fixing it calmly and honestly. So: time management, communication, and staying calm under pressure - three things this job taught me that I'll use in any job I have next."
Marker's note. This opening earns marks because it does four things a written paragraph on the same topic would not need to do in the same way: (1) it PREVIEWS the exact structure and number of points ("three things... managing my time, talking to customers, and handling mistakes"), giving the listener a map before the detail arrives; (2) it marks pauses explicitly, showing the speaker has planned delivery, not just content; (3) each point is short, concrete and followed by one specific example, never a long compound sentence; (4) the close deliberately REPEATS the same three words used in the opening ("time management, communication, staying calm"), reinforcing the message for a listener who only heard it once. A written reflection on this delivery should name these choices using the correct metalanguage: signposting, pacing, pausing, repetition, register.
The middle-income trap of spoken delivery: overcorrecting
The most common failure mode is not "not planning enough" but planning a full written script and then reading it aloud, word for word, with the eyes down. This produces a talk that sounds like an essay, not a performance, and loses the audience within seconds even when the content is excellent. The fix is always the same: keep the planning rigour of writing, but convert the final product into cue cards and rehearsed delivery, not a page to be read.
- Reading a full script word for word
- This kills eye contact and natural rhythm, no matter how strong the content is. Fix: speak from cue cards with key words only.
- Skipping rehearsal
- Spoken delivery is a physical skill; it only improves with practice, not with more planning time on the page. Fix: rehearse aloud, timed, ideally in front of one other person, before any assessed talk or interview.
- Rushing under nerves
- Nervous speakers speed up, which makes them harder to follow and signals anxiety. Fix: deliberately slow the pace and treat pauses as a tool, not a failure.
- Memorising an interview answer so rigidly it sounds robotic
- A word-for-word script falls apart if the question is phrased differently than expected. Fix: prepare the KEY POINTS and one example per point, then speak them flexibly.
- Confusing "formal" with "stiff" in an interview register
- A formal register should still sound warm and natural, not like reciting a policy document; over-formal, jargon-heavy answers can sound evasive rather than professional.
- Match technique to command word
- If asked to "explain" how speaking differs from writing, name a specific feature (signposting, shorter sentences, repetition, delivery) AND the mechanism behind it (the listener cannot reread; a writer can revise), not just a list of adjectives like "spoken texts are more casual."
- Always quote the metalanguage
- Use "signposting", "register", "pace", "pausing", "cue cards" and "audience/purpose" precisely; a vague answer that says "he spoke well" without naming a technique will not reach the top band.
- For a stimulus/extract question, diagnose before you fix
- Identify the SPECIFIC problem in the extract (filler words, a run-on sentence, no signposting) with a short quotation, then explain the concrete fix, rather than giving generic advice like "practise more."
- For an extended response comparing spoken and written texts, argue a position
- Do not just list differences; state whether planning, structure or delivery is shared or distinct, and use one worked example of technique to prove the point.
Examples in context
Example 1. Same content, two deliveries. Imagine two students giving the same two-minute talk about a part-time job. The first reads a dense paragraph from a page without looking up, in a flat rush. The audience loses the thread within seconds. The second uses cue cards, opens with "Today I'll tell you the three things my job taught me", pauses between points, looks up at the room, and ends with a clear final line. Same content, very different result. The second student understood that spoken English is delivered, not just written.
Example 2. Interview versus application, same candidate. A candidate's written application can be redrafted several times until every sentence is polished; in the interview a week later, the SAME experience must be explained live, adapting to whatever the interviewer actually asks, with tone, pace and eye contact doing work the resume never had to do. Preparing key points and examples, rather than memorising the application word for word, lets the candidate handle both texts well.
Try this
- Plan a two-minute talk on a topic you know, written in short, spoken sentences with clear signposting, then say it aloud once before writing any of it down as cue cards.
- Make cue cards with key words only, then deliver the talk aloud and time it against your two-minute target.
- Practise one interview answer using a specific real example rather than a vague claim, then ask a friend for one piece of feedback on your pace and eye contact.
Exam-style questions
Questions in the style of NESA exam questions on this dot point, each with a worked answer. They are written by ExamExplained unless tagged "Past paper"; the year shows the paper a question is modelled on.
HSC 2023-style15 marksChoose ONE of the English Studies modules you have studied this year and explain why its skills will be valuable in your future life. In your response, make close reference to ONE text you have studied.Show worked answer →
A Section III extended response worth 15 marks, arguing the future value of a module with reference to one text. Achieving through English lets you draw on this dot point about planning and delivering spoken texts.
Open by naming the module and your text, then state your line: much real-world English is spoken, from presentations to job interviews, so learning to deliver clear spoken texts is essential. Develop with the text, explaining how it taught you to plan content like writing but deliver it like a performance, using short sentences, signposting and controlled pace, volume and eye contact.
Markers reward a clear sense of future value, well-chosen evidence, accurate metalanguage (register, signposting, pace, delivery), and language suited to the audience. Avoid summarising; argue why the skill lasts.
HSC 2021-style6 marksExplain how preparing for a job interview as a spoken text differs from writing a job application, with reference to TWO specific choices a speaker must make.Show worked answer →
A short reflection task of the kind the exam and portfolio use, asking you to compare spoken and written communication for the same purpose.
A strong answer shows that an interview is delivered live, so the speaker cannot redraft and the listener cannot reread. It names two choices: controlling pace and pausing so answers are clear under pressure, and giving specific spoken examples rather than a memorised script, keeping a formal but warm register. It contrasts this with the written application, which can be drafted, refined and proofread before sending.
Markers reward a clear grasp that speaking is delivered, not just written, and two concrete, justified speaker choices.
Practice questions
Original practice questions graded from foundation to exam level, each with a full worked solution. Try them before revealing the solution.
foundation2 marksName TWO features of spoken language that make it different from written language, other than volume.Show worked solution →
Any two of: shorter sentences (so a listener can follow without losing the thread); signposting words such as "first", "next" and "finally" that a reader would not need in the same way; deliberate repetition of key points, because a listener cannot scroll back to reread; a more natural, conversational rhythm rather than dense written phrasing; and non-verbal delivery choices (pace, pausing, eye contact) that a page cannot carry.
Marking spine: 1 mark for each correctly named feature (2 marks total). A feature copied straight from a written-text checklist (e.g. "correct spelling") does not count, since it is not specific to speech.
foundation3 marksExplain why signposting language ('first', 'my main point is', 'to finish') matters more in a spoken presentation than in an essay.Show worked solution →
A reader can reread a paragraph, flick back a page, or pause to check the structure of an essay; a listener cannot. Signposting language does the reader's own re-checking for them in real time, telling the audience exactly where the talk is up to and what is coming next, so they do not lose the thread of the argument as it goes past once, live.
Marking spine: identifies that listening is a one-pass, real-time process unlike reading (1), explains that signposting substitutes for the listener's inability to reread/check back (1), gives a plausible signpost example (1).
foundation3 marksA student's cue card for a class talk reads: 'Today I'll cover three things my part-time job taught me: time management, talking to customers, and handling mistakes.' Explain why this is a strong opening line for a spoken presentation.Show worked solution →
This opening tells the audience the exact structure and number of points before the talk begins, acting as a spoken table of contents. Because the listener cannot see a heading or scroll ahead, stating "three things" upfront lets them track progress mentally as the talk continues, and it also disciplines the speaker to stick to that structure rather than wandering off topic.
Marking spine: identifies the line previews structure/number of points (1), links this to the listener's inability to see/reread ahead (1), notes the benefit for the speaker (staying on track) (1).
core5 marksA short ORIGINAL extract from a student's rehearsal notes reads: 'So basically what happened was, like, I was working on this project and there were, um, quite a few problems that came up, and I guess what I learned was, you know, to plan ahead more, which I think is pretty important for like any job really.' Identify TWO delivery or language problems in this extract and explain how the speaker should fix each one for a formal spoken presentation.Show worked solution →
Problem 1: filler words and hedging ('like', 'um', 'you know', 'I guess', 'basically'). These weaken the speaker's authority and make the point sound tentative rather than considered. Fix: rehearse the point as a clean, complete sentence in advance (e.g. "This project taught me to plan ahead, a skill valuable in any job") and replace filler with a deliberate pause, which reads as confidence rather than hesitation.
Problem 2: overlong, run-on sentence structure ('so basically what happened was... which I think is pretty important for like any job really'). A single sentence stacking several clauses is hard for a listener to follow because there is no natural pause to process each idea. Fix: break the idea into two or three short spoken sentences with a signpost, e.g. "A problem came up on my project. I learned to plan ahead. That skill matters in any job."
Marking spine: 2 marks for correctly identifying each problem with specific evidence quoted from the extract (4 total), 1 mark reserved across both for a workable, spoken-appropriate fix (not just "use better words").
core6 marksExplain TWO reasons a job interview should be prepared for differently from a written job application, even though both address the same employer and the same role.Show worked solution →
A 6-mark "explain" needs two distinct reasons, each linked to a mechanism (why the spoken/written difference matters), not just a restatement that "one is spoken and one is written."
Reason 1: an interview cannot be redrafted (about 3 marks). A written application can be drafted, proofread and revised before it is sent, so every sentence can be polished; an interview answer is produced live, in real time, with no chance to delete a weak sentence once it is out. This means the candidate should prepare flexible content (key examples and structure) to speak from, rather than a memorised script, so that if a question is phrased unexpectedly they can still adapt on the spot instead of freezing.
Reason 2: an interview carries non-verbal and vocal signals a written page cannot (about 3 marks). Tone, pace, pausing, eye contact and posture all communicate confidence and interest in an interview in ways a resume or cover letter cannot carry at all; a candidate who prepares only content, and not delivery (a warm but formal tone, steady pace, eye contact), can undersell strong written credentials by seeming flat or rushed in person.
Marking spine: two distinct reasons (2 marks each for the reason plus 1 mark each for a specific consequence/example), not two versions of the same point.
exam8 marks'A spoken text is planned like an essay but delivered like a performance.' To what extent do you agree? In your response, refer to the DEMANDS of planning, structuring and delivering a presentation OR interview for a nominated audience and purpose.Show worked solution →
An 8-mark "to what extent" response needs a clear position (largely agree, with a qualification), developed across planning, structure and delivery, with a worked example of technique, not just a list of tips.
- Position
- Largely agree: the CONTENT of a spoken text is planned with the same rigour as a written text (a clear purpose, an audience, two to three developed points), but its STRUCTURE and DELIVERY genuinely require performance skills that essay-writing does not, because a listener processes the text once, live, and cannot reread it.
- Planning is essay-like
- Both a spoken presentation and a written essay begin with the same questions: who is the audience, what is the purpose, and what two or three points will best serve that purpose. A speaker who skips this planning and "just talks" typically rambles, just as a writer who skips planning produces an unfocused essay; the discipline of selecting content and a clear line of argument is shared.
- Structure and delivery are performance-specific
- Because the audience cannot reread or pause the speaker, a spoken text needs explicit signposting ("first", "my main point is", "to finish") that would feel clunky in a polished essay, shorter sentences than written prose would use, and deliberate repetition of the key message. Delivery adds a layer writing does not have at all: pace (slowing under nerves rather than rushing), pausing (a tool, not a failure), volume, eye contact and the choice to speak from cue cards rather than read a script, so the speaker can adapt to the room in real time. A worked example: a candidate opens with "Today I'll cover three things my volunteering taught me," delivers each point with one concrete example and a brief pause before moving on, and closes by restating the message; the SAME content read flatly from a full script, eyes down, would communicate far less despite identical wording.
- Qualification
- The performance element does not replace planning; a beautifully delivered talk with no clear structure or evidence still fails its purpose, just as excellent handwriting does not rescue a poorly argued essay. The claim is best stated as: planning is shared with writing, but structure and delivery add a genuinely separate, performance-based skill set that must also be rehearsed.
Marking spine: a clear, sustained position (2), planning-is-shared argument with reasoning (2), structure/delivery-is-different argument with a specific worked example of technique (3), a qualification that shows nuance rather than one-sided agreement (1). An answer that only lists delivery tips with no argued position stays mid-band.