The preexisting electronic documents exception

The short version

The three conditions

The exception is codified at 28 CFR § 35.202 (Source: 28 CFR § 35.202 ) . Each condition has a specific meaning:

Condition 1: Conventional electronic document

The rule applies the exception only to "conventional electronic documents." DOJ's preamble and fact sheet identify this category as PDF, Word, Excel, and PowerPoint files. The exception does not cover web pages, web applications, mobile app content, or other non-document web content. A document embedded in a web page (an iframe, an HTML5 viewer) is still a document for purposes of the exception, but the surrounding web page is not.

Condition 2: Created before the compliance deadline

The reference date is the entity's applicable compliance deadline, not the rule's adoption date. For entities serving 50,000 or more people, that date is April 24, 2026. For entities serving fewer than 50,000 people, and for all special district governments, that date is April 26, 2027. A document created after the relevant deadline cannot qualify for the exception, regardless of its current use.

Condition 3: Not currently used

This is the operative condition and the source of most misapplication. "Currently used" means used by the entity in connection with applying for, gaining access to, or participating in the entity's programs, services, or activities. It is broader than "actively distributed." A document does not have to be currently being downloaded to count as currently used; it has to be currently relied on, referenced, or required by some program or service.

What qualifies

A document that satisfies all three conditions can qualify. Examples that commonly meet the test:

• A 2017 grant report submitted to a funder under a closed grant cycle, retained for historical record but not referenced in current grant activity
• A 2018 ISER section that has been superseded by a more recent accreditation submission and is no longer the operative document
• A 2015 special-meeting agenda for a committee that no longer exists and whose work product is not currently referenced
• An archived copy of a prior-year tax-form filing retained for retention compliance but not relied on in current operations
• A withdrawn policy that has been replaced and is retained only for historical reference

In each case, two facts are doing the work: the document was created before the deadline, and the entity is not currently using it for any program-related activity. Both facts have to be documentable.

What does not qualify

The exception does not reach the following, even though they may colloquially seem "preexisting":

Documents linked from current pages

If a current page on the entity's website links to a 2018 document as supporting material, reference material, or required reading, the document is currently used. The exception does not apply.

Forms in current use

A registration form, application form, permit form, or public records request form created before the deadline that is still in current use for current registrations or applications is not preexisting in the regulatory sense. Use of the form in a current program is precisely what the "not currently used" condition excludes.

Catalogs and schedules still distributed

A college catalog created before the deadline that is still the current academic year catalog, or a class schedule still being used to enroll students, is currently used and does not qualify.

Policies that are the controlling reference

A 2014 board policy that remains in effect and is the controlling reference for current decisions is currently used regardless of its creation date. The fact that it is old does not make it preexisting.

Documents referenced in current notices

A document referenced in current public notices, current meeting agendas, or current required postings is currently used. The exception does not apply.

The "not currently used" test

Because the third condition is the operative limit, it is worth working through the test carefully. The rule language is "not currently used by the entity for activities such as applying for, gaining access to, or participating in the entity's programs, services, or activities."

A workable test asks four questions about the document:

1. Is it linked from a current page? A link from a current page is evidence of current use. The exception likely does not apply.
2. Is it referenced by a current program? If a current program, service, or process requires consulting the document, the exception does not apply.
3. Is it the controlling version? If the document is the current operative version of a policy, schedule, form, or notice, the exception does not apply.
4. Does it exist purely as a record? If yes (retained only for retrospective inspection, audit, or historical reference), the exception may apply.

A document that fails any of the first three tests is currently used. A document that passes all four (no current links, no current program reference, not the controlling version, retained only as a record) is a candidate for the exception.

Analyzing by document class

Per-document analysis across a multi-thousand-document estate is impractical. A class-based analysis is faster and produces equally defensible documentation. The structure of a class analysis:

1. Define the class. Example: "All special-meeting agendas from 2014 to 2020 in the /board/archive/ directory."
2. Verify the conditions hold for the class. Confirm the class members were all created before the deadline, are all conventional electronic documents, and are uniformly not currently used (no current links, not referenced by current programs).
3. Document the analysis. A short memo or table entry: class description, conditions verified, evidence of non-current-use (no inbound links from current pages, not referenced in any current program documentation), date of analysis, person doing the analysis.
4. Re-verify periodically. Class membership can change: a new link from a current page can pull a member back into current use. A periodic check (annually) is reasonable.

Class analysis turns an unmanageable per-document task into a manageable per-class task, and produces the documented record that supports the exception claim.

What documentation should look like

An exception claim is only as defensible as the documentation that supports it. Useful documentation includes:

• A written analysis (per document or per class) identifying the documents at issue and applying the three conditions
• Evidence supporting the "not currently used" condition: link-analysis output showing no current inbound links, or a documented review of current program materials confirming no current reference
• The date of the analysis and the name of the person or role responsible
• A retention plan: when will the analysis be revisited, what will trigger re-verification
• Where the documents physically live on the server (so future inquiries can be answered)

The form of the documentation matters less than its existence. A spreadsheet, a memo, a compliance tracker entry, a wiki page: all are acceptable. An undocumented assertion is not.

Common misapplications

"It's old, so it's preexisting"

Age alone is not the test. Use is the test. A document from 2014 that is currently the controlling policy is not preexisting in the regulatory sense.

"It's in the archive folder"

Folder location is not the test. A document in /archive/ that is linked from current pages or referenced by current programs is currently used. The folder name does not control the analysis.

"It's not on the homepage"

Prominence is not the test. A document buried three clicks deep that is part of a current process is still currently used.

"Nobody downloads it anymore"

Download count is not the test. The rule asks whether the document is used in current programs, not how often. A rarely-downloaded form that is still the required form for a current program is currently used.

"We've blanket-applied the exception to all pre-2026 documents"

Blanket application across an undocumented set is the most exposed posture. The exception applies per document or per documented class. A blanket claim without analysis is not a documented exception; it is an undocumented assertion that the rule does not apply, which is a different argument with no statutory basis.