Transparency · Government workflow
9 minute read

Document workflows that support transparency and information requests

A workflow blueprint for Spanish public bodies handling Ley 19/2013 transparency requests — receipt, internal search, redaction, response, and audit log within statutory deadlines.

An ayuntamiento information officer received 23 transparency requests in March alone — up from a steady 6 to 9 monthly the prior year. The workflow she inherited was paper-based and built around the assumption of one request every two weeks. Within six weeks of the volume spike she was missing the 30-day statutory response deadline on roughly a third of submissions, triggering automatic appeals to the Consejo de Transparencia.

The fix was not faster work. The fix was a documented workflow that handles intake, internal routing, redaction, and response within a predictable cycle regardless of monthly volume. This guide describes that workflow in detail, calibrated to the requirements of Spain's transparency law (Ley 19/2013 de Transparencia, Acceso a la Información Pública y Buen Gobierno) and the practical realities of Spanish public administration.

Legal context Ley 19/2013 establishes the right of any citizen to request public information held by Spanish public bodies. Requests must be responded to within 30 calendar days (extendable to 60 in complex cases with notification). Refusals must cite a specific exemption from the law. Failure to respond is grounds for appeal to the Consejo de Transparencia y Buen Gobierno or its regional equivalents.

The four operational phases every request passes through

Day 0-2
Receipt & registration
Acknowledge within 48 hours
Day 3-15
Search & retrieval
Internal request routing
Day 16-25
Redaction & review
Apply exemptions and legal check
Day 26-30
Response & delivery
Formal reply with documents

Phase 1: Receipt and registration

Requests arrive through three channels: the Portal de Transparencia online form, postal submission, and presentation at the public registry office. Whichever channel the request used, registration follows the same procedure: assign a unique reference number, record the requester's identity and contact, capture the request scope, and send an acknowledgement within 48 hours.

Step 1.1

Register in tracking system

The transparency unit maintains a tracking spreadsheet or dedicated case management system. Every request gets a unique reference of the form AAAA-NN-XXXX where AAAA is the year, NN the originating service, and XXXX a sequential number. The reference appears on every internal communication and external response.

The tracking record captures: requester identity, request date, scope (in plain text), responsible service, status, deadline date (30 days from receipt), and current owner.

Step 1.2

Send acknowledgement

The requester receives a formal acknowledgement within 48 hours of registration. The acknowledgement confirms receipt, provides the reference number, states the statutory response deadline, and identifies the responsible service.

Templated acknowledgement letters or emails reduce drafting time. The transparency unit maintains four to six template variants for different request types and selects the closest match.

Step 1.3

Initial scope assessment

A senior officer reviews the request within five working days to assess scope: does it ask for information that exists, is the request sufficiently specific to action, does it fall within the body's remit. If clarification is needed, the requester receives a specific clarification letter (clock pauses pending response).

Requests outside the body's remit get redirected to the appropriate body with notice to the requester within ten days.

Phase 2: Internal search and retrieval

The transparency unit issues a formal internal request to the service holding the information. This internal request specifies the scope, the deadline (typically ten working days for collection), and the format required. The receiving service has a designated transparency liaison whose role includes responding to internal requests within deadline.

Searching for documents requires consistent procedures: queries against the document management system using metadata filters, checks of physical archives if relevant, and consultation with the staff who handled the underlying matter if institutional knowledge is needed. Search logs capture what was searched and where, providing evidence that the search was reasonable in scope.

Phase 3: Redaction and legal review

Retrieved documents are reviewed for exemptions under Ley 19/2013 Article 14. Common exemptions include national security, public safety, ongoing investigations, professional secrecy, intellectual property, and protection of personal data. Each redaction is marked with the specific legal basis applied, allowing the redaction logic to be defended if challenged.

Common redaction categories

Personal dataNames of private individuals, identification numbers, contact details — redacted per Article 15 and GDPR considerations
Commercial confidentialityPricing, trade secrets, supplier information when disclosure would harm legitimate commercial interests
Ongoing proceedingsDocuments relating to disciplinary, criminal, or civil proceedings still pending resolution
Internal deliberationPre-decision drafts where disclosure would compromise frank advice — narrow exemption under Spanish law
Public safetyInformation whose disclosure would create risk to public security or critical infrastructure
Third-party rightsWhere disclosure would harm legitimate rights of a third party, with mandatory consultation

Redaction tooling matters. Black-marker-on-paper redactions get scanned and the document remains technically searchable for the redacted text in the OCR layer. Proper digital redaction with tools like Adobe Acrobat's redaction feature or Foxit's equivalent permanently removes the redacted content and re-OCRs the result. Public bodies have lost transparency appeals where redactions were defeated by simple text selection in the released PDF.

Phase 4: Response and delivery

The formal response includes: a covering letter referencing the original request and reference number, the redacted documents in the requested format (typically PDF), an index of documents provided, citations of exemptions applied for any redactions or refusals, and information about appeal rights and timeframes.

Response delivery follows the channel the requester specified. The Portal de Transparencia handles electronic delivery automatically once the response is uploaded. Postal responses require certified mail. The internal tracking record captures the delivery date and method.

Volume management and queue prioritisation

High volume periods (typically following news events or political cycles) require queue prioritisation. The transparency unit uses three priority tiers: red (deadline within 5 working days, highest urgency), amber (deadline 5 to 15 working days, normal processing), green (deadline 15+ working days, baseline processing). Reviewing the queue weekly and re-tiering as deadlines approach prevents the deadline-missed scenarios.

Aggregate metrics tracked monthly: total requests received, total responded within 30 days, total responded within extended 60-day window, average response time, appeal rate, and appeals upheld at Consejo level. These metrics feed annual transparency reporting and identify procedural issues before they compound.

Document storage that supports transparency from the start

The fastest transparency workflow starts with documents being stored well to begin with. Records management practices that support transparency: consistent metadata at creation (author, date, subject, classification), version control on shared documents, retention schedules that prevent inappropriate destruction, and DMS search capability that surfaces relevant records on subject keywords. Bodies investing in records management upstream spend less effort on transparency response downstream.

Five workflow improvements that compound over time

Investments worth making

  • Templated acknowledgement and response letters covering 80 percent of common request types
  • Internal liaison roles in every service with defined response timeframes
  • Centralised case management replacing spreadsheet tracking once volume exceeds 50 requests monthly
  • Proper digital redaction tools and training for the transparency unit
  • Annual review of refused requests to identify policy or systemic disclosure gaps

Appeals and the Consejo de Transparencia

Requesters dissatisfied with a response (refusal, partial disclosure, late response) can appeal to the Consejo de Transparencia y Buen Gobierno or the regional equivalent. The appeal process runs in parallel with administrative appeals (recurso de reposición). The public body has 15 working days to respond to the Consejo's information request and 30 days for formal positioning on the appeal.

Tracking appeals and Consejo decisions improves the workflow over time. Patterns emerge: certain exemption categories are commonly rejected on appeal, certain refusal templates do not stand up to scrutiny, certain services consistently take too long to provide internal responses. Acting on these patterns reduces appeal rates and improves response quality.

滚动至顶部