English situational writing and functional writing examinations test whether a student can make language do a practical job for a real reader. An email, letter, report, article, speech, proposal or notice is not successful merely because it contains the expected layout. The response must identify the audience, purpose, required content, source facts and desired action, then organise those elements so the reader can understand and use them.
How to write situational writing, functional writing, emails, letters, reports and speeches in an English exam therefore begins with a communication contract. Students need to distinguish fact from proposal, required point from optional detail, formal relationship from artificial stiffness, persuasion from invented evidence, and genre convention from empty template. The strongest response sounds appropriate because its decisions fit the situation.
This world-facing handbook continues the How English Examination Works series. It builds on the question-decoding handbook, the exam-writing handbook and the source-transformation route. Its distinct ownership is practical communication: audience, purpose, context, source fidelity, tone, organisation and action.
The 50-second quick read
ROLE → READER → PURPOSE → FACTS → REQUIRED POINTS → ACTION → TONE → VERIFY. Who are you? Who will read this? What must the reader know, think or do? Which facts are supplied and cannot be changed? Which points are compulsory? What action or outcome is requested? Choose tone and structure from those answers. Then verify that every required point survived.
Part I. Functional writing is communication engineering
1. Genre is not the first question
Before deciding how an email or report looks, identify what the response must accomplish.
Purpose determines which conventions matter.
2. Audience changes explanation
A school principal, close friend, event participant and general public possess different background knowledge and expectations.
Write what this reader needs, not everything you know.
3. Role changes authority
A student representative can recommend and report observations but should not invent approval they do not possess.
The writer’s position constrains claims.
4. Source facts are protected
Dates, costs, locations, restrictions and supplied outcomes should remain accurate when transformed.
Fluent invention is still inaccurate if it changes the source.
5. Proposals must be labelled as proposals
We could introduce a booking system is different from a booking system has been approved.
Modal verbs can protect factual integrity.
6. Required points need visible coverage
A response can be elegant yet incomplete if one compulsory bullet point disappears.
Map requirements before drafting.
7. Tone is relational
Formal does not mean pompous; friendly does not mean careless. Tone expresses the relationship between writer, reader and purpose.
Choose language the situation can support.
8. Organisation follows reader action
If the reader must decide, put the decision and reasons where they can be found. If the reader must attend, make date, place and instructions clear.
Structure should reduce reader work.
9. Persuasion needs mechanisms
A proposal becomes convincing when the reader can see how it addresses the problem and what trade-offs remain.
Invented statistics are not necessary.
10. Courtesy is functional
Please, thank you and respectful acknowledgement can support cooperation, but excessive politeness can bury the request.
The reader should still know what is being asked.
11. Formatting supports navigation
Headings, paragraphs and lists can help in genres where they are appropriate, subject to the examination’s permitted conventions.
Formatting is useful when it makes information easier to recover.
12. The ending should close the transaction
A practical response often needs a request, recommendation, next step, invitation or concise conclusion.
Do not let the piece simply stop after the final fact.
Part II. Original source packet
13. The scenario
A school is planning a Saturday learning festival. Students, families and community guests will visit classrooms, demonstrations and performances. After last year’s event, visitors reported three problems: they found rooms difficult to locate, some performances started while audiences were still moving between venues, and several displays had nobody available to explain the work.
The planning team is considering numbered venue zones, a one-page visitor map, ten-minute movement intervals between major performances, and a student rota for display explanations. Some student groups are concerned that fixed rota duties will reduce the time they can spend visiting other exhibits.
14. Task A: email the event coordinator
Prompt: As a student representative, write an email recommending how the festival should address the three visitor problems. Explain one disadvantage of your proposal and how it could be reduced.
15. Decode Task A
Role: student representative. Reader: event coordinator. Purpose: recommend. Required content: navigation, movement timing, display explanation, one disadvantage and mitigation. Protected facts: the reported problems and proposed mechanisms. Permission: reason about and combine proposals without pretending they are already approved.
16. Model email body
I recommend organising the festival around numbered venue zones, a simple visitor map and visible movement intervals between major performances. These changes address the three problems reported after last year’s event without requiring visitors to learn the school’s internal room names.
For navigation, the same zone numbers should appear on the map, corridor signs and room entrances. Visitors could then follow one consistent system from arrival to destination. For timing, a ten-minute movement interval between major performances would make the transfer period part of the published programme rather than leaving audiences to move while the next event is beginning.
Displays need a different solution. Each participating group could create a rota so that at least one student familiar with the project is available during agreed periods. A short written explanation could remain beside the display when the student temporarily steps away.
The main disadvantage is that fixed duties would reduce students’ freedom to visit other exhibits. To limit this, rota periods could be kept short, published early and exchanged between group members before the final schedule is confirmed.
I suggest trialling the zone map and rota with one section of the festival plan before the programme is finalised. This would allow the team to identify confusing routes or unrealistic duty periods while changes are still possible.
17. Why the email works
The response turns each source problem into a mechanism, distinguishes recommendation from approval and acknowledges the student groups’ concern. It does not invent visitor percentages, budgets or guaranteed outcomes.
18. Task B: write a notice for visitors
Prompt: Using the same scenario, write a short visitor notice explaining how to find venues and move between major performances.
19. Model notice content
Finding Your Way at the Learning Festival
Festival venues are organised into numbered zones. Please use the visitor map and follow the matching zone signs displayed along the corridors and outside participating rooms.
Major performances include a ten-minute movement interval. When one performance ends, use this interval to travel to your next venue before the published start time.
If you are unsure where to go, check the nearest zone sign against your map before continuing. Please avoid waiting in doorways while other visitors are entering or leaving rooms.
20. Same facts, different communication
The email explains and recommends because the coordinator must decide. The notice gives direct usable instructions because visitors must navigate. Genre transformation changes selection and tone while the underlying facts remain stable.