Community Transparency Domain

Overview#

A police department faces community pressure to demonstrate improvements in officer conduct following a period of public scrutiny. Leadership wants to publish performance data but cannot expose individual officer records. They need aggregate metrics that show real trends without creating individual identification risks. The Community Transparency domain provides exactly that boundary: privacy-preserving dashboards that demonstrate accountability without enabling the identification of any specific officer.

Minimum sample size enforcement, configurable anonymisation levels, and automated report generation make community transparency a routine operational function rather than a one-off communications exercise.

Key Features#

Privacy-preserving dashboards with full, partial, and aggregate-only anonymisation levels.
Professionalism score breakdowns across formality, clarity, empathy, and de-escalation dimensions.
Trend analysis with week-over-week, month-over-month, quarter-over-quarter, and year-over-year comparisons.
Report generation in PDF, HTML, JSON, and CSV formats with scheduled cadences.
Configurable dashboard visibility (public, authenticated, internal).
Minimum sample size enforcement to prevent individual identification.
Unit-level anonymised breakdowns for departmental comparison.
Executive summary generation for reporting periods.

Use Cases#

Police departments publish community accountability dashboards showing aggregated professionalism metrics, demonstrating measurable improvements in de-escalation performance without exposing individual officer data.

Law enforcement agencies produce quarterly transparency reports with aggregated metrics for elected officials, oversight bodies, and community boards, generated automatically rather than requiring manual data extraction and formatting.

Departmental leadership uses trend analysis to track performance improvements over time, identifying units with positive trajectories and those requiring additional training investment before patterns become public issues.

Oversight bodies configure public dashboard visibility to allow community access to core accountability metrics while keeping more detailed internal performance data restricted to authorised personnel.

Integration#

Integrates with professionalism scoring, analytics, and reporting domains. Supports public URL access for community engagement.

Open Standards#

GraphQL (June 2018 specification): the entire Community Transparency API, public dashboard queries, professionalism aggregate queries, department metrics, and report generation mutations, is implemented as a typed GraphQL schema using Strawberry, giving clients precise, self-documenting access to anonymised data.
ISO 8601 (date and time format): all timestamps returned by the service, including date_from, date_to, generated_at, and trend period labels, are serialised as ISO 8601 strings via Python's .isoformat() method, ensuring unambiguous interchange with consuming clients.
JSON (RFC 8259): dashboard payloads, dashboard configuration, and one of the report export formats are all plain JSON; dashboard configuration is stored as a JSON string in the database and decoded on read.
JWT (RFC 7519) / JWK (RFC 7517): access to all authenticated GraphQL operations is gated by an RSA-signed JWT (RS256) verified against a JWKS endpoint; the IsAuthenticated permission class decodes and validates the bearer token on every request.
CSV (RFC 4180): comma-separated values is one of the supported report export formats, allowing transparency reports to be opened directly in spreadsheet tools used by oversight bodies and elected officials.
ISO 32000 (PDF): PDF is the default report export format for generated transparency reports, covering monthly summaries, quarterly analyses, annual reports, and city-council briefings.
W3C WCAG 2.2 / WAI-ARIA 1.2: the public community URL and stakeholder portal surfaces that display aggregated dashboard widgets are web interfaces expected to meet WCAG 2.2 accessibility conformance, covering perceivable and operable content for community members with disabilities.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14