Making Public Records Truly Accessible Online: An Administrator's Guide

Legal duties, digitization barriers, and portal practices that balance openness and privacy

By Max SheltonReviewed by PAP Editoral TeamUpdated October 15, 202625+ min read

What you’ll learn in this article…

  • Federal FOIA requests hit a record high in fiscal year 2025.
  • ADA Title II makes WCAG 2.1 Level AA the portal accessibility standard.
  • California's records clock: 10 days to decide, extendable 14 more days.

Public records work has shifted from answering requests to anticipating them. Federal FOIA requests hit a record in fiscal year 2025, per the Justice Department's tally across 117 agencies, while processing fell behind.

For administrators, a record can be legally public under FOIA or a state statute and still exist only in a basement box, a microfilm reel, or a retired vendor's database. Residents expect it online, free, and searchable, and under the DOJ's ADA Title II rule, whatever goes online must meet WCAG 2.1 Level AA.

Each scan also forces a privacy call: redaction that was optional at the counter becomes unavoidable at internet scale.

Public vs. Online: What Records Access Actually Means

A record's public status does not guarantee that it is online, free, or instantly downloadable. Administrators who conflate the two set resident expectations they cannot meet and generate avoidable friction for their own staff.

Three Distinct Ideas

Keep these separate when you talk about access:

  • Public: The record is subject to disclosure under law and not fully exempt. Its status says nothing about how someone gets it.
  • Available on request: A resident can obtain the record by submitting a formal request, which staff then locate, review, redact, and release within a statutory window.
  • Online, free, and easy: The record sits on a portal, searchable and downloadable without any request at all.

What the Law Actually Requires

Most federal and state public records laws, including those governing public sector pay transparency, require agencies to respond to requests. They generally do not require you to post records online in advance, even as a digital government implementation roadmap pushes agencies toward portal-based access. FOIA and its state counterparts guarantee a process, not a proactively published library. That legal floor is lower than what most residents assume, and the gap is where frustration lives.

When people cannot find a document they believe should be a click away, they file a request. Each request consumes staff time for intake, search, redaction, and response, so the gap between expectation and reality directly inflates workload.

A Simple Scope Test

To decide what belongs on the portal versus what stays request-only, ask of each record category:

  • Is it requested frequently by the public?
  • Is it low-sensitivity or easily redacted at scale?
  • Does it exist in a consistent digital format?

Categories that clear all three are proactive-disclosure candidates. Everything else stays on request until you can close those gaps.

A request to a federal agency and a request to a county clerk follow two different legal maps, reflecting the federal state collaboration framework. The federal Freedom of Information Act (FOIA) governs records held by federal departments and agencies. State and local government records, from city council emails to state agency contracts, are controlled by that state's own public records act, and no single state law mirrors another exactly.

The four mechanics requesters ask about

Most public records work with administrators revolves around four questions. First, deadlines: state laws set response windows, often between three and fifteen business days, though extensions are common for complex requests. Second, fees: agencies may charge for search time, review time, or copying, but fee structures and waivers differ widely, with some states capping costs or waiving fees for public interest requests. Third, exemptions: the law lists categories of records that may be withheld, but almost all exemptions are discretionary, not mandatory. Fourth, appeals: if a request is denied, the requester has a route to challenge that decision, usually through an administrative appeal and then a court.

Common exemption categories vary by state

Personal privacy, law enforcement records, deliberative process, security, and attorney-client privilege appear in most public records acts, but the boundaries shift. For example, one state may exempt all investigative files, while another releases closed investigations. Some states add exemptions for critical infrastructure or trade secrets. Administrators should read their state's exemption list alongside attorney general guidance, not assume a federal standard applies.

Undigitized records and proactive disclosure

Digitization status does not change the legal obligation. If a record exists only on paper, in a legacy database, or in offsite storage, the requester can still ask for it, and the agency generally must search those sources. The work may take longer and cost more, but the right of access does not evaporate because a record is not online. At the same time, many states now push records online through proactive disclosure mandates, a shift in public policy making. These laws require agencies to post certain categories, such as meeting minutes, budgets, contracts, and salaries, without waiting for a request. Proactive posting reduces request volume and is the clearest legal lever for moving records from filing cabinets to portals.

