The entry is the supporting argument
Outside of Festival of Media, the entry is there to support your case video

Open any entry portal this year and the blank page doesn't stay blank for long. A tool will happily give you three fluent paragraphs about your campaign in under a minute. Structured, grammatical, reading exactly like every other agency's three fluent paragraphs about their campaign. That used to be the hard part. It isn't anymore.
Fluent prose is free now. Everyone entering this show has something that writes clean sentences on command. The entries that still lose aren't losing on sentence quality. They're losing on the thing a language model can't hand you: judgment about what was actually worth writing about in the first place.
That's an uncomfortable shift if you spent years getting good at the writing itself. The writing was never nothing. A strategist who could turn a messy campaign into a clean, well-paced case study earned that the hard way. But a skill that used to be scarce and is now available to everyone stops being the thing that separates a winner from a loser, whether or not that feels fair.
What a jury was always actually scoring
Start with what a juror is actually doing when they get to you. Imagine reaching your case study video after sixty others in a single day, one film after another after another, slowly losing your mind. By the time your two minutes come up they are fried, impatient, and forming an impression in the first ten seconds whether they mean to or not. In a lot of shows the written entry is not even the first thing they see. It's what they turn to when they have a further question, or when the room is debating whether to shortlist you and someone wants to check a detail before arguing for or against. Most of the time, that's its job: the supporting document behind the film, consulted when it matters, not read cover to cover for the prose.
Which is exactly why you build it alongside the case video script, not after. The video and the entry are one argument told twice, at different depths. If the written entry says something the film doesn't support, or answers a question the film never raised, the two come apart the moment a juror checks one against the other. Build them together and everything ties: the film makes the case, the entry backs it when someone goes looking.
None of that means the writing gets to be sloppy. It means it isn't being read as writing. A juror who has watched sixty films and is now scanning your entry for one answer isn't grading prose. Underneath whatever your entry actually says, they're checking one thing: did this team see something nobody else saw, and did they build a real case for why it mattered.
That question doesn't get easier just because the writing got smoother. If anything it gets harder, because when every entry reads equally fluent, fluency stops signaling anything. A tired juror scanning a stack of equally polished paragraphs is hunting for the one that still surprises them, not the one with the cleanest sentence in paragraph two.
So here's the reframe. Underneath its prose, the entry is an argument. Not a report on what happened. A case, built for a specific skeptical reader, that a specific claim is true and matters. Judge it as a report and it only has to be accurate. Judge it as an argument and it needs a claim worth making, evidence that holds, and a reason the reader should care. Most entries that read fluent and forgettable are reports wearing an argument's clothes.
The four parts, in the order a juror actually reads them
A juror doesn't read your entry the way you wrote it. They read it the way anyone reads a case being made to them, checking each part against the one before. Four parts, in that order.
The claim. What, specifically, is this entry asserting. "We ran a successful campaign" is not a claim, it's a category. A claim is specific enough to be wrong: this campaign solved a problem nobody else in the category had named, or found an audience behavior nobody else had used. If it could describe half the entries in the room, it's not a claim yet.
The mechanism. Why the claim holds. This is the part most entries skip or blur, because it means actually explaining the causal line from the insight to what got built to why it worked, instead of describing all three and hoping the reader connects them. A juror who can't trace that line in a sentence or two starts doubting the team could either.
The proof. The checkable evidence that the mechanism actually happened and actually worked. Numbers, specifics, named details a juror could verify if they wanted to. This is a whole discipline on its own, and it gets its own piece next week: what makes a results section survive a skeptical read instead of just looking impressive on the first pass.
The so-what. Why any of this matters beyond your own satisfaction. To the category, to the client's business, to the industry watching. This is what turns a strong case study into a memorable one, and it's usually the first thing cut when an entry runs long, which is exactly backward.
Skip the mechanism and the claim reads as a coincidence. Skip the so-what and the proof reads as trivia. All four have to hold, in this order, to survive a tired reader's attention.
Most fluent-but-forgettable entries die quietly at the claim, long before a juror gets near the numbers. The prose is smooth precisely because there was never a sharp, specific claim underneath it to make smooth prose hard. Vague claims are easy to write fluently. Specific ones aren't, and that difficulty is exactly the signal a juror is trained to notice.
So where does a tool actually help
None of those four parts are writing tasks the way a first draft is. They're judgment calls: what's the real claim, does the mechanism connect, is the proof specific enough, does the so-what land. A tool that drafts fluent paragraphs doesn't make any of those calls for you, and pretending it does is exactly how an entry ends up reading like everyone else's this cycle.
The honest use of a tool here is the one "July's Mistake, October's Emergency" already made the case for: catching what a tired writer missed, not replacing the argument. Scoring a draft against the six dimensions a real jury reads for, insight, strategic clarity, the idea, execution, results evidence, storytelling, is a mistake-catching exercise. You run it after the argument already exists. It can't invent the thing nobody else saw. It can tell you, honestly, whether your case for it holds up once it's written down.
That's a different job from the one this piece is about. This piece is about building the argument before a word of the draft exists: settling the claim, the mechanism, the proof, and the so-what, in that order, so whatever gets drafted afterward, by you or with a tool's help, has an actual case underneath it instead of three fluent paragraphs standing in for one.
One thing to do differently this week
Before you draft the next entry, write the four parts as four separate sentences. Not prose yet. One sentence for the claim. One for the mechanism. One for the proof, even if it's a placeholder for a number you don't have yet. One for the so-what. If any of the four is hard to write, that's the actual problem with the entry, and no amount of drafting, by a person or a tool, fixes a gap at that level.
An entry with four solid sentences underneath it can survive being written badly. An entry with four fluent paragraphs and no real claim underneath cannot survive being read carefully.
Shortlist's Jury Mode runs that same six-dimension read on a finished draft, months before a real juror sees it. It catches whether the case holds. It was never going to be the thing that finds the case worth making.
Once the claim, mechanism, and so-what are settled, the proof is where most entries fall apart under a skeptical read. That's next week.
Your final edit, brought forward as fast as possible.
30+ shows. Unlimited entries. The judgment stays yours.
Start free trial