Skip to main content

service issue

Report or review a service issue.

Incidents should make it clear what went wrong, who reviews it, and how corrective action is tracked.

normal user journey

Complete the task in clear steps.

  1. 1Open an issue with a safe summary and affected service.
  2. 2Independent reviewers classify cause and corrective action.
  3. 3Public records show resolution status and aggregate outcome.

public record boundary

What stays visible.

  • Issue category
  • Resolution status
  • Corrective action summary

service-portal guidance

What to know before you submit.

CivicSyn should answer the practical questions first: what this page does, what status means, what deadline or process might apply, and how to correct or appeal a public record.

Fees, deadlines, and process guidance

Report a missed service

Use incidents for missed deliveries, blocked repairs, safety issues, service failures, or public records that need urgent attention.

Corrective action

The public record should explain what changed after review without exposing sensitive details.

Status timeline

01

Opened

The issue is recorded with a safe summary.

02

Triage

The right team reviews urgency and affected service area.

03

Investigating

Evidence and partner context are checked privately when needed.

04

Closed

Corrective action and public outcome are published.

Next best actions

File appeal

If the incident outcome is wrong or incomplete, challenge it.

File appeal

public-safe intake

Report issue

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.

Missed meal delivery escalated to provider follow-up and route fix.