STOCKPORT FIRE DISTRICT OPERATIONS

Command overview.

Apparatus readiness and incident activity, all in one place.

ACTIVITY SNAPSHOT

Incident volume

Last 6 months

Station 49 Station 50

FLEET STATUS

Unit readiness

MOST RECENT

Incident activity

ATTENTION ITEMS

Fleet watchlist

!

SECURE STAGING DATABASE SHARED RECORDS

District records.

Verified district records from Cloudflare D1, shared across your authorized devices.

STAGING · SECURE RECORDS

Shared staging database. All operational navigation uses stockport-command-staging with your Google officer identity. Edits require server-side permissions and explicit confirmation. Existing historical browser files are not automatically imported; production is separate.

Sign in with Google to load staging records.

Not connectedNot loaded

Cloud overview

Choose a category to inspect its staging records.

Search Station

Waiting for authorized records

This is a staging operations register, not an emergency dispatch display. Changes require permission and confirmation. Some incident creation, inventory service history, advanced reports, and archive-import functions remain under integration testing. Large or permission-limited results are flagged instead of reported as complete totals.

FLEET OPERATIONS

Apparatus.

Track unit availability, service information, and notes.

SERVICE SCHEDULES

Maintenance watchlist

Next 30 days & overdue

EQUIPMENT ACCOUNTABILITY

Inventory.

Manage SCBA air packs, cylinders, tools, and anything else the district needs to track.

Equipment can be assigned to a station or individual apparatus. Inspection dates and history are recorded on each item's details.

INCIDENT OPERATIONS

Incident log.

Review response timestamps, dispatched apparatus, and activity by station.

District call numbers reset January 1 (Eastern Time). A call is counted only when a district apparatus has an en-route or on-scene time; dispatch-only records are retained without a call number. CAD incident IDs never change.

DISTRICT MEMBERSHIP

Personnel.

Member qualifications, station assignments, training totals, and certification history.

PERSONNEL DEVELOPMENT

Training.

Record drill details and automatically credit each attending member.

CAD drill identifiers are retained. Officer-added attendance, time, topics, and equipment are protected from re-import overwrites. Drills never increase the annual emergency-call total.

DISTRICT ADMINISTRATION

Meetings.

Schedule and record district meetings, attendance and session hours in shared D1.

Meeting hours are recorded separately and do not count toward annual training requirements or emergency incident totals. Attendance and changes are stored in staging D1.

COMMUNITY & DISTRICT ACTIVITIES

Special details.

Track event staffing and participant-hours separately from training and emergency incidents.

PERFORMANCE & TRENDS

Analytics.

Compare year-to-date results, all-time history, and personnel training progress.

TRAINING & STAFF DEVELOPMENT

Training analytics

SIX-MONTH TREND

Calls by station

Station 49 Station 50

CALL DISTRIBUTION

Incident categories

RESPONSE PERFORMANCE

Dispatch to scene

APPARATUS ACTIVITY

Unit responses

REPORTING & INSIGHTS

Reports.

Build detailed district reports with configurable datasets, dates, stations, search and exports. Database backup and restore remain under Administrator.

REPORT BUILDER

Start with a report template

Customizable

Report templateFind records containingRecord orderRows shown in preview

Report exports currently use records loaded into this browser. D1 reporting will replace this source once the authenticated database report API is available.

LIVE REPORT PREVIEW

Matching records

—

NEXT STEP · STAGING ONLY

Review your backup for cloud transfer

Read-only check

Choose the full JSON backup you just downloaded. We'll check its record counts, duplicate IDs and common compatibility issues right here on your device. This check does not upload the file, restore data or write to Cloudflare.

Choose full dashboard backup (.json)

Your backup remains on your device during the initial check. Nothing is sent until you separately confirm a staging import below. Production databases remain untouched.

No backup selected yet.

Controlled import to testing database

After reviewing your file, we'll compare every existing staging record before enabling import. Emergency calls, drills, special details, responses, apparatus information, maintenance schedules, service history and compatible personnel records are covered. Attendance credits and annual training requirements need separate cloud features; you can hold those records in your full backup and choose a clearly identified partial staging import. Inventory or certification records still block import.

Any accepted write goes only to stockport-command-staging through your Google-authorized Worker. This is a one-time migration, not ongoing cloud synchronization. Browser-only colors, layout, draft permissions and local change logs are not migrated; the original JSON backup keeps them. The original backup and browser-local records remain unchanged.

Optional: defer training-only records. I understand that attendance credits and annual training requirements will NOT be placed in staging now. Their only portable safety copy is my downloaded full JSON backup; I will keep that file to import them later.

Choose the same JSON backup above to compare it with staging.

I reviewed the counts and authorize writing these records to the staging database only.

Next phase · training record compatibility

After the main import is complete, check the deferred training session, member attendance and annual-hour requirements against the staging roster. This is a read-only review of your saved JSON and staging records; it cannot change either database.

Choose your original full backup above to enable this check.

One-time OSHA duplicate cleanup · staging only

The original browser backup contains Osha hours, Osha, and Osha, all set to eight hours for all classes. You confirmed that the intended rule is OSHA Annual Training · 8 hours · Interior, Exterior, Fire Police. This process retains one original source ID, archives the extra imported staging rule with an audit entry, and removes duplicate rules only from a new corrected backup. Your existing local data and original JSON file are not changed automatically.

