A map is somebody’s account
A settlement may have an official survey name, a railway abbreviation, and an older riverside nickname. Decide whose map the audience sees. A courier’s route sheet prioritizes entrances and dependable landmarks; a ceremonial atlas prioritizes borders. Neither must contain every local name. Their differences can supply a story without requiring a page of explanation.
Choose two naming forces
For a small fictional canal district, choose trade and water level. Trade gives Rivet Quay, Canvas Court, and Spindle Yard. Water level gives Low Steps and High Door. Together they create a vocabulary with room to grow. A third influence, such as a vanished orchard, can enter as a deliberate exception rather than another unrelated decorative word.
Make exceptions earn their space
Suppose the district contains Apricot Square even though it now houses metalworkers. A former orchard explains the exception, but the story should leave a trace: a tree on an old sign, a spring fair, or a street vendor’s nickname. The name does not need an exposition paragraph. One observable trace can make the history feel recoverable.
Check the scale of every label
A narrow crossing and a continent should not feel like the same kind of label. Put the district names into a sample map at the smallest intended size. Shorten minor labels first. Keep formal titles in a legend if their full length interrupts navigation. A name can have a rich ceremonial form while the map uses its practical form.
Write a naming ledger
For each location, record present name, who uses it, the visible anchor, and any older form. Add a reason whenever a new label breaks the system. This helps a second writer build another street without copying the existing names or making everything sound accidentally unrelated.
Let disagreement remain readable
Two names can reveal an unresolved history, but readers need a bridge between them. “The timetable calls it Copper Reach; the ferryman still says Apricot Bend” is enough to connect the labels. Introduce that connection before a quest requires the player to know both. The design goal is meaningful uncertainty about the past, with clarity about where to go.
Give different scales different jobs
Expand the canal example into a hierarchy: the city has a stable public name, the district refers to an old waterway, the street records a working trade, and a particular building uses a recognizable object. The names relate through the town’s material life without sharing an identical prefix. Write the hierarchy in one ordinary delivery address and one spoken direction. If a reader cannot tell whether a label denotes the entire district or one doorway, add a type word or establish the scale in the first scene. Geographic richness should make the world feel inhabited while allowing the audience to reach the next relevant place.
Let a former use leave physical evidence
Apricot Square becomes more convincing if something remains: a worn tree mark on a repair-shop sign, a spring custom, or a boundary that follows the old orchard wall. Choose one trace and show it before explaining all of the history. The trace need not prove every account residents tell. A former worker may remember the orchard as a place of rest, while a planner sees the same wall as an obstacle. A name can preserve those competing memories. Label speculative explanations as such within your project notes so a later writer does not accidentally convert one speaker’s belief into the setting’s unquestioned historical narration.
Make an outsider’s map visibly partial
A tourist map may omit workshop entrances; a delivery sheet may omit monuments; an administrative plan may preserve obsolete district boundaries. Give each map a stated purpose, then decide what its names emphasize. When the player compares two documents, the difference should follow from those purposes rather than appear only when a puzzle needs a surprise. Introduce at least one harmless example of the convention first. A route legend explaining that former ferry stops retain their old names prepares the audience to recognize a later ferry reference. The clue then rewards attention to a world rule instead of demanding an arbitrary guess.
Use disagreement without losing the destination
Two forms can point to one place, but connect them before ambiguity becomes expensive. A clerk can say, “The old address is Apricot Turn; use Copper Reach on the current form.” The line is brief enough to fit a scene and does not settle which name residents prefer. Maintain a table linking present label, earlier form, speaker community, and visible location. If the plot deliberately withholds one connection, give the audience enough other information to investigate it fairly. Do not rely only on a subtle color difference, an inaccessible decorative symbol, or a long note that no character has a reason to read.
Design the next district as a test
Add a neighborhood with a different livelihood and ask whether your naming rules still help. If the entire system depends on water, an inland repair district may need an older route connection or a clearly marked exception. Avoid inventing a historical explanation solely to save every random candidate. Sometimes the simpler revision is to choose another word. Record whether a new form follows the shared rule, preserves an older local layer, or deliberately signals a later institution. A useful naming system can grow without making every place sound identical and without needing a new page of justification for each ordinary lane.
Prepare a map register for revision
The register should include a stable reference, display label, full ceremonial form if needed, older forms, pronunciation intention where useful, and a short explanation of the naming force. Add where each form first appears in the work. During revision, test changes in the actual map, quest text, dialogue, and search interface. A shortened label can solve a cramped display but create a conflict with another street, so inspect the surrounding set. Exported generator drafts are useful raw material; the project register is where you turn one attractive suggestion into a consistent place that other contributors can find, describe, and develop.
Make the next draft your own.
Try the method in a tool, keep a candidate in your notebook, and revise it against your actual project.
A correction or a question about this piece? Contact Drafitlem.
