Skip to main content

Public coordination, not black-box planning

Coordinate essentials in public.

CivicSyn is open infrastructure for the work cities, co-ops, and neighborhoods already do — matching demand to capacity for food, repairs, care, supplies, transit, and power. The system recommends; people decide; every decision leaves evidence.

10
essential domains, one shape
4
actor roles, separate views
100%
decisions with evidence

ask first

Get an answer, then take the right next step.

Residents can ask about requirements, fees, deadlines, request status, public records, capacity offers, and appeals. CivicSyn answers with citations and routes people into the correct workflow.

Accurate

Grounded in public routes and records.

Actionable

Every answer has a workflow link.

Safe

Private details stay out of public pages.

Ask CivicSyn

Answers link to the correct application, record, or workflow.

ENESFR+80

fallback · needs_review

I can help route this to the right CivicSyn workflow.

public guidance

I do not have enough public context to answer that precisely. The safest next step is to start a request, search public records, or contact the pilot team.

  • Use Get help when someone needs a service or response.
  • Use Public records when you want to verify a reason, outcome, or spending record.
  • Use Contact when the question needs staff review or private details.

Do not paste private household, medical, legal, or restricted evidence into public questions.

domain ›

Different views for different jobs

Pick what you need to do — see the next step for that work.

Residents, providers, coordinators, and public reviewers need different next steps. CivicSyn keeps one shared public record while tailoring the action.

Food security · what a resident gets

See aggregate need in your neighborhood. Sign up to volunteer a delivery shift, donate, or flag a missed meal.

Public snapshot

One shape, every domain: demand × capacity × inventory × delivery.

Local pilots publish the four public axes that explain how essential services are being matched. Aggregate summaries are public; private case detail stays protected.

Demand

meals / 24h

Open meal needs

  • School backpack program1,240+8%
  • Senior congregate sites880−2%
  • Shelter network612+22%

Capacity

meals available today

Kitchen capacity

  • Eastside Co-op Kitchen900
  • St. Marks Parish420
  • Northgate HS cafeteria0closed Tue

Inventory

expiring ≤ 48h

Cold-chain stock

  • Dairy (gal)184
  • Produce (lb)2,310
  • Protein (lb)640

Delivery

filled / scheduled

Courier shifts

  • AM bicycle co-op8 / 8
  • Midday van fleet3 / 6
  • PM walking volunteers12 / 15
local pilot · region summary · freshness clearly markedaggregate public view · private case details stay protected

Public record

Current public snapshots

Reading public-safe summaries from CivicSyn. Private case details, internal file details, and workspace-only fields stay out of this view.

Food dashboard

loading

Loading snapshot…

Capacity dashboard

loading

Loading snapshot…

A public decision, explained

The system can suggest. People decide. Every decision leaves evidence.

No black box. Residents can see the plain-language reason, the public evidence summary, and the path to correct or appeal the outcome.

public decisiondomain · food security
reason available
  1. Draft
  2. 2Review
  3. 3Approve / reject
  4. 4Recorded

title

Reallocate 184 gal dairy expiring in 36h

proposed action

Move 120 gal from West warehouse → Eastside Co-op Kitchen for backpack program; donate 64 gal to senior sites.

rationale

  1. 01Backpack program is +8% week-over-week and short on protein-equivalent calories.
  2. 02Eastside Co-op has refrigeration headroom (62%) and a Tue 2pm pickup already scheduled.
  3. 03Sending to shelters would exceed their cold-storage cap by 40 gal.

who & what is affected

≈ 1,240 students · 12 sites · $0 incremental procurement cost

evidence trail

source
USDA stock report · co-op intake log · school survey
freshness
updated 14m ago
confidence
high — 3 independent sources

public accountability

  • District nutrition lead
  • Co-op steward
  • Public reviewer (rotating)

Corrections and appeals create a public-safe record. No silent action. No private changes without reasons.

human-centered government UX

Design principles CivicSyn must honor.