How Much Pressure Are Records Offices Under?

Federal FOIA demand hit a record in fiscal year 2025, according to the Justice Department's summary of annual reports from 117 agencies. Requests grew faster than processing, which is why administrators increasingly treat proactive online disclosure as a way to relieve pressure, not an optional extra. The summary did not publish government-wide backlog, full-grant, or median processing figures, and comparable state and local request volumes are not consistently reported.

Federal agencies received a record 1,707,197 FOIA requests in fiscal year 2025, up 13.7% from 2024

State-by-State Accessibility: How Jurisdictions Compare

There is no national standard for public records online accessibility, so deadlines, fees, and portals vary widely between states and between a state and its own cities. The table below is a sample of states, one state agency, and several local governments drawn from attorney general guides, city records offices, and the National Freedom of Information Coalition. It is not a 50-state survey. A few patterns stand out: some deadlines are flexible standards ("as soon as possible" in Delaware, a "reasonable" estimated completion date in Oregon) rather than fixed day counts, and fees range from flat per-page charges to itemized staff-time billing. The most complete online portals in this sample are run by cities such as Seattle and Tacoma, not by states, and statutes change, so confirm details against the current law before you rely on them.

JurisdictionStatutory Response DeadlineFee ApproachOnline Request Portal / Online AvailabilityNotable Feature or Gap
California (state)10 days to determine whether to disclose; a limited 14-day extension may apply$0.10 per page for direct duplication; full costs may be charged for compiling or extracting electronic data or for programmingNo centralized statewide request portal identified; the state DOJ explains how to request its own recordsElectronic data requests can cost far more than paper copies when compilation or programming is needed
Pennsylvania (state)5 business days$0.25 per printed page for the first 1,000 pages, then $0.20; $1.00 per CD or DVD; actual USB, mail, and courier costs; $5.00 certification feeNo centralized statewide request portal identified; the Attorney General publishes Right-to-Know resourcesShort fixed deadline paired with a tiered per-page fee schedule
Delaware (state)As soon as possible, but no more than 15 business days after receiptFirst 20 standard black-and-white pages free; then $0.10 per single-sided or $0.20 per double-sided sheet; administrative processing fees allowedState FOIA request form can be submitted electronically through an online portal to various state entitiesStaff processing time may be billed, but legal review of whether a record is exempt may not
Delaware Department of JusticeNo more than 15 business days after receiptStatutory fee structure applies unless the public body adopts a different one; administrative fees exclude legal reviewRequested through the State of Delaware FOIA portal by selecting the Attorney General's OfficeShows an agency routing requests through a shared statewide portal instead of its own system
Michigan (state)5 business days, with a possible 10-business-day extensionMay cover search, examination, review, copying, separating exempt information, and mailing; labor charges limited to unreasonably high costs that must be specifically identifiedAttorney General accepts FOIA payments online; no centralized statewide submission portal identifiedAgencies must justify and identify labor costs before charging for them
Oregon (state)No hard completion date: after 15 business days, written notice with a reasonable estimated completion date satisfies the requirementCost of fulfilling the request; compilation costs may be required up front; fees may be waived or reduced in the public interestNo centralized statewide request portal identified in the DOJ toolkitReasonableness standard rather than a fixed completion deadline
Portland, OregonNot stated on the city page (set by state law)Fee schedule covers standard fees, staff time, and bureau- or office-specific chargesOnline Public Records Request PortalCharges can differ by bureau or office within the same city
Seattle, WashingtonNot stated on the city page (set by state law)Not detailed on the city page; payments are handled onlinePublic Records Request Center for submitting requests, paying, downloading records, tracking status, and messaging disclosure officersFull request lifecycle handled in a single system
Tacoma, WashingtonAcknowledgment and a specified next action within 5 business daysInspection free; $0.15 per paper page, $0.10 per scanned page, $0.05 per 4 electronic files, $0.10 per GB transmitted, staff time $0.49 per minute; 10% deposit on large requestsOnline Public Records Request Center for submitting requests, paying charges, and receiving recordsLarge requests released in installments, with payment required before each subsequent installment
Union City, CaliforniaNot stated on the city page (set by state law)Inspection free; duplication charges for photocopies, CDs, and DVDs limited to direct cost or a statutory feeOnline portal for submission, status tracking, communication, and downloading recordsCity identifies the portal as the fastest way to submit a request
New Orleans, LouisianaNot stated in the cited sourcePortal may prompt payment of a copying and mailing feeOnline public records portal describedFee payment is built into the portal workflow

