Environment

The functions every environment company runs on. It has no schema of its own: companies here are mapped on the Non-profit schema, and what it does not cover is recorded as gaps.

Baseline: Non-profit v2
Inherited from: Non-profit
Mapped on the schema: 52 of 52 placed here
Primitives: 55 in 8 parts
Last updated: 3 Nov 2026

What the registry holds here

Environment and below · public parts only

With public findings: 52
Public parts: 117
Distinct sources: 68
Last change: 2 Nov 2026

Organizations by public parts

Counts of what public research has found and sourced, each part with its source on the organization’s profile. They say what is known, not how much of the industry exists.

Deepen this industry

Focused research on the organizations with the fewest mapped parts in environment; what it finds is public for everyone.

Forest Stewardship Council3 parts
Native Seeds/SEARCH3 parts
Island Conservation3 parts
International Rivers3 parts
Audubon Society of Portland3 parts

How automatable each primitive is, estimated from the 446 organizations mapped in public on the Non-profit schema, which this industry inherits: the share of those with the primitive that run it on software. Estimate from public data: the share of mapped organizations that run this on software. Not a recommendation.

LevelAll55 High4 Medium31 Low20

Primitive	Layer	Automation	Peers on software	Software parts named most
Mission and cause Demand: winning customers	Decisions	LowLayer only	1 of 446 mapped; too few to read	—
Development team Demand: winning customers	People	LowLayer only	0 of 446 mapped; too few to read	—
Program fees and suggested gifts Demand: winning customers	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Grant agreements and service contracts Demand: winning customers	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Partners and contractors Supply: making or delivering the offer	People	LowLayer only	0 of 446 mapped; too few to read	—
Participant and supporter care Customers: keeping them	People	LowLayer only	0 of 446 mapped; too few to read	—
Donor stewardship Customers: keeping them	People	LowLayer only	0 of 446 mapped; too few to read	—
Budgets by fund Money: getting paid and paying	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Restricted funds and cost allocation Money: getting paid and paying	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Org structure People: who does the work	People	LowLayer only	0 of 446 mapped; too few to read	—
Performance and pay People: who does the work	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Policies and culture People: who does the work	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Volunteers People: who does the work	People	LowLayer only	0 of 446 mapped; too few to read	—
Security and access Systems: tools and data	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Charitable registration and tax status Control: rules the company runs under	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Charity regulation Control: rules the company runs under	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Insurance and risk Control: rules the company runs under	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Health, safety and environment Control: rules the company runs under	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Strategy and theory of change Direction: deciding where it goes	Decisions	LowEstimate	0 of 418 on software	—
Board governance Direction: deciding where it goes	Decisions	LowLayer only	0 of 446 mapped; too few to read	—

The rule, the same for every industry: with 5 or more organizations having the primitive, 50% or more of them on software is high, 20% or more medium, below that low. With fewer, the level rests on the primitive's layer alone and says "Layer only". Software parts are counted once per organization; a detected technology is named by its product. See the blueprint for which organizations run each.

LevelAll55 High4 Medium31 Low20

Primitive	Layer	Automation	Peers on software	Software parts named most
Mission and cause Demand: winning customers	Decisions	LowLayer only	1 of 446 mapped; too few to read	—
Development team Demand: winning customers	People	LowLayer only	0 of 446 mapped; too few to read	—
Program fees and suggested gifts Demand: winning customers	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Grant agreements and service contracts Demand: winning customers	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Partners and contractors Supply: making or delivering the offer	People	LowLayer only	0 of 446 mapped; too few to read	—
Participant and supporter care Customers: keeping them	People	LowLayer only	0 of 446 mapped; too few to read	—
Donor stewardship Customers: keeping them	People	LowLayer only	0 of 446 mapped; too few to read	—
Budgets by fund Money: getting paid and paying	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Restricted funds and cost allocation Money: getting paid and paying	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Org structure People: who does the work	People	LowLayer only	0 of 446 mapped; too few to read	—
Performance and pay People: who does the work	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Policies and culture People: who does the work	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Volunteers People: who does the work	People	LowLayer only	0 of 446 mapped; too few to read	—
Security and access Systems: tools and data	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Charitable registration and tax status Control: rules the company runs under	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Charity regulation Control: rules the company runs under	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Insurance and risk Control: rules the company runs under	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Health, safety and environment Control: rules the company runs under	Decisions	LowLayer only	0 of 446 mapped; too few to read	—
Strategy and theory of change Direction: deciding where it goes	Decisions	LowEstimate	0 of 418 on software	—
Board governance Direction: deciding where it goes	Decisions	LowLayer only	0 of 446 mapped; too few to read	—