Skip to main content

community need

Report a neighborhood or organization-level need.

Community groups can summarize demand patterns, source reliability, and urgency without publishing raw resident rows.

normal user journey

Complete the task in clear steps.

  1. 1Submit aggregate need and source context.
  2. 2Reviewers validate duplicates, stale data, and consent boundaries.
  3. 3Accepted batches inform public dashboards and reviewable decisions.

public record boundary

What stays visible.

  • Aggregate need by area or organization.
  • Source freshness and data quality summary.
  • Private rows and raw uploads stay restricted.

public-safe intake

Report community need

Keep private details out of this public page. A signed-in workspace can attach restricted evidence when needed.

Read privacy notes

examples, not promises

What people should expect.

These examples explain the journey shape. Actual local status comes from published public records or an authorized workspace.

A food pantry reports 180 additional household visits over the weekend.