These principles turn public coordination from a dashboard into a service people can actually complete, understand, trust, and challenge when something goes wrong.

Use one design system

Shared colors, typography, spacing, cards, tables, forms, focus states, and status labels make the public site feel credible and predictable.

Organize around top tasks

People should not need to learn internal modules. They should see get help, offer capacity, track a request, see outcomes, and appeal.

Make states visible

Links, buttons, tabs, statuses, loading states, empty states, and visited paths need clear visual changes so people know where they are.

Guide every transaction

Complex workflows become trustworthy when each page says what you need, what happens next, and how to correct or appeal an outcome.

Trust model

Six commitments that bound what this software is allowed to do.

Coordination without these commitments becomes surveillance, monopoly, or a black box. CivicSyn refuses all three.

  • commitment · 01

    Public-safe

    Aggregate by default. Private case details stay with the people who own them.

  • commitment · 02

    Human-governed

    Recommendations require accountable review. No silent execution.

  • commitment · 03

    Open by design

    Open data shape, open rules, open audit. No vendor capture of essentials.

  • commitment · 04

    Local-first

    Every local pilot can keep serving people during outages and share only the summaries neighbors need.

  • commitment · 05

    Evidence or it didn't happen

    Every decision carries source, freshness, confidence, and rationale.

  • commitment · 06

    Cooperative posture

    Co-ops, unions, public agencies, and nonprofits are first-class operators.

One infrastructure · ten essential systems

Start with one. Add more when the evidence trail works.

Each domain uses the same public explanation shape: need, capacity, inventory, delivery, funding, and governance. Click any tile to preview what residents and partners would see.

  1. domain · 01

    Food security

    Kitchens, food banks, delivery, public meal procurement.

    pilot domain
  2. domain · 02

    Housing repair

    Habitability requests, contractor capacity, materials, code review.

    pilot domain
  3. domain · 03

    Childcare

    Slots, sliding-scale subsidies, qualified caregivers, sibling-keep rules.

    pilot domain
  4. domain · 04

    Eldercare

    In-home support, meal delivery, transport-to-care, caregiver respite.

    pilot domain
  5. domain · 05

    Disaster response

    Shelters, supply caches, mutual-aid routes, sit-rep in public.

    pilot domain
  6. domain · 06

    Medicine & supply logistics

    Pharmacy stock, vaccine cold-chain, PPE, redistribution between sites.

    pilot domain
  7. domain · 07

    Public procurement

    Open bids, vendor concentration limits, local-retention targets.

    pilot domain
  8. domain · 08

    Workforce & labor capacity

    Open shifts, fair-call rotation, prevailing wage, apprenticeship.

    pilot domain
  9. domain · 09

    Transit bottlenecks

    Crowding, missed connections, paratransit gaps, detour evidence.

    pilot domain
  10. domain · 10

    Energy resilience

    Outage equity, medical-baseline households, community battery dispatch.

    pilot domain

Pilot path

One domain. One region. Ninety days. Then federate.

Cities, counties, school districts, public-health authorities, food banks, co-ops, hospitals, mutual-aid networks, and labor councils can run a CivicSyn pilot. The default first domain is food security, because its data shape is the most generous to the others.

  1. 01

    Pick one domain, one region

    Food security, eldercare, or housing repair are the most common starting points. One county, two zip codes, or one district is enough.

  2. 02

    Choose the local pilot home

    One agency, co-op, or coalition publishes public summaries and coordinates the signed-in workspace for operators.

  3. 03

    Connect existing operators

    Kitchens, clinics, contractors, drivers, councils, co-ops — bring whoever is already doing the work. No greenfield.

  4. 04

    Run for 90 days in public

    Reasons and outcomes are public from day one. Aggregate dashboards, named reviewers, corrections, and appeals stay visible.

  5. 05

    Expand only after the public record works

    Add a domain. Add a region. Connect with neighbors only after the evidence trail can explain each outcome.