Project work can create strong conditions for CLIL. Students have a reason to read, discuss, negotiate and present while solving a subject problem. It can also become confusing if the final product is clear but the language demands and assessment are left implicit.
CLIL Notebook can draft the structure of a project: parallel briefs, content objectives, language objectives, vocabulary, discussion questions, review checks and criteria. The teacher then turns those pieces into a realistic sequence for the available time and class.
Plan backwards from the final evidence
Start with what students must produce and what that product should demonstrate. Then identify the language needed to complete and explain it. A project on UML and Java aggregation, for example, may require students to name relationships, justify a design, compare options and document code.
The stages should prepare students for that evidence. Vocabulary and a shared model belong early. Group briefs need comparable expectations. Discussion questions should prompt the reasoning the teacher wants to hear. Assessment criteria should make both technical work and communication visible without confusing the two.
Classroom example: UML and aggregation
Laura Rosati used a three-session sequence with 19 B2 students. On 4 November, the class began with vocabulary from the application's Language Objectives and built a collective UML diagram for a warehouse management example. Students then completed a consolidation task.
On 12 November, groups worked on Hotel Management, Music Quiz, Sports League Manager, Fitness Tracker and Video Game Inventory. Each brief required a UML diagram, Java classes using aggregation and code documentation. Students kept the application-generated brief visible while they worked on iPads.
Discussion questions asked how UML clarified object relationships and why aggregation mattered in managing data. These questions prompted technical talk in English. On 13 November, students completed the projects and were assessed with a revised rubric.
Assessment is where teacher judgement becomes visible
The application produced draft criteria, but the teacher changed the weighting. Collaboration and participation received 4 of the 10 points, twice the value of any other single criterion. The choice reflected what she wanted students to do during the project, not a default generated by the system.
A draft rubric can save time and reveal missing areas. It should never determine the value of each criterion automatically. The weighting must match the curriculum, the age group, the stage of learning and the evidence students can reasonably produce.
A reusable planning pattern
- Define the final subject product and the decisions students must make.
- List the language functions needed to complete and explain the work.
- Model one example with the whole class.
- Create parallel group briefs with the same level of demand.
- Use questions that require technical explanation, not only recall.
- Edit the rubric so its weighting reflects the real purpose of the project.
In the UML case, the teacher organised generated briefs, a common model, discussion questions and a revised rubric across three sessions. Students then had to justify design choices rather than repeat definitions.