The Buried Footnote

Investigate what is missing

A Public-Records Request Cannot Recover a Record That Was Properly Destroyed

Access law governs the route to existing executive records; retention rules govern when the records exist, are held, transferred, or destroyed. A missing document can present an exemption, search, or lifecycle question, and those are not the same bad afternoon.

Records covered

Public-records access and records retention touch when a request searches for a record whose lifecycle status determines whether it can be produced, transferred, or certified as destroyed.

Establishes / only indicates

The absence ledger establishes whether access, retention, hold, transfer, or destruction rules govern the missing item; it only indicates the most plausible documentary explanation for non-production.

Declines to state

It declines to claim that non-production proves unlawful destruction, nonexistence, or an exemption.

Predictive coding.

E-discovery dashboards.

A forensic timeline travelling from a project mailbox into the consciousness of a deputy minister.

Somebody will sell you a platform that makes every deleted PDF feel personally accountable. It will have a button labelled “insights.”

Then there is the schedule.

The schedule has a series, an authority, a cutoff, a final fate, and the warmth of a municipal snowplough.

It doesn’t know what a scandal is.

It knows whether the Norchester Footbridge email, or FINAL_final_revised_USE_THIS.xlsx, reached a prescribed point. And whether ordinary disposition was allowed.

Your request and your schedule are adjacent systems with separate mandates.

The request seeks a record held or controlled by the body.

The schedule assigns temporary destruction or permanent transfer.

A hold interrupts ordinary disposition. An exemption governs release of something still held.

They touch.

They do not merge.

The request is not a time machine

Start with your record hypothesis.

A request for a final inspection report and project emails about a named bridge, between 1 January and 30 June, identifies the public body, the likely program office, the project or contract number, the date range, the format, and a fee ceiling.

It seeks existing records.

Not an explanation for a decorative lighthouse bollard, and not a newly manufactured spreadsheet.

Your access process gives you four moments.

Acknowledgement.

Determination.

Production.

Closure.

An acknowledgement says only that the request arrived.

California requires a determination within 10 calendar days, with unusual circumstances adding no more than 14.

A federal US agency ordinarily has 20 working days.

Neither clock is a delivery date. A calendar is not a loading dock.

Coverage has three variables you have to fix.

Institutions bound.

The definition of record or document.

Level of government.

A statute may reach executive agencies and leave courts or legislatures to separate regimes.

It reaches records held or controlled in the institution’s functions.

Not interrogatories.

Not policy defences.

Not the actually useful report that never existed.

Your ordinary search has three passes.

Locate the systems.

Run queries or manual retrieval.

Test results for responsiveness.

Keep your repositories, your terms, your date interval, your attachments and your metadata.

A mailbox, a shared folder and a contract file can all be in scope.

An email with the bridge in a signature block can be nonresponsive. Its attachment without the keyword can be responsive.

Documents have families and poor filing habits.

A blank response has offices

Ask whether anybody located a responsive record before you reach for exemption.

Responsiveness is scope.

Exemption is disclosure.

The US federal framework gives you 9 FOIA exemptions, and most discretionary withholdings require foreseeable-harm analysis.

None of that explains a search failure, a transfer, or a routine destruction. It governs material still under consideration for release.

Review applies two filters for you. Whether a rule covers the material, and whether nonprotected information can be segregated.

Regulation 1049/2001, Article 4, requires release of the remaining parts where only part is covered.

Its ordinary exception period runs no longer than 30 years, subject to continuing protections.

A partial release is an output.

A black rectangle over selectable text is a costume.

Your decision letter has three elements. The records or a delivery link. An explanation of withholding or absence.

Review rights.

A partly withheld US DOJ page is ordinarily marked with its exemption. A wholly withheld page ordinarily tells you volume.

That explains an access decision.

It does not revive a series destroyed before your request arrived.

So the useful follow-up names the missing custodian, attachment, repository, series or interval. Then asks whether transfer or destruction was checked.

Canada’s federal process ordinarily requires an answer within 30 days.

A failure by the statutory or validly extended date is a deemed refusal, and you generally have 60 days after learning of it to complain.

Delay is a process condition. It is not a conclusion about search, lifecycle, or exemption.

The schedule has two exits

Retention began long before your request.

Its first variable is final fate, and it has exactly two values. Temporary destruction, or permanent transfer.

An approved authority assigns it after appraisal. Not a system owner with an expensive shared drive and a hunch.

One programme can hold permanent decisions, temporary drafts and case files, and a permanent sample or summary.

One department, several fates.

Your inventory starts with four fields.

Business function.

Records created.

System or location.

Accountable owner.

Then it adds format, date span, growth, restrictions and authority.

Your material groups by the same disposition authority and date.

A group can include a primary record, an export, attachments, paper, chat, and a warehouse extract.

Establish the authoritative copy before you call another one a duplicate.

