Skip to main content

public decisions

See public decisions and request status without reviewer controls.

Public visitors should see reasons, outcomes, corrections, and appeals. Signed-in reviewers can open the full decision workspace on this same path.

normal user journey

Complete the task in clear steps.

  1. 1Find a public decision or request status.
  2. 2Read why it happened and what evidence was considered.
  3. 3Submit a correction, complaint, or appeal.

public record boundary

What stays visible.

  • Decision reason
  • Status
  • Outcome
  • Appeal/correction status

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

Why this happened

Public decisions should show the reason, status, expected outcome, and what evidence categories were considered.

No reviewer controls on public pages

Public visitors can read, correct, or appeal. Signed-in reviewers use separate workspace controls.

Status timeline

01

Queued for public explanation

A decision or request status is ready to explain.

02

Reason published

The public record states why the path was chosen.

03

Outcome tracked

Execution, delay, complaint, or completion status updates the record.

04

Correction or appeal

People can Submit correction or File appeal when the record is wrong.

Next best actions

Search public record

Open related decisions, requests, spending, outcomes, and appeals.

Search public record

Submit correction

Flag a public record that is incomplete or inaccurate.

Submit correction

File appeal

Challenge the decision or outcome with evidence.

File appeal

marketplace-style workflow

Familiar controls for real coordination work.

CivicSyn borrows the good parts of marketplace browsing, request boards, settings panels, and notification preferences, then adapts them for public-safe essential-service journeys.

Building Permits

Status: Submitted x
Map record 1Map record 2Map record 3Map record 4Map record 5Map record 6Map record 7Map record 8Map record 9Map record 10Map record 11Map record 12
Record #Submitted dateSubmitted ByApplicant CompanyAddressRecord TypeStatus
#R-NEW-26-0004January 8, 2026, 10:57amMarcus HaleRed Oak Builders100 Wayne Manor Dr, Gotham City, NY 10001Residential New ConstructionSubmitted
#R-NEW-25-0040December 19, 2025, 12:32pmElena OrtizMaple Ridge Builders221B Crime Alley, Gotham City, NY 10002Residential New ConstructionSubmitted
#MEC-25-0002December 8, 2025, 10:15amAisha RahmanNorthside Mechanical77 Blackgate Rd, Gotham City, NY 10004MechanicalWaiting
#DEM-25-0003December 10, 2025, 8:12pmOwen CarterCornerstone Builders12 Iceberg Ln, Gotham City, NY 10009DemolitionPending
#PLU-25-0001December 10, 2025, 8:10pmRiley BennettPinecrest Construction333 Falcone St, Gotham City, NY 10011PlumbingCompleted
#RES-25-0032December 5, 2025, 9:33amLeah DiazWayne Enterprises18 Stage St, Gotham City, NY 10019Residential New ConstructionSubmitted

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.

Why a delivery was rerouted, why a repair was prioritized, or why spend changed.