Final Scenario

The complete, playtest-revised scenario packet — runnable by a Keeper who wasn't in the room for any of the studios.

Due: 21 May 2027 · Weight: 40%

The brief

Submit the finished, playtested scenario: everything a Keeper who has never spoken to you would need to run it.

This is the semester’s whole pipeline arriving in one place: premise, truth and antagonist, structure, scenes, clue web, puzzles, checks, NPCs, atmosphere, and — critically — the revisions your Assessment 3 playtest surfaced. A scenario that reads well but ignores what the playtest found broken is not a finished scenario by this course’s standard.

What you submit

The complete packet: scenario text organised by scene, clue map, NPC sheets, and any player handouts, assembled so someone else could pick it up and run it without you in the room. Include a short note naming at least one specific change you made because of your playtest.

For a worked example of what a finished packet feels like at the table, see the Play demo scenario — or go straight to building your own from this submission.

The spec

The brief poses the problem and leaves room for a response. The spec is the fixed part: what a marker checks. Some lines can be checked mechanically; the rest call for judgement.

the packet is complete — scenario text, clue map, NPC sheets and any handouts, in one place
a reader who wasn't in your studios could run at least one scene from the page alone
the draft names at least one specific change made in response to your playtest

How it is marked

Judged as a whole against whether an independent Keeper could run it cold — whether the packet answers "what happens in this scene" for every scene, whether the clue web is actually redundant in play, and whether the final draft visibly responds to what the Assessment 3 playtest revealed, rather than ignoring it.