top of page
Search

The Rules I Didn't Know I Was Writing

Writer: D. Patrick Dillon
D. Patrick Dillon
Nov 6
9 min read

Beyond the Manuscript | When Storytelling Decisions Became Falcon Hollow Canon

 

When I started writing Father's Day, I wasn't thinking about canon.

Actually, I wasn't thinking about a series, either. I was trying to write a murder mystery set in a small fictional Maryland town called Falcon Hollow. I needed a police department, a few businesses, some interesting locations, and a detective named Duke Mantz who could move through the story without getting himself completely lost.

That seemed reasonable enough.

What I didn't realize was that every time I made a decision about Falcon Hollow, I was establishing something that might matter in another story. And another. And possibly several more after that.

At the time, those decisions didn't feel particularly important. They were simply details that helped move the story along.

But somewhere along the way, Falcon Hollow stopped being just the setting for a mystery novel. It started becoming a town with a history, a geography, a municipal government, and people who had lives beyond whatever crime Duke happened to be investigating.

And that meant I was creating rules.

I just didn't know it yet.

 

One Idea Leads to Another

 

I've mentioned before how a question about driving distances helped start this whole worldbuilding adventure. Duke and Brooke Allen were traveling between locations during the investigation in Father's Day, and I began wondering whether the distances and travel times actually made sense.

That led to a fairly simple thought.

Maybe I should make a town map.

So I opened PowerPoint and started putting one together.

Of course, if you know anything about the way my mind works, you can probably guess what happened next.

I'd be working on one thing, and another idea would pop into my head. I'd follow that idea for a while, and then something else would occur to me. Before long, I wasn't just figuring out where a few streets and buildings belonged. I was thinking about what the rest of the town might look like.

And then came another thought.

Wouldn't it be interesting if Falcon Hollow had its own municipal website?

Well, why not?

So off I went in another direction.

Before I knew it, the fictional town I'd created to support one murder mystery had a small website, a developing street map, and a growing collection of places that existed whether Duke needed to visit them or not.

Somewhere during all of that, I began to realize that Falcon Hollow could become something more than the setting for a single book.

I hadn't sat down with a grand plan to create a fictional community. I hadn't outlined five future novels or designed an elaborate fictional universe before writing the first chapter.

One idea simply led to another.

And every one of those ideas left something behind.

 

When a Decision Becomes a Fact

 

Here's something I didn't fully appreciate in the beginning.

When you're brainstorming a story, almost anything can change.

You can move a building, rename a character, eliminate a scene, or decide that the restaurant you invented yesterday would work better somewhere else. Nothing is necessarily permanent while you're still figuring things out.

But once you put a detail into a finished story, particularly one you've published, the situation changes.

You've told the reader something about your fictional world.

Maybe you've established that a particular business is near the lake. Maybe you've described the police department or explained how two characters know each other. Perhaps you've given someone a habit, a personal history, or a relationship that will matter later.

Those details might have been small decisions when you made them, but they become part of the world you've presented to readers.

And if you're planning to return to that world, you need to remember them.

That's where the idea of canon begins to matter.

I didn't start out using that word very often. I was just trying to keep things straight. But eventually I understood that some of my earlier choices had become established facts about Falcon Hollow.

There comes a point when I have to tell myself I can't do something in a new story because I've already written something else.

Which is a rather strange position to find yourself in when you're the person who invented the town in the first place.

I can make up an entire police investigation, invent a suspect, and decide who committed the crime. But I can't casually move the police department across town if I've already established something that makes that impossible.

Well, technically I can.

But then I have some explaining to do.

 

The Police Department That Needed a New Home

 

One of the better examples of how this developed happened while I was working on Known by Another Name.

In Father's Day, the police department was already part of Falcon Hollow. I knew where I intended it to be, and I'd been developing the town map around the locations used in that first story.

But I hadn't given the police department a specific street address in the novel.

That turned out to be fortunate.

Known by Another Name introduced another part of Falcon Hollow's public safety operations. The story involved a fire investigation, which meant bringing in Fire Chief Conklin, EMS Captain Naomi Takada, and other personnel who hadn't been part of the original mystery.

As I developed that side of the town, I decided that police, fire, and EMS would operate from a shared Public Safety Building.

It made sense for Falcon Hollow.

There was just one problem.

At one point, we had Naomi driving to the police department.

Except, under the arrangement I'd just established, she was already in the same building.

She didn't need to get into a vehicle. She needed to walk down the hall.

That was when I realized I had to be more careful about the decisions I was making.

I couldn't simply move the police department on the map and assume everything would work out. I needed to go back through Father's Day and check what I'd actually written.

Had I identified the building's location in a way that would prevent the change? Had I described anything about the surrounding area that might cause a contradiction? Was there something in the original story that I'd forgotten?

Fortunately, there was enough flexibility to make the shared Public Safety Building work.

But the experience taught me something.

A decision that seems perfectly reasonable in the story you're currently writing can create a problem with a story you've already finished.

And sometimes the only way to know whether you're creating that problem is to go back and check.

I wish I could say I immediately developed a careful system for doing that.

I didn't.

It was pretty messy in the beginning.

 

A Town Has More to Remember Than Its Streets

 

Geography was only part of the problem.

As Falcon Hollow grew, so did the number of things I needed to remember.

