Address the request to the public body that actually controls the records

Record the body's legal name, government level, department, records contact, address, and verification source. State agencies, boards, commissions, counties, municipalities, school districts, public trusts, law-enforcement offices, and other institutions may keep separate systems. The Oklahoma Attorney General's request form covers that office's records. It does not make the Attorney General the records source for every Oklahoma body.

Distinguish the body from contractors, vendors, private employers, insurers, hospitals, associations, courts, federal agencies, and tribal entities. An organization can perform public work or receive public money without answering every coverage, custody, or control question. Oklahoma court records use court systems and rules. Federal executive-agency records use Freedom of Information Act offices. Tribal sovereigns and entities require specific law, policy, waiver, and forum analysis. The Oklahoma location of the record or event does not settle those classifications.

Confirm the current official request channel. Some bodies identify a clerk, records manager, legal division, online portal, form, email address, or mailing process. Record any identity proof, authorization, incident number, case number, or subject-specific process. A police report, body-camera file, personnel document, licensing record, procurement file, email archive, and health record may be held by different units or subject to distinct access rules.

If custody is uncertain, state the uncertainty and ask for routing rather than asserting that one office controls every source.

Use concrete identifiers: subject, project, incident, permit, contract, vendor, official, sender, recipient, office, location, case number, report number, date range, and known system. Break record types into separate lines, such as correspondence with attachments, memoranda, policies, manuals, logs, dispatch audio, photographs, video, inspection material, invoices, purchase orders, agendas, minutes, database exports, or audit trails. Explain uncommon terms. If the date range is broad, connect it to a described event or decision.

Ask for an available electronic form that keeps the material usable when format matters. A scanned image may not substitute for a searchable text file; a flat report may omit database fields. A video export may require a player; an email PDF may omit attachments or headers. State the need without claiming entitlement to metadata or native format. If inspection rather than copies is desired, verify the body's procedure.

Fees, search, review, duplication, inspection, electronic delivery, deposits, and estimates should be addressed through current authority and the body's instructions.

Keep the request accurate and proportionate. Do not include a legal accusation simply to make the language forceful. Avoid asking for confidential personal information that is not necessary. Where privacy, privilege, law-enforcement, personnel, student, health, security, or proprietary information may be involved, identify the public portion and expect record-specific review. A request can invite a discussion about narrowing. Every scope change should be confirmed in writing and preserved with the original version.

Log the date and content of every response. An acknowledgement may confirm receipt but not coverage, scope, search completion, or a production date. A clarification request can expose ambiguity about the body, record type, system, date range, format, or fee. A fee estimate may reflect an assumed scope that should be confirmed. If the body redirects the request, identify whether it is transferring, referring, or merely suggesting another custodian and retain the communication.

Inventory the production by category, date, file type, numbering, custodian, and stated search. Preserve cover letters, folders, filenames, redaction markings, and an untouched source set. Note missing attachments, broken media, absent dates, duplicate files, unexplained sequence gaps, or a record type not addressed. A no-record response may reflect custody, terminology, retention, or search choices. It should not be presented as proof that the underlying event did not occur without further factual basis.

Read any withholding or denial against the current statute and actual language used. Do not assume an exemption is valid or invalid from its name. Privacy, privilege, law-enforcement, personnel, confidential business, security, and other interests can be record-specific. The next step might be clarification, narrowing, a corrected custodian, a Public Access Counselor complaint, another authorized review route, or no further action. That decision requires the complete request and response record.

If information may be deleted or overwritten, analyze preservation separately. A request does not necessarily suspend routine retention or place every possible custodian on notice. Identify video overwrite, device replacement, account deletion, employee departure, vendor changes, backups, messaging systems, and other loss risks. Any preservation communication should name the sources and recipients appropriate to the matter and should not imply that sending a form proves compliance.

Track every independent deadline. Open-records correspondence should not be assumed to toll a governmental tort claim, employment charge, civil limitation, administrative appeal, contract notice, subpoena response, court deadline, or federal Freedom of Information Act review period. Record the actual event, decision, receipt, and governing route for each. A public-access dispute and the underlying claim may involve different parties, remedies, evidence, and courts or tribunals.

Recheck the official law, form, address, portal, custodian, and source page before a consequential step. The Oklahoma Attorney General publishes current office-specific instructions and a Public Access Counselor complaint route. The Oklahoma Corporation Commission publishes its own process. Those examples show why the recipient matters. This worksheet creates a reviewable working document. It does not file, deliver, preserve, enforce, or prove the request.