TraverseOps | Municipal Field Operations

TraverseOps Field workspace

Workspace Demo workspace

Signed out Local demo cache

Worker

Field access TraverseOps Demo workspace | Signed out | Local demo cache

Daily field summary and urgent municipal work

Sync pending Signed out 0 pending changes

Demo/local mode This workspace is using local demo cache, not a production municipal cloud workspace.

Total hydrants 0

Needs service 0

Sewer network 0.0 km

Catch basins 0

Valves 0

Manholes 0

Water mains 0.0 km

Active work orders 0

Workspace setup

No assets have been imported yet.

Import an editable GIS asset layer first, or load sample field data to try maps, work orders, inspections, and reports before connecting a real municipal workspace.

Current Focus

No asset selected

Pick a hydrant or sewer line to see details, save notes, or create work.

Local-only demo cache

Search

Find Asset

Asset ID Show Sort list by Rows

Page 1

Search by asset ID or choose a simple saved view.

List

Asset List

This table is the keyboard and screen-reader alternative to the map. Search or filter assets, select a row to open the asset panel, then use row actions to change status, create a work order, or start an inspection without using map markers.

Use asset search and saved views to find records.
Press Enter on a focused row to select that asset.
Use the action buttons for status, work orders, and inspections.

Municipal asset registry. Use this table instead of the map to search, select assets, review status and open work, change status, create work orders, and start inspections.
Asset ID	Type	Status	Open Work	Last Inspection	Updated	Action

No assets match the current search or saved view. Clear the filters, import an asset layer, or load sample field data to populate the registry.

Active assets 0

0 critical faults

Map

Active map filters

Layer preset: Hydrants

Layer controls

Water

Sewer

Boundaries

Reference

Water

Fire hydrant inventory points with inspection and service status.

Water valve locations for operations and maintenance.

Water distribution mains shown as line assets.

Service areas or supply zones used for planning context.

Sewer

Sewer main segments and line assets used for issue tracking.

Access points tied to sewer inspections and field notes.

Drainage inlets and catch basin assets for stormwater work.

Boundaries

Parcel or property outlines for location context.

Reference

Use the Reference preset to show all available map context at once.

Status

Legend Markers, lines, and work indicators

Marker colors

In-service asset Needs service Selected asset

Asset types

Hydrants Manholes Catch basins Valves

Lines and areas

Sewer mains Water mains Property boundaries Water supply areas

Work orders

Marker with open work order Line asset with open work

0 tracked hydrants

0 sewer segments

Streets base layer

Map legend

In service Needs service Open work Selected Sewer main Water main Catch basin

Counts

Quick Counts

What is loaded in the current map view.

0 Total Hydrants
0 Needs Service
0.0 km Sewer Lines

Selected

Selected Asset

Awaiting asset

Pick an asset from the map or list to save notes, change status, or create work.

No asset selected

Select an asset before saving notes, creating work, or starting an inspection. Search the registry, use your current location, or narrow the map to assets that need service.

Search asset ID, street, or nearby address Enter an asset ID or nearby location, then use the asset list or map result to open the asset workflow.

Pick an asset row or map marker to open the field workflow.
Import assets or load sample data if the registry is empty.

Asset Type Asset type comes from the mapped asset or import. Asset ID Use the municipality's existing GIS or asset registry identifier. Status Status changes are recorded on save for the selected asset.

Open work orders for this asset will appear here when work data is loaded.

Last Inspection Optional date from the last known inspection record.

Completed inspection history will appear here after inspection records are synced.

No linked inspections are saved for this asset yet. Start an inspection to record the template, result, severity, inspector, date, and evidence.

Notes Notes should be specific enough for a supervisor or crew member to act on later.

Saved notes for this asset will appear here.

Photo

Optional asset evidence photo. Use JPG, PNG, or HEIC from the field device when supported.

Photos attached to inspections and work orders will appear here.

Add a photo here for the selected asset. Inspection photos appear when linked inspection records include evidence.

History will appear after asset changes are saved to the cloud.

Geometry, source layer, coordinates, and import metadata will appear here when GIS metadata is available.

Coordinates: Not available
Geometry type: Not available
Source layer: Not available
Import run: Not available
External GIS ID: Not available

