hackforla/311-data

PRD - Investigate Community Impact Statements

Open

#2,022 opened on Sep 10, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (73 forks)auto 404
Feature: ResearchGood First IssueRole: Product Managementon agenda: pmsize: 1pt

Repository metrics

Stars
 (73 stars)
PR merge metrics
 (PR metrics pending)

Description

Overview

We need to understand the definition, framework, content, and formatting requirements of Community Impact Statements (CIS) so that Neighborhood Council members can use data from our 311 tool to help build CIS.

Details

Research found that Neighborhood Council members are interested in using our tool to build help build impactful CIS. Therefore we should make sure our tool compatible for this use.

Action Items

Research

  • Find existing Community Impact Statement
    • add any found documents to the Resources section below
  • Find instructional literature (definition, how-to, etc)
    • add any found documents to the Resources section below
  • Review all added resources

Document Findings (as a comment on this ticket)

  • Define: Community Impact Statement
  • Framework: what are the parts of a CIS? Do they all follow the same format / is there a template?
  • Content: what goes in each section?
  • Formatting requirements: if an NC member were to use our tool generate materials/content/data for a CIS, how do we make sure that information is compatible with a CIS?

Resources/Instructions

Contributor guide

Research direction
Search for existing Community Impact Statements (CIS) and instructional guides, review them to define CIS, identify common frameworks and sections, and determine formatting requirements for compatibility with the 311 tool.
Tech stack
None
Domain
documentation
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90