Choose the original full JSON backup above, then review the OSHA cleanup. No changes can happen before a corrected backup has been downloaded.

I saved the corrected full JSON backup, reviewed the source IDs and counts, and authorize archiving the redundant OSHA requirement in stockport-command-staging only.

Controlled import of deferred training records

Once the separate staging Worker has been upgraded, compare the final training items with existing cloud records. The linked session and attendance are saved together; annual rules are separately audited. No production writes are allowed.

Waiting for an upgraded staging API. Do not use the original archive Import button for deferred training.

I reviewed the final training records and authorize importing them into stockport-command-staging only.

The report exports on this page currently reflect browser-loaded records. Full cloud database backups and restores are restricted to Administrator.

WORKSPACE MANAGEMENT

Data & settings.

Back up your dashboard, import records, or start with a clean roster.

PERSONAL WORKSPACE

Appearance & layout

Saved on this device

Customize how the dashboard looks for you. These preferences will be associated with your Google account when shared sign-in is connected.

Sidebar color Primary color Accent color Page background Text size Layout spacing Corner style Reduce motion

Changes apply instantly on this device.

⇩

Reports

Build customized reports and export selected records as CSV, HTML, or PDF. Full database backup and restore are managed under Administrator.

⇧

Import records

Restore a dashboard JSON backup, or import an incident CSV exported from this dashboard. Imported records remain on this device.

✉

Import CAD reports and archives

Import a single Columbia County closed-incident email/PDF or a collection of messages from a .mbox file. Review duplicates, responses, drills and details before saving structured data locally.

◉

Workspace mode

🔒

About data storage

The shared operational registers use the authenticated staging D1 database. Some legacy import, report, and demonstration tools still use browser-local records; those are not complete district backups.

No live CAD/dispatch integration

SOFTWARE INFORMATION

Version & update history

Current: V36.8.1

The version shown here identifies the dashboard frontend package. Backend Worker deployments and D1 migration numbers are tracked separately.

View the latest 3 updates

V36.8.1 Current
Made Officer Activity easier to read with summaries, field-by-field changes, and side-by-side before/after values.
V36.8
Added the D1 officer activity explorer, audit filters and exports, hourly authenticated-session observations, and server-side permission consistency checks.
V36.7.1
Added an expandable release history to Data & Settings and clarified the shared D1 versus browser-local storage notice.

SECURE OPERATIONS · STAGING VERIFICATION

Administrator.

Verify Firebase officer access, then prepare shared storage and reliable backups.

STAGING AUTH TEST · DATA STILL LOCAL

Important: Firebase sign-in and an officer-permission check now use the separate staging API. The dashboard's editing and administration controls still work only on this browser's local records; they do not write to D1. Local activity history is not a server-side audit log.

SHARED CONFIGURATION · D1

Field Management

Administrator only

Manage dropdown choices and identifiers used throughout the district dashboard. Changes are shared between authorized users. Existing records and service history are preserved.

Choose a field category to manage its shared values.

IDENTITY & PERMISSIONS

Cloud database user access

Manage linked Google sign-in accounts and per-user rights. These controls update officer permissions through the authenticated D1 API.

Loading administrator access controls…

DATABASE PROTECTION · ADMINISTRATORS

Full D1 backup & restore

Full-system backups belong here. A complete backup must include shared records, every officer account, permissions, personal color schemes, tile selections, and all other saved user preferences from the database. Restore will require a database-wide preview and explicit confirmation.

The database backup and restore endpoints are not yet available. Browser-local backups are not a substitute for a D1 backup. No database will be changed from this panel until server-side restore safeguards are completed.

IDENTITY & ACCESS

Officer accounts

Staging invite created

SFD

Authorized officerActual role and permissions are verified by the staging server after Google sign-in.

Officer verified

Each officer can have custom access to individual functions. Starting presets are optional; explicit Allow or Deny settings override them. The Worker enforces actual permissions, but these editor controls still save local planning drafts only and do not change any officer account in staging.

INDIVIDUAL ACCESS CONTROL

Permission editor

Local plan · not enforced

Select a planned officer to choose exactly which actions they may take. You can also register new permission definitions in the backend as future dashboard modules are added.

ACCOUNTABILITY

Change history

This is a basic activity list from this browser only. It cannot identify or verify individual users. In production, incident, apparatus, maintenance, and permission changes will include the authenticated actor, timestamp, and before/after values in a server-side audit table.

RELEASE READINESS

Integration checklist

1. Staging D1 preparedExisting staging migrations were verified earlier; later migrations 0012 and 0013 require a fresh status check before use. Production remains separate.

2. Staging API deployedstockport-command-api-staging responds to its health check with the dedicated D1 binding; new backend features require a separately approved staging update.

3. Verify Google officer sign-inFirebase domain authorized and primary administrator invited; confirm a signed-in /me response above.

4. Reconcile archive before syncingBack up the browser's historical records, compare counts and test officer access. No automatic cloud import.

5. Protect & recoverScheduled D1 exports, restoration drills, and server-side audit history remain to be validated.