Help

Help Me

Field Help

Use the buttons below for common field tasks.

Filters Asset focus Search + sort Dispatch routing

Choose a suggested action below.

Admin workflow

Add Asset

Admin only

Add a hydrant or sewer line at the center of the map.

Asset Type Choose the municipal asset class that matches the record being added. Asset ID Optional. Leave blank to generate a local demo ID. Status Initial field status for the new asset. Inspection Date Optional known inspection date from existing records. Latitude Decimal latitude for the asset location. Longitude Decimal longitude for the asset location. Notes Optional location context, condition, or source note.

Work

Work Orders

Editor+

Pick an asset first, then create the job for a crew.

No asset selected. Work orders must be linked to a mapped asset.

Linked Asset ID Linked Asset Type

View Sort Only show my work

0 open | 0 active | 0 done

Title Use a concrete task name crews can recognize in the field. Priority Critical and high work stays prominent in the priority queue. Due Date Choose the expected field completion date. Assign to Enter a crew name, operator, or municipal staff email.

No work orders are visible in this view. Select an asset and create a work order, or adjust the filters to review completed work.

Access

Team Roles

Roles keep map viewing, field updates, and admin settings separated.

Viewer

Monitor assets, map layers, and overall work load.

Editor

Update asset condition, complete inspections, and manage work.

Admin

Create new assets, manage imports, and control settings.

Today

Today's Field Summary

Loading workspace

Start here to dispatch crews, review overdue work, catch failed inspections, and confirm the workspace is ready for field use.

0 Open work orders
0 In Progress
0 Assigned to crews
0 Overdue work
0 Failed inspections needing follow-up
0 Pending sync changes

Priority queue

Priority Queue

Urgent open work orders, failed inspections, and assets already marked needs service.

No urgent work, failed inspections, or needs-service assets are loaded right now. Items appear here when due dates, inspection results, or asset status need field attention.

Your work

Assigned to You

Active work orders assigned to the signed-in user, sorted by priority and due date.

No work orders are assigned to you right now. Assignments appear here after work orders are assigned to your user or email.

Assigned work

Assigned Work

Active work orders assigned to a crew or operator, sorted by priority and due date.

No assigned work is loaded yet. Create a work order and choose an assignee so supervisors can see what crews own today.

Due dates

Overdue Work

Open or in-progress work orders that have passed their due date.

No overdue work orders are loaded. Due dates on active work will surface here when they pass.

Inspections

Failed Inspection Follow-Ups

Failed inspections without a linked follow-up work order.

No failed inspections are waiting for follow-up. Failed results will appear here until follow-up work is created.

Recent activity

Recent Activity

Latest asset updates, created work orders, completed inspections, import runs, and admin changes from this workspace.

No recent activity is loaded yet. Update an asset, create a work order, submit an inspection, run an import, or save admin settings to build this activity trail.

Sync

Sync Status

Sync pending Sync status will appear after the workspace connects.

Sync state is based on the current data source and connection status.

No queued changes Last sync not recorded No retries pending

Offline asset updates, work orders, inspections, notes, and evidence metadata will appear here until they sync.

Sync pending Current state

No queued changes Queued changes

No cloud sync yet Last sync

Data source not reported Data source mode

Map shortcuts

Quick Map Shortcuts

Jump to the map view crews need before they leave the yard.

Work

Field Work Board

Dispatch work by status, priority, due date, assignee, and linked infrastructure location.

View Filter the board by current work order status. Sort Choose how cards are ordered inside each status lane. My assigned work Shows work assigned to the current signed-in user when an email is available.

Create a work order from a selected asset when a repair, inspection follow-up, or service request needs triage.

Use Start Work on an open item once a crew accepts the task and is heading to the asset location.

Mark field work complete after crews finish the task so it appears in reports and closeout review.

No work orders have been created yet. Start by selecting an asset on the map, then create a work order tied to that infrastructure location.

Work detail

Select a work order

No selection

Choose a work order from the board or list to review crew assignment, due date, linked asset, notes, comments, and attachments.

Status: Not selected
Priority: Not selected
Due date: Not selected
Assignee: Not selected
Linked asset: Not selected

Notes

Notes will appear here when a work order is selected.