Barriers to Online Access: Backlogs, Legacy Paper, Silos, and Funding

A digitization backlog is the pile of records that exist only on paper, microfilm, or outdated electronic formats. None of it can be searched or released online until someone scans, indexes, and reviews it. Even the best-resourced records agency in the country is far behind.

The Scale of the Problem

The National Archives' holdings have grown from about 3 billion pages to roughly 12 billion over the past 40 years.1 NARA has digitized around 500 million of those pages, roughly 4 percent, leaving about 11.5 billion pages offline.1 Meanwhile, about 100,000 cubic feet of new unprocessed records arrive each year, on top of incoming electronic records.2

Funding is moving the other way. NARA's FY 2026 request of $414.7 million came in $59.5 million below the FY 2025 enacted level,3 and advocacy analyses describe the proposal as a 33 percent cut to electronic-records programs.4 Those are proposed figures, not final appropriations. No comparable national estimate exists for how much state or local material remains undigitized. That gap is itself a warning: most jurisdictions are not measuring the problem.

Four Recurring Barriers

  • Legacy paper and microfilm: Decades of permits, minutes, and case files sit in boxes or on film that must be handled, scanned, and indexed one item at a time.
  • Siloed departmental systems: Clerks, police, planning, and HR often run separate platforms with no shared search, so one request triggers several manual hunts.
  • Thin funding: Digitization competes with frontline services and rarely survives a tight budget cycle.
  • Understaffed records offices: A small team handling request intake, redaction, and retention has little capacity left for conversion projects.

Sizing and Prioritizing Your Backlog

Measure the backlog in three dimensions, an Evidence-Based Policymaking approach, before you request money. Count volume in linear feet or boxes. Pull request logs to see which series people actually ask for. Then check each series against your retention schedule. Records already eligible for destruction should be disposed of lawfully, not scanned.

With that inventory in hand, rank work using a simple lens:

  • High demand: Series that generate repeat requests pay back scanning costs fastest.
  • High risk or at-risk media: Brittle paper, fading microfilm, and obsolete storage formats may not survive another decade.
  • Legally required: Records that statutes or proactive-disclosure policies require you to post come first, regardless of demand.

A backlog you can describe in feet, request counts, and retention status is a Government Reform budget request. One you cannot describe is just a complaint.

Born-Digital Records: Texts, Teams Chats, and Vendor Transitions

A paper file sits still until someone moves it; a text thread deletes itself in thirty days unless someone intervenes. That contrast explains why born-digital communications now generate more compliance failures than any filing cabinet ever did.

The Record Follows the Business, Not the Device

NARA Bulletin 2015-02 treats electronic messages about agency business as federal records, covering text messaging, chat and instant messaging, social media messaging, and voice messaging.1 Advisory AC 23.2025 extends that reach to third-party applications including WhatsApp, Signal, Telegram, WeChat, and Snapchat, even when the account is personal. North Carolina's digital communications guidance reaches the same conclusion from state law: texts and instant messages sent by public employees in the course of business are public records, alongside email, social media, and websites. Notably, NARA's electronic messages schedule carves out collaboration platforms such as Microsoft Teams and SharePoint, but exclusion is not exemption. Those messages simply need coverage under a different approved schedule.

Where Agencies Lose Records

Three failure modes recur: platform auto-delete settings that destroy content before anyone evaluates it, staff conducting business on personal devices outside any capture system, and migrations where a vendor contract ends and the data goes with it. Retention attaches to the record and its schedule, not to the platform, so a switch in providers does not reset an obligation.1

