The Joint Recruitment Examination (JRE) is the gateway to the Administrative Officer (AO) and Executive Officer (EO) grades. The full paper runs three hours and carries two essay questions, one in Chinese and one in English. The English question is often where candidates are separated. It does not test how many policies you have memorised. Instead it hands you a thick set of reference materials and checks whether you can read through them under time pressure, analyse them, and write a recommendation that takes a clear, defensible stand. Fewer than 20% of candidates pass the JRE and are invited to interview, and a scattered essay with a wishy-washy recommendation is a common reason for being screened out.
This guide focuses on the English paper: what it actually tests, what the fictional-city case study tends to look like, how to digest a large volume of reference material, the structure a recommendation should follow, how to weigh options, and the practical points on language and time. Every case example below is original and illustrative only; none reproduces any real examination question.
What the English paper really tests
First, the framing. The JRE English question is not a language test, and it is not a comprehension exercise with blanks to fill. It simulates a day in the life of a civil servant: your boss hands you an issue, attaches a batch of background material, and asks you to analyse the situation, compare workable options, and give a clear recommendation on what should be done. In other words, it tests policy thinking and English writing at the same time.
Marking broadly runs along three axes:
Analysis — whether you have identified the core problem, backed your points with the materials, and seen the trade-offs between options.
Judgement — whether you end with a clear, feasible, well-reasoned recommendation rather than lobbing the choice back to the reader.
Writing — whether the structure is clear, the English is accurate and professional, and you can make complex information readable under pressure.
A common misconception is that flowery English scores better. The opposite is true. Markers want clear, precise, professional official English. A loosely organised answer dressed up in grand vocabulary is worth far less than a tightly structured one that commits to a decision.
What the fictional-city case study looks like
The English question is usually set in a fictional city that closely resembles Hong Kong: densely populated, economically developed, with a government that has to balance competing interests under limited resources. The city is fictional on purpose. It stops you leaning on memorised policy and forces you to think through the material in front of you. You will be asked to analyse a social problem or policy controversy and recommend one option out of several.
Here is an original example, purely to show the shape of the task. Suppose the fictional city has chronic congestion in its central business district and the government is considering electronic road pricing. The pack might include traffic-flow statistics, air-quality data, objections from the business chamber, a letter of support from a green group, a news clipping on how a neighbouring city handled it, and an internal government assessment. Your job is to synthesise these conflicting sources, analyse the pros and cons, and advise the government whether to act, and if so how.
Common issue types (illustrative):
Transport and road pricing, public housing supply, public health (such as tobacco control or disease response), digital policy (such as data protection or the use of AI), the environment and waste charging, and an ageing population and welfare allocation. These echo real Hong Kong tensions but arrive wrapped in a fictional city. Knowing the basic tension in each of these families saves precious time on the day.
How to digest a large volume of material
Many candidates realise on their first attempt that there is more material than they can read in full. That is by design. The paper is testing your ability to filter and prioritise information, not to read every clipping word for word. The first-hand lesson is blunt: do not read dutifully from the first page to the last, or you will run out of time before you finish.
The practical move is to spend two or three minutes scanning the headings and sources of every document and, in your head or on scrap paper, tag each one: is this background data, a stakeholder position, or a policy option? Then group the material by stance — those for, those against, and the neutral data. Reading same-stance sources together instantly surfaces the argument-and-counterargument pairs.
Four buckets for the material:
1. Background — the statistics and facts that define the scale of the problem, used to set up your opening.
2. Stakeholder views — the concerns of businesses, residents, green groups and professional bodies, the basis for weighing impact.
3. Policy documents — internal assessments, legal limits and fiscal constraints that decide which options are feasible.
4. External references — clippings on what other cities did, borrowed to support or to caution.
One key habit: as you read, circle any quotable figure or phrase and note which document it came from. When you write, every point ideally ties back to a specific piece of evidence. "According to the traffic data, peak-hour speeds have fallen to ten kilometres per hour" is always more persuasive than a vague "traffic is bad".
The structure a recommendation should follow
A good recommendation should read like an internal document you could hand straight to your boss. It needs no essay-style flourish at the top; it should get to the point and move in clear layers. The structure below is dependable:
Open: define the problem and the objective — a sentence or two on what the issue is and what the government is trying to achieve (for example, "to ease congestion while limiting the hit to shopkeepers"). A clear objective gives you the yardstick for everything that follows.
Middle: analyse the options — take each option in turn, set out its pros and cons and its impact on each stakeholder, and back it with the material.
Recommend: commit clearly — state which option you choose, why, and how you answer the main objections to it.
Close: implementation and risk — sketch the steps, timing or mitigating measures, showing you have thought about execution.
Use clear paragraph signposting or bullet points to separate the parts so the marker can see your logic at a glance. Avoid folding analysis, opinion and recommendation into one giant block, which is the surest way to lose the reader, and the marks.
How to weigh the options
Weighing is not a single line of good and a single line of bad. What actually scores is comparing every option against the same set of criteria — effectiveness, cost, impact on different stakeholders, feasibility and risk. When all options are measured on one ruler, the winner emerges naturally and your recommendation has a reason to exist.
Take the road-pricing example again. The charge would ease congestion significantly and raise revenue, but hits small CBD shops and lower-income drivers harder. "Do nothing" is gentlest on business but fails to answer worsening air and congestion. "Expand public transport" faces little political resistance but is slow to bite and costly. Put all three into one comparison and you will find none is perfect, and that is exactly the point.
A common mistake: in an effort to look objective, candidates write every option as a 50-50 draw and then flinch from a verdict at the end. Judgement is precisely what the marker is looking for. Acknowledging the trade-off, admitting your chosen option has a cost, and then explaining why it is still the best on balance reads as more mature, and scores better, than pretending a perfect answer exists.
Language and time management
On language, aim for clear, precise, professional English rather than fireworks. Favour the active voice and explicit subjects: "The government should introduce..." beats the evasive "It could perhaps be considered that...". The recommendation section especially must be decisive: use phrasing like "I recommend" or "The preferred option is", and resist diluting your stance with a string of might, maybe and perhaps. When you proofread, watch subject-verb agreement, tense and connectives, as these small slips do the most damage to a professional impression.
On timing, do not simply split three hours down the middle. For the English question, including reading, budget roughly the first third to reading the material, sorting it and outlining, the bulk of the middle to writing, and a few minutes at the end to proofread. The first-hand lesson: cut corners on the reading-and-planning phase and the writing turns messy. It is better to go slower up front and get the structure clear, because the writing then flows faster. Also balance the two questions, one Chinese and one English, so you do not sink so much time into one that the other runs short.
Three checks before you stop:
— Is my recommendation clear enough? After reading it, does the reader know exactly what I am telling the government to do?
— Does each main point tie back to a piece of evidence from the material?
— Have I answered the strongest objection, rather than only the side that suits me?
To prepare more systematically, start with the JRE full exam guide to grasp the overall flow and marking, then pair it with the JRE Chinese paper guide to practise pacing both questions. To drill case-study analysis and recommendation structure specifically, work through our study section point by point, or download the JREHK app to rehearse with realistic scenario questions.
About the examples in this article
Every case-study scenario here, including the fictional city's road-pricing issue, and every material type is original work by the JREHK editorial team, used only to illustrate the analytical approach and recommendation structure. Nothing reproduces any real examination question or official model answer. Actual exam questions, format and marking criteria follow the official announcements.