Your schedule’s clock has three cutoff families.

Age-based, event-based, block-based.

Age-based rules count from creation or receipt. Event-based rules count from case closure or supersession.

Block-based rules group a calendar or fiscal period before later action.

“Destroy when 3 years old,” “destroy 7 years after case closure,” and “transfer 15 years after supersession” are three different machines.

“End of fiscal year plus 5 years” is not “5 years after creation.”

A retention number without its cutoff event is a date wearing a fake moustache.

NARA gives federal permanent material a range of 15 to 30 years after cutoff, generally 30 years old or older.

Security-classified records ordinarily aren’t approved before 25 years, and transfers below 15 or above 30 need more information.

Those figures exist to show you one thing. Transfer and request response live on different calendars.

A hold stops the clock

A hold makes your calculated destruction date wait.

Its scope has five dimensions you have to set.

Matter.

Custodians.

Repositories.

Interval.

Subject or record type.

“Preserve project communications” is a policy sentence.

A working control needs mailbox names, workspace IDs, paths, account status, and enough exceptions to reach deletion, backup expiry, inactive accounts and third-party systems.

Your routine has five actions.

Define scope.

Identify custodians and repositories.

Suspend disposition.

Send and track notices.

Monitor acknowledgement and collection.

Your register keeps the start date, the scope version, the series, the owners, the exceptions, and the release authority.

NARA’s model suspends the normal cycle on receipt.

Your question is whether the series and the repositories were blocked before disposition.

Release reverses your control without an automatic purge.

Get written release.

Update controls.

Identify material beyond ordinary retention.

Resume disposition review.

If three matters overlap one mailbox, releasing one does not remove the other two.

The system has to look again.

Transfer, with luggage

Transfer runs you through seven checks.

Permanent designation.

Eligibility.

Holds and restrictions.

Inventory.

File and metadata validation.

Request.

Receiving-archive acceptance.

For federal electronic records, the transfer request identifies series, date span, authority and legal-transfer type.

That’s custody.

Not deletion.

Your package has four variables.

Authority.

Inventory.

Technical representation.

Descriptive metadata.

Files can need checksums, directories, encodings, data dictionaries, schemas, code lists, or query context.

A records-centre box is 1 cubic foot in NARA transfer and billing guidance.

Paper has consequences.

And non-production can mean several things to you.

No responsive item located.

A transfer.

Proper destruction.

An exemption for a still-held passage. Or a narrow lawful refusal to confirm or deny existence.

Those are not synonyms.

Each has its own authority, dates and records.

Destruction needs a receipt

The temporary route runs you through eight checks.

Identify the candidate population.

Validate series and authority.

Calculate cutoff and due date.

Search holds and restrictions.

Get approval.

Destroy by a suitable method.

Receive evidence.

Enter a certificate.

Freeze the candidate population before review.

Otherwise your certifier signs a moving target.

Cross-cut shredding, pulping, secure erase, cryptographic erasure and certified media destruction are methods.

Not authorities.

Method shows processing, not eligibility. Schedule shows eligibility, not that every copy was reached.

Your certificate connects them.

Event ID, series and authority, dates or identifiers, volume or count, method, location, execution date, certifier, exceptions, vendor certificate.

Unauthorized destruction leaves you a different trail.

The federal report includes description, volume and dates if known, circumstances, attempted salvage or reconstruction, and safeguards.

It establishes an incident record. Not the cause, not the completeness, and not the legal outcome for every missing item.

Four passes, then stop

Your useful method is neither “assume cover-up” nor “assume schedule.”

Start with the request’s named series, custodians and date interval.

Keep your acknowledgement, determination, production and closure in separate rows.

Then compare the response against the actual lifecycle material.

Schedule version.

Series code.

Cutoff trigger.

Disposition date.

Hold status.

Transfer receipt.

Destruction certificate.

REQUEST
body | custodians | named series or project | date interval | received date
acknowledgement | determination | production | closure

SEARCH AND ACCESS
repositories | queries or retrieval | responsive set | exemption or severance basis
not-found explanation | review rights

LIFECYCLE
series code | schedule version | cutoff event | final fate | hold status
transfer request or receipt | destruction event ID | certificate | limitation

Run four passes over it.

Scope, access, lifecycle, evidence.

Scope compares your request against the search universe.

Access identifies a release, a partial release, a withholding, a no-records result, or a narrow no-confirmation response.

Lifecycle tells you temporary, permanent, hold, transfer, or destruction eligibility.

Evidence asks whether the schedule, the register, the receipt or the certificate identifies the same population and the same dates.

It measures paperwork, not plots.

What the ledger says

Call it the absence ledger.

It keeps your possible explanations separate, and dated.

It cannot recover a properly destroyed record. It cannot prove nonexistence, a perfect search, a complete hold, or a lawful destruction.

It shows you which controlled system should answer your absence, and whether that system left a record.