Three Controls Worth Putting in Place

  • Written policy: Define approved channels, forbid agency business on uncaptured personal accounts, and require case-by-case evaluation rather than blanket transitory treatment.
  • Retention settings: Align platform defaults to the governing schedule. Unscheduled messages must be held as permanent until disposition is approved.
  • Contractual export rights: Require machine-readable export, migration support, and post-termination access in every vendor agreement.

Portal Accessibility and Usability: WCAG, Language Access, and Search Quality

The U.S. Department of Justice's ADA Title II web accessibility rule makes WCAG 2.1 Level AA the technical standard for state and local government web content and mobile apps. A 2026 interim final rule, effective April 20, 2026, revised the original 2024 compliance dates: entities serving 50,000 or more people now have until April 26, 2027, while smaller entities and special districts have until April 26, 2028. For a small records office, work in this order: inventory portal, app, and PDF content; fix anything currently used to request or access records first; then document any undue-burden or fundamental-alteration claims in writing.

Requirement AreaWhat It Means for a Records PortalCommon FailurePractical Fix
Large entities (population 50,000 or more)Records portals and mobile apps must conform to WCAG 2.1 Level AA by April 26, 2027, unless compliance would cause a fundamental alteration or undue financial and administrative burden.Portal or app web content does not conform to WCAG 2.1 Level AA.Remediate portal web content and mobile-app content to WCAG 2.1 Level AA by April 26, 2027.
Small entities (population under 50,000)Records portals and mobile apps must conform to WCAG 2.1 Level AA by April 26, 2028.Treating the extended deadline as an exemption. Title II still requires accessible services, programs, and activities in the meantime.Use the additional time to bring portal web content and mobile apps into WCAG 2.1 Level AA conformance by April 26, 2028.
Special district governmentsCovered web content and mobile apps must conform to WCAG 2.1 Level AA by April 26, 2028.Leaving covered portal content inaccessible on the assumption that the rule applies only to larger governments.Inventory the district's portal and app content, then remediate covered content to WCAG 2.1 Level AA by April 26, 2028.
2026 interim final rule (revised deadlines)Revises the 2024 Title II compliance dates for web content and mobile apps. Effective April 20, 2026.Accessibility plans still built around the original 2024 compliance dates.Update plans to the revised dates: April 26, 2027 for populations of 50,000 or more; April 26, 2028 for populations under 50,000 and special districts.
Public records portals and mobile apps (scope)Any portal or app used to provide or access a government service, program, or activity must be accessible under Title II and meet WCAG 2.1 Level AA by the applicable deadline.Content is not readily accessible to and usable by people with disabilities, or does not meet WCAG 2.1 Level AA.Test and remediate portal and app content against WCAG 2.1 Level AA, and document any claimed fundamental alteration or undue-burden exception.
Posted PDFs, including scanned documentsA posted PDF generally must meet WCAG 2.1 Level AA when it is covered web content, including when it is currently used to apply for, access, or participate in a government service. A scanned image with no text layer cannot be read by assistive technology or found by search, so it fails on both accessibility and findability.Assuming a file is exempt because it is a PDF. The archival exception covers only files posted before the compliance date that are not currently used for access or participation.Make currently used PDFs accessible, and remediate or replace older PDFs whenever they are needed to access or participate in government services.
Pre-compliance-date documents (archival exception)A word-processing, presentation, PDF, or spreadsheet file is excused from WCAG 2.1 Level AA only if it was available before the entity's compliance date and is not currently used to apply for, access, or participate in services.Losing the exception without realizing it. If any one of the three conditions is missing, including current use for access or participation, the file must conform.Keep an inventory recording each file's type, posting date, and current use, and remediate any file that does not satisfy all three conditions.

Best Practices for Digitization and Proactive Disclosure

Most agencies still treat digitization as a conversion project when it works better as a triage sequence. The order matters more than the equipment budget, because scanning the wrong boxes first locks in years of sunk cost without reducing a single request.

