FAQ | Sitehunt

If you don’t see your question here, contact us and we’ll point you to the right answer (or add it to this page).

Most asked

How frequently is enrichment data refreshed in Sitehunt?

Sitehunt refreshes enrichment on rolling schedules that vary by source (some layers update more often than others). When enrichment changes, you can review what changed and when, and your team can override or supplement enrichment with local data when needed.

What user roles are available in Sitehunt and how do permissions differ?

Sitehunt supports role-based access so teams can collaborate without losing control.

Admin: Manages organization settings, users, and configuration.
Editor: Creates and updates properties, files, and responses (within allowed scopes).
Viewer: Read-only access for stakeholders and partners.

Can we export our data from Sitehunt?

Yes. Sitehunt is designed around data portability. You can export property records and supporting information in open formats so you’re never locked in.

If you’re moving systems or need a full backup/export, we support a complete export upon written request (see the export SLA described on the About page).

Do I need GIS experience to use Sitehunt?

No. Sitehunt is built for economic developers first. Mapping and spatial context are presented in plain language so you can answer site-selector questions without being a GIS specialist.

If you do have GIS capacity, you can still bring in GIS layers and workflows as needed.

Is Sitehunt a GIS platform?

No. GIS is great at answering where something is. Sitehunt is built to answer whether a site works: utilities, zoning, workforce access, constraints, and fit. It still gives you mapping tools and spatial context where they help.

Data & accuracy

Is the data accurate?

Sitehunt is designed to help teams defend their data.

Sources are transparent: enrichment is tied to known sources/layers.
Edits are traceable: key actions and updates can be audited.
Local knowledge wins: your team can override enrichment with local datasets and verified updates.

Can we bring our own data (or corrections)?

Yes. Many teams keep “gold source” spreadsheets, utility letters, or internal datasets. Sitehunt is built to incorporate that information rather than forcing you to start over.

Users & access

Do you charge per user?

No. Sitehunt is designed for collaboration, so you can add stakeholders and partners without budgeting per-seat licenses.

Can partners (utilities, regional allies) collaborate with us?

Yes. Partners can be given the right level of access so they can help fill in data gaps and contribute to RFI responses without exposing admin settings or unrelated work.

Exports & ownership

Who owns the data?

You do. Your property records and local edits are yours, and the platform is built to keep your data portable.

What does “export” include?

At a minimum: property records and structured fields. Depending on what your team stores, exports can also include attachments and generated deliverables (like site sheets) in standard formats.

Mapping & GIS

What kinds of mapping does Sitehunt support?

Sitehunt includes mapping as a tool inside the workflow. Use it to understand access, context, and constraints, and to generate maps for deliverables.

Can we still use our existing GIS tools?

Yes. Sitehunt is designed to complement GIS (and replace the “spreadsheet + email chaos” around it), not force you to abandon tools you already rely on.

RFIs & deliverables

How does Sitehunt help with RFIs?

Sitehunt is designed to reduce RFI response time by keeping property data complete, consistent, and ready to assemble into response packages.

What deliverables can we generate?

Common outputs include site sheets/spec sheets, exportable datasets, and presentation-ready summaries. What’s available depends on the product configuration your team is using.

Getting started

Do we need to install anything?

No. Sitehunt is browser-based.

How long does onboarding take?

It depends on where your data starts today. If you already have a spreadsheet (or a handful of priority properties), onboarding usually starts with import + enrichment, then a guided workflow to close the gaps that matter for your typical RFIs.