Docs
Event Scopes

Event Scopes

Understanding notification event categories and configuring what changes trigger alerts.

Event scopes define the categories of permit changes that can trigger notifications. Configure which scopes you want to be notified about to control alert volume and relevance.

What Are Event Scopes?

Event scopes categorize different types of permit changes:

  • Each scope represents a type of update
  • You choose which scopes trigger notifications
  • Reduces noise from irrelevant updates
  • Focus on changes that matter to you

Available Event Scopes

Status Changes

Scope: status

Notifies when permit status changes:

  • Pending → In Review
  • In Review → Corrections Required
  • Corrections → Approved
  • Any status transition

Recommended for: Everyone tracking permits actively

Example notification:

"BLD-24-001234 status changed from In Review to Corrections Required"

Processing Updates

Scope: processing

Notifies on workflow/processing changes:

  • Assigned to reviewer
  • Department transfer
  • Review cycle completion
  • Workflow step changes

Recommended for: Those needing detailed progress tracking

Example notification:

"BLD-24-001234 assigned to Plan Review Department"

Conditions/Comments

Scope: conditions

Notifies when conditions or comments are added:

  • Correction comments from reviewer
  • Conditions of approval
  • Required actions noted
  • Plan check comments

Recommended for: Anyone needing to respond to feedback

Example notification:

"BLD-24-001234 has new correction comments from Building Department"

Inspections

Scope: inspections

Notifies on inspection-related changes:

  • Inspection scheduled
  • Inspection completed
  • Inspection results (pass/fail)
  • Re-inspection required

Recommended for: Construction phase tracking

Example notification:

"BLD-24-001234 - Framing inspection scheduled for 01/25/2026"

Fees

Scope: fees

Notifies when fees change:

  • New fees assessed
  • Fee amounts updated
  • Payment received
  • Balance changes

Recommended for: Financial tracking, ensuring timely payments

Example notification:

"BLD-24-001234 - New fee added: Impact Fee $2,500.00"

Attachments

Scope: attachments

Notifies when documents are added/modified:

  • New plans uploaded
  • Approval letters added
  • Correction notices attached
  • Any document changes

Recommended for: Document-heavy permits, plan tracking

Example notification:

"BLD-24-001234 - New document attached: Approved Plans (Rev 2)"

Scope: related

Notifies about related permit changes:

  • Sub-permits created (electrical, plumbing)
  • Master permit updates
  • Linked permit changes

Recommended for: Complex projects with multiple permits

Example notification:

"BLD-24-001234 - Related permit ELE-24-005678 has been issued"

Alerts

Scope: alerts

System-generated alerts:

  • Permit approaching expiration
  • Unusual activity detected
  • Jurisdiction notices
  • System warnings

Recommended for: Proactive permit management

Example notification:

"BLD-24-001234 - Alert: Permit expires in 30 days"

Configuring Event Scopes

In Account Settings

  1. Go to Settings → Account → Notifications
  2. Find "Event Scopes" section
  3. Toggle each scope on/off
  4. Save preferences

Per-Permit Override

For individual permits:

  1. Open permit details
  2. Click notification settings
  3. Customize scopes for this permit
  4. Different from your defaults

Minimal Alerts (low volume):

  • Status: On
  • Fees: On
  • All others: Off

Standard Tracking:

  • Status: On
  • Conditions: On
  • Fees: On
  • Inspections: On
  • Others: Off

Comprehensive (high volume):

  • All scopes: On

Scope Behavior by Channel

Email Notifications

  • All scopes available
  • Full detail in email body
  • Can include attachments info
  • Links to permit details

SMS Notifications

  • All scopes available
  • Condensed message format
  • Key information only
  • Character limit applies (320 chars)

Scope Combinations

High-Value Combinations

Action Required:

  • Status + Conditions
  • Know when to respond

Financial Tracking:

  • Fees + Status
  • Track payment requirements

Construction Phase:

  • Inspections + Status + Conditions
  • Field-ready information

Conflicting Scopes

No scopes conflict—they're additive:

  • Enable any combination
  • Each trigger independent
  • Multiple scopes can fire for same event

Event Examples by Scope

Status Scope Examples

FromToTypical Cause
PendingIn ReviewReview started
In ReviewCorrectionsIssues found
CorrectionsIn ReviewResubmitted
In ReviewApprovedReview passed
ApprovedIssuedFees paid

Inspection Scope Examples

EventDetails
ScheduledDate, time, inspection type
CompletedPass/fail, inspector notes
CancelledReason if available
Re-inspectionRequired corrections

Fee Scope Examples

EventDetails
New FeeFee type, amount
PaymentAmount paid, balance
AdjustmentReason, new amount
RefundAmount, reason

Troubleshooting