Linked asset preview

Asset ID: Not selected
Type: Not selected
Status: Not selected

Select a work order to see its linked asset.

Comments

Comments will appear here after a crew member adds the first work-order comment.

Add comment

Attachments

Attachments will appear here after work-order evidence files are implemented.

Statuses

Work Status Guide

Open Needs assignment, scope confirmation, or triage.
In progress Field crew acknowledged and work is active.
Completed Repair done, awaiting reporting or quality review.

Crew tips

Assigning Work

Priority first Critical and high-priority work should not sit unowned.

Bundle nearby tasks Route work by geography to reduce windshield time.

Close the loop Completed work should update asset condition immediately.

Traffic control

Plan Register

TAC metadata

0 Total plans

0 Ready

0 Active

0 Devices

View

0 plans | 0 ready | 0 active | 0 scheduled devices

Saved traffic control plans will appear here with status, linked work, setup date, and device counts.

Builder

Traffic Control Plan Builder

Plan title Status Template Choose a template to load the initial traffic device schedule. Linked work order Link a work order when the plan supports scheduled field work.

Linked asset ID Linked asset doc Location Crew

Setup date Expiry date Notes

Ready to draft a traffic control plan.

Device schedule

Signs, Cones, Barriers, and Flaggers

Select a template to preview the device schedule.

Printable summary

TAC sign metadata

Temporary Condition Sign Catalog

Metadata is summarized from the TAC Sign Pattern Manual temporary-condition sign pages. No sign artwork is stored in the app.

Template workflow

Municipal Inspection Workflow

Select the asset, choose the municipal inspection template, record the field result, complete the checklist, attach evidence, and submit the record for reporting or follow-up work.

Current inspection

Select an asset from the map or asset list before submitting an inspection.

Linked asset
Template
Result
Evidence
Submit

Inspection template Templates define the required municipal checklist for the selected asset class. Use for routine hydrant checks, seasonal flushing support, obstruction review, cap condition, leaks, and pressure or flow observations. Linked Asset ID Use the selected hydrant, valve, manhole, sewer line, or other mapped asset ID. Inspection result Choose Fail when the asset needs service, repair, or supervisor review. Failure severity Severity controls follow-up priority when failed inspections create work orders.

Failed inspection requirements

Document the issue before submitting

Choose the severity that matches field urgency.
Enter findings that describe the defect, location, and recommended follow-up.
Attach photo evidence when required by workspace settings.
Follow-up work orders can be created automatically when enabled by an admin.

Follow-up work order preview

Title: Follow-up work order
Priority: Low
Due date: Not scheduled
Linked asset: Link an asset before submitting

Findings and field notes Required for failed inspections. Keep notes concrete enough for supervisors and crews to act on.

Failed inspections require clear findings. Photo evidence may be required by workspace settings.

Photo evidence

Inspection evidence preview

No inspection photo selected.

Required checklist for the selected template:

Template driven

Complete every checklist item before submitting the inspection.

Ready when linked asset, checklist, and required evidence are complete.

Quality controls

Inspection QA Snapshot

Quality score is a completeness signal for saved inspections. It starts at 100 and drops when records fail, omit findings, omit photo evidence, or save without a checklist.

0% Average completeness score
0% Failed inspection rate
0 Follow-up work orders

Fail result (-40) Reduces the score because failed assets need clearer review and possible work orders.

Missing findings (-15) Lowers confidence because supervisors cannot see what was observed in the field.

Missing photo (-10) Reduces evidence quality, especially for failed inspections and visible defects.

Missing checklist (-20) A missing checklist means the inspection did not capture the required template controls.

No QA flags need review. Continue saving inspections with notes and evidence photos; failed or low-quality submissions will appear here.

Trend watch

Inspection Compliance Trends

No weekly inspection trend exists yet. Start an inspection for a linked hydrant, sewer line, or manhole to begin tracking pass and fail movement.

Template adherence

Template Compliance

No template compliance records exist yet. Run the first inspection, then review whether the hydrant or sewer template is producing complete field records.

Field history

Recent Inspections

Completed inspections will appear here with the template, result, severity, linked asset, inspector, date, and evidence. Choose a template, link an asset, complete the checklist, and save the first field inspection.

