Government
Government and public sector document management
Public sector document management is dominated by disclosure and disposal. Freedom of information and public records requests come with statutory deadlines, disposition schedules are legally mandated rather than advisory, redaction has to be irreversible, and published documents must meet accessibility duties such as WCAG 2.2 AA.
Why documents are difficult in government
Public sector document management is dominated by two obligations that pull in opposite directions. Disclosure law requires you to find and release records to anyone who asks, within a statutory deadline. Records law requires you to destroy records when their scheduled period expires, and destroying them earlier or later are both failures. Most private-sector organisations can defer both; a public body cannot.
The consequence is that structure and classification are not housekeeping. A request framed as "all correspondence about this planning decision" has to be answerable within twenty working days, which is achievable from a classified repository and effectively impossible from a set of departmental network drives. And because responses are published, the redaction has to be irreversible rather than a black rectangle over readable text.
Regulatory pressure
Three statutory pressures that shape the configuration
Freedom of information and public records access
What it requires. Requests for recorded information must be answered within a statutory period — twenty working days under the UK Freedom of Information Act 2000, twenty business days under the US FOIA — with exemptions applied on a case-by-case basis and reasons given.
What it means for a document system. Retrieval speed becomes a legal requirement rather than a convenience. It also means the search has to be demonstrably reasonable: you may have to describe how you searched, which needs a saved, reproducible query rather than someone’s recollection of where they looked.
Statutory records disposition schedules
What it requires. Records must be retained and disposed of in accordance with an approved schedule — under the US Federal Records Act and NARA general records schedules, or a comparable national or local instrument.
What it means for a document system. Disposal is mandatory rather than discretionary, and unauthorised destruction is an offence in several jurisdictions. That makes disposition review with a recorded authorisation the only defensible model: automated deletion cannot evidence who authorised it.
Public sector accessibility duties
What it requires. Published documents and digital services must meet an accessibility standard — WCAG 2.2 level AA under the EU Web Accessibility Directive and the UK public sector accessibility regulations, Section 508 in the US.
What it means for a document system. A scanned PDF with no text layer is not accessible, so OCR becomes an accessibility measure as well as a search one. Published response documents need a text layer, logical structure and alternative text, which is a document-production requirement rather than a website one.
Capability mapping
Five capabilities mapped to public sector requirements
Reproducible search for disclosure requests
OCR across scanned correspondence plus enforced metadata makes a request answerable as a query. Saved searches can be re-run, which is what lets you evidence that the search was reasonable and adequate if the response is challenged on appeal.
Disposition review with recorded authorisation
Scheduled disposal raises a review, and an authorised officer confirms it. The confirmation is recorded with their name, the date and the schedule item relied on — which is the evidence that destruction was authorised rather than accidental.
Exemption handling as a workflow
Applying an exemption is a decision that must be reasoned and is subject to internal review and appeal. A workflow records who applied which exemption to which document, on what basis, so an internal review has a file rather than an inbox.
Recorded access for accountability
Every view and download is logged with actor, timestamp and version. In a public body this serves accountability as much as security: questions about who saw a document before a decision, or after a leak, are answerable from the record.
Multi-entity separation for shared services
Branch and department separation under central administration suits shared service arrangements, arm’s-length bodies and combined authorities, where several entities must be administered together but their records must not be commingled.
Taxonomy
A starting folder taxonomy
Governance and decisions
- Committee and cabinet papers
- Decision records and delegated decisions
- Minutes and agendas
- Statutory registers
Information rights
- FOI and access requests
- Search records and exemption decisions
- Response documents as published
- Internal reviews and appeals
Service delivery
- Case files by service area
- Licences, permits and applications
- Inspections and enforcement
- Correspondence with the public
Procurement and contracts
- Tender documentation and evaluations
- Contracts and variations
- Contract management and performance records
- Transparency publications
Corporate
- Policies and procedures (controlled)
- Workforce records
- Finance and audit
- Records disposition schedules and destruction certificates
The information rights branch holds the record of how you responded, not just what you released. When a response is appealed, the search you ran and the exemption you applied are the material in question — and they are records in their own right with their own retention period.
Worked example
A worked workflow: an access request from receipt to publication
Step 1: Log and acknowledge
The request is recorded with its receipt date, which starts the statutory clock, and assigned to a case owner. The deadline is calculated rather than remembered.
Step 2: Search and record the search
A saved search identifies candidate records across contents and metadata. The query itself is stored, so the adequacy of the search can be evidenced on review.
Step 3: Review, exempt, redact
Each candidate is reviewed. Exemptions are applied with a recorded basis, and redactions are applied irreversibly to the released copy while the unredacted original is retained.
Step 4: Respond and retain
The response is issued and filed with the request. Both, plus the search record and exemption decisions, are retained under the schedule item for information rights records.
Retention
Retention expectations
| Record class | Commonly applied period | What starts the clock | Source |
|---|---|---|---|
| Governance and decision records | Often permanent, or transferred to an archive | Not applicable — permanent preservation | National archive schedules; UK Public Records Act 1958 |
| FOI / access request files | Commonly 3 years, longer where appealed | Closure of the request, or of the final appeal | Organisational schedule; NARA GRS 4.2 in the US federal context |
| Procurement and contract files | 6–7 years after contract end, longer for major works | Contract expiry or final payment | Limitation periods and audit requirements |
| Licences and permits | Life of the licence plus a defined period | Licence expiry or revocation | Sector-specific statute |
| Case files involving children | Extended well past the age of majority | Subject reaching the age of majority | Statutory guidance; periods are long and vary by jurisdiction |
| Destruction certificates | Permanent | Not applicable | Evidence that authorised destruction occurred must outlive the records |
These classes are illustrative and must be replaced with the approved disposition schedule applicable to your jurisdiction and tier of government before anything is destroyed. Unauthorised destruction of public records is an offence in several jurisdictions, and no vendor page should ever be treated as a schedule.
FAQ
Government document management: common questions
Can DocumentMS help us meet FOI deadlines?
The binding constraint on an FOI response is almost always retrieval, not review. OCR over scanned correspondence and enforced metadata turn a request into a query, and saving that query means you can evidence that the search was adequate if the response is appealed — which is the part organisations most often cannot demonstrate.
Does it support irreversible redaction?
Destructively, and on a copy. The released version is flattened so the redacted content is removed from the file rather than covered, and the unredacted original is retained separately as its own record with its own permissions. This matters more than it sounds: a black rectangle drawn over selectable text in a PDF is not a redaction, and published responses have leaked that way repeatedly — the text is still in the file and a reader can select it.
Can we load our statutory disposition schedule?
Yes, from CSV or XLSX, with a dry run that reports every unmapped item before anything is applied. The harder part is rarely the import: schedule items are written against business functions, document types are defined against what a file is, and the two do not correspond one to one. That reconciliation is worth doing deliberately rather than automating, which is exactly why the dry run reports mismatches instead of guessing at them.
How does this handle shared services across several bodies?
Branch and department separation under central administration lets several entities be administered together while keeping their records separate. That suits combined authorities, arm’s-length bodies and shared back-office arrangements where commingling records would itself be a problem.
Are published documents accessible?
OCR gives scanned documents a text layer, which is the precondition for accessibility, and is why we treat OCR as an accessibility measure rather than only a search one. Full WCAG 2.2 AA conformance for a published document also needs logical structure and alternative text, which is a document-authoring responsibility the system supports rather than replaces.
Última revisión: 2026-09-01. Compare all ten industry configurations.