← All articles

By ·

How to Hire a GIS Contractor: Scoping Checklist, SOW Template and Red Flags

To hire a GIS contractor, scope deliverables first, then write a SOW fixing CRS, formats, metadata and ownership. Template and vendor questions inside.

A council chamber with wood panelling and rows of seats, where municipal GIS contracts are usually approved
Photo: Michael D Beckwith on Unsplash

To hire a GIS contractor, first write down the decision the work supports and the exact datasets you want back. Then issue a statement of work that fixes the coordinate system, file formats, metadata, data dictionary, acceptance tests and data ownership. Interview vendors on how they handle bad data, and pay for a small pilot first.

This guide covers when a small city or county should outsource GIS services, a scoping checklist, a copyable SOW template, interview questions that expose weak vendors, and how to accept the work.

Should a small city or county outsource GIS or hire staff?

There are four realistic models, not two. The right one depends on how often you need GIS, not on how much you like maps.

ModelWhat it looks likeFits whenTypical weakness
In-house staffOne or more GIS employees own the data and the toolsWeekly operational edits (addressing, permits, utilities), many departments using GISOne-person departments are fragile; vacancies stall everything
ContractorA consultant or firm does defined projectsMigrations, cleanups, analyses, web apps, one-off studiesNo one inside owns the data after the contractor leaves
HybridA trained staff member owns the data; a contractor handles heavy or specialist workMost small cities and counties with NG911 obligationsNeeds a clear split of responsibilities in writing
Shared serviceA county, regional commission or larger neighbour provides GISVery small towns and townshipsYou queue behind other members' priorities

What this looks like in real municipalities

A quick cost check for in-house versus contractor

The May 2025 BLS median wage for US cartographers and photogrammetrists is $39.13 an hour, which is about $81,400 a year at 2,080 hours before benefits, software and training. In Canada, the Job Bank median for GIS and geomatics technicians is CA$38.10 an hour. If your real GIS workload is a few projects a year, a contractor billing a few hundred hours costs much less. If it is a steady stream of edits across departments, staff win. The GIS consultant cost guide has task-level hour estimates for typical projects.

Line chart of annual cost against GIS hours needed per year: an in-house employee at the BLS median wage costs about $81,390 a year, which a contractor matches at 814 hours at $100 an hour or 603 hours at $135 an hour

Break-even between one in-house GIS employee (wage only) and a contractor. Below a few hundred hours a year, contracting is far cheaper.

How do you scope a GIS project before you hire a GIS contractor?

Most bad GIS projects fail at scoping, not at analysis. Work through this list before you write an RFP or send an email.

  1. Name the decision. "Choose three sites for a new store" or "pass the state NG911 GIS submission" is a scope. "Improve our GIS" is not.
  2. List the inputs and who owns them. Address points, centerlines, parcels, customer lists, field boundaries. Note the format, the coordinate system if known, and who can answer questions about each.
  3. Send a real sample. A few hundred records of the actual data. Contractors quote very differently once they see the street names.
  4. Define the area. A boundary file, not a description.
  5. Define every deliverable. Datasets, maps, reports, apps and code, each with a format.
  6. Write the acceptance test. How you will decide the work is done, in numbers.
  7. Decide what happens after delivery. Who maintains the data, and whether you need training or documentation.
  8. Set a budget range and a date. Saying a range gets better proposals than hiding it.
  9. Check standards that apply. For 911 data, the NENA NG9-1-1 GIS data model and any state or provincial submission rules. See NG911 GIS data readiness.

What should a GIS statement of work include?

The template below is written to be copied and filled in. Square brackets are placeholders. It is a practical starting point, not legal advice; have your procurement office or lawyer review the ownership and liability clauses.

STATEMENT OF WORK: [Project name]

1. PURPOSE
   This work supports the following decision or obligation: [one sentence].

2. AREA AND INPUTS
   2.1 Area of interest: [boundary file name], supplied by Client.
   2.2 Client supplies: [list datasets, format, approximate record counts].
   2.3 Client contact for data questions: [name, role], response within
       [3] business days.

3. TASKS
   3.1 [Task, e.g. standardize address point attributes to NENA schema]
   3.2 [Task]
   3.3 Internal quality control before each delivery.

