Reading Long Novels: What the RSC's Middlemarch Adaptation Teaches Student Writers
Reading long novels like Middlemarch becomes manageable when you borrow an adapter's discipline: decide what you are tracking before you start. The RSC's staging, which the Guardian review says must handle a roughly 900-page novel juggling multiple storylines across three years, shows the problem plainly. No staging can carry every thread, so read with tools instead of willpower. This plan gives you four: anchor cards from the review, a storyline ledger, a checkpoint log for one character's trajectory, and a revision audit for your own competition draft.
Stage one: turn the review into anchor cards before you open the book
The Guardian's review of the RSC's Middlemarch at the Swan Theatre asks a question worth stealing: how do you adapt a novel of roughly 900 pages for the stage without flattening its moral, philosophical and psychological complexities? The review describes a book that juggles multiple storylines and perspectives, weaves local life into the socio-political backdrops of its age, and follows its characters' trajectories with such detail that they become hard to replicate in another form. That is the scale that can make a long classic feel daunting before chapter one. Our suggested method flips the problem: instead of committing to finish and hoping willpower holds, borrow an adapter's discipline and decide what you are tracking before you start. The review's confirmed details become your tracking targets, written as anchor cards.
Our suggested exercise: before chapter one, write three anchor cards using only details the review confirms. Card one: the RSC staging includes George Eliot herself as a character. Card two: the review's title says the production hurtles from deathbed panto to jolting marital tragedy. Card three: the novel spans three years in a fictional Midlands town. Under each card, write one open question, such as where a novelist-as-character might sit in the story or when the three years begin. Then read the opening chapters as a search task, hunting for passages that could attach to each card. To evaluate: after your first ten chapters, each card should hold at least one attached passage or a note on why nothing fits yet; a still-empty card means the question needs rewriting, not that the book has beaten you.
Stage two: keep a storyline ledger so no thread goes quiet unnoticed
The review's description of Middlemarch is a map of why long classics stall readers: a roughly 900-page novel that juggles multiple storylines and perspectives, weaves local life into the socio-political backdrops of its age, and spans three years in a fictional Midlands town. In a book built this way, threads rarely end cleanly—they go quiet. A subplot can sit untouched for dozens of pages while another dominates, and a reader returning after a break often can't remember which thread was where. For many readers that is the stall point—not boredom, but lost orientation. The fix is to read the way an adapter reads, tracking every thread as material that must be accounted for. Our suggested tool is a storyline ledger: one row per thread, updated at every session's end, so no thread goes quiet unnoticed.
Our suggested exercise: open a page—paper or a file—and give one row to every storyline you detect. Three columns: the chapters where the thread appears, its year within the novel's three-year span, and a one-sentence status update written at the end of every reading session. The one rule: never delete a row. When a thread goes dormant, don't drop it—write dormant since chapter X, with the page number. The ledger's value shows at the stall points: before resuming, scan the dormant rows, pick up any thread in under a minute, and read on with the whole weave in view. To evaluate: after twenty chapters, test yourself—name each thread's last event without opening the ledger; any thread you misname is the one your updates are too vague on, so tighten the one-sentence rule.
Stage three: log one character's trajectory at fixed checkpoints
The review makes one claim worth testing rather than merely accepting: Middlemarch follows the trajectories of its characters with such detail that they become hard to replicate in another form. That detail is spread across roughly 900 pages, so the change it describes likely accumulates too slowly to notice page by page—our interpretation, not the review's words, and one you can check. The method borrows the adapter's problem: an adapter must decide who a character has become by the end, so a reader testing the claim should record who the character is at fixed intervals. Pick one major character and set checkpoints by page count, so the intervals stay honest even when chapter lengths vary. At each checkpoint you log the same three things, keeping the format identical every time, because comparable entries are what make the comparison at the end mean anything.
Our suggested exercise: every hundred pages, log three lines about your chosen character—what they want right now, what they actually do, and one line quoted verbatim, with its page number. Quote exactly; paraphrase poisons evidence. The three-line cap forces you to compress a hundred pages into what matters. At the end, compare your first and last checkpoints and write the arc as three short stage directions. Then run our suggested hypothesis test: mark which logged changes could plausibly be played in a staged scene and which resist. Treat what resists as an open finding to verify against the text, not a guaranteed result—the review claims difficulty of replication, not which changes resist. To evaluate: if first and last checkpoints read identical, either the character stood still or your lines ran too vague; reread one span to learn which.
Stage four: audit your own competition draft with the same trajectory test
The review's central question—how to adapt a roughly 900-page novel for the stage without flattening its moral, philosophical and psychological complexity—is a question about selection: an adapter cannot keep every scene, so every scene must justify its place. That pressure is what a revising writer lacks: you wrote every scene, so each tends to feel necessary. The checkpoint habit from stage three offers a way to import the pressure. If a character's trajectory is tracked by what they want and what they do at fixed points, a scene's value can be tested against those tracks: does it move any of them? Our suggestion treats that as a working hypothesis to test on your own entry, not a rule the review states—an adapter's lens applied to prose, with results you verify rather than assume.
Our suggested exercise: apply the checkpoint habit to your own competition draft. Mark the start, middle and end with what your protagonist wants and actually does at each point, in the same three-line format used for reading, so the entries stay comparable. If two checkpoints read the same, flag that stretch as a candidate for revision. Then cut or compress any scene that fails to move a tracked trajectory, keeping every cut in a separate file so you can restore what the draft misses. To evaluate: after revising, re-log the three checkpoints and check that each remaining scene moves at least one tracked want or do; if the arc now reads as three distinct stages, the test did its work. Since CWA accepts rolling entries and allows multiple works in the same category, a revised draft can be entered as its own eligible work.