top of page
Search

When One Reference Document Wasn't Enough

Writer: D. Patrick Dillon
D. Patrick Dillon
Nov 5
7 min read

Beyond the Manuscript | Building the Falcon Hollow Reference Library


When I started writing Father's Day, I never imagined I'd eventually need an entire collection of reference documents just to keep track of a fictional town. I had a few character descriptions, some notes about locations, and whatever information I'd managed to save from my conversations with ChatGPT. At the time, that seemed like more than enough.

Of course, as I explained in my previous article, keeping track of those notes was another matter entirely.

But eventually I did begin organizing things. I had Word documents containing descriptions of Falcon Hollow, character sheets explaining who people were, and notes about the town's geography and history. I also had the Editorial Guide, which I'd developed to address the recurring problems with ChatGPT's writing style.

The trouble was that Falcon Hollow hadn't stopped growing while I was trying to organize it.

By the time we began putting together the more formal reference documents, Father's Day was finished, Historical Perspective was completed, and I was working on Known by Another Name. New characters had entered the stories, familiar characters had developed more detailed backgrounds, and Falcon Hollow itself had become considerably more complicated.

Some of those early reference documents were already outdated.

And when I started comparing them, I discovered that a few of them couldn't even agree with one another.

 

Which Version of Falcon Hollow Are We Talking About?

 

One of the problems with developing a fictional community over several stories is that decisions change. Sometimes you deliberately revise something because a better idea comes along. Other times, you forget what you originally established and unknowingly create a different version.

I'd managed to do a little of both.

Take Vin Caruso, for example. At one point, his background involved being a Marine military policeman who came to Falcon Hollow after Duke Mantz. Later, we'd established that Vin had joined the Falcon Hollow Police Department before Duke arrived.

That might seem like a small detail, but it affects their relationship, their professional histories, and how they interact in the stories. If Vin was already working in Falcon Hollow when Duke arrived, that needed to remain consistent.

Then there was Duke's nickname. Originally, I'd established that he'd acquired it in high school. But while developing Falcon Hollow Origins, I decided the nickname should come from his military experience instead.

That was an intentional change. I preferred the newer version because it worked better with the story I was telling. Unfortunately, some of the older reference material still reflected the original explanation.

And those were just the characters.

The Falcon Hollow Gazette apparently couldn't decide where it wanted to conduct business. At various points, I'd placed the newspaper near Civic Circle, farther up Main Street, and somewhere off Main Street on Raven Boulevard.

For a fictional newspaper, it certainly got around.

Street names weren't much better. Was it Lakeshore Avenue or Lakeshore Boulevard? Had I called it Lakeview at some point? I'd used different names while developing the town, and not every document reflected the same decision.

Individually, these weren't enormous problems. But when you start putting them together, they become a serious continuity headache.

And by this point, I was no longer writing a single novel. I was developing stories that shared characters, locations, and histories. A contradiction in one reference document could easily find its way into another manuscript.

Something had to give.

 

Putting Everything on the Table

 

Eventually, I decided we needed to stop adding information to the existing documents and figure out what we actually had.

So I gathered the reference material we'd created, uploaded the documents into ChatGPT, and essentially said, "All right, let's find the contradictions."

I had my handwritten notes beside me, along with the older character sheets and town descriptions. We began comparing information, identifying inconsistencies, and deciding which versions needed to be preserved.

It wasn't simply a matter of choosing the newest information.

Sometimes an earlier description was better, and we went back to it. Other times, a change we'd made while writing a later story was intentional and needed to replace the original version. And occasionally, we'd discover that something had changed without either of us remembering exactly when or why.

Those were the decisions we had to work through.

The process was part document review, part editorial discussion, and part detective work. We'd find one contradiction, settle on the version we wanted, and move on to the next.

I suppose there's something appropriate about an author of mystery novels having to investigate his own fictional town.

But that's essentially what we were doing. We were examining the information we'd accumulated, trying to establish what was correct, and determining which details should remain consistent as the stories continued.

