Nonprofit consultant-selection guide
Guide 2: Map systems and stakeholders before procurement
Create enough shared operating context to scope real work without exposing protected information.
Map records, work, and ownership together
List each system of record, what it is trusted to hold, who administers it, who uses it, and where information enters or leaves. Trace representative workflows across development, programs, finance, communications, operations, and leadership where they actually intersect.
Mark duplicate entry, spreadsheets used as shadow systems, manual reconciliations, exports, vendor-managed connections, and processes understood by only one person. These facts shape effort and risk more than a feature wish list.
Separate evidence from assumptions
Label what the team has observed, what a system report confirms, what policy requires, and what still needs discovery. Include rough ranges only when they are supported and safe to share. Do not present hoped-for data cleanliness or staff capacity as a fact.
Use public, fictional, or redacted examples during selection. Data access should follow an approved purpose, minimum scope, security method, and accountable owner after the engagement terms are settled.
Give affected people a defined role
Identify the executive sponsor, business owner, system administrator, daily users, information-security or privacy reviewer, procurement owner, and final acceptance authority. Small nonprofits may assign several roles to one person, but the decisions still need names.
Plan how frontline staff and people affected by the service will inform requirements when appropriate. Participation should be safe, purposeful, and clear about what is and is not being decided.