Sequence the Work: Stop, Publish, Then Scan

Start by stopping the bleeding. Records created today in email, chat platforms, and case management systems should be captured and retained correctly before anyone touches a filing cabinet, or the backlog simply regenerates. Next, publish what people already ask for. The Justice Department's proactive disclosure guidance reflects a long-standing practice of posting records once they have been requested roughly three times, though the department frames this as guidance rather than a universally binding threshold.1 HHS, in its 2026 Chief FOIA Officer Report, pushes further: post frequently requested records quickly and systematically in advance of any public request, in the most useful, searchable, and open formats available.2 Agencies taking this approach report less duplicative processing, though quantified savings are rarely published.

Only after those two steps should you digitize the backlog, prioritized by demand and risk. NARA's digitization strategy covering 2015 through 2024 framed the goals plainly: expand online access, protect fragile originals from handling, and enable reuse.3

Mine Your Own Request Log

Your request-tracking system already identifies the record types that drive most of your volume: salary tables, inspection reports, permits, incident logs, contracts, body-camera indexes. Pull a year of requests, cluster them, and publish the top tier as standing datasets. Everything posted proactively is a request you never process twice.

Scanning, Metadata, and Formats That Last

  • Metadata: Maryland State Archives, whose guidelines were updated in January 2025 and follow FADGI specifications, captures file type, file name, creator name, creation date, and record classification.4 The New York State Archives advises adding fields beyond the minimum based on actual access needs, not hypothetical ones.5
  • Text accuracy: New York certifies OCR at 95 percent accuracy or better where searchable text is required.5 EPA notes that only human review and re-keying achieve full content-indexing accuracy, and recommends supplementing with cataloging.6
  • Formats: Archival PDF/A with embedded text, plus structured exports such as CSV or XML per batch, keeps files usable across vendor changes.

Before You Scan, Dispose

Run the retention schedule first. Digitizing records already eligible for destruction converts a storage problem into a permanent discovery liability. For small offices, phase scanning by record series, join a shared services agreement with a county or regional body, or ask your state archives whether it runs a grant or contract imaging program for local governments.

Case Examples of Strong Public Records Portals

California agencies running online public records portals work from the same statutory clock: 10 days to decide whether responsive records exist, extendable by up to 14 more days in unusual circumstances. The portals below show how three agencies put that clock online. One caution up front: the available evidence comes from the agencies' own pages. It documents features and legal response standards, not audited outcomes, request volumes, median turnaround, or denial rates. No independent journalism or open-government review turned up in the research. Treat these as illustrative designs, not proven performers.

Three California Portals

  • Orange County: Requests are filed electronically, and the requester is emailed when a response or record is available. The county states plainly that its 10-day determination is not a production deadline.1 Records follow within a "reasonable time" after staff collect them, review exemptions, and possibly consult counsel. Putting that distinction in writing is the portal's clearest strength.
  • California Department of Financial Protection and Innovation: The online portal receives requests instantly, avoiding the two to three business days that mail typically adds. The department says it strives to make non-exempt records available within its 10- or 24-day frame "whenever possible under the circumstances," which is a goal, not a guarantee.2
  • California High-Speed Rail Authority: The authority aims to tell requesters within 10 days whether records will be provided. If unusual circumstances block a determination, it explains the delay and gives a determination date, with the extension capped at 14 days.3

What the Evidence Does Not Show

The sources reviewed do not describe public request logs, searchable posted responses, or fee transparency for these portals, so none of them should be credited with those features here. Any claim of faster responses or higher completion rates would also be unsupported. If a vendor or agency makes such a claim, flag it as self-reported until an auditor, newsroom, or open-government group confirms it.

Transferable Lessons for a Mid-Sized Office

  • Intake: Accept requests electronically and send automatic notifications at each status change.
  • Expectations: Tell requesters in plain language that a determination is not the same as production.
  • Extensions: When you extend, give a date and a reason rather than silence.
  • Evidence: Publish your own response-time and volume data. Without it, outside reviewers have nothing to evaluate, and your portal's reputation rests on assertion.

