Implementing PMM is a multi-month project that combines configuration, training, and ongoing operational discipline. The four-phase routine covers: install the package and configure the basic objects, design the Program structure with the operational team, build the service delivery capture workflow, and operationalize reporting for staff and funders. PMM is free but staff time is not; pace the project realistically and resist over-engineering the data model before live operations begin.
- Install PMM and configure the basic objects
From Salesforce Setup, install the Program Management Module managed package from the Salesforce.org distribution. Confirm the package installs cleanly and the new objects (Program, Program Engagement, Service Schedule, Service Delivery) appear in Object Manager. Assign the relevant permission sets to the staff who will use the module: program coordinators, service delivery staff, evaluation staff. Configure the basic page layouts for each object to match your operational vocabulary; PMM ships with generic field labels that you may want to customize (Student instead of Participant, Class instead of Session). Document the customizations in the runbook.
- Design the Program structure with the operational team
Work with program coordinators to map your nonprofit programs into PMM structure. Each top-level program becomes a Program record. Cohorts (Fall 2025 Job Readiness, Spring 2026 Job Readiness) become Program Cohort records. Service schedules (the weekly class times) become Service Schedule records. Validate the mapping with the actual coordinators who will use the system; PMM mappings that look right on paper sometimes do not match how the program actually operates. Iterate before going live. Document the mapping in the program operations runbook so future coordinators inherit the structure.
- Build the service delivery capture workflow
Pick the capture path that fits your operation. For classroom-based programs, a coordinator-facing roster page where staff check off attendance after each session works well. For drop-in services (food pantry, walk-in counseling), a kiosk or mobile app where clients check in at arrival works better. For field-based programs (home visits, outreach), the Salesforce Mobile App with offline capability is the path. Implement the chosen workflow as a custom Lightning record page or a Flow-driven screen. Train staff on the capture process; the workflow has to be fast and unambiguous, or staff will skip it and the reporting data quality collapses.
- Operationalize reporting for staff and funders
Build the standard PMM reports for daily and weekly operational use: today expected service deliveries, attendance rate by cohort, engagements approaching their end date. Build a Program Manager dashboard combining these reports. Build the grant-specific reports each funder requires; coordinate with grants management staff to ensure the metrics and the report formats match the funder requirements. Schedule the grant reports to email to the appropriate staff before the funder deadline. Train the program team on reading the reports and acting on the metrics; the data is only useful if the team consumes it regularly.
- PMM is free, but staff time is not. Pace implementations realistically; over-engineering the data model before live operations begin produces complexity the staff cannot maintain.
- Service Delivery capture quality determines reporting quality. Sloppy capture produces grant reports that misrepresent the nonprofit work, with real funding consequences.
- PMM and NPSP coexist through the shared Contact object. Plan the relationship explicitly; without coordination, donor data and client data drift apart and the constituent 360 view breaks.
- PMM is being incrementally absorbed into Nonprofit Cloud. For new implementations on Nonprofit Cloud, use the equivalent Nonprofit Cloud objects rather than installing PMM separately.
- Grant reporting requirements vary by funder. Each funder has specific metrics and formats; build grant-specific reports during implementation, not after the first reporting deadline.