{
 "slug": "release-authorization-receipt",
 "topic_id": "TOPIC-198",
 "cluster": "Government Benefits, Procurement & Public Sector Identity",
 "tier": "Tier B",
 "title": "Public records requests and redaction authority: who decided this could be released?",
 "summary": "Agencies are adopting automated and AI-assisted redaction to manage backlogs, shifting review from page-by-page human work to exception handling. An improper release cannot be undone.",
 "lede": "A records officer approves a release. The system records a status change. Somewhere in the released package is a home address, a medical detail, or an informant's name — and the question of who examined the pages before they went out has no recorded answer.",
 "date": "2023-10-18",
 "category": "Compliance",
 "author_id": "constance-ibe-whitmore",
 "tags": [
  "FOIA",
  "public records",
  "redaction",
  "AI assisted review",
  "records management",
  "privacy"
 ],
 "image_title": "Release Authorization Receipt",
 "schema": "Article",
 "key_takeaways": [
  "Records systems track request state. Redaction tools produce output documents. Approval is a status transition unbound to the released bytes or to the model's proposed redactions.",
  "An improper release is irreversible in the way a wrongful payment is not, which changes the control calculus.",
  "Binding the approver to the released file and to the model's proposal makes AI-assisted disclosure auditable rather than assumed."
 ],
 "body": [
  {
   "type": "h2",
   "text": "Why irreversibility changes the analysis"
  },
  {
   "type": "diagram",
   "kind": "flow",
   "alt": "A release decision, and the record it leaves",
   "caption": "The judgement is granular. The record is a case status.",
   "nodes": [
    {
     "label": "Request received",
     "note": "logged"
    },
    {
     "label": "Exemptions applied per passage",
     "note": "judgement",
     "bad": true
    },
    {
     "label": "Segregability assessed",
     "note": "judgement",
     "bad": true
    },
    {
     "label": "Case closed, released",
     "note": "one status field",
     "bad": true
    }
   ]
  },
  {
   "type": "p",
   "html": "Most of the controls in this series address money, which can sometimes be recovered. A public records release cannot be recalled. Once a document is disclosed, it is disclosed — to the requester, potentially to a publication, potentially permanently online."
  },
  {
   "type": "p",
   "html": "That asymmetry means the control has to act before the release rather than detect afterwards, and it means the evidentiary question — who approved this, having seen what — is the only question that will matter in the subsequent inquiry."
  },
  {
   "type": "h2",
   "text": "What the obligations require"
  },
  {
   "type": "p",
   "html": "Freedom of information statutes require agencies to disclose records unless an exemption applies, and to segregate and release reasonably segregable non-exempt portions. State public records laws follow a similar structure with their own exemptions."
  },
  {
   "type": "p",
   "html": "The judgement about what is exempt is a legal determination made by a human. The statutes do not prescribe how that determination is evidenced, which was uncontroversial while the determination was made page by page by a person."
  },
  {
   "type": "h2",
   "text": "What automation changed"
  },
  {
   "type": "p",
   "html": "Backlogs drove adoption of automated and AI-assisted redaction. A tool proposes redactions — names, identifiers, exempt categories — and a human reviews exceptions rather than pages."
  },
  {
   "type": "p",
   "html": "That is a reasonable response to volume and it changes the record in the same way it changed clinical documentation and batch record review: the human's act shifts from examination to disposition, and the system captures the disposition without capturing what was examined."
  },
  {
   "type": "table",
   "head": [
    "Element",
    "Before automation",
    "After automation"
   ],
   "rows": [
    [
     "What the reviewer saw",
     "Every page",
     "An exception set"
    ],
    [
     "What the record captures",
     "A status change",
     "A status change"
    ],
    [
     "What the model proposed",
     "n/a",
     "Not recorded in the release record"
    ],
    [
     "Human overrides",
     "Implicit in the markup",
     "Not distinguished"
    ]
   ]
  },
  {
   "type": "h2",
   "text": "The Release Authorization Receipt"
  },
  {
   "type": "code",
   "text": "{\n  \"type\": \"manav-stmt/1\",\n  \"action\": \"records_release_authorisation\",\n  \"render\": [\n    \"Request: [tracking number]  Requester class: [category]\",\n    \"Records released: [count]  Pages: [count]\",\n    \"Released package hash: [value]\",\n    \"Exemptions applied: [citations]\",\n    \"Redaction tool: [name, version]  Proposal hash: [value]\",\n    \"Human overrides: [count added] / [count removed]\"\n  ],\n  \"approver\": \"[records officer, credential assertion]\"\n}"
  },
  {
   "type": "p",
   "html": "Two hashes do the work. The released package hash fixes exactly what went out. The proposal hash fixes what the tool suggested, so the override count is verifiable rather than asserted."
  },
  {
   "type": "h2",
   "text": "The override count as a governance signal"
  },
  {
   "type": "p",
   "html": "An agency running AI-assisted redaction should watch the distribution of overrides per release, by officer."
  },
  {
   "type": "p",
   "html": "A sustained zero-override rate is not evidence the tool is perfect. It is a prompt to check whether exception review is occurring. A high removal rate — the officer removing redactions the tool proposed — is a different signal and may indicate over-redaction, which is its own statutory problem since agencies are required to release segregable portions."
  },
  {
   "type": "h2",
   "text": "The counterweight, stated fairly"
  },
  {
   "type": "p",
   "html": "There is a real risk of this argument being used to slow disclosure, and it should be resisted."
  },
  {
   "type": "p",
   "html": "Public records backlogs are a genuine accountability failure. Automation that reduces them is a public good. Nothing here argues for reverting to page-by-page review, and an agency citing release-authorisation concerns as a reason to delay disclosure would be misusing the argument."
  },
  {
   "type": "p",
   "html": "The point is narrow: automation is good, and its outputs should be attributable. Those are compatible."
  },
  {
   "type": "h2",
   "text": "What a defensible release record contains"
  },
  {
   "type": "table",
   "caption": "Per-redaction, not per-case",
   "head": [
    "Element",
    "Why"
   ],
   "rows": [
    [
     "Which passage",
     "Redactions are per-passage judgements"
    ],
    [
     "Which exemption relied on",
     "The legal basis, not a category"
    ],
    [
     "Segregability assessment",
     "Required, and rarely recorded per passage"
    ],
    [
     "The deciding officer",
     "By name, with their authority"
    ],
    [
     "The version released",
     "So the released copy is bound to the decision"
    ]
   ]
  },
  {
   "type": "h2",
   "text": "Objections and honest limits"
  },
  {
   "type": "p",
   "html": "<strong style=\"font-weight:600\">“Our FOIA system logs everything.”</strong> It logs the case. The decisions inside the case — which exemption, applied to which passage, by whom — are the part that gets challenged and the part that is usually narrative."
  },
  {
   "type": "p",
   "html": "<strong style=\"font-weight:600\">“This would slow processing.”</strong> For a routine full release, nothing changes. The record matters where exemptions were applied, which is a minority of cases and all of the litigation."
  }
 ],
 "faq": [
  {
   "q": "Does this slow down releases?",
   "a": "No. It adds a signing gesture to an approval the officer already performs. It does not add a review step."
  },
  {
   "q": "Does the receipt disclose the withheld content?",
   "a": "No. It carries hashes of the released package and the tool's proposal, plus counts. Nothing about the withheld material is revealed."
  },
  {
   "q": "Could this be used to justify delay?",
   "a": "It should not be, and the article says so. Backlogs are an accountability failure and automation that reduces them is beneficial."
  },
  {
   "q": "Is any of this statutorily required?",
   "a": "No. Statutes require disclosure and segregation of exempt material. The evidentiary form of the approval is not prescribed."
  },
  {
   "q": "Why isn't a case status enough?",
   "a": "Because redaction judgements are per-passage, and a challenge is about a specific withholding rather than about the case."
  },
  {
   "q": "Does this slow routine releases?",
   "a": "No. A full release is unchanged. The record matters where exemptions were applied — a minority of cases and most of the litigation."
  },
  {
   "q": "What should be bound?",
   "a": "The released version, so the decision provably covers the copy that went out."
  }
 ],
 "sources": [
  {
   "t": "FOIA.gov — the Freedom of Information Act",
   "u": "https://www.foia.gov/"
  },
  {
   "t": "NIST AI Risk Management Framework",
   "u": "https://www.nist.gov/itl/ai-risk-management-framework"
  }
 ],
 "related": [
  {
   "slug": "determination-receipt",
   "title": "Prior authorization by model",
   "category": "Definitional"
  },
  {
   "slug": "ferpa-consent-receipt",
   "title": "FERPA disclosure authorization",
   "category": "Vertical"
  },
  {
   "slug": "annex-22-ai-oversight-receipt",
   "title": "EU GMP Annex 22",
   "category": "Developer"
  }
 ],
 "image": "https://cdn.twc.sh/images/igcache/Release%20Authorization%20Receipt/1500_900/blog.jpg",
 "wordcount": 840,
 "url": "/blog/release-authorization-receipt.html",
 "reading_time": "4 min read",
 "seo_title": "Public records redaction: who authorised release?",
 "meta_description": "Agencies are adopting automated and AI-assisted redaction to manage backlogs, shifting review from page-by-page human work to exception handling.",
 "hub": {
  "slug": "topics/public-sector-identity",
  "title": "Public sector identity"
 },
 "answer": "A records officer applying exemptions and segregability judgements, recorded as a case status in a FOIA tracking system. When a release later proves to have disclosed something it should not have, the record shows that a case was closed, not who made which redaction decision on what basis.",
 "answer_q": "Who decided this record could be released?",
 "glossary": [
  {
   "term": "Segregability",
   "def": "The requirement to release any reasonably separable non-exempt portion of a record."
  },
  {
   "term": "Exemption",
   "def": "A statutory basis for withholding. Applied per passage, and the thing challenged on appeal."
  },
  {
   "term": "Records officer",
   "def": "The individual applying exemptions and making the release determination."
  }
 ],
 "checklist": {
  "title": "Making a release decision defensible",
  "id": "release",
  "desc": "Four steps.",
  "steps": [
   {
    "name": "Record per-passage, not per-case.",
    "text": "That is the granularity of the judgement."
   },
   {
    "name": "Capture the exemption relied on.",
    "text": "As structured data, not free text."
   },
   {
    "name": "Bind the released version.",
    "text": "So the decision covers the copy that went out."
   },
   {
    "name": "Sign it as the deciding officer.",
    "text": "Named, with their delegated authority."
   }
  ]
 },
 "cta": {
  "title": "Where this fits in Manav",
  "html": "Manav binds the authorising official to the exact release, award or record change, and produces a receipt another agency, an auditor or a counterparty can verify without access to the issuing system.",
  "href": "../docs.html",
  "label": "See authorisation receipts"
 }
}