Flashback

A flashback interrupts the present of a story to show an earlier event in scene, then returns. It is a way to deliver backstory as drama rather than summary, letting the reader experience a past moment instead of being told about it. Used well, a flashback lands a piece of the past exactly when the present scene gives it weight.

The danger is that every flashback stops the story's forward motion. Jump back too often, or for too little, and the present narrative loses momentum while the reader waits to return to it. The rule is that a flashback has to earn its interruption: the past it shows must matter enough, right now, to justify pausing the present. Most flashbacks that drag are ones that did not need to be scenes at all.

Why flashbacks are a continuity risk

Flashbacks are one of the easiest ways to break continuity. They move through time, so they invite contradictions: a character knowing something in the past they should not, an event placed wrong on the timeline, a detail that conflicts with the present. They also strain point of view, since the narrator has to hold two moments in time at once. A memoryless model handles none of this reliably, and will happily drop a flashback that contradicts the established timeline.

How FireQuill helps

FireQuill keeps your timeline as established fact and checks new prose against it, so a flashback that places an event wrong or reveals knowledge too early gets flagged. The past stays consistent with the present because the system holds both. You decide when to reach back; the checks keep the reach from tangling the timeline.

See how timeline consistency works in continuity.