Four Systems, Eleven Ring Binders: ‘The Service Does Not Maintain Such A List.’
The refusal quoted in every account of park disappearances is true, and it is a description of an IT estate. A 1998 schedule then destroys unit incident reports seven years after a case closes.
LAKEWOOD, Colorado — "The Service does not maintain such a list."
That sentence, or one very close to it, is the load-bearing fact in the whole literature of park disappearances. It is quoted, almost always, as an evasion.
We spent twenty-two months and nine requests establishing that it is a description of an IT estate.
Nine Requests
We began at a single park, because one park is a small thing to ask for. It answered in six weeks with 41 incident records and a note saying it could not speak for anywhere else.
The second request went to the region and was refused: the region does not hold unit incident files.
The fifth was refused as unreasonably burdensome. The sixth was narrowed to a count rather than the records themselves and was refused on the ground that producing a count would require producing the records.
The ninth went to the national records officer. It came back with the sentence in the headline, and with something no request of ours has ever produced before: a cost estimate of $1.41m and 3,900 staff-hours to compile one list, itemised by unit, together with a two-page explanation nobody had asked for.
The explanation is the story.
Four Platforms, Eleven Filing Cabinets
Thirty-one units run the current incident system, in service since 2011. Fourteen record incidents inside a computer-aided dispatch system, where an incident is a field on a call rather than a record in its own right. Six use law-enforcement case management with a different schema and restricted access.
Eleven units keep paper. Ring binders, by year, at the unit.
And one park is still running a flat-file database installed in 1996. A regional systems inventory from 2007, released to us apparently by accident, lists it with a planned retirement date of 2009. We telephoned the park in August. It is on one machine, in one office, and the chief ranger there described the arrangement to us as "fine, so long as nobody moves it".
Item 34-C
Under the 1998 records-retention schedule, incident reports held at unit level are classed temporary and destroyed seven years after case closure, unless a case remains open or a hold has been placed.
That single line explains a graph that appears in almost every published treatment of this subject: the record thins going backwards, and the thinning is read as an era when fewer people went missing.
It is not. It is an era that has been through the shredder on schedule. It is also the reason the early years of the file this newspaper built by asking all 63 units separately are a map of what survived rather than of what happened.
Our own vault holds a useful contrast in PX-2179 — one British police force that kept its wildlife-report log for thirty unbroken years, 604 pages of it, and released the lot for £310. The difference is not diligence. It is that somebody, once, wrote a schedule that said keep.
One Records Officer
There is one records officer for all 63 units. Her name is Marion Estrellado-Fyfe and she spent fifty-one minutes on the telephone walking our reporter through the 1998 schedule, line by line, without once suggesting we were wasting her time.
At the end she asked whether we intended to print the retention code. People write to her about this, she said, twice a month, and they are not cranks, and she would like somewhere to point them.
So: item 34-C. Temporary. Seven years from case closure.
Her reply to this piece is printed below in full, and she is sharper with us than we were with the agency.
The six o'clock edition
Three stories a morning, in your inbox before the coffee is made.
Sources & Method
We filed nine requests over twenty-two months, each narrowed on the specific ground the last one was refused, and published every request and every response as it arrived rather than at the end. Then we read the 1998 retention schedule beside the 2007 systems inventory with the officer who administers both.
Who we spoke to
- Marion Estrellado-Fyfe, Records officer for the service, all 63 units. Telephone, fifty-one minutes, with a follow-up in writing; she asked to be named and asked that the retention code be printed 6 August 2026 Walked our reporter through the 1998 schedule line by line. Her reply to this piece is printed in full below.
- Nine freedom-of-information responses, One park, two regional offices, the national records officer. Filed by this newspaper between October 2024 and August 2026, each request narrowed on the previous refusal; all nine published entire 2024–2026 The fifth was refused as unreasonably burdensome. The ninth arrived with a cost estimate nobody had requested.
- Records-retention schedule, 1998, Item 34-C, incident and case reports at unit level. Public document; read against the nine responses and against the 2007 regional IT retirement schedule Read July 2026 Classes unit incident reports temporary. Seven years, unless a case is open.
- Regional IT retirement schedule, 2007, Systems inventory for one region, with planned decommission dates. Released in the seventh response, unredacted, apparently by accident Received March 2026 Lists the 1996 flat-file database with a retirement date of 2009. It was still in service when we telephoned the park in August.
- Prof. Aurelie Osterkamp-Nwosu, Records management, and a former government schedule-writer. Interviewed by video call; read all nine responses before speaking to us July 2026 Says a destruction schedule that outlives its systems is the ordinary condition of government, not the exception.
Documents
- PX-2179 — Thirty years of one police force's wildlife-report log, 1996–2026, with the 1980 capture file accepted
What we could not confirm
- How many incident reports have actually been destroyed under item 34-C. Nobody counts what is destroyed, because a destruction certificate records a box and a date range rather than a number of records. The service could not tell us and did not pretend it could.
- Whether the four platforms could in fact be joined. Two vendors told us it is straightforward; the service says the identifiers do not survive the join and it has never tried. We have no way to test either claim without the systems in front of us.
- Whether the 2007 IT schedule was released deliberately. It came in a batch of 340 pages with everything else redacted to the usual standard. We asked; we were told the release was reviewed and stood. That is not the same as being told it was intended.
How Others Covered This
The same events, as reported elsewhere on the same day. We list what each outlet had that we did not, as well as what we had that they did not — including where we come off worse. Why we print this.
-
The Hollow Post$1.41 Million To Tell You Who Went Missing
Read the cost estimate as a price put on silence, and the seven-year destruction rule as the mechanism.
Had that we did not
The estimate itself, quoted accurately, and the fact that the agency volunteered it. That is a real disclosure and they were first to it.
Left out
The itemisation. The estimate is broken down by unit and eleven of the lines are somebody driving to a park to open a filing cabinet.
-
The Continental WireAgency Says No Central Record Of Park Disappearances Exists
Ran the response as issued, in 190 words, with a line of context and no question put back.
Had that we did not
The sentence, correctly attributed, on the day it arrived. Nobody else had it for nine days.
Left out
That the sentence is a description of an IT estate and not a position, which one telephone call would have established.
-
They Buriedthis newspaperFour Systems, Eleven Ring Binders: ‘The Service Does Not Maintain Such A List.’
Escalated one refusal at a time until the refusals explained themselves, then went and read the retention schedule line by line with the person who administers it.
Had that we did not
All nine requests and all nine responses, the itemised estimate, and the retention code, printed because she asked us to print it.
Left out
We put one civil servant's fifty-one minutes in our story because it made us look diligent. She is the only records officer for 63 units and our nine requests were nine of her afternoons. — V. Ashcombe-Doyle, standards editor
Right of Reply
They Buried contacted Marion Estrellado-Fyfe, records officer on 11 August 2026 with the full draft, the figure and the two schedules, and eight days to answer. Replied 19 August 2026. Printed entire and unedited. She asked for no changes to the piece and made none to her own letter.
Thank you for sending the draft. I have three objections and one request, and I would like all four printed.
First: the word incompatible is doing something in your piece that it does not do in my office. Those four systems are not incompatible in the sense of having failed. Each of them was bought for a purpose and each of them meets that purpose. A dispatch system exists so that somebody in trouble at nine at night gets a unit sent to them. It records an incident as an attribute of a call because that is what it needs in order to send the unit. It is not broken because it cannot also serve as a national statistical register of the missing. Nobody ever asked it to be one. If you want it to be one, that is a decision somebody has to make, fund and specify, and I would welcome it, and it has never once appeared in a budget I have seen.
Second: the estimate. I itemised it because I would rather people saw what the money is than argue with a round number, and I see that you have printed the itemisation, which I am grateful for. But please do not let it be read as a price. Eleven of those lines are a person driving to a park and opening a cabinet, and the reason it is expensive is that the work is genuinely there and genuinely has to be done by hand. It is not a toll.
Third, and this is the one I mind: your piece has fifty-one minutes of my time in it, and a sentence about how I sounded. I did not give you those minutes to become a character. I gave them because the alternative was that you would write about the schedule without understanding it, as most people do.
Now the request, which is the reason I telephoned you back at all. Print the code. Item 34-C of the 1998 schedule. Temporary, seven years from case closure, retained beyond that only where a case remains open or where a hold has been placed.
I receive letters about this perhaps twice a month, and they are not from cranks. They are from a woman in Ohio whose brother went into a park in 1991, or a man who has been told his father's file cannot be located. They believe a record was taken away from them by somebody who decided to take it away. What actually happened is that a schedule written in 1998, by people who had never heard of their family, classed a category of paper as temporary, and a clerk in 2001 did exactly what the schedule said. That is worse in some ways and better in others, but it is at least a thing a person can be angry at correctly, and they cannot be angry at it correctly until they can read it.
So: 34-C. If you print nothing else of mine, print the number, and I will have somewhere to point them.
Published unedited under our right-of-reply guarantee.
How was this story?
We publish the result, whatever it is. Reader verdicts appear on the front page and in our newsroom metrics.
Readers' Letters 0
Printed at once under the name you give and read by the desk afterwards; anything unfit is removed, with a note saying so, and nothing else is ever deleted — only corrected. Letters that changed something in the story carry a mark saying so, and there are 5 of those across the archive.