Supervisor reports

Reports

See where work is piling up, what needs attention first, which assets are causing repeat calls, and whether crews are closing work on time.

Report filters apply to records currently loaded in this browser. Filters run on currently loaded workspace records in this browser. They are not server-side historical queries.

Exports

CSV and PDF exports will include the currently filtered manager summary, waiting work, overdue attention list, completed work trend, inspection issues, asset workload, and crew assignments.

0 Open jobs to manage
0 Jobs closed this week
0% Overdue share
0% Inspections needing action

Open jobs

How long requests have been waiting

Backlog aging appears after work orders are created. Add work order created dates so supervisors can see which requests are starting to stall.

Needs attention

Jobs to review before they slip further

Overdue risk appears after active work orders have due dates and priorities. Add both so high-risk items can be surfaced before they slip.

Work completed

Are crews closing work each week?

Closure trend appears after work orders are marked completed. Close finished field work to build the four-week throughput view.

Inspection issues

What inspections need follow-up?

Inspection reporting appears after inspections are submitted. Save inspection result, template, evidence, and linked asset data so supervisors can review completion, failures, follow-up work, and template pass rates.

Work by asset type

Which infrastructure is driving work?

Asset type workload appears after work orders are linked to mapped assets. Link work to hydrants, valves, manholes, sewer lines, or water assets to see demand by infrastructure class.

Asset condition

Which assets are healthy or need service?

Asset condition reporting appears after mapped assets are loaded. Add asset status, open work, and inspection dates to see in-service, needs-service, unknown, open-work, and last-inspected coverage.

Repeat problem spots

Where are issues happening again?

Geographic clustering is not implemented yet. Hot spots will appear here when the same asset has repeated work orders or failed inspections in the loaded report data.

Crew assignments

Who has open work right now?

Crew load appears after work orders are assigned. Add assignees so supervisors can compare active work by crew or operator.

Admin access required

GIS Imports require an Admin role

Imports can create or update municipal asset records, record GIS source details, and affect field workflows. Ask a workspace admin or owner to run imports, review data mapping, or grant the appropriate role.

Viewers and editors can still use maps, work orders, inspections, and reports that their role allows. Import controls are hidden until an Admin signs in.

Admin ingest

Imports (Admin)

Use this workflow to prepare a municipal GIS or asset dataset and decide whether it should become editable operational assets or remain a read-only reference map overlay. Current static support is partial: configured demo imports can run, while file preview and validation are shown as admin workflow placeholders.

1. Upload Choose whether the source is an editable asset layer or reference GIS overlay.
2. Preview Review sample records before any commit.
3. Map Fields Match source columns to TraverseOps fields.
4. Validate Check IDs, coordinates, duplicates, and status values.
5. Confirm Review what will be created or updated.
6. Results View committed records and import history.

Upload

Choose the dataset and source

Dataset Type Choose an asset type when crews will edit status, notes, inspections, or work orders. Choose a reference layer for large GIS context that should stay read-only on the map. Dataset Name or File Enter a dataset name, source file name, or hosted layer name before logging an import run. Source Type Shapefile import is planned but not available yet. Use GeoJSON or CSV for current asset import planning, or record a hosted overlay source for large read-only GIS layers. Source Location File upload and URL ingest are not fully implemented in this static workflow. Record the source here for review, especially if a large layer will be served as a map overlay instead of imported as editable assets. Mapping / Validation Notes Note ID fields, coordinate fields, duplicate handling, field mapping assumptions, and pilot workflow context.

Preview

Sample records

This step will show sample rows, geometry type, coordinate coverage, and record counts before any changes are saved.

Asset ID Type Status

HYD-001 Hydrant In service

Map Fields

Match source fields to TraverseOps

Asset ID: Required unique identifier
Status: Map to In service, Needs service, or Unknown
Geometry: Point, line, polygon, or coordinates

Validate

Checks before commit

Asset IDs present and unique.
Coordinates or geometry available.
Status values mapped to supported conditions.
Duplicate records and missing required fields reviewed.

Missing asset ID Block commit when a row or feature has no stable asset ID. The admin should map an ID field or remove the row.

Invalid geometry Hold records with missing coordinates, malformed geometry, or unsupported coordinate values for review.

