2002 Ghost History Conference Guests and Itinerary

The 2002 conference page is the kind of record that survives by accident. It tells you who spoke, where the day was held, what it cost to get in, and nothing more. It does not tell you how the room felt.

The details cited in this entry were checked on folklore studies.

If you have ever tried to reconstruct an evening from a programme alone, you already know the problem. A printed itinerary is a skeleton. It gives you order and timing, and it leaves out the parts that people actually remember. That is the shape of the 2002 conference record as it survives online, and it is worth reading slowly because it shows exactly what a ghost conference looked like at the turn of the century: a small guest list, a fixed schedule, a ticket price, and a location.

What the 2002 conference page actually records

The page is an event notice, not a report. It lists guests, sets out an itinerary, names a location, and states what tickets cost. Those four things are the spine of it. Everything else you might want, including how many people attended and what anyone said, has to be found somewhere else or not at all.

That is normal for event pages from that period. They were written before the event, to get people through the door. They were not written afterwards to explain what happened. So the page functions as a promise rather than a record, and reading it as a promise changes what you notice. You stop looking for conclusions and start looking at the arrangement: who was placed where in the day, how the programme was broken up, and what the organisers thought a paying audience wanted.

Why an itinerary tells you more than a summary

An itinerary is a set of editorial decisions. Order implies importance. Length implies confidence. A talk given a long slot is a talk the organisers believed in, and a short slot near the end is often a talk that was added late or kept deliberately light.

For anyone tracing how Ontario ghost folklore was presented to the public, that structure matters more than the transcript usually would. Long after the speakers have stopped giving the talk, the shape of the day still shows what counted as a proper conference programme in 2002. Compare that with how ghost stories get told now, in walking tours and community radio segments, and the difference is not in the subject. The subject is the same. The difference is the format, and format is what an event page preserves best.

What does a ticket price tell you about an audience?

A ticket price is a filter. It says who the organisers expected to walk in, and it says something about the scale of the venue they had booked. A low price suggests a room filled with local members and curious neighbours. A higher price suggests a paying public and a programme built to justify the cost.

The 2002 page publishes the ticket cost alongside the programme, which is why the two should be read together. The price is not a fun fact. It is a clue about how the day was funded and who was welcome. When an event runs on ticket money, the programme has to hold an audience for a full day, and that pressure shows up in how the itinerary is paced. You can trace it in the breaks, in the order of the talks, and in whatever was placed last to send people home satisfied.

Guests, and the limits of a guest list

A guest list is the most human part of any event page, and also the most fragile. It gives you names and, sometimes, a line about what each person was known for. It does not give you what they said.

This is where an event record becomes useful to folklore research rather than just nostalgia. A name attached to a subject shows you who was considered an authority at that moment, in that place. That is a historical fact about a community, not about the paranormal. It tells you which voices a paying audience in 2002 was expected to trust, and it lets you follow those voices forward or backward through other records. If you are tracing a single haunting story across decades, knowing who was on the stage in a given year is often the thread that keeps the story from breaking.

For a wider view of how this kind of account gets gathered and kept, the field is studied under a name of its own: folklore studies treats tales, customs and beliefs as things a group transmits and maintains, which is exactly what a conference programme documents without meaning to.

Location, and why the building is part of the story

Where an event is held shapes what can be held there. A hall with a stage suits a lecture. A smaller room suits a discussion. A historic building adds its own atmosphere whether or not anyone mentions it, and organisers know this.

When the venue is itself part of Ontario's older built history, the choice is rarely accidental. The room becomes part of the evening's argument. You do not need a single word of the talks to understand that, because the location statement on the page does the work. Ontario's haunted places and the stories they keep are usually buildings first and legends second, and a conference held inside one borrows that weight for free.

How the day was broken up

Programmes of this kind tend to follow a pattern that has barely changed in twenty years. A welcome, a run of talks, a break for food or air, more talks, then a closing item. The 2002 itinerary is built the same way, and that familiarity is the point.

What changes between years is the content of the slots, not their arrangement. That is why the itinerary is more reliable than memory when you are trying to date a story. Memory compresses. It puts the best talk first and forgets the order of everything else. The printed schedule does not compress. It sits there with its times attached, and if you want to know whether a particular account was circulating in Ontario in 2002, a slot on that schedule is firmer ground than anyone's recollection of a good evening.

What the page leaves out

It leaves out the room. No attendance figure, no reaction, no follow-up, no indication of whether the programme ran to time. An event page cannot tell you whether the day worked.

It also leaves out the afterlife of the talks themselves, which is the part folklore research actually cares about. A story told once from a stage either enters circulation or it does not. If it does, it turns up later in other settings: in a newsletter, in a broadcast, in a tour guide's script. If it does not, it stays where it was said. The 2002 page cannot tell you which happened, but it gives you the date and the voices, and that is enough to start looking. Ontario's witness reports follow that same route from a single telling into wider retelling, a path traced in this site's account of how Ontario's witness reports become retold legends.

The value of an ordinary event record

Most event pages are unremarkable, and the 2002 conference page is one of them. That is what makes it worth keeping. The dramatic years get written about. The ordinary years get a programme with a ticket price and a venue, and if nobody saved that programme, the year vanishes from the record entirely.

Places like Spadina House show the same pattern at a much larger scale, where the building's public history and its ghost stories have been layered together for decades, as covered in the archive on Spadina House and Toronto's historic house stories. The mechanism is identical. Something is presented to an audience, the audience carries it away, and the only proof that the presentation happened is the notice that advertised it.

So if you have a programme from a local ghost event, a 1990s newsletter, or a ticket stub in a drawer, that slip of paper is doing the work this 2002 page does. It holds one day still. Archive it before it goes, and check the genealogy methods used for tracing Ontario house histories, which apply just as well to tracing the events held inside those houses.