The Horror of the Missing Record

There is a particular kind of fear that only exists when something is missing.

Not lost.

Not destroyed.

Missing.

There is a difference.

A lost document existed once. Someone remembers reading it. There might be a reference to it in an email, a photocopy in somebody's desk, or an entry showing when it was removed from the archive.

A destroyed document leaves evidence of its destruction.

A missing document is different.

A missing document leaves a hole.

And sometimes the shape of that hole tells you exactly what should have been there.

The empty space

Imagine you are reading the records of an investigation.

There are twelve documents.

Document 01: Initial incident report.

Document 02: Witness statement.

Document 03: Scene photographs.

Document 04: Medical examination.

Document 05: Supplementary witness statement.

Document 06: Search log.

Document 07: Search log.

Document 08: Search log.

Document 10: Recovery report.

Document 11: Internal correspondence.

Document 12: Case closure.

You noticed it.

Of course you did.

There is no Document 09.

Nothing needs to tell you that Document 09 matters.

The archive has already told you.

Something happened between the final search and the recovery.

Someone recorded it.

And whatever they recorded is no longer here.

That is the horror of the missing record.

The writer hasn't shown you anything.

They have removed something.

And your imagination immediately begins trying to reconstruct it.

We trust records more than we realise

Most of our lives are documented.

Birth certificates.

Medical histories.

School records.

Employment files.

Bank statements.

Passports.

Flight manifests.

CCTV.

Phone records.

Receipts.

Emails.

Photographs.

Location histories.

We leave administrative debris everywhere we go.

This is so ordinary that we barely notice it.

If you stay in a hotel, there is a record.

If you board an aircraft, there is a record.

If you are admitted to hospital, there is a record.

If you die, there will be several.

Modern life operates on the assumption that things which happen leave traces.

That assumption is incredibly useful for horror.

Because the absence of an expected trace feels wrong.

Consider two statements.

Nobody knows where Daniel went.

And:

Daniel's access card records him entering the building at 21:14. There is no record of him leaving.

The second is worse.

The building has become a closed system.

The record establishes a boundary.

Daniel entered.

Daniel did not leave.

Therefore Daniel should still be inside.

The horror comes from the contradiction between the administrative record and reality.

We believe both.

They cannot both be true.

Something has to give.

Something should be here

The strongest missing records are not random.

They are expected.

A folder containing documents numbered 1, 2, 3, 5 and 6 immediately creates a question.

A security system retaining footage from every night except Tuesday creates a question.

A ship's log containing entries for every day of a voyage except 17 June creates a question.

A hospital patient whose file contains blood tests, medication charts and nursing observations but no admission form creates a question.

Nobody has to say:

THIS IS IMPORTANT.

The structure says it for you.

The reader understands the system.

Then the system fails.

This is one of the reasons bureaucracy works so well in horror.

Bureaucracy establishes patterns.

Forms repeat.

Reports follow templates.

Reference numbers increase sequentially.

Logs are completed at regular intervals.

Every boring piece of administrative consistency teaches the reader what normal looks like.

Which means eventually you can remove one thing.

And the reader will feel it.

The document that everyone has read

There is another version of this technique that I love.

The missing document that everyone else has seen.

You never show it to the reader.

Instead, you show its shadow.

An email:

I've read Carter's report. We need to discuss this before anything is circulated.

A second:

Agreed. Do not forward the attachment.

Then:

I've spoken with Carter. He understands why the report cannot remain on the system.

Then perhaps:

Please confirm all copies have been destroyed.

We never see Carter's report.

We don't need to.

In fact, showing it might make things worse.

Not worse for the characters.

Worse for the horror.

Because whatever I write has limits.

The missing document does not.

The reader can imagine something perfectly tailored to frighten them.

All I need to provide is the reaction.

This works particularly well when the people reacting to the missing material are normally restrained.

A terrified person saying something is frightening tells us very little.

A pathologist saying:

I would prefer not to examine another specimen.

is different.

A police officer writing:

No personnel are to enter the property alone under any circumstances.

is different.

A researcher writing:

We have discontinued attempts to reproduce the result.

is different.

Professional language acts as a measuring instrument.

The more controlled the person usually is, the more significant the deviation becomes.

