Working with GIS consultants without losing control
A good consultant can strengthen Māori GIS capability. A weak commercial arrangement can leave an iwi, hapū or Māori organisation dependent on the consultant for access to its own system.
The useful question is whether the relationship supports the kaupapa, leaves capability behind and makes it practical for the organisation to continue the mahi after the engagement ends.
A contract matters, but it is not the whole relationship. Whakawhanaungatanga, trust, clarity about roles and a shared expectation of capability transfer can matter just as much as clauses about accounts and intellectual property.
Strong and weak arrangements
| Area | Strong practice | Weak practice |
|---|---|---|
| Relationship | kaupapa, roles, expectations and handover are understood by both sides | supplier relationship is treated as purely transactional |
| Cloud tenant | organisation owns it; supplier has delegated access | supplier owns it and invoices the client |
| Administrators | more than one organisational admin | only consultant has master access |
| Domain | registered to organisation | registered personally by developer |
| Data | complete export in agreed usable formats | client gets only maps or screenshots |
| Metadata and attachments | included in handover | forgotten or trapped in platform |
| Source code | organisation repository or contractually accessible | only on consultant laptop |
| IP | Māori data, configuration and reusable supplier IP are distinguished | blanket contractor-ownership clause |
| AI | training, model-improvement and tool use are visible | contract silent |
| Subprocessors | named and locations understood | unknown |
| Exit | process, time and cost defined and tested | we can sort that out later |
| Backups | retention and deletion behaviour documented | live delete mistaken for complete deletion |
| Capability | training, pairing and runbooks are deliverables | supplier remains indispensable |
Keep the platform relationship with the organisation
Where practical, the iwi, hapū or Māori organisation can hold the main relationship with the platform, including:
- cloud subscription
- ArcGIS organisation
- domain
- code repository
- billing account
- password vault
- database account
- support contract
The supplier can then have the access needed to do the work.
That makes changing suppliers easier and reduces the risk that a commercial dispute becomes an access problem. It also keeps mana whakahaere over the technical environment close to the organisation whose kaupapa the system exists to serve.
See Access and security, Cloud is not one thing and The one-person GIS.
Define what a complete export means
Before relying heavily on a platform, it helps to know what can actually be exported.
That may include:
- vector and raster data
- attachments and photographs
- metadata
- relationship tables
- coded values
- schemas
- forms
- application configuration
- scripts
- documentation
- source code where applicable
- role and account configuration
- provenance and context needed to interpret the material
Testing the export before project close is much easier than discovering gaps during a supplier change.
Returning files without the kōrero, source context and project history needed to understand them is not a complete handover.
See Metadata and documentation, Whakapapa of data and Backups are data too.
Separate Māori data from supplier IP
A supplier may legitimately retain ownership of reusable software, libraries or generic methods. Project data, Māori-held information and project-specific content are different things.
Contracts are clearer when those categories are separated rather than collapsed into one blanket IP clause.
For Māori GIS, some relationships and responsibilities also sit outside ordinary copyright language. That is another reason to keep the kaupapa and source context visible alongside the legal terms.
Make AI use visible
A modern supplier may use generative AI, coding assistants, document-processing tools or AI-enabled SaaS.
Useful things to know include:
- which AI services are used
- what project material is sent to them
- whether content can be used for model training or product improvement
- where prompts, files and outputs are retained
- what subprocessors are involved
- what happens to generated derivatives at the end of the work
The point is not to ban AI by default. It is to avoid discovering later that project material was flowing through a service nobody had considered.
See AI and Māori GIS, Artificial intelligence and GIS and Local AI and Māori GIS.
Handover is part of the mahi
Handover works better when it is built into the project rather than left to the final afternoon.
Useful milestones can include:
- account transfer
- documentation
- paired administration
- training and capability transfer
- backup and recovery test
- export test
- supplier-access removal
- unresolved-issue register
- introduction of replacement kaimahi or supplier where relevant
A good handover leaves the organisation able to continue the mahi without depending on one external person.
See GIS succession, When funding ends and After the mapper leaves.
Practitioner note
Consultants and vendors can accelerate Māori GIS work, especially where specialist capability would be uneconomic to employ permanently.
The practical test is whether the engagement leaves the organisation more capable at the end than it was at the beginning. If every future change still requires the original consultant, the software may work while capability transfer has not.
Supplier questions
The full Supplier questionnaire provides a longer list. A shorter discussion can cover:
- Who owns the tenant, domain and administrator accounts?
- Where is each data class stored, processed and backed up?
- What subprocessors exist?
- What AI services are used and how is project material treated?
- Can data, metadata, attachments and provenance be exported completely?
- What remains in backups after deletion?
- What happens on non-payment or contract end?
- What is the exit cost and timetable?
- Who owns custom code and configuration?
- What capability, documentation and practical knowledge will remain after handover?
Related pages
- Working with iwi, hapū and whānau
- The one-person GIS
- Templates and registers
- Cost of a Māori GIS
- Access and security
- GIS succession
Last verified: 26 August 2026