Product management
AuraScore 79/100

Municipal Open Data Platform Adoption Report

Assess municipal data platform utilization, identify consumption barriers, and establish governance protocols.

Use this template when auditing municipal or regional open data portals. It provides public sector data managers with a clear assessment of dataset utility, security adherence, and civic adoption strategies.

Template

Role: Public Sector Data Product Director with expertise in open government initiatives and municipal data governance.

Context

  • Municipal Authority: {{municipality_name}}
  • Key Consumer Groups: {{target_data_consumers}}
  • Core Published Datasets: {{core_datasets}}
  • Data Privacy & Compliance Standard: {{privacy_framework}}
  • Documented Adoption Bottleneck: {{adoption_bottleneck}}
  • Performance Period: {{reporting_horizon}}

Task

Generate a comprehensive data platform adoption report for {{municipality_name}} that diagnoses consumption hurdles, ensures compliance with {{privacy_framework}}, and proposes an actionable product enhancement strategy for {{core_datasets}} across {{reporting_horizon}}.

Method

  1. Review the current catalog of {{core_datasets}} against usage trends across {{target_data_consumers}}.
  2. Audit data ingestion and publishing pipelines against privacy safeguards mandated by {{privacy_framework}}.
  3. Investigate the root causes behind {{adoption_bottleneck}} from both technical and community viewpoints.
  4. Define standard API and metadata quality criteria to improve interoperability for civic developers and analysts.
  5. Formulate data stewardship workflows to ensure reliable schema maintenance and scheduled updates.
  6. Design civic engagement initiatives (e.g., hackathons, developer office hours) tailored to {{target_data_consumers}}.
  7. Establish key performance indicators (KPIs) to measure portal success over {{reporting_horizon}}.

Constraints

  • MUST ensure no data release recommendation breaches the standards of {{privacy_framework}}.
  • MUST address the operational challenges identified in {{adoption_bottleneck}} with direct solutions.
  • Do not recommend proprietary commercial licensing that restricts open public access.
  • Ensure recommendations are actionable by municipal staff within {{reporting_horizon}}.

Output format

Generate a detailed governance and adoption report structured as follows:

  1. Executive Summary
  2. Dataset Catalog & Utilization Audit
  3. Privacy & Regulatory Compliance Assessment
  4. Remediation Strategy for Adoption Bottlenecks
  5. Developer Experience & Data Quality Standards
  6. Strategic Roadmap & Performance Indicators (for {{reporting_horizon}}) Length must be between 900 and 1400 words.

Self-review

  • Ensure all datasets listed in {{core_datasets}} are evaluated in the catalog audit section.
  • Verify that privacy recommendations comply strictly with {{privacy_framework}}.
  • Confirm that the proposed developer experience measures directly eliminate {{adoption_bottleneck}}.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

business-strategy
business-product
public-sector-nonprofit
open-data
governance
public-sector