SfSkills Domains Docs GitHub

Home / admin / program-outcome-tracking-design

program-outcome-tracking-design

Design guidance for program outcome measurement in Salesforce nonprofit orgs: logic model structure, indicator taxonomy, impact reporting design, and grant compliance reporting using NPSP Program Management Module (PMM) or Nonprofit Cloud (NPC) Outcome Management. NOT for configuring PMM programs, cohorts and service deliveries - use admin/npsp-program-management. NOT for setting up grant tracking, funding awards and disbursements - use admin/grant-management-setup.

Open the skill folder on GitHub

Program Outcome Tracking Design

This skill activates when a nonprofit BA or program staff member needs to design an outcome measurement framework in Salesforce — mapping logic model components to platform objects, building indicator tracking, and designing grant compliance reports. It does NOT cover CRM Analytics report building, PMM package setup, or fundraising analysis.

Before Starting

Gather this context before working on anything in this domain:

Core Concepts

PMM Does Not Ship Outcome or Indicator Objects

NPSP Program Management Module (pmdm namespace) provides operational service delivery tracking — who received what service when. It does NOT provide dedicated Outcome__c, Indicator__c, or LogicModel__c objects. Nonprofits that expect PMM to "do outcomes" are commonly disappointed.

What PMM provides for outcome-adjacent tracking:

Structured logic model outcome tracking (indicators, targets, actuals, baseline comparisons) requires custom objects on NPSP/PMM orgs.

NPC Outcome Management (NPC Only)

Nonprofit Cloud has a distinct Outcome Management feature with native objects:

ObjectRole
OutcomeRepresents a program result statement
IndicatorA measurable proxy for an Outcome
Indicator ResultThe actual measured value at a point in time
Participant GoalAn individual-level outcome target

This feature is NOT available in NPSP/PMM orgs. Designs using Outcome or Indicator objects require NPC licensing.

Logic Model Structure in Salesforce

A standard nonprofit logic model maps inputs → activities → outputs → outcomes → impact. In Salesforce:

Logic Model LayerPMM ObjectNotes
ActivitiesService__cType of service delivered
OutputsServiceDelivery__c (Quantity__c)Units delivered
Outcomes (completion)ProgramEngagement__c (Stage__c)Graduated/completed status
Outcomes (measured)Custom Outcome__c or NPC IndicatorRequires custom design or NPC
ImpactReports and dashboardsAggregated across cohorts

Common Patterns

Custom Outcome Tracking on NPSP/PMM

When to use: NPSP org with PMM where grant reporting requires measured outcomes beyond service counts.

How it works:

  1. Create a custom Outcome__c object with fields: Program__c (lookup to Program__c), Indicator__c (text or lookup), TargetValue__c, ActualValue__c, MeasurementDate__c, ProgramEngagement__c (lookup).
  2. Define the indicator taxonomy based on grant requirements (e.g., "Number who gained employment," "Percentage with improved housing stability").
  3. Staff enter Outcome records per participant per measurement period.
  4. Build reports joining ProgramEngagement__c → Outcome__c to aggregate indicators by program and grant period.

Why not ServiceDelivery Quantity: ServiceDelivery Quantity tracks units of service (sessions, hours) — not outcomes. Using it for outcome measurement conflates activity outputs with program results, producing grant reports that describe activity, not impact.

NPC Outcome Management

When to use: Nonprofit Cloud org with Outcome Management enabled.

How it works:

  1. Enable Outcome Management in NPC Setup.
  2. Create Outcome records defining program result statements.
  3. Create Indicator records linked to each Outcome with measurement type and unit.
  4. Create Indicator Results at assessment intervals (monthly, quarterly, program end).
  5. Create Participant Goal records for individual-level targets.
  6. Build reports on Indicator Result to track aggregate progress vs. targets.

Why not custom objects: NPC Outcome Management provides a structured, supported framework that connects outcomes to program enrollments natively, reducing custom development and avoiding data model fragmentation.

Decision Guidance

SituationRecommended ApproachReason
NPSP/PMM org — simple output countingServiceDelivery__c Quantity__c + reportsBuilt-in, no custom objects needed
NPSP/PMM org — grant requires measured outcomesCustom Outcome__c object + ProgramEngagement lookupPMM has no native Outcome object
NPC org — outcome measurementNPC Outcome Management (Outcome, Indicator, Indicator Result)Native, supported, no custom dev
Grant reporting on participants who completed programProgramEngagement Stage__c = GraduatedBuilt-in completion tracking
Pre/post measurement (surveys, assessments)Custom Outcome__c with pre/post measurement date fieldsPMM does not have survey instruments
CRM Analytics impact dashboardsCRM Analytics with PMM data sourcesThis skill does NOT cover CRM Analytics — separate skill
  1. Platform confirmation — Determine NPSP/PMM or Nonprofit Cloud (NPC). This is the branching decision point for all subsequent design choices.
  2. Grant requirements analysis — Collect all grant reporting templates and indicator definitions before designing objects. Reports drive data model requirements.
  3. Logic model mapping — Map each logic model component (outputs, outcomes, impact) to available PMM objects and identify gaps requiring custom objects.
  4. Data model design — For NPSP/PMM, design custom Outcome__c object with appropriate fields and lookups. For NPC, configure Outcome Management.
  5. Report design — Design the grant compliance report layout first; validate that the data model supports the required aggregations (by program, by service, by cohort, by grant period).
  6. Staff training design — Define the data entry workflow for staff: when to create Outcome records, how to measure indicators, and how measurement dates align with grant reporting periods.
  7. Review — Validate that outcome objects use PMM standard object lookups (not Contact directly), that all grant indicator definitions are reflected in the data model, and that report date ranges match grant periods.

Review Checklist

Salesforce-Specific Gotchas

  1. PMM ships no Outcome or Indicator objects — The most common misconception. PMM provides operational service delivery tracking, not outcome measurement. Outcome tracking requires custom objects on NPSP/PMM orgs or the NPC Outcome Management feature.
  2. Using NPSP Opportunity reports for program impact is incorrect — Opportunities in NPSP represent gifts, not program results. Reports on Opportunity Amount have no relationship to program outcomes. Grant reports using Opportunity data to claim program impact conflate fundraising data with program data.
  3. NPC Outcome Management is not available in NPSP/PMM orgs — Attempting to create Outcome or Indicator objects in an NPSP/PMM org fails — these are NPC-specific objects. Design for each platform separately.

Output Artifacts

ArtifactDescription
Logic model to Salesforce mappingLogic model components mapped to PMM objects and custom objects
Outcome data model designCustom Outcome__c or NPC Outcome Management object model
Grant compliance report designReport layout showing indicator aggregations aligned to grant template

Dependencies

Package files