4. DELIVERABLES
   4.1 Datasets
       | Name | Geometry | Format | Approx. features |
       | [address_points] | Point | GeoPackage | [12,000] |

   4.2 Coordinate reference system
       - Horizontal: [EPSG code and name], datum realization [e.g. NAD83(2011)
         or NAD83(CSRS)], epoch [e.g. 2010.0] where applicable.
       - Vertical (if any): [datum and units].
       - Linear units: [US survey feet / metres].
       - No dataset is delivered in an undefined or "unknown" CRS.

   4.3 File formats
       - Primary: OGC GeoPackage (.gpkg), one file, one layer per dataset.
       - Secondary: [Esri file geodatabase, ArcGIS Pro version X] if required.
       - Shapefile only on request, with a field-name crosswalk.
       - Tabular outputs: CSV, UTF-8.
       - Maps: PDF at [size], plus the project file used to make them.

   4.4 Metadata
       - One metadata record per dataset following [FGDC CSDGM / ISO 19115],
         including source, processing steps, date, CRS and contact.

   4.5 Data dictionary
       - For every field: name, alias, type, length, allowed values or
         domain, whether nulls are allowed, source, plain-language meaning.

   4.6 Code and methods
       - Scripts or models used to produce the results, with a README
         explaining how to rerun them.
       - A methods note of [2-5] pages describing assumptions and limits.

5. ACCEPTANCE CRITERIA
   5.1 Zero invalid geometries (self-intersections, null shapes).
   5.2 100% of features carry all fields marked required in the dictionary.
   5.3 All datasets in the CRS specified in 4.2.
   5.4 [Project-specific test, e.g. >= 98% of address points match a
       centerline range with the same street name and correct parity].
   5.5 Client reviews each delivery within [10] business days and returns
       one consolidated list of defects. Contractor fixes defects that
       fail 5.1-5.4 at no cost.

6. OWNERSHIP AND LICENSING
   6.1 On payment, Contractor assigns to Client all copyright and other
       rights in the deliverables created under this SOW. This assignment
       is in writing and signed by both parties.
   6.2 Contractor keeps ownership of pre-existing tools and code, and grants
       Client a perpetual, royalty-free license to use, modify and share
       any of them included in the deliverables.
   6.3 Third-party data: Contractor lists every third-party source and its
       license (for example, OpenStreetMap under ODbL) and flags any
       attribution or share-alike obligations.
   6.4 Contractor does not reuse Client data for other clients and deletes
       working copies within [30] days of final acceptance, on request.

7. SCHEDULE AND MILESTONES
   - Kickoff: [date]
   - Pilot delivery on [sub-area]: [date]
   - Draft delivery: [date]
   - Final delivery: [date]

8. PRICE AND PAYMENT
   - Pricing model: [fixed fee / hourly with not-to-exceed of $X / retainer].
   - Payment tied to accepted milestones: [e.g. 20% pilot, 40% draft,
     40% final].
   - Work outside this SOW requires a written change order with hours and
     cost before it starts.

9. ASSUMPTIONS AND EXCLUSIONS
   - [e.g. Field verification is excluded.]
   - [e.g. Client provides imagery access.]

Why each clause is there

Deliverable formats compared

FormatOpen standardMany layers in one fileLong field namesDate with timeBest use
GeoPackageYes (OGC)YesYesYesPrimary deliverable
Esri file geodatabaseNoYesYesYesTeams working in ArcGIS
ShapefilePublished spec, multi-fileNoNo (10 characters)NoLegacy systems only
GeoJSONYes (IETF RFC 7946)NoYesAs textWeb maps, small datasets
CSV with coordinatesYesNoYesAs textTables and point lists

What questions expose a weak GIS contractor?

Ask these in the interview. The answers tell you more than a portfolio.