A smaller claim, with somewhere to put its shoes.

The procedure

  1. An acknowledgement, determination, production, and closure are separate stages of a public-records request.
  2. A focused request identifies likely custodians, a named series or project, and a date range so the search can be tested.
  3. Coverage and responsiveness are determined before an exemption is applied to a record or passage.
  4. A retention period is incomplete without its cutoff event, series authority, and final fate.
  5. A hold is bounded by matter, custodians, repositories, time interval, and subject or record type, and it suspends ordinary disposition.
  6. Permanent transfer and temporary destruction are separate lifecycle paths with separate records of control.
  7. A destruction certificate identifies the population, authority, dates or identifiers, method, execution, and exceptions rather than merely saying that material was deleted.

Questions

Does a public-records request make an agency find a document it already destroyed?
No. Public-records access generally reaches records that the public body holds or controls; it does not require the body to recreate a record that was properly destroyed under an applicable disposition authority. A response can still require a search and an intelligible explanation. The relevant records question is whether the item was responsive, held, transferred, lawfully destroyed, or subject to another access rule.
What is the difference between an acknowledgement and an actual records decision?
An acknowledgement records that the request arrived and can assign a reference number. A determination states the institution’s disclosure decision, while production delivers records or a link to them. Closure records the completed response and review rights where applicable. California requires a determination within 10 calendar days, with unusual circumstances adding no more than 14 days; that determination deadline is not necessarily the delivery date.
How should a request name records so the search can be checked?
A focused request identifies the public body, likely program office or custodians, a named project or record series, a date range, and the preferred delivery format. It asks for existing records rather than an explanation or a newly created spreadsheet. The search can then record repositories, queries, manual retrieval, attachments, metadata, and the basis on which records were treated as responsive.
Is a missing record automatically an exemption?
No. Coverage and responsiveness come before exemption analysis. A record can be outside the request’s scope, not located after a search, held by another body, transferred to archives, destroyed under a schedule, or withheld under a specific access rule. In the U.S. federal framework there are 9 FOIA exemptions, but an exemption label does not substitute for identifying the relevant record and legal test.
What does a retention period need besides a number of years?
A retention rule needs the record series, approved authority, cutoff event, final fate, and any hold status beside the interval. The three common cutoff families are age-based, event-based, and block-based. “Five years after creation” differs from “end of fiscal year plus five years,” and a case file can use closure rather than the date of each individual document.
Can an agency destroy a record while a legal hold applies?
A hold suspends ordinary deletion and disposal for its defined scope. That scope has five dimensions: matter, custodians, repositories, time interval, and subject or record type. The responsible records process records the hold start date, affected series, owners, exceptions, and release authority, then reconciles those controls with disposition runs before records are destroyed.
Does releasing one hold mean the records can be deleted immediately?
No. A hold release is a controlled reassessment, not an automatic purge. The authority that imposed the hold supplies a written release; the register and system controls are updated; records beyond their ordinary retention date are identified; and normal disposition review resumes. If 3 matters overlap the same mailbox or case set, release of one matter does not release the other two.
What happens when a requested record was transferred to an archive?
A permanent record follows a transfer path rather than a destruction path. The process confirms permanent designation, eligibility, holds and restrictions, inventory, files and metadata, transfer request, and receiving-archive acceptance. A transfer request identifies the series, date span, disposition authority, and legal-transfer type. Transfer can change where a record is held without showing that it has ceased to exist.
What proves that a temporary record was actually destroyed under a schedule?
A defensible disposition record identifies the candidate population, series, authority, cutoff and due date, hold review, approval, method, execution evidence, and certificate entry. The certificate carries the disposition event ID, covered dates or identifiers, volume or record count, location, execution date, certifier, exceptions, and vendor certificate where applicable. A statement that material was securely deleted does not identify eligibility.
Can a records request force a public body to explain why a policy decision was made?
Not ordinarily. Public-records access seeks qualifying existing records held or controlled by the public body; it does not generally require the body to answer questions, defend a policy, compile a new report, or acquire a document it neither possesses nor controls. A request can identify decision records, emails, reports, or other existing materials that may contain the recorded reasons.
Does a late response prove that records were destroyed or withheld?
No. A late response is a procedural issue, not a conclusion about the lifecycle or content of a record. In Canada’s federal system, a missed statutory or validly extended response date can be a deemed refusal, and a requester generally has 60 days after learning of the missed deadline to complain to the Information Commissioner. That process can examine delay, search, withholding, or request treatment.
What is the smallest way to check why a requested record was not produced?
The smallest check preserves the request scope and then compares the response with the applicable series authority, cutoff event, hold status, transfer record, or destruction certificate. It keeps acknowledgement, determination, production, and closure separate. The result can identify whether access, search, retention, hold, transfer, or destruction rules govern the missing item; it does not prove an unlawful destruction or an exemption.