IB Film SL common mistakes
IB Film SL · Understand the traps and how to avoid them.
Writing a close-reading sequence analysis as a shot-by-shot inventory that describes what is visible in each shot ("a medium shot of a woman; cut to a close-up of a phone") without ever stating what the formal choice produces in meaning or affect.
Candidates treat textual analysis as a test of observation and vocabulary, so they list techniques to prove they noticed them. Under time pressure, description is the safest thing to write, so the response fills with it and the interpretive claim is squeezed out or left implicit.
What to do instead
Adopt a claim-first structure: open the paragraph with a sentence asserting what the sequence does (for example how the editing pattern constructs the protagonist's disorientation), then cite only the two or three formal details that support that claim, and close by naming the effect on the spectator. Delete any shot description that does not serve a stated claim.
Naming a technique without the precise film-language term, or using terms loosely and interchangeably - writing "the camera moves in", "fast cutting", "the music gets louder" instead of specifying a dolly-in or zoom, acceleration of cutting rhythm against an average shot length, or a crescendo in the non-diegetic score.
Candidates often know the concept but not the accepted vocabulary, or they worry that using technical terms incorrectly will cost more marks than staying vague. Vague description feels safer, so precision is never practised.
What to do instead
Build a personal glossary organised by track (cinematography, editing, sound, mise-en-scène, performance) with a one-line definition and a filmed example for each term. Before the exam, practise converting three descriptive sentences into precise ones. In the essay, pair every term with its function so the vocabulary is doing analytic work rather than decorating.
Structuring the textual analysis around the film's plot or chronological story order, retelling what happens in the sequence and attaching analysis as an afterthought, rather than organising by formal argument.
Narrative is the most familiar way into a film, and recounting it feels like demonstrating knowledge. Candidates also fear that skipping plot summary will make the response look thin to an examiner who has not seen the film.
What to do instead
Plan the essay around two or three analytical claims, each becoming a paragraph, and use plot only as the minimum context needed to locate a moment. A useful test: if a sentence could appear in a plot synopsis, cut it or convert it into an observation about how the story is told.
In the comparative study, comparing two films only by surface content (both are about a family, both have a sad ending) while ignoring the cultural, industrial, historical, or theoretical contexts that make the comparison meaningful, and citing no researched sources.
Students default to thematic similarity because it is easy to spot, and they may not realise that the comparative study is assessed on researched context and the use of an organising framework, not just on finding parallels.
What to do instead
Choose an explicit comparative framework before selecting evidence - for example auteur theory, genre convention, national cinema and funding context, or spectatorship and reception - and let every point of comparison run through it. Keep a research log with sources for each contextual claim, and in the essay attribute context to a source rather than asserting it.
Treating the two compared films as interchangeable, so the response alternates between them without ever putting them in genuine dialogue - no point where film A is shown to do something film B refuses, complicates, or answers differently.
The comparative essay is often written film by film because that is how notes were taken. Candidates also fear that direct contrast will look like favouritism or oversimplification, so they keep the two halves politely separate.
What to do instead
Write in paired paragraphs: state a shared concern, show how each film handles it, then state what the difference reveals about context or theory. Draft a comparison grid with the framework's categories as rows and the two films as columns, and build paragraphs from rows rather than from films.
Submitting production work whose creative intention is written after the film is finished as a retrospective justification, so the stated intention does not match what the finished piece actually does and the reflective process reads as a description of tasks completed.
Production schedules slip and reflection gets left until the end, when the only available material is memory. Students also believe the intention statement must sound impressive, so they write ambitions that the footage cannot support.
What to do instead
Write the creative intention before shooting as a short, testable statement of intended audience response, and keep a dated production journal with decisions, problems, and revisions. In the reflection, quote the original intention and evaluate honestly where the film met, missed, or changed it, using specific evidence from the edit.
Crediting production roles vaguely ("we all did a bit of everything", "I helped with the edit") so the candidate's individual creative and technical contribution cannot be identified.
Genuine collaboration is messy and shared, and candidates worry that claiming specific authorship looks arrogant or unfair to teammates. Group harmony is prioritised over clear documentation.
What to do instead
Define named roles at the planning stage with written responsibilities, and log who did what at each stage, including the candidate's own decisions and the reasoning behind them. In the portfolio, describe your contribution in terms of specific choices made and their effect on the finished film, while crediting collaborators accurately.
Producing technically weak work - inconsistent sound levels, uncontrolled exposure, shaky or unmotivated camera movement, abrupt cuts - and then treating the flaws as stylistic choices in the reflection rather than addressing them.
Candidates invest their energy in story and performance and underestimate how much a viewer's reading is shaped by basic craft. When time runs out, technical problems are rationalised rather than solved.
What to do instead
Build a pre-shoot checklist covering sound recording with a separate microphone and monitored levels, exposure and white balance set per location, and a locked-off or deliberately motivated camera. Do a test shoot and a rough-cut review against the checklist, and fix problems in the edit before writing the reflection.
In the collaborative project, treating planning as a formality - no research question, no schedule, no defined division of labour - so the project drifts, deadlines collide, and the final research presentation cannot explain the inquiry that drove it.
Students often begin filming or researching immediately because planning feels like delay, and group members avoid early disagreement about roles. The absence of a plan only becomes visible when the deadline arrives.
What to do instead
Produce a one-page project charter at the start: research question, intended outcome, milestone dates, named responsibilities, and a decision-making process for disagreements. Review it at each milestone and record changes with reasons, so the presentation can trace how the inquiry evolved.
Using film terminology inaccurately or inconsistently across the portfolio and presentation - conflating diegetic and non-diegetic sound, misusing mise-en-scène to mean only set design, or calling any repeated image a motif without showing its function.
Terminology is often learned from casual film discussion rather than from precise study, and candidates reuse impressive-sounding words without checking definitions. Errors survive because no one audits the vocabulary before submission.
What to do instead
Do a terminology audit of your own drafts: highlight every technical term and verify it against a reliable definition, correcting or cutting any term you cannot define in one sentence. In the presentation, define contested terms briefly the first time you use them and tie each to a specific example from your own work.