IBM Public Sector Sweden

Lidingo Stad

Document Processing · Security and Compliance

Lidingö stad needed to reduce the manual effort required to review official documents, redact sensitive information and comply with Sweden’s transparency laws without exposing personal or classified data.

50% reduction in processing time

Reported impact

Business outcome

The municipalities in the project reduced processing time for public-document requests while preserving transparency obligations and better protecting sensitive information.

  • Compliance
  • Productivity Improvement

Solution

As part of the Rätt till insyn project, Lidingö stad worked with IBM and ATEA to test whether generative AI could speed up the confidentiality review process for public-document requests. The municipality’s staff had been manually reading requested documents, identifying personally identifiable or otherwise sensitive information and then redacting material before release. IBM watsonx.ai became the core of the pilot, providing a generative AI layer for analyzing document content and highlighting information that may need redaction. The approach fits into the municipality’s existing document-handling workflow rather than replacing it outright: staff still perform confidentiality assessments, but they do so with machine assistance that shortens review time and improves consistency. The result is a document-processing pattern geared to transparency, privacy and legally compliant public access.

Data flow

Official documents requested under transparency rules are reviewed with watsonx.ai assistance so staff can identify sensitive content, apply redactions and release compliant versions more quickly.

Solution architecture

1 components · 1 layer
  1. Compute
    • IBM watsonx.ai Analyzes official documents to help identify sensitive content that may need redaction before public release.

Architecture clues

  • Designed to align with Sweden’s Freedom of the Press Act
  • Project involved multiple Swedish municipalities
  • Solution supports confidentiality assessments before release

Evidence from the source

50% reduction in processing time
Each individual request necessitates the responsible employee to perform a confidentiality assessment, reviewing all requested documents and determining what needs to be redacted.
Lidingö stad Municipality ... uses generative AI to successfully streamline its data masking process, protecting sensitive data, improving efficiency, and ensuring compliance with Sweden’s transparency laws.
Transparency Evidence & methodology 90/100 reference value · 84% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence84%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    Lidingo Stad customer story

    First-party
    https://www.ibm.com/case-studies/lidingo-stad
    Source type
    Vendor-published customer story
    Published
    Feb 5, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.