QuestionA strong answerA red flag
"Here is a sample of our data. What problems do you see?"Names specific issues: mixed CRS, duplicate addresses, inconsistent street types, invalid geometry"Looks fine" without opening it
"How will you know the output is correct?"Describes automated checks plus a manual sample, with numbers"We review everything carefully"
"Which coordinate system will you deliver in, and why?"Asks what your other systems use, names an EPSG code and datum realization"WGS84" for everything, or "whatever the data is in"
"What happens when the data does not match the standard?"Logs exceptions and returns a list for your decision, does not silently delete records"We clean it up," with no record of what changed
"Can we rerun this without you?"Hands over scripts or models with a READMEProcess lives only in their head or in manual clicks
"Who owns the deliverables and any tools you use?"Clear split between assigned deliverables and licensed pre-existing toolsReluctance to put ownership in writing
"Tell me about a project where the data was worse than expected."A specific story with what they changed in scope or priceNo examples, or blames the client
"Who exactly will do the work?"Names the person and their roleA senior name in the proposal, unnamed juniors doing the work

For NG911 work, add one more: ask them to walk through the checks in NG911 centerline and address QA checks and say which ones they automate. Vague answers about "NENA compliance" without mentioning address ranges, parity or road segment connectivity are a warning sign.

What are the red flags in a GIS proposal?

  1. A price with no task breakdown. You cannot tell what was assumed.
  2. No mention of your data. A generic proposal written before looking at the inputs.
  3. Deliverables described as software screenshots. "An ArcGIS dashboard" is not a dataset spec.
  4. No acceptance criteria, or "to client satisfaction" only. That invites endless revisions or an early declaration of done.
  5. Proprietary lock-in. Deliverables only usable inside the vendor's hosted platform, with no export.
  6. Unlimited revisions at a fixed price. Either the price is padded or quality will drop on later rounds.
  7. Silence on third-party data. Business listings, imagery or parcel data with license terms that do not allow your intended use.
  8. No plan for after delivery. No documentation, training or handover.

How should you accept GIS deliverables?

Run three layers of checks before you sign off.

Automated checks

Validate geometry, CRS and required fields with a script or tool. Open-source tools such as GeoLint, which I wrote, check for invalid geometries and CRS mismatches in batches. Most desktop GIS software has equivalent validation tools. These checks map directly to acceptance criteria 5.1 to 5.3 in the template.

Sampled manual review

Pick 30 to 50 features at random and compare them with imagery or source records. Pick another 10 from the places you know are hard, such as a new subdivision or a road that changed names.

Fitness for use

Load the data into the system that will use it, whether that is a CAD system, a web map or a reporting tool. Many problems only appear at this step, such as a field type the target system rejects.

When outsourcing GIS is the wrong approach

If you need a GIS project scoped or done, or want a second opinion on a statement of work, email me at mahad.imran29@gmail.com.

Frequently asked questions

Should a small town hire a GIS person or outsource GIS?

If the town needs GIS edits every week, such as new addresses, permits or utility updates, it needs at least a trained staff member who owns the data. Project work like a data migration, a web map or an NG911 cleanup is usually cheaper to contract. Many small municipalities use a hybrid: a part-time internal data owner plus a contractor, county or regional commission for heavier work.

What file format should I ask a GIS contractor to deliver?

Ask for GeoPackage as the primary format because it is an open OGC standard, holds many layers in one file and keeps long field names and full date-time values. Add an Esri file geodatabase if your staff work in ArcGIS. Accept shapefiles only as a secondary copy, since field names are limited to 10 characters and date fields cannot store a time.

Who owns the GIS data a contractor creates for me?

Do not assume you do. In the US, contractor work is a work made for hire only if it fits one of nine statutory categories and both parties sign a written agreement saying so. In Canada, the author is the first owner and any assignment must be in writing and signed. Put an explicit assignment or license clause in the contract and have your lawyer review it.

Can a county outsource NG911 GIS data maintenance?

A county can outsource the initial cleanup and the quality checks, but daily maintenance works best with someone local who learns about new addresses and road changes as they happen. A common pattern is a contractor for the cleanup and automated QA, with a county staff member or regional partner making the routine edits and the contractor reviewing them on a schedule.

How do I compare GIS contractor proposals fairly?

Give every bidder the same deliverables list, the same sample data and the same acceptance criteria, then ask for task-level hours rather than a single total. Score proposals on how specifically they address your data problems, not on software logos. A short paid pilot on a small area is the most reliable way to separate two close bids.

Let's talk.

Best way to reach me is email. I respond to most things.