Duplicate asset ID Show whether duplicates update existing assets or conflict inside the same upload before committing.

Unsupported file type Accept only supported source types. Shapefile remains planned until backend processing exists.

File too large Stop oversized files and suggest hosted reference layers or bbox-loaded map layers for large datasets.

Empty dataset Warn when a file has no usable rows or features after parsing and field mapping.

Successful import Show created and updated asset counts, then link admins to the map and import history.

Partial import with errors Show imported records, skipped records, and downloadable error details before final review.

Confirm

Review import impact

This step will summarize creates, updates, skipped records, warnings, and the target workspace before commit. The current button commits only supported configured imports.

Results

Import outcome

Results will show committed record counts, validation warnings, failed rows, and links back to the map and import history.

GeoJSON import guidance

What admins should check before committing GeoJSON

Supported geometry Point features are expected for hydrants, valves, manholes, and catch basins when field crews will update individual assets. LineString features fit editable sewer or water mains only when work orders and inspections need to attach to each line. Polygon or MultiPolygon features should usually stay as read-only boundaries or reference areas unless the layer has a defined field workflow.

Required asset ID Every imported feature needs a stable asset ID from the source data. Use an existing municipal ID where possible; avoid row numbers that may change between exports.

Asset type mapping Map source classes to TraverseOps asset types such as hydrant, valve, manhole, catch basin, sewer main, water main, boundary, or custom layer. Only map a source as an operational asset when crews need to edit it, inspect it, or create work against it.

Duplicate behavior Supported imports should update matching asset IDs instead of creating duplicate assets. If duplicate IDs are found in the same file, review them before commit.

Large-layer handling Large mains, parcels, boundaries, and supply areas may be better kept as hosted reference GeoJSON or bbox-loaded map overlays unless field crews need to edit individual features. Serving them as overlays keeps the map useful without turning every GIS feature into an editable asset.

CSV import guidance

Expected columns for spreadsheet-style asset imports

CSV import is not fully wired in this static workflow yet, but the wizard is structured for files where each row represents one editable operational asset with coordinates and mapped fields. Large spreadsheets used only for GIS context should be treated as reference overlays or reviewed before import.

Column Required Purpose

asset_id Yes Stable municipal asset ID

type Yes Hydrant, valve, manhole, etc.

latitude Yes WGS84 latitude

longitude Yes WGS84 longitude

status Yes In service, Needs service, Unknown

Optional fields Include inspection_date, notes, external_gis_id, address, install_year, route, zone, or any source fields that help field crews understand and maintain the editable asset.

Type mapping Normalize CSV type values to TraverseOps asset classes before commit. For example, HYD, hydrant, and fire hydrant should map to Hydrant.

Coordinate checks Latitude and longitude should be decimal degrees. Rows with missing or invalid coordinates should be held for review before they appear on the map.

Shapefile import planned

Expected support once backend processing exists

Shapefile import does not work in the current static app. It will require backend support to unpack a .zip, read .shp, .shx, .dbf, and .prj files, reproject geometry when needed, and run validation before committing records.

Expected package Admins should expect to upload a ZIP containing the shapefile parts together, including projection metadata when available.

Validation needed The backend should verify geometry type, coordinate reference system, required asset IDs, duplicate IDs, and asset type mapping before commit.

Current workaround Export the layer to GeoJSON or CSV first, then use the current import planning workflow to document source, mapping, validation notes, and whether the layer should be imported as editable assets or served as a read-only map overlay.

No import runs have been logged yet. Start with one editable asset layer for operational field work, choose its dataset type, record the source file and validation notes, then commit the supported import or save the run history for admin review. Large read-only GIS context layers can be logged as overlays instead of imported as editable assets.

Import history

Saved runs show dataset source, import outcome, counts, timing, owner, and notes from supported import activity. Rollback requires cloud import tracking and is not available for local/demo import logs.

Dataset	Source Type	Status	Imported Count	Error Count	Started By	Started At	Completed At	Notes	Action

Import rules

Recommended Source Handling

