Choose the tool only after you know what record exists and who controls it

Describe the information in operational terms: email messages, text messages, body-camera files, dispatch audio, personnel actions, schedules, contracts, invoices, inspection logs, photographs, database entries, audit history, device data, claim files, video, access logs, or a named report. Identify the event, people, accounts, locations, and date range that would allow a custodian to find it.

Separate a record that likely exists from a question that asks an office to explain or create a new analysis. A useful inventory records the expected format, system name, owner, and reason the item matters.

Map custody beyond the visible organization. A public office may use a contractor, cloud platform, shared service, body-camera vendor, communications provider, insurer, payroll processor, laboratory, records repository, or another agency. A business may divide control among headquarters, local management, information technology, human resources, a third-party administrator, and individual devices. Legal possession, custody, or control is not resolved by a brand name or server location.

The map should state what is known, how it is known, and which custodian question remains open.

State the purpose without pretending the tool decides entitlement. A visitor may need public information, personal records, discovery, proof for an administrative filing, evidence for a claim, or confirmation that data has not been destroyed. Public-records law, consent, contract rights, discovery rules, subpoenas, authorizations, agency procedures, and voluntary cooperation have different predicates. The correct next step depends on the responsible party, record, relationship, proper court or tribunal, and current authority—not on which template is easiest to download.

For messages, retain the complete conversation, participants, timestamps, time zone, attachments, reactions, edits, and export information. For photographs and video, retain the original file, metadata, device or system source, and any native player or proprietary export needed to view it. For databases, identify the table or report, field definitions, query, filters, export date, audit log, and whether the result is a snapshot or live output. Screenshots and printouts should be labeled as derivatives, not silently substituted for the source.

Document handling should be reproducible. Record who collected an item, from what device or system, when, by what method, and where the unchanged source copy is stored. Use access controls and a working copy rather than repeatedly opening or renaming the original. Preserve relevant envelopes, headers, file paths, folder structure, checksums when used, and correspondence about collection. Avoid instructing a person to enter an account, take property, defeat a security control, or retain information they are not authorized to access.

Preservation scope must be proportionate and source-specific. Identify active and archived systems, automatic deletion, device replacement, application retention, backup cycles, departing personnel, shared drives, personal devices used for work, surveillance overwrite, and vendor termination. A generic demand to preserve everything may not communicate the important sources. Conversely, an artificially narrow list can miss later-discovered custodians. The plan should be updated as the facts and systems become clearer, with changes recorded rather than retroactively hidden.

An Oklahoma Open Records Act request concerns records of a covered Oklahoma public body under current state law and the recipient's process. A federal Freedom of Information Act request concerns records of a federal executive-branch agency. Neither route should be used as a generic demand to a private company, court, legislature, or sovereign entity without analysis. The proper office may hold only part of the material.

A request should identify the actual body, describe the records, address format and fees as appropriate, and preserve the sent version and response.

A preservation letter or litigation hold addresses retention, not automatic access. Its legal effect depends on the parties, dispute, foreseeability, control, content, delivery, and governing law. An acknowledgement is useful but does not prove that every source was identified or suspended from deletion. Internal hold practice, external notice, court orders, discovery obligations, regulatory retention, and ordinary business schedules are different concepts. This hub should not label a downloadable letter as completed preservation.

A subpoena uses court or authorized proceeding process and can impose duties, objections, protections, and consequences that a voluntary request does not. The issuing forum, service, recipient, scope, place of compliance, response date, privilege, privacy, burden, possession, custody, control, and objection procedure all matter. A person who receives process should not rely on a public-records or preservation template as the response. The document itself and current rules must be reviewed promptly.

Use one table with separate status fields. For a request, record the recipient, legal route, exact text, attachments, delivery, tracking, acknowledgement, clarification, estimate, production, withholding, denial, appeal information, and unresolved gaps. For preservation, record the trigger, scope, custodians, systems, notice version, delivery, acknowledgement, changes, collection, and release decision. For subpoena work, record the issuing tribunal, case caption, issuing attorney or clerk, service, compliance terms, objections, communications, production, testimony, and court orders.

Do not convert portal or tracker labels into legal conclusions. Sent means transmitted, not received. Submitted means the portal accepted data, not that the request is valid. Acknowledged means a response was received, not that the scope is preserved. Produced may mean a partial production. Closed may reflect an administrative status rather than complete compliance. Each material status should be supported by the underlying correspondence, file set, order, or custodian confirmation and should state the remaining question.

Set recheck triggers. Official pages, statutes, court rules, forms, contact details, agency practices, system owners, and retention settings change. Recheck before a deadline-sensitive action, after a new custodian is identified, when a production exposes a new data source, when a device or vendor is changing, or when the forum changes. The hub should route visitors to the right working resource while preserving the boundary that no public template itself completes the legal task.