Prepare an ArcGIS nonprofit application
The application is easier when the organisation can explain both who it is legally and what it wants GIS to do.
Prepare the organisation facts
Have available:
- legal entity name
- NZBN/Charities Services/incorporation details where applicable
- constitution/trust deed or public purpose summary if requested
- main activities
- website or other public description
- primary organisational contact
Do not reshape the organisation to sound like an American 501(c)(3). Esri explicitly uses local review outside the US.
Prepare the GIS use case
A one-page use case can cover:
- number of staff/kaimahi who need to create/edit maps
- number who only need to view
- whether ArcGIS Pro is required
- field collection needs
- public StoryMaps/web maps
- internal/private maps
- partner/council sharing
- approximate data volumes, especially imagery/attachments
- training needs
A useful first-year scope
Avoid buying or configuring an enterprise-scale environment before one workflow works. A realistic first year might be:
- one ArcGIS Online organisation
- a small number of creator/editor users
- one taiao or marae field workflow
- one internal web map
- one public StoryMap or map if useful
- completion of core e-learning
- documented admin/handover
Questions for Eagle
Ask directly:
- Does our legal entity meet the current NZ Esri Nonprofit Program criteria?
- What ArcGIS Online/Pro user types are included or discounted?
- What is the current annual term and renewal process?
- What support is included locally?
- How are ArcGIS Online credits/storage charged under this programme?
- Can products be added later rather than all at once?
- What happens to data/content if we do not renew?
After approval
Create at least two administrators, an organisation naming convention and groups for actual projects. Put the organisation, not one consultant or volunteer, in control of the subscription and core content.
See The one-person GIS and GIS succession.
Last reviewed: 26 August 2026