Authors who build stories around a character walking through a fictional city face a specific organizational challenge: each location must carry sensory detail, emotional weight, and narrative function simultaneously, while the overall sequence must feel like a natural journey rather than a checklist. This article walks through one author's method for managing that complexity using place cards and a plot index, applied to a clearly invented city.
A Place Card System for the Fictional City of Velmara
Consider a hypothetical project in which a protagonist named Sera walks through the fictional port city of Velmara over the course of a single autumn afternoon. The city has no real-world counterpart; its districts, landmarks, and street names are entirely invented for this story. The author begins by listing every location Sera will physically enter or observe from a distance. For this project, that list contains eleven places, ranging from the Salt Gate entrance arch to a rooftop garden above a shuttered bookbindery. Each place becomes a card.
In this example, each place card contains five fields. The first field is the location name, written as it will appear in the story, such as the Salt Gate or the Undercroft Market. The second field holds two or three sensory anchors: a smell, a sound, or a visual detail that will recur whenever the character returns to that spot. The third field records the emotional register of the scene set there, for instance dread, relief, or quiet curiosity. The fourth field lists which plot threads are advanced or revealed at this location. The fifth field is a status marker indicating whether the scene has been drafted, outlined only, or left as a gap the author intends to fill later.
The choice to limit sensory anchors to two or three per card is deliberate. In this example, the author found that longer lists made it harder to keep descriptions consistent across revision passes. When a place has five listed smells and four sounds, the author risks contradicting an earlier scene or diluting the one image that should stay vivid in the reader's memory. Keeping each card focused on a small set of anchors makes it easier to check consistency during editing and gives each location a distinct identity without overloading the planning document.
Sequencing Scenes Along the Walking Route
Once the place cards exist, the next task is arranging them into a walking sequence that feels geographically plausible within the fictional city. In this example, the author draws a rough sketch of Velmara's districts on a single sheet of paper, not as a precise map but as a spatial reminder of which locations are close together and which require the character to cross a bridge, climb a hill, or pass through a gate. The sketch is not meant for publication; it serves only to prevent contradictions such as Sera arriving at the Undercroft Market immediately after leaving the rooftop garden, when in the story's internal geography those two places are separated by an entire district.
The plot index is a separate document that lists scenes in the order they will appear in the finished story. Each entry references the place card by name, notes which chapter or section the scene belongs to, and records a one-sentence summary of what the character learns or experiences there. In this example, the index entry for the Salt Gate reads: Sera arrives through the arch, notices the tide mark on the stone, and recalls a conversation from the previous chapter that now seems ominous. This level of detail is enough to orient the author during drafting without locking the scene into a fixed version too early.
The index also serves as a pacing tool. By reading down the list of one-sentence summaries, the author can spot stretches where too many consecutive scenes share the same emotional register or where the character moves between locations without any internal reflection. In this example, the author noticed that scenes four through six all carried a tone of quiet observation, so a brief moment of tension was added at the transition between the fifth and sixth locations. The index made that gap visible in a way that reading individual scene drafts in isolation did not.
Preparing a Public Address for Sharing Your Story
Once the place cards are sequenced and the plot index reflects the intended pacing, the story structure is complete enough to draft from. If the author later decides to share the finished story or the planning documents with readers online, a custom web address becomes a practical consideration. This step is entirely optional and separate from the creative work described above; it does not affect how place cards are written or how scenes are ordered. The table below compares the first action at two domain registrars for authors who choose to take this step.
| Check | NamesLink | Namecheap |
|---|---|---|
| Availability check | Enter the desired domain name in the search box on the homepage to view registration status for each available suffix | Enter the desired domain name into the Search field on the Domain Name Search page and click Search to view availability and similar suggestions |
Tracking Unresolved Clues and Pending Descriptions
Record every unresolved story thread directly on the place card where it is introduced or where it is meant to pay off. In this example, the card for the Undercroft Market carries a note that Sera overhears a fragment of conversation she does not yet understand, and that this fragment must connect to a reveal planned for the rooftop garden scene three locations later. Writing the connection on both cards means that if the author revises one scene, the other card reminds them to check whether the link still holds.
Pending descriptions are handled differently from unresolved clues. A pending description is a spot where the author knows a scene needs sensory detail but has not yet decided what that detail will be. In this example, the card for the Canal Bridge has a note reading: needs a sound detail, possibly distant bells or water against stone, decide during second draft. This kind of note keeps the card honest about its completeness without forcing a premature decision. The author can return to these flagged spots in a dedicated revision pass focused solely on sensory texture, rather than trying to solve every gap during the initial drafting phase.
The status marker on each card plays a supporting role here. In this example, three statuses are used: drafted, outlined, and gap. A card marked gap means the author knows the character passes through that location but has not yet written any scene content for it. A card marked outlined has a plot index entry and a rough sense of what happens, but no prose. A card marked drafted has at least one full scene written. During revision, the author can filter the list by status to see how much work remains and whether any gap cards are blocking the narrative flow between two drafted scenes.
Updating the Index When Scenes Change
Check the plot index every time a scene is substantially revised, not just when a scene is added or removed. In this example, the author rewrote the Canal Bridge scene to shift its emotional register from melancholy to uneasy anticipation. That change meant the one-sentence summary in the index no longer matched the scene, and more importantly, it altered the pacing pattern the author had previously corrected. Updating the index entry to reflect the new register made the shift visible again, allowing the author to confirm that the surrounding scenes still provided adequate contrast.
Cascading changes are a particular risk in a walking story because the character's physical movement creates implicit transitions. If the author decides to cut the Undercroft Market scene entirely, the character must still get from the Salt Gate district to the Canal Bridge district. In this example, the author handled such a cut by adding a brief transitional paragraph to the previous scene rather than inventing a new location. The place card for the Undercroft Market was not deleted but was instead marked as removed from sequence, preserving its sensory anchors and thread connections in case the author later decided to reintroduce the location in a different position or in a sequel.
The author in this example also maintains a short revision log at the bottom of the plot index document. Each entry records the date, the scene affected, and a brief reason for the change, such as moved Salt Gate reveal earlier to strengthen opening tension. This log is not part of the story itself and is not intended for readers. It exists so that after several weeks of revision, the author can trace why a particular scene moved or why a thread was reassigned to a different location, reducing the chance of accidentally undoing a deliberate earlier decision.
Choosing Which Places Serve the Story
List the narrative function of every place card and ask whether that function is already fulfilled by another card earlier or later in the sequence. In this example, the author initially included a card for a small chapel near the canal, intended to provide a moment of stillness. However, the rooftop garden scene already offered a quiet reflective beat with stronger thematic resonance because it overlooked the entire city. The chapel card was therefore marked as removed from sequence, and its single sensory anchor, the smell of cold incense, was reassigned to the interior of the bookbindery where it served a different emotional purpose.
The decision to keep or cut a place is qualitative rather than rule-based. In this example, the author uses three guiding questions. Does this location reveal something about the character that no other scene reveals? Does it advance or complicate a plot thread that is otherwise unresolved? Does it provide a sensory or emotional contrast that the surrounding scenes lack? If the answer to all three is no, the card is a candidate for removal. This does not mean the location is bad or uninteresting; it means the story as currently structured does not need it. The card remains available if the structure changes in a later revision.
Sometimes a place card survives but its role shifts significantly during revision. In this example, the Salt Gate was originally planned as a simple arrival scene with minimal plot content. After the author decided to move a key reveal earlier in the story, the Salt Gate became the location where Sera first notices the tide mark that later proves significant. The card's sensory anchors stayed the same, but its plot thread field expanded from none to one, and its status changed from outlined to drafted. The plot index entry was updated to reflect the new function, and the revision log recorded the reason for the change. This kind of role shift is common in walking stories because the fixed route constrains where reveals can physically occur, making each location a potential candidate for carrying more weight than originally planned.
Frequently asked questions
How detailed should each place card be before I start writing scenes?
In this example, the author fills in the location name and one sensory anchor before drafting begins, then adds emotional register and plot threads during the outlining phase. The card does not need to be complete before the first scene is written; it needs enough information to distinguish the location from others in the sequence and to remind the author what role the place plays. Over-specifying a card too early can make it harder to adjust the scene when the draft reveals a better direction.
What should I do when two place cards seem to serve the same narrative function?
Compare their sensory anchors and emotional registers. If both cards provide the same type of contrast or reveal the same aspect of the character, one is likely redundant. In this example, the author resolved the overlap by keeping the card with stronger thematic connections and reassigning the other card's unique sensory detail to a third location. If both cards carry distinct plot threads that cannot be merged, consider whether one thread can be moved to a different location without losing its effect.
Should the plot index include scenes that I plan to cut later?
In this example, the author keeps removed scenes in the index but marks them clearly with a removed from sequence label. This preserves the record of why a scene existed and what it contributed, which is useful if a later structural change creates space for it again. Deleting a scene from the index entirely risks forgetting that a particular thread or transition was once handled there, which can lead to gaps the author does not notice until a much later revision pass.
域名注册入门指南 | NamesLink. Retrieved 2026-10-27. ↩︎
How to register a domain name - Domains - Namecheap.com. Retrieved 2026-10-27. ↩︎