Most people who visit a heritage trail are not academic historians. They're curious — about the place they live in or are visiting, about the people who came before them, about how things got to be the way they are. Your writing should reward that curiosity with stories that are clear, specific, and genuinely interesting. That's harder than it sounds, but this chapter will help.
Tone and voice
The tone that works best for heritage trails sits somewhere between a knowledgeable friend and a good museum label — warm and conversational, but precise and accurate. It is not the tone of an academic paper, and it is not the breathless enthusiasm of a tourism brochure.
Some principles to keep in mind:
- Write as if you're talking to someone standing next to you. "The building you're looking at was once a malthouse" is better than "The edifice in question formerly served as a malting facility."
- Use the present tense where possible. "The mill stands on the site of an earlier watermill recorded in the Domesday Book" feels more immediate than "The mill stood on the site."
- Avoid jargon. Terms like "vernacular architecture," "ridge and furrow," or "enclosure award" need a brief explanation for most readers — or can simply be replaced with plain language.
- Be confident, not hedging. "It is thought that this may possibly have been used as..." is less effective than "This building served as..." If you're genuinely uncertain, say so once clearly: "Tradition holds that..." or "Local records suggest..."
- Use active sentences. "The canal company built the wharf in 1805" is stronger than "The wharf was built by the canal company in 1805."
How long each stop should be
Visitors are standing up, possibly in wind or rain, holding a phone. They are not going to read an essay. Each stop description should be readable in 30–60 seconds — that is roughly 80 to 150 words.
If you find you have more to say than 150 words allows, that is a signal to either cut material or split the content across two stops. It is rarely a signal to write more.
Audio guides can be slightly longer because listening requires less effort than reading. A 200-word audio script is approximately 90 seconds of narration at a natural pace — about right for a point of interest. See the section on writing for audio below.
Structure of a stop
Each stop works best when it follows a loose three-part structure: orient, inform, connect.
e.g. "The low brick building to your right, now a private house, was once the village lock-up."
e.g. "Built in 1843 to designs by the county surveyor, it held up to four prisoners overnight before they were transported to the county gaol at Northampton. The last recorded use was in 1897, when a farmhand named William Tebbott was held here after a brawl at the Crown Inn."
e.g. "The building's survival is largely accidental — it was used as a coal store for most of the twentieth century, which kept it structurally sound."
You don't need to follow this structure rigidly — it's a scaffold, not a formula. But if a stop feels flat or unfocused, checking whether it has all three elements often reveals what's missing.
Writing a strong opening
The opening sentence is the most important sentence in any stop. It needs to tell visitors immediately what this stop is about and make them want to read on. Most first drafts bury the interesting thing two or three sentences in — the editing task is usually to move that thing to the front.
This area of the village has a long and interesting history. The land was originally part of the manorial estate and over the centuries has seen many uses. The building that stands here today dates from the Victorian era...
In 1874, a man died in this building after falling into the machinery. The inquest at the Bell Inn returned a verdict of accidental death, and the mill owner paid for his funeral — though not for his family's loss of income.
The strong version opens with a specific event that creates immediate human interest. The weak version opens with generalities that delay the reader's reward.
Some reliable opening gambits:
- A specific date and event — "On the night of 14 March 1916, this building caught fire..."
- A striking contrast — "The car park you're standing in was, until 1962, a terrace of twelve cottages..."
- A direct question — "Why does a small village like this have a building large enough for 400 worshippers?"
- A named individual — "In 1851, a 70-year-old woman named Hannah Watts was living alone in this cottage, working as a lace-maker..."
The power of specificity
Specific details are what make heritage writing memorable. General statements about "the important role the canal played in local trade" wash over readers. A specific detail — the name of a boatman, the price of coal per ton, the name of the horse that worked the towpath — sticks.
The pub was an important social centre for the village community, where local people would gather to socialise and discuss the issues of the day. It played a significant role in village life for many generations.
The pub's back room served as the village's polling station until 1929 — voters collected their ballot papers from the bar. On election days, the landlord reportedly did record trade.
When you're doing your research, collect specific details even when you're not sure you'll use them: names, numbers, dates, prices, quantities, occupations. These are the raw material of good trail writing. A census return that records a family of nine living in a two-room cottage tells a human story more powerfully than any general description of Victorian poverty.
Then and now
One of the most effective techniques in trail writing is the direct contrast between what a place looks like now and what it looked like in the past. Visitors are standing in the present — connecting that to the past through a precise description of what has changed makes history feel immediate rather than abstract.
This area was once the site of the village's main industrial activity, with several workshops and outbuildings clustered around a central yard. The industry declined in the early twentieth century.
The houses behind you stand on what was, until 1934, a yard containing a smithy, a wheelwright's workshop, and stabling for twelve horses. The chestnut tree at the far end of the car park is the only survivor of that earlier landscape.
Historic photographs strengthen this technique enormously — a visitor who can look at an old photo and then look up at the same view transformed by time has a moment of genuine historical connection. See Chapter 3 for guidance on sourcing and using historic images.
Writing for audio
If your trail includes audio guides, the text needs to be written differently from stop descriptions intended to be read. Audio writing is closer to speech — it needs to sound natural when spoken aloud, and it needs to work without the visual support of headings, bold text, or images.
Key differences from written text
- Shorter sentences. A sentence that reads well on screen can be hard to follow when spoken. Aim for sentences of 15–20 words at most.
- No lists. Bullet points don't translate to audio. If you have a list of three things, write them as: "There were three reasons for this: first... second... and third..."
- Signpost the structure. Listeners can't skim back. Use phrases like "But the more interesting story..." or "What happened next was..." to guide people through the narrative.
- Avoid figures that are hard to absorb by ear. "1,247 bricks" is hard to process when heard. "More than a thousand bricks" lands more clearly.
- End with a direction cue. The last sentence of an audio stop should guide visitors to the next one: "Continue along the path and you'll see the old mill building ahead of you."
Stop titles
The title of each stop appears on the map and at the top of the stop description. It needs to do two things: tell visitors what the stop is about, and make them want to open it.
The most common mistake is a title that is merely a label — "The Old Mill," "St Peter's Church," "The Village Green." These tell visitors nothing they couldn't see for themselves. A better title carries a hint of the story:
The Old Mill
St Peter's Church
The Manor House
The Canal Wharf
The mill that burned twice
A church built by a guilty conscience
From manor to military hospital
Where the coal boats turned
Story titles work especially well for audio guides, where visitors hear the title before deciding whether to listen. A title that poses an implicit question — "A church built by a guilty conscience" — creates curiosity that the stop then satisfies.
Editing your work
Good trail writing is almost always the product of several drafts. The first draft gets everything down; subsequent drafts cut, clarify, and sharpen. Here is a practical editing checklist to work through once you have a first draft of each stop:
- Count the words. If it's over 150, what can you cut without losing the essential story?
- Read it aloud. Does it sound natural? Do you stumble anywhere?
- Check the opening sentence. Does it immediately tell the visitor what this stop is about? Is the most interesting thing at the front?
- Remove qualifications. Cut "it is thought that," "may have been," "in some ways," and similar hedges unless they're genuinely necessary for accuracy.
- Cut adjectives. "The magnificent Victorian Gothic church" tells visitors less than "the church, built in 1876 to hold a congregation of 600."
- Check for jargon. Would a visitor with no prior knowledge of the area understand every term?
- Ask someone else to read it. Ideally someone who doesn't already know the story. Where do they lose the thread? What questions do they have that you haven't answered?