The objective wasn't to create a perfect historical record of every idea I'd ever considered. It was to establish one Falcon Hollow that I could rely on going forward.

 

One Document Wasn't Going to Cut It

 

Once we started sorting through everything, another problem became apparent.

Even if we managed to reconcile all the contradictions, where were we going to put the information?

I suppose we could have created one enormous Word document containing everything about Falcon Hollow. Character histories, street locations, municipal departments, town history, writing rules, businesses, relationships, and whatever else we'd established.

But I could already imagine the headache that would create.

Every time I needed to check something about a character, I'd have to search through pages of unrelated material. A question about the police department might be buried somewhere between a restaurant description and the town's history. And as Falcon Hollow continued growing, that single document would become increasingly difficult to maintain.

We needed a better way to separate the information.

I don't remember the exact conversation where we decided how many reference documents to create or precisely how to divide the subjects. I wish I did, because it would probably make for an interesting story of its own.

What I do remember is recognizing that different kinds of information needed their own place.

The characters needed something more comprehensive than the old character sheets. The town's geography needed to be documented separately so I could keep track of streets, buildings, and locations. Falcon Hollow's government and institutions needed their own descriptions. And we needed a way to record the established decisions that shouldn't casually change from one story to another.

The Editorial Guide already served a different purpose. It addressed how I wanted the novels written, rather than the facts about the fictional world itself.

Gradually, what had been a scattered collection of notes and individual Word documents began taking the form of a reference library.

We developed the Falcon Hollow Character Bible, World Bible, World & Geographic Guide, and Canon, alongside the Editorial Guide. Each document had a particular purpose, and together they gave me a much more practical way to keep track of the town.

It wasn't about creating paperwork for the sake of paperwork. It was about being able to find the information I needed without spending half my writing time trying to remember where I'd put it.

 

A Town That Was Still Growing

 

One thing I hadn't fully appreciated when I began writing Father's Day was how much a fictional community could change as additional stories developed.

Characters who initially appeared in supporting roles could become more important. New businesses and locations would emerge because a scene needed them. The town government, police department, and other institutions would require more detailed explanations as their roles expanded.

And every time I established something new, there was another detail that needed to be preserved.

The reference documents didn't stop that development, nor were they supposed to. I still wanted the freedom to follow an idea when it occurred to me, even if that idea took me somewhere I hadn't originally planned to go.

What changed was how I handled the information afterward.

Instead of depending entirely on my memory, an old conversation, or a notebook that might have disappeared beneath the papers on my desk, I had designated places to record what we'd established.

That didn't mean the documents were always perfectly current. They still needed attention as new stories were written and decisions changed. But at least I had a structure that made maintaining them possible.

And perhaps more importantly, I had begun recognizing that some decisions carried more weight than others.

Changing the description of a room might be a relatively minor adjustment. Changing when a character joined the police department, where a major business was located, or how an important event occurred could affect several stories.

Those were the kinds of decisions that needed particular attention.

 

More Than Just a Collection of Notes

 

Looking back, creating the Falcon Hollow reference library was one of those developments I never anticipated when I started writing.

I wasn't trying to build an elaborate system for managing a fictional universe. I was trying to write mystery novels, and the town I'd created to support those stories kept getting more complicated.

Eventually, the original notes and character sheets simply weren't enough.

We had to review what we'd written, resolve contradictions, replace outdated information, and organize the results into something I could actually use.

And even after all that work, Falcon Hollow continued to surprise me. New characters appeared, familiar locations took on greater importance, and decisions made in one story sometimes affected something I wanted to do in another.

The reference library gave me a way to manage that growth without constantly starting over.

But it also raised another question I hadn't really considered when I began writing.

At what point does a detail in a fictional story stop being just an idea and become an established fact that the author needs to respect?

As it turned out, I'd been making those decisions for months without realizing I was creating a set of rules.

And that brings me to another part of this adventure: the rules I didn't know I was writing.

 
 
 

Comments


bottom of page