There were characters' backgrounds, relationships, occupations, personalities, and mannerisms. There were municipal departments and businesses, each with their own people and responsibilities. There were details about the town's history, its buildings, and how different parts of the community connected.

And then there was the writing itself.

I wanted the characters to remain recognizable from one story to the next. I wanted their conversations to sound like the same people speaking, even when the circumstances changed. I wanted the overall narrative style to remain consistent rather than feeling as though every new book had been written by someone different.

Consider Brooke Allen.

One of her small mannerisms is a three-taps, pause, three-taps habit that can appear when she's nervous or concentrating particularly hard.

That's not a major plot point. It isn't something that needs an entire chapter of explanation.

But it's part of Brooke.

If I return to her character several books later, I don't want to have to reread every earlier appearance to remember whether she had that habit, how it worked, or when it tended to appear.

The same applies to a character's background or the way someone speaks. Those details help give the people of Falcon Hollow continuity.

And the more stories I write, the more difficult it becomes to keep all of that information in my head.

Especially when my mind is already bouncing around between three or four other ideas.

 

Bringing Everything Together

 

The earliest Falcon Hollow guides began appearing in March 2026, while the town and its stories were still developing.

They weren't comprehensive reference documents. They were working materials: town descriptions, worldbuilding notes, character information, and decisions I'd made along the way.

Some of those early documents had rather grand titles, but I think of them now as guides. They were attempts to capture what I knew about Falcon Hollow at the time.

As more stories developed, those notes accumulated.

Some decisions were revised. Some ideas were abandoned. Others became firmly established through the stories themselves.

Eventually, it became clear that I couldn't keep treating every collection of notes as an independent source of information.

I needed one consistent authority for Falcon Hollow.

That didn't mean putting everything into one enormous document. It meant reviewing what I'd already created, deciding which information was established, reconciling anything that conflicted, and organizing it so I could find the answers when I needed them.

That work eventually led to the reference system I use today.

The Falcon Hollow Canon records established facts and decisions. The World Bible provides broader information about the community and how it functions. The Character Bible keeps track of the people who live and work there. The World & Geographic Guide addresses the physical town, its locations, and how everything fits together. And the Editorial Guide helps maintain consistency in the way the stories are written.

They're separate references, but they're meant to describe the same place.

More importantly, they give me somewhere to go when a question comes up.

I don't have to rely on remembering a conversation from six months earlier or searching through several manuscripts to find out what I decided about a particular character.

At least, that's the idea.

I still have to remember to check the references.

And ChatGPT still needs an occasional reminder that a suggestion made during brainstorming isn't automatically an established fact.

But now there's a way to settle those questions without reinventing Falcon Hollow every time we start another story.

 

The Stories Can Change. The Town Needs to Remain Recognizable.

 

Here's the part that matters most to me.

I don't want every Falcon Hollow mystery to be the same.

One story might involve a murder. Another might center on a serial arsonist. Somewhere down the road, I might decide to write about a crew responsible for a string of bank robberies throughout the region, with Duke becoming involved because the same crew has hit Falcon Hollow's local bank.

Those are different investigations, with different characters, different circumstances, and different demands on the story.

And that's exactly what I want.

The plots should be free to change. New people should be able to arrive. Existing characters should be able to grow, change jobs, develop relationships, and experience things that affect their lives.

Falcon Hollow shouldn't be frozen in time.

But there's a difference between allowing a fictional community to evolve and forgetting what you've already established about it.

If a department relocates, that can become part of the town's history. If a business closes, another can take its place. If a character changes over time, the stories can show why.

Those are developments.

They're not the same as accidentally placing a building on the wrong street or having someone drive across town to reach an office that's actually down the hall.

And that distinction is what the reference documents help me maintain.

They don't tell me what crime Duke has to investigate next. They don't dictate the plot or prevent me from introducing something new.

They help me make sure that whatever I introduce belongs in the Falcon Hollow I've already created.

 

Giving My Brain Room to Write

 

I suppose this is the biggest lesson I've taken from the whole experience.

When I first started developing Falcon Hollow, I thought the challenge was going to be creating enough material to make the town believable.

Now I realize that creating the material was only part of it.

The other challenge was remembering what I'd created.

And I don't particularly want to spend my writing time trying to remember whether the police department was on one street or another, whether a character worked in a particular building, or whether I'd already established something about a relationship three books earlier.

I'd rather spend that time figuring out what happens next in the story.

That's what a well-developed reference system gives me.

It provides a place for the decisions I've already made, so I don't have to carry all of them around in my head. It helps me maintain the geography, the characters, the town's history, and even the voice and style of the writing.

It also gives me room to follow those unexpected ideas that seem to appear whenever I'm supposed to be working on something else.

I can still wander off in another creative direction. I can still decide that Falcon Hollow needs something I hadn't thought about before.

I just need to make sure it fits.

And when it does, that new decision becomes another part of the town's established world.

Looking back, I never really sat down and decided to write a set of rules for Falcon Hollow.

I was writing stories.

I was building a map because I needed to understand driving distances. I was creating buildings and departments because the investigations required them. I was developing characters because the town needed people who felt as though they actually lived there.

And one decision at a time, I was creating a community that had to remain consistent from one story to the next.

The rules were there long before I recognized them.

All I eventually did was start writing them down.

And now, instead of trying to remember every detail of a town that doesn't exist, I can get back to the part I enjoy most.

 
 
 

Comments


bottom of page