Public source coverage
Code enforcement cases
Track open and historical enforcement records where cities expose separate datasets for current and legacy cases.
Watch every public record on your buildings, in one place.
CivicGuard onboards your buildings, runs a historical backfill, and quietly notifies you when new violations or status changes appear across supported public city sources.
- Public/open city data
- Initial historical backfill
- Per-building source selection
- Email alerts on changes
civicguard.io/portal
Portfolio overview
Buildings monitored
Buildings
12
Active sources
27
Open alerts
3
455 Garden Ave · LA
Code enforcement · case opened
1280 Walnut St · Philadelphia
Notice of violation · status updated
78 Bryant · San Francisco
Initial backfill complete
Live in
Los Angeles, CASan Diego, CAChicago, ILPhiladelphia, PASan Francisco, CA
Key platform facts
Supported cities
0
LA, San Diego, Chicago, Philadelphia, San Francisco
Email contacts
0
Per building — 1 primary + up to 2 additional
Unified portal
0
Buildings, violations and source context together
Four steps to switch from spreadsheets to continuous monitoring.
Configure each building once, pick the public sources that matter, and let CivicGuard handle the backfill, recurring checks and email alerts.
01
Add your building
Choose a supported city and enter the address or parcel/property ID required for that city.
02
Choose city sources
Select the departments and public datasets to monitor. Source options vary by city and are saved per building.
03
Run initial backfill
We normalize the identifier, run the historical backfill, and email an onboarding report.
04
Stay updated
New violations and material status changes appear in the portal and trigger email alerts to your contacts.
Available now in five U.S. cities, with more on the roadmap.
Every city ships with its own onboarding fields and source mix. You choose which sources to monitor per building — your selection stays attached to the ongoing monitoring flow.
The full picture across public city sources, not just the final notice.
CivicGuard pulls from public/open city datasets and keeps source context attached to the records you see in the portal. Available sources vary by city — the monitoring model stays consistent.
Primary records
Building violations and notices
Capture official building department violations, notices of violation, and related enforcement records tied to your monitored buildings.
Related context
Inspection complaints and signals
Pull in complaint and inspection datasets where available so you see the full picture, not just the final notice.
Optional enrichment
Permits and supplemental context
Store relevant contextual records like permit activity when those sources help explain the broader building history.
Ongoing monitoring
New and changed records
Detect newly ingested violations plus important status changes so teams respond without checking each city site by hand.
Canonicalized output
Deduplicated violation views
Overlapping source records collapse into a cleaner canonical view so operators don't chase duplicates.
Portal & alerts
One portal for buildings, violations, and email notifications.
Users get a single web portal for monitored buildings and violations. Admins get operational visibility across users, buildings, and system-ingested records.
- Filter violations by building, source, status, severity, and date.
- Open detail pages with linked building context and source-level visibility.
- Receive an initial backfill summary after onboarding, then ongoing email alerts.
- Route notifications to one primary alert email and up to two additional contacts.
Built for ongoing public-data monitoring, not one-off lookups.
The product is designed for multi-city public-data monitoring, ongoing change detection and cleaner operational review across users, buildings and violations.
Multi-source coverage by city
Each city has its own source configuration, so buildings get monitored against the relevant public datasets — not a one-size-fits-all feed.
Deduplicated, canonical records
Overlapping records converge into a cleaner violation view so operators review one operational timeline instead of juggling source duplicates.
Operational visibility for admins
Admins review users, buildings, violations and system activity from a global view while USER accounts stay focused on their portfolio.
Ready to see your buildings monitored?
Start monitoringTwo roles, one clear operational model.
Violations are ingested from public/open government sources. This workflow is about visibility, monitoring and notifications — not manual record creation.
USER
Building onboarding & monitoring
- Add buildings in supported cities
- Choose the sources to monitor per building
- Receive initial reports and follow-up email alerts
- Review violations and building context in the portal
ADMIN
Operational visibility across the system
- View users, buildings, and violations from a global workspace
- Monitor onboarding and troubleshooting workflows
- Track system-ingested records across accounts
- Support customer operations without manual entry
Quick answers about how CivicGuard works.
Public-source monitoring, supported-city onboarding, portal visibility, and email alerts for building operators.
Which cities are supported?
CivicGuard currently supports building monitoring in Los Angeles, San Diego, Chicago, Philadelphia, and San Francisco.
How do source selections work?
Source options vary by city. When a user onboards a building, they choose the departments and public datasets to monitor for that specific city and building.
What happens after I add a building?
The system stores the building identifiers, normalizes the address or parcel data, runs an initial historical backfill, and sends an initial report before ongoing monitoring continues.
How are alerts delivered?
Each building requires a primary alert email and can include up to two additional email recipients. The system sends notifications when new violations appear or important statuses change.
Can users create violations manually?
No. violations are system-ingested from public/open government sources. The product is designed for monitoring, review, and notification workflows rather than manual violation creation.
What can admins see?
ADMIN users have operational visibility across users, buildings, and violations so they can oversee onboarding, monitoring, and troubleshooting workflows across the platform.
Start monitoring buildings across supported cities.
Create an account, onboard a building, choose the city sources to monitor, and let CivicGuard handle the initial backfill and the ongoing public-record monitoring.
Los Angeles, CASan Diego, CAChicago, ILPhiladelphia, PASan Francisco, CA