A fantasy name suggests a larger world when several people inside that world have reasons to say it differently. Tolkien’s invented languages offer an example of how those differences can arise. This workshop puts the principle to work on a fictional riverside craft guild, using wholly new forms and a naming problem small enough for one evening.
Start with the speakers
The guild lives on the twin banks of an imagined river. People on one bank maintain markers for boat crews. On the other they copy tide schedules and repair lamps. Before making a name, define which people will say it and what they need from the conversation. The name shouted in thick fog has to survive missed sounds. The title written by a clerk can be longer, because writing persists and the caller can point to a particular line. If the group needs a ceremonial version, decide when a person would reasonably speak it. These are separate scenes in the same world. A reader can hear the relationships if every form answers a need that actually exists in the story.
Carl Hostetter’s introduction for the Tolkien Estate describes the place of invented languages in Tolkien’s work, including Quenya and Sindarin. The reusable lesson is the depth provided by a system of speakers, related forms and settings. Taking an authentic-looking name from a published world would leave the guild with someone else’s relationships and histories. Create a rule that belongs to your particular community. A limited rule, applied consistently in three places, can suggest more history than thirty striking but unrelated candidates. Write it down in an ordinary sentence and ask a friend to predict a fourth name without seeing the answer.
Choose a visible working object
The founders consider a lamp suspended beside a bend. It is a useful image because it has a location, a job and people responsible for it. Draw the bend, the landing and the place with the best sightline. The object belongs to a community before it belongs in a title. For this exercise, the older local sound for something bright and carried is neral. The crossing root is tav. These are invented labels for the draft. Their meanings are defined here only. The group can set them aside if they have other associations in a shared language or resemble people or places its players already know.
Suppose the household by the landing calls the lamp Neral, the clerks refer to the crossing as Tav, and the guild initially writes Neral Tav in its notes. Ask whether another combination of the two forms should have the same meaning. In this draft, tav marks crossings when it comes at the end, so a form ending in tav suggests a place a traveler can pass through. Place the invented forms beside transparent English descriptions in your writing notebook. That makes it possible to explain an early revision by showing what was learned, without pretending to discover an ancient translation the group never established.
Give one change a reason to spread
Talk through how a listener normally learns a route. They may hear a short description from a boat crew and then see a longer form on a map at the docks. The founder tries ending a word with l immediately before the t that begins tav. In quick speech they hear a soft boundary. On the quay the two words begin to sound like Neraltav. The group chooses one simple pattern: adjacent roots fuse in route names, while they stay separate in entries that inventory objects. This is a design choice for an imaginary speech community. The pattern can appear in another name, such as Mor Tav becoming Mortav, after the writer defines mor as a break in the bank.
Read the proposed change aloud in short and long sentences. If speakers stumble, adjust the invented forms while they remain in draft. One player regularly says the second example with a prominent t and asks if the marker lamp still belongs to the title. Adding an extra vowel at the seam would make it easier for that person, but applying it only once would weaken the appearance of a system. The team writes down both approaches and picks the one it can apply in a useful range of names. The result sounds related by agreement and repetition. A decorative apostrophe would not create that relationship by itself.
Give institutions their own naming habit
The map keeper uses Neraltav to refer to a route, while the guild needs a title that identifies people responsible for safe passage. A proposed ending en means a steward in the fictional river community. Two roots are enough for most settings, so the title begins as Tavren, an abbreviated form for a crossing steward, written with a bridging r chosen for clarity. A plaque could say Tavren Circle. In speech a gate worker might say the Tavren are meeting after dusk. The root table gives the reader a route to work out why a group announcement bears the same mark as a crossing slip, even when the writer never delivers a paragraph of exposition.
Keep one name at each layer. The map marks Neraltav, the roster shows Tavren Circle and the first invitation identifies the people who mark the route. Resist asking a newcomer to learn the entire system on their way to the first meeting. The writer can introduce the easy form in an introduction, then give an older version when a damaged sign prompts a real question in the story. A useful naming distinction creates a new action for the reader: knowing which group is calling, which route to take or which old label an archivist is trying to interpret. If a new form changes none of those choices, it can remain in the notebook.
A translation can keep the story accessible
The guild tries Lampbend for its public-facing English event label. Residents are free to speak their local form in play. A friend new to the setting can recognize a meeting at Lampbend before learning the role of Neraltav. If a Japanese version is part of the campaign, a natural description of a lamp by a crossing can convey part of the relationship without implying that every syllable in the made-up root has a dictionary counterpart. Write the translation beside the first scene where the name matters. Review whether the translated label points to the same physical thing as the invented one, especially if a word can also stand for an organization.
The labels can coexist in a map legend. One column gives the name people see in game, one gives what characters say and one gives the practical point for arriving players. A small place that changed hands could have two local names, but give both a reason to persist. Imagine the district runner learned the ceremonial form from a parent while maintenance volunteers learned the route abbreviation from dispatch notes. Neither person is mistaken by default. The story gains texture when the disagreement concerns whose record is trusted under particular conditions. The distinction should nevertheless remain legible to players who use an external calendar to arrive on time.
Let a mistake improve the draft
Early in the story a stranger follows a similar label to the less accessible bank. The obvious fix is to give the two places a different sound. First ask how the original mistake happened. If the spoken name was clear but the map shows two similar words in the same region, revise the route label on the map. If a character was told to follow Tavren instead of going to Neraltav, the instruction confused people with place. The guild tries an updated invitation: meet at the Lampbend crossing; look for the Tavren lantern on the eastern bank. Two distinct cues help a reader who missed one word in the title.
The writers also reject Tavaren, because it too closely resembles Tavren in hurried speech and it has no useful function in the existing set. They keep Neral for the lamp itself rather than give the object a second title to make it seem old. This choice demonstrates a less visible aspect of language design: recurring forms increase recognition. A small set sounds established when a word resurfaces in a new circumstance with the underlying relationship intact. Put the rejected candidates in a notes column, and include the actual error each one produced, so the next writer does not bring back an attractive spelling that already failed a reading test.
Put your rules in a scene
From the landing, a guide recognizes an older inscription on a bronze plate. Another player reads the recent paint above it. The old word marks every place where a boat can cross during mild conditions. The recent paint names the one crossing currently staffed by the guild. Someone choosing a route in a snowstorm has a reason to care. Use an ordinary sentence to introduce the conflict, then allow a character trained in the system to explain the difference in the forms. The audience can now see the value of the rule, because it changes what people do before the night's crossing.
Read the scene to somebody who has the root table and to somebody who has never seen it. The second listener should still be able to explain why the old marking would lead them astray. The first reader should be able to predict what a new route sign would look like. If both fail in different ways, decide whether a more transparent translation or a stronger internal pattern would address the problem. The team may keep a poetic original only where the story provides enough context. A single technical-looking spelling cannot carry the entire burden of making a fictional place plausible.
Decide what the names let the next writer invent
A friend wants to add a site where the maintenance crew leaves broken lamps for repair. Give them the root table and ask which existing form could point to a place and which describes the people doing the work. They might keep Neral as the material reference and borrow a plain modern noun for the shelf. If they add a route, the familiar tav ending will help readers identify it. The number of established forms can stay small while the number of scenes grows. Document one correct extension and one tempting application that would change the meaning people already know.
Check the audience beyond your draft
Look up finalists in the game and in the ordinary tools your table or guild uses. Search exact forms and plausible spellings that other people typed after hearing the name. An invented word can already belong to a real person, organization or a different fictional world. If an association affects how others understand your title, decide whether a transparent phrase or adjusted root works better. Find another member who can speak a language represented in your audience if a string seems likely to be read differently there. Have them describe their impression without giving them your preferred explanation beforehand.
Before finalizing, record each form with a pronunciation in ordinary terms, its function, who uses it, and a place it appears. Keep one real-world explanation for the people who need to find the group quickly. A useful name family is stable enough for a new writer to contribute without reading a founder’s entire archive. That stability also leaves room for revision: if someone invents a second crossing pattern, they can describe how their people differ and show where that difference becomes useful in play. The system supports creativity because the next person has a place to begin.
Keep a small error ledger beside the root table
A naming system becomes useful when its mistakes can be repaired without rewriting the whole setting. Add a small ledger with three columns: the form that caused confusion, the mistaken interpretation, and the smallest proposed repair. In this workshop, Tavren was confused with Neraltav because an invitation named a group where the reader needed a destination. The repair is not automatically a new root. “Meet at Lampbend; the Tavren will guide you” separates place from people while preserving both established forms. Record that solution so another writer does not later add a third synonym for the same crossing.
Distinguish a broken rule from a missing explanation. If a new place ends with the institution marker despite being introduced as a route, the draft may be inconsistent. If the rule is consistent but a new reader cannot infer it, a short plain-language cue may be enough. Do not manufacture an elaborate historical exception every time a draft contains a mistake. Exceptions become convincing when they serve a story and recur meaningfully, not when they protect every accidental spelling. Keep one rejected example in the ledger as a teaching aid. It shows collaborators the boundary of the system more clearly than a long assertion that all forms should feel related.
Ask a second writer to extend the system without coaching
Give a collaborator the existing forms and ask them to name two different things: a newly marked crossing and the volunteers who inspect its lamps. Do not supply your preferred answer. Ask them to explain which part of each form identifies its role. If they can produce plausible extensions but use a different rhythm, you have a stylistic decision to discuss. If they cannot distinguish route from organization, the documentation is missing a functional rule. Repair that gap before adding another page of vocabulary. A larger word list will not necessarily clarify a relationship that was never stated.
Then exchange tasks. Let the collaborator invent a local term and explain its role while you attempt to use it in a sentence. This reverses the assumption that only the founder's intuition counts as evidence. A usable shared system gives later writers enough support to contribute, while allowing them to notice weaknesses in the original rules. Keep the test bounded: two new forms and one scene are enough to expose many practical problems. Do not demand that a friend become a linguist before joining the creative exercise. The objective is reliable collaboration on a small fictional world, not the appearance of having designed a complete historical language.
Hand over a scene, not merely a vocabulary list
Finish the exercise with a short usable scene. A visitor reaches two signs during heavy rain. One carries the old crossing name; the other identifies the currently staffed route. A volunteer explains the difference in an ordinary sentence, and the visitor makes a sensible choice. Give a new reader the scene without the root table. They should understand the action even if they do not remember every invented syllable. Give another reader the table as well and ask which new form they could predict. The two readings test accessibility and internal consistency separately.
Store the scene with the handful of forms it uses, their ordinary explanations, and the rule that connects them. Label invented meanings as decisions made for this setting. Keep the source of any real literary inspiration separate from the fictional dictionary so later writers do not accidentally present a homemade form as an established translation. When you add another district, expand only the rule or distinction that the new scene needs. If a label neither changes what someone understands nor helps them act, it can remain an unused draft. The completed asset is a small system people can read, extend, and revise with confidence, rather than a large collection whose attractive spellings conceal inconsistent purposes.