How Should a Record Move From Request to Release?

Use the full workflow for one-off requests, where the statutory response clock and the requester's scope drive each step. For proactive postings, run the same sequence once per record series, then reuse the approved redaction rules on every future batch so routine releases move faster without new legal review.

Five ordered steps from logging a records request through legal review, verified redaction, and documented release.

Balancing Transparency and Privacy: The Administrator's Role

If a record is already open for inspection at the counter, why does posting the same record online create new risk? Because scale changes everything. A paper file requires someone to show up, pay copy fees, and handle one record at a time. The same file on a public portal can be harvested continuously by automated scrapers, merged with other sources, and resold by data brokers into products the original disclosure statute never contemplated. Practical obscurity was a real, if accidental, privacy control, and digitization removes it.

What State Law Already Restricts

Several states have written specific personal-data carve-outs into their records statutes. Ohio Revised Code §149.43 shields a designated public service worker's residential address, Social Security number, residential and emergency telephone numbers, bank and credit-card numbers, and medical information.1 Oregon Revised Statutes §192.377 requires redaction of residential addresses, telephone numbers, personal email addresses, personal cell numbers, Social Security numbers, and employer identification-card numbers submitted in confidence. Florida Statutes §119.0712 makes personal information in motor-vehicle records confidential consistent with the federal Driver's Privacy Protection Act of 1994.3 Texas treats a voter's Social Security number, driver's-license number, and personal-identification-card number as confidential, and its election address confidentiality program keeps an applicant's residence address, phone number, date of birth, emergency contact, and family-member information out of Public Information Act releases.4

More is pending. New Jersey bills introduced in 2026 (S553, S1941, and S1472) would require redaction of Social Security numbers, credit-card numbers, unlisted phone numbers, driver-license numbers, and home addresses of judicial and law-enforcement officers,67 with one proposing a secure portal for covered persons to submit redaction requests.8 Hawaii's SB3015 would set a three-business-day acknowledgment window and a 30-day corrective action period.9 None of these is enacted, so track them rather than plan around them.

A Four-Question Decision Framework

  • Legal requirement: Does a statute mandate disclosure, mandate redaction, or leave discretion?
  • Public interest: Does release illuminate government conduct, or only expose a private individual?
  • Privacy harm: What is the realistic risk of harassment, identity theft, or aggregation by third parties?
  • Channel: Post proactively, release on request with redaction, or withhold with a written basis?

Liability and Career Value

Failed redaction is not a clerical slip. Wisconsin treats redaction as a partial denial reviewable by mandamus, and §19.36(6) requires releasing separable disclosable portions.5 Flattened PDFs, unscrubbed metadata, and portal misconfigurations create breach exposure. Administrators who can defend these calls in writing become genuinely hard to replace.

Building Records and Transparency Skills in Public Administration

Transparency work presents a recurring tension: release too much and you risk privacy harms, release too little and you erode public trust. Administrators who can manage that tension are increasingly valuable, not as technical archivists but as translators between legal obligations, technology constraints, and public expectations.

Skills the work demands

  • Records law: FOIA, state public records acts, and their exemptions.
  • Information governance: retention schedules, metadata, chain of custody, and disposal.
  • Privacy risk assessment: spotting personal identifiers, health data, or security-sensitive details before release.
  • Digital service design: building portals that are searchable, accessible, and usable by non-experts.

Where to build them and where they lead

MPA and MPP programs increasingly address MPA career skills through public law, information management, ethics, and digital government coursework. A specialization in records and transparency can lead to MPA career paths such as records officer, public information officer, city clerk, open government coordinator, or compliance analyst. These positions sit at the intersection of legal risk, technology, and public engagement.

Next steps

1. Pursue a recognized records management certification, such as the Certified Records Manager or a state archives credential. 2. Take a short course or continuing-education module on public records law and FOIA exemptions. 3. Compare MPA concentrations that include information governance or digital service design on the related degree pages at publicadministrationpolicy.org, and use the Careers in Public Administration & Policy pages to map local job titles and certification expectations.

Recent News

Recent Articles