Hydrants Import as editable operational assets when crews need to update status, complete inspections, attach photos, or open work orders on individual hydrants.
Large GIS layers Serve parcels, boundaries, supply areas, and very large mains datasets as read-only map overlays unless crews need direct write access to individual features.
Operational versus reference Operational assets are searchable records that crews change; reference GIS layers provide map context and may be loaded from hosted GeoJSON or bbox layer APIs.
Validation notes Record transforms, source dates, and QA assumptions inside each import run.

Advanced / Developer notes

Editable/searchable operational layers are stored in the configured records backend so inspections, work orders, notes, and evidence can attach to each asset. Large read-only reference GIS layers can stay as hosted GeoJSON overlays or use the bbox layer API for map display.

Layer model

Layer Strategy

Editable layers Operational assets that crews inspect, update, and link to work orders.

Reference layers Read-only GIS overlays loaded for context without creating editable asset records.

Run logging Every import should leave an audit note and date trail.

Admin access required

Workspace Administration requires an Admin role

Admin pages control users, roles, crews, templates, imports, map layers, organization settings, billing placeholders, and audit review. Ask a workspace admin or owner to make changes or update your role.

Viewers and editors do not have access to admin settings. The workspace app will keep operational pages available based on your current role.

Admin console

Workspace Administration

Configure the municipal workspace in small, reviewable sections. Features that require cloud administration or billing systems are shown as placeholders until those services are connected.

Users & Roles Crews Asset Types Inspection Templates Work Order Settings Map Layers Imports Organization Settings Billing Audit Logs

Users & Roles

Role Matrix

Use roles to keep shared devices read-only, allow field editors to update operational records, and reserve imports and settings for administrators.

Current user Signed out

Current role Viewer

Invite status Not connected in this workspace

Viewer Can view asset maps, asset details, work orders, inspections, and reports. Cannot edit assets, submit inspections, run imports, change settings, or view billing.

Field Crew Intended for mobile crews who complete assigned work orders, submit inspections, add field notes, and attach evidence. Import, settings, and billing access should stay disabled.

Editor Can update operational assets, create and edit work orders, complete inspections, add notes, and manage field records. Cannot manage imports, organization settings, or billing.

Admin Can manage GIS imports, map layers, inspection templates, work-order settings, users, roles, and audit review. Billing access may depend on organization policy.

Owner Intended for the municipal account owner with Admin permissions plus billing, plan, cancellation, and organization-level controls when those services are connected.

Invite user Email Use the municipal staff email address for the workspace invitation. Role Choose the least-privileged role that matches the user’s field or admin responsibilities.

User invitations require a connected cloud workspace with invite handling. This static/demo workspace shows the form structure only.

Capability	Viewer	Editor	Admin
View assets and maps	Yes	Yes	Yes
Update status and notes	No	Yes	Yes
Create assets and configure layers	No	No	Yes
Access imports and admin settings	No	No	Yes

User invitations are not wired in this static workspace yet. Invite flows should collect name, email, role, department, and whether the user needs mobile field access.

Crews

Crew Assignments

Crews group field users so supervisors can assign work to a team, filter work-order boards and reports by crew, and compare workload across operators.

No crews configured Crews will appear here with supervisor, members, service area, active work count, and reporting filters once cloud crew management is connected.

Create crew Crew name Name used for assigning work orders and filtering reports. Supervisor Optional supervisor contact for crew coordination. Service area Optional service area, department, or asset focus.

Crew creation requires a connected cloud workspace. When implemented, crews can receive work assignments and power reporting filters for backlog, overdue work, inspections, and crew load.

Crew management is not implemented yet. A cloud workspace should support crew names, supervisors, members, service area, active/inactive status, assignment rules, and report filters.

Asset Types

Operational Asset Registry

Water Hydrants, valves, water mains, and supply areas.

Sewer Manholes, sewer mains, blocked lines, and issues.

Reference Property boundaries and custom read-only GIS overlays.

Asset type customization is not implemented yet. Start with the built-in municipal classes, then add custom fields after import requirements are known.

Inspection Templates

Template Library

Templates define checklist items, required evidence, result options, severity, and whether failed inspections create follow-up work. Required checklist items should be completed before submission; failed results can require photos, findings, severity, and follow-up settings.

Hydrant routine Required checklist: cap condition, flow or pressure reading, and leak or obstruction check. Failed results should capture severity, findings, and evidence photos.

