Writing a useful event review
B1.2 · Turn scattered observations into a short report that explains a problem and supports an improvement.
B1 reporting of events, reasons, simple comparison and recommendations.
Model
La primera jornada de reparación del barrio permitió arreglar varios objetos, pero también mostró un problema de organización. Llegaron veinticuatro personas y solo había dos mesas de trabajo. Quienes traían una lámpara o un aparato pequeño tuvieron que esperar mientras se revisaban objetos más grandes.
La espera no significa que los voluntarios trabajaran mal. Cada reparación necesitaba un tiempo distinto y no se había pedido información sobre los objetos antes de la jornada. Por eso el grupo no pudo preparar materiales ni distribuir bien los turnos. Algunas personas se marcharon sin preguntar cuándo podrían volver.
Para la próxima sesión propongo recoger una descripción breve de cada objeto al inscribirse. Así podremos separar las reparaciones sencillas de las que requieren más tiempo y explicar mejor la espera. También conviene tener una persona en la entrada que informe sobre los turnos. Estas medidas no aseguran que todo se repare, pero pueden ayudar a organizar el trabajo y evitar que alguien espere sin información.
La espera no significa que los voluntarios trabajaran mal
· The report avoids an unsupported explanation of a problem.no se había pedido información sobre los objetos
· A cause relevant to organisation connects observations to a recommendation.Estas medidas no aseguran que todo se repare
· The conclusion limits what the recommendation can promise.
Task
Write a brief report for the team planning the next language exchange. Reorganise these notes: 18 people attended; the meeting ran from 17:00 to 18:30; three people said afterwards they could not hear their partner; those three sat beside the open entrance; nobody measured noise levels; the room has a quiet corner with six seats; the organiser’s favourite snack was apple cake; participants asked for more time in pairs; the first 40 minutes were introductions to the whole group, followed by 35 minutes in pairs and 15 minutes of closing discussion. Review a teammate’s conclusion, “The event failed because every participant disliked the room.” Explain what the notes support, what they do not support and propose two practical improvements with reasons. Do not invent a satisfaction survey. This is an invented case. Write in Spanish. The word range is a guide, not an automatic pass/fail rule. Use the criteria for teacher assessment or self-assessment; there is no automatic mark.
140–200 words
Planning
- Which observations support a problem, and how far can you generalise them?
- How does the time distribution relate to the request from participants?
- Which two changes could address the observations without promising a measured effect?
Criteria
- Organise the event information around a useful review for the planning team.
A report should help a decision rather than reproduce unordered notes.
- Separate observations, possible explanations and unsupported generalisations.
The strength of the conclusion must match the evidence.
- Recommend two practical changes, each linked to a relevant observation.
Recommendations require reasons, not just personal preferences.
- Use paragraphs and connectors to distinguish results, limits and recommendations in understandable Spanish.
A reader needs to follow the reasoning and recognise who reported each issue.
Review
Keep your first draft. For each criterion, quote evidence from your own text and mark evidenced, partial or not yet evidenced. Revise a weak passage and explain how the change helps this reader. If all four are evidenced, justify a specific factual or language check. Compare meaning with the guide; different wording is welcome, and matching the example does not by itself prove success.