FAQ

Questions buyers ask.

The seven we hear most often, answered directly. If yours isn't here, write us — the answer will be in the next round.

Who is WorkmanIQ for?

Small-to-mid-sized municipalities, public works departments, water and sewer authorities, facilities teams, and fleet operations. The buyers are typically Public Works Directors, City or Town Managers, Utility Supervisors, Facilities Leads, and the IT and procurement teams that approve the purchase.

If your team currently runs on spreadsheets, paper tickets, an aging legacy CMMS, or a citizen-intake-only tool with nothing behind it — you're our buyer.

How long does setup take?

A standard onboarding takes 2–4 weeks end to end: tenant provisioning, divisions and roles, user import, asset import, and integration wiring (ESRI, SeeClickFix, telematics if applicable). Pilots can be running in days.

You don't need to migrate everything before you go live. Most teams start with their highest-pain division and expand as the platform proves itself.

Can we start with one department?

Yes. Most agencies start with one division — usually Streets or Water — prove out the workflow in weeks, then bring on the others. Divisions are first-class objects in the platform: each gets its own categories, SLAs, staff, dashboards, and integrations.

There is no architectural penalty for adding divisions later. The tenant's data model is designed for it.

Does it work offline?

Yes — this is one of the things we built first, not last. The platform installs as a Progressive Web App on iOS, Android, Windows, and Mac. Field crews can:

Create work orders, close them out, leave comments, take photos, capture voice notes, scan QR codes, and update status — all without a signal. The moment connectivity returns, the platform syncs everything in the background. No "try again" dialogs, no lost data.

Can it import our existing assets?

Yes. We support three import paths:

ESRI ArcGIS: Bidirectional sync — assets created or updated in either system propagate to the other.
CSV import: A guided importer with field mapping and validation. Common shapes (asset registries, PM schedules, vendor lists) are supported out of the box.
API: A documented REST API and inbound webhooks for systems that prefer programmatic onboarding.

How does AI use our data?

AI calls are scoped to your organization, rate-limited per user, and logged for audit. The AI Assistant is read-only — it analyzes operational data, it does not modify it. Only the prompt context required for the task is sent to the model, not your entire database.

Your data is not used to train third-party models. You can configure your own OpenAI key per tenant, or use ours. AI features can be disabled per-tenant if your jurisdiction requires it.

Full detail is on the Security & Procurement page.

What systems can it integrate with?

The integrations our customers use most often are in the box:

Citizen intake: SeeClickFix v2.
GIS: ESRI ArcGIS (bidirectional).
Telematics: Samsara, Geotab webhooks.
Mapping: Google Maps, Places, Geocoding.
Locates: Utilisync / 811 / MissDigg.
Notifications: Web Push (VAPID), email, daily digest.
Custom: Public REST API and inbound webhooks (API-key authenticated) for everything else.

How is it priced?

Per-organization pricing, not per-seat. Annual or monthly billing. Government cooperative purchasing welcome. No-cost pilots are available for qualifying agencies. Reach out and we'll send numbers tailored to your divisions and asset count.

Do you have references in our region?

Likely — ask us. We'll connect you to the closest comparable agency in your division mix and size.

Still have questions?

Send us yours — we'll answer directly, and your question may end up here for the next buyer.

Ask a question arrow_forward