Sewer visual Required checklist: access point condition, blockage or debris check, and surface hazard review. Failed inspections can create follow-up work for blocked lines or manholes.

Catch basin check Required checklist: grate and frame condition, sediment or debris level, and drainage flow path. Photos help document cleaning or repair needs.

Valve exercise Required checklist: location and access, exercise turns or operating status, and box or surface condition. Severity should distinguish access issues from urgent repair needs.

Create template Template name Template name crews will see before starting an inspection. Asset type Asset class this checklist applies to. Failed inspection behavior Configure what additional evidence or follow-up is needed after a failed inspection.

Template creation and editing require cloud template storage. When implemented, admins should be able to configure required checklist items, photo rules, severity levels, and automatic follow-up work-order settings.

Work Order Settings

Rules and Follow-Up Defaults

These settings shape how municipal work orders move through the field queue, how priority is interpreted, when due dates become risky, and what happens after failed inspections.

Statuses Open means work is waiting to be started. In progress means a crew has begun the task. Completed means the work is closed but can be reopened if more action is needed.

Priorities Low is routine, Medium is normal scheduled work, High should be handled soon, and Critical should stay visible in the priority queue until resolved.

SLA warning days before work is treated as overdue risk Used by dashboards and reports to flag active work orders that are approaching or past their expected completion window. Require photo evidence on failed inspections When enabled, failed inspection submissions should include a photo before they are considered complete. Auto-create follow-up work orders after failed inspections When enabled, a failed inspection can prepare a linked follow-up work order with priority based on severity.

Workspace settings are using the current defaults. Review inspection rules before field rollout, invite the municipal users who need access, and save changes when policy decisions are final.

Map Layers

Layer Visibility and Sources

Map layer administration should distinguish editable operational assets from read-only reference overlays.

Operational layers Hydrants, valves, manholes, catch basins, mains, and other records crews update.

Reference overlays Property boundaries, water supply areas, parcels, and large GIS layers served for map context.

Layer source editing is not implemented in Admin yet. Use Imports to record source files and the Map page to view current layer controls.

Imports

Data Ingest Governance

Operational asset imports Use for records crews will inspect, update, and connect to work orders.
Reference GIS overlays Use for large read-only context layers that should not become editable assets.
Rollback planning Rollback requires cloud import tracking before it can be safely enabled.

Organization Settings

Organization Profile

Organization settings identify the municipality, workspace URL slug, default timezone, administrative contact, and support contact shown to staff.

Municipal profile Municipality name Municipality or public works organization name. Workspace slug Short workspace identifier used in production URLs. Timezone Default timezone for due dates, reports, and audit timestamps. Contact email Administrative contact for workspace access questions. Support contact Support contact shown to municipal staff.

Organization profile editing requires backend workspace storage. These disabled local placeholders show the fields a production workspace should manage.

Organization profile editing is not implemented yet. The app currently displays configured workspace identity when available and falls back to demo/local workspace labels.

Billing

Plan and Usage

Billing should summarize the current plan, users, asset limits, storage limits, and billing contact. Payment collection is not implemented in TraverseOps yet.

Current plan Pilot placeholder

Plan records are not connected. Use this as a read-only placeholder until billing storage exists.

Users Not metered locally

Production billing should show invited users, active users, and role mix.

Asset limits Not enforced locally

Limits should account for editable operational assets and large read-only GIS overlays separately.

Storage limits Not measured locally

Storage should include evidence photos, import files, reports, and retained audit history.

Billing contact Not configured

A cloud workspace should store the municipal billing or administrative contact for plan notices.

Billing and payments are not implemented in this static app. Municipal pilots should review scope, user count, asset count, import support, storage needs, and billing contact before production rollout.

Audit Logs

Workspace Activity

Audit logs help administrators review imports, settings changes, asset edits, work-order activity, inspection submissions, and user changes.

Filters apply to audit rows currently loaded in this workspace. Cloud audit history uses the normalized audit_logs table when connected.

No audit rows loaded.

No admin audit records are loaded yet. TraverseOps will track import runs, import rollback attempts, settings changes, user and role changes, template edits, layer changes, billing updates, and other administrator actions when cloud audit logging is connected.