We still haven't seen the missing document.

But now we know what it did to the people who did.

Deleted is not the same as missing

Deletion tells a story.

Someone removed something.

That gives us an actor.

FILE DELETED — 14:32

Immediately, we can ask who deleted it and why.

But sometimes I prefer something quieter.

NO FILE ASSOCIATED

That's different.

There should be a file.

The database expects a file.

The reference exists.

The metadata exists.

Perhaps the title exists.

Perhaps the creation date exists.

But the document itself does not.

Now we don't even know whether someone removed it.

Maybe it was never uploaded.

Maybe the system corrupted it.

Maybe somebody made a mistake.

Those are all perfectly reasonable explanations.

And reasonable explanations are useful.

Horror needs somewhere for scepticism to live.

If every strange event immediately proves the supernatural, there is very little room for dread.

The missing record gives the reader an escape route.

Probably an administrative error.

Probably corruption.

Probably somebody forgot.

Probably.

Then you do it again.

One missing record is an error

This is where absence becomes evidence.

One missing CCTV recording means nothing.

Hard drives fail.

Two missing recordings are interesting.

Three recordings, from three different systems, covering exactly the same seventeen minutes?

Now we have a problem.

This is one of my favourite structures in documentary horror.

You don't prove the impossible with one extraordinary piece of evidence.

You prove it with several ordinary pieces of evidence that should have nothing to do with each other.

A police report is missing.

Fine.

The ambulance dispatch recording from the same period is missing.

Odd.

The local radio station's archive contains a blank section at the same time.

Very odd.

A private answering machine recorded continuously through the incident.

There is seventeen minutes of tape.

There is just nothing on it.

Now absence itself has become the event.

Something didn't merely happen.

Something happened that records refuse to contain.

That is much more interesting.

The record that proves someone is gone

Missing records can also work in reverse.

Sometimes the document exists.

The person doesn't.

Imagine finding an employee record for someone nobody remembers.

Their name appears on rotas.

They received a salary.

They attended meetings.

Their access card opened doors.

There are emails addressed to them.

There are emails from them.

Their annual appraisal was completed.

They took nine days of annual leave.

They worked there for eleven years.

But ask anyone in the office:

Who is Peter Vale?

Nobody knows.

Now the records are doing something much worse than failing.

They are insisting.

The system says this person existed.

Human memory says they didn't.

And systems are supposed to be the backup for human memory.

That's why we keep records.

People forget.

Paper doesn't.

Databases don't.

Photographs don't.

Until they do.

The reader becomes the investigator

There is another reason I like missing documents.

They give the reader something to do.

A traditional horror story tells you what happened.

Documentary horror can make you discover what happened.

You notice the numbering.

You compare timestamps.

You realise an attachment mentioned earlier isn't included.

You remember somebody referring to an interview you haven't read.

Nobody announces the mystery.

You find it yourself.

That changes the relationship between the reader and the story.

You aren't sitting beside the campfire anymore.

You're opening the box.

You're sorting the papers.

You're noticing that the inventory says 28 photographs when the envelope contains 29.

And perhaps you wish you hadn't noticed.

That moment matters.

Because the discovery belongs to you.

The author didn't point at it.

The narrator didn't explain it.

You found the discrepancy.

Which means, for a moment, the fictional archive becomes something you are genuinely examining rather than merely reading.

Leave the space empty

There is always a temptation to explain.

Especially in horror.

What was in Document 09?

Who deleted the CCTV?

What happened during the missing seventeen minutes?

Who was Peter Vale?

Eventually, surely, we have to tell the reader.

I don't think we always do.

Sometimes the hole is the thing.

You can describe its edges.

You can show what came before it.

You can show what came after.

You can show people desperately trying to stop anyone from asking what used to be there.

But the centre can remain empty.

Because once the missing document is recovered, it becomes just another document.

It has words.

It has boundaries.

It has an ending.

While it is missing, it contains everything.

And somewhere in that empty space is whatever the reader was hoping you wouldn't show them.

So don't.

Leave the number in the index.

Leave the gap in the archive.

Let someone mention the attachment.

Let the system insist that something should be there.

Then move on.

The reader won't.