4.1 Funding Programs, Funding Opportunities (NOFOs) & Public Discovery

4.1 Funding Programs, Funding Opportunities (NOFOs) & Public Discovery

Public sector grantmaking represents one of the most critical mechanisms through which municipal, state, and federal governments execute public policy. Whether distributing federal pass-through funds from major infrastructure legislation, providing disaster recovery subsidies to affected communities, or funding community-based non-profit social programs, government agencies are held to strict standards of transparency, fiscal stewardship, and regulatory compliance.

In Salesforce Public Sector Solutions (PSS) and Salesforce Grantmaking, the grantmaking lifecycle begins long before an applicant submits a proposal. It starts with establishing strategic funding programs, publishing formal Notices of Funding Opportunity (NOFOs), configuring eligibility rules, and providing intuitive public discovery portals. Mastering this data model and its public-facing discovery patterns is essential for the Accredited Professional AP-222 examination.

---

The Hierarchical Grantmaking Data Model: Programs vs. Opportunities

Public sector funding flows through a multi-tiered hierarchy. Legislative bodies appropriate statutory budgets to agencies for specific public policy mandates. Agencies translate these appropriations into overarching grant programs, which in turn publish discrete, competitive funding solicitations.

Salesforce Public Sector Solutions models this hierarchy through two core standard objects: FundingProgram and FundingOpportunity.

┌─────────────────────────────────────────────────────────────┐
│                     FundingProgram                          │
│  "State Clean Energy & Decarbonization Initiative"         │
│  • Total Budget: $50,000,000 (5-Year Appropriation)         │
│  • Legislative Mandate: SB-350 Clean Energy Act             │
│  • Strategic Focus: Grid Modernization & Solar Equity       │
└──────────────────────────────┬──────────────────────────────┘
                               │ 1:N Child Solicitations
       ┌───────────────────────┴───────────────────────┐
       ▼                                               ▼
┌────────────────────────────────┐   ┌────────────────────────────────┐
│      FundingOpportunity        │   │      FundingOpportunity        │
│  "FY26 Municipal Solar Grants" │   │  "FY27 Grid Resilience NOFO"   │
│  • Allocation: $15,000,000     │   │  • Allocation: $20,000,000     │
│  • Window: Mar 1 - May 30      │   │  • Window: Oct 1 - Dec 15      │
│  • Min: $100K | Max: $1.5M     │   │  • Min: $250K | Max: $3.0M     │
└────────────────────────────────┘   └────────────────────────────────┘

The Funding Program (FundingProgram) Standard Object

The FundingProgram object represents the top-level strategic umbrella or multi-year legislative initiative. It acts as the parent container for budgeting, policy tracking, and macro-level reporting.

Key architectural attributes of FundingProgram include:

• Name & Description: The formal title of the public program (e.g., Small Business Revitalization Fund, Affordable Housing Trust Initiative, or Clean Drinking Water State Revolving Fund).
• Parent Program (ParentFundingProgramId): Supports recursive hierarchical nesting, allowing a mega-program (such as a multi-billion-dollar federal block grant) to contain sub-programs administered by distinct state bureaus.
• Total Budget Allocation: The overarching fiscal appropriation authorized by legislation.
• Fiscal Year & Period of Performance: The multi-year statutory timeframe within which appropriated funds must be obligated and liquidated.
• Program Manager & Governing Authority: The internal department, bureau director, or program officer legally accountable for program execution.
• Status: Operational lifecycle states such as Planned, Active, On Hold, or Completed.

The Funding Opportunity (FundingOpportunity) Standard Object

While a FundingProgram defines the strategic policy mandate, agencies do not accept applications directly against the parent program. Instead, agencies publish discrete, time-bound grant solicitations known in government as Notices of Funding Opportunity (NOFOs), Requests for Applications (RFAs), or Grant Solicitations. In Public Sector Solutions, each solicitation is modeled as a FundingOpportunity record.

A FundingOpportunity is always a child of a FundingProgram. It defines the specific operational terms, competitive criteria, application timeframes, and funding caps for a single grant round or fiscal cycle.

Hierarchy Comparison: Program vs. Opportunity

[!IMPORTANT] AP-222 Architecture Core Rule: In Public Sector Solutions, applicants never apply to a FundingProgram. They always apply to a specific child FundingOpportunity. Applications (IndividualApplication) maintain a lookup to FundingOpportunityId, which rolls up through the opportunity to the parent FundingProgram for budgetary reconciliation.

---

Configuring a Notice of Funding Opportunity (NOFO)

Publishing a NOFO in the public sector requires rigorous configuration to ensure public equity, prevent unauthorized submissions outside statutory deadlines, and enforce legislative criteria.

Key NOFO Configuration Elements

1. Application Submission Windows:
   • Start Date (StartDate): The exact date and time when the solicitation opens for public submissions.
   • End Date / Deadline (EndDate): The hard statutory cutoff date and time. Portal intake forms must automatically transition to read-only or closed status once this timestamp passes to comply with administrative procurement laws.
2. Financial Bounds & Award Parameters:
   • Total Amount Available (TotalAmountAvailable): The total financial pool budgeted for this specific competition.
   • Minimum Award Amount (MinimumAwardAmount) & Maximum Award Amount (MaximumAwardAmount): The statutory floor and ceiling for individual grant awards. For instance, a community development NOFO may enforce a minimum award of $50,000 and a maximum cap of $500,000. Intake OmniScripts validate applicant requested amounts against these limits in real time.
   • Expected Number of Awards: Estimated grant count, used by financial officers to calculate target award distributions.
3. Applicant Eligibility Criteria:
   • Standard picklists and multi-select filters define which entity classifications are qualified to apply (e.g., 501(c)(3) Non-Profit, Local Municipal Government, Tribal Nation, Higher Education Institution, Small Commercial Enterprise).
   • Geographic boundaries: Eligible counties, census tracts, or designated environmental justice zones.
4. Cost-Share & Matching Fund Requirements:
   • Many public grants require recipients to contribute matching funds (e.g., a mandatory 20% non-federal cash or in-kind match). The opportunity record specifies whether cost-sharing is required and the mandatory percentage ratio.
5. Application Instructions & Required Document Templates:
   • Standard guidelines, logic model templates, narrative formatting guidelines, and links to required budget spreadsheets or statutory disclosures.

---

Public Discovery via Experience Cloud Grantmaking Portal

Government agencies are legally mandated to make grant opportunities publicly discoverable, accessible, and competitive. Public Sector Solutions delivers this discovery layer through Experience Cloud sites configured with Grantmaking components.

┌─────────────────────────────────────────────────────────────────────────┐
│                     Experience Cloud Grantmaking Portal                 │
│                                                                         │
│  ┌───────────────────────┐  ┌────────────────────────────────────────┐  │
│  │ Faceted Search Filter │  │ Search Results: Funding Opportunities  │  │
│  ├───────────────────────┤  ├────────────────────────────────────────┤  │
│  │ Category: Clean Energy│  │ 🌿 FY26 Community Solar Deployment    │  │
│  │ Status: Accepting App │  │    Agency: Dept of Energy & Env       │  │
│  │ Entity: Non-Profit    │  │    Deadline: May 31, 2026             │  │
│  │ Geography: State-wide │  │    Award Pool: $15M ($100K - $1.5M)   │  │
│  │ Deadline: Next 30 Days│  │    [Check Eligibility]  [View NOFO]   │  │
│  └───────────────────────┘  └────────────────────────────────────────┘  │
└────────────────────────────────────┬────────────────────────────────────┘
                                     │ Click "Check Eligibility"
                                     ▼
               ┌──────────────────────────────────────────┐
               │    OmniScript Pre-Eligibility Screener   │
               │  1. 501(c)(3) tax-exempt status verified?│
               │  2. Located in eligible service county?  │
               │  3. Can provide 20% matching funds?      │
               └─────────────────────┬────────────────────┘
                        Eligible?    │
                   ┌─────────────────┴─────────────────┐
                   ▼ YES                               ▼ NO
     ┌──────────────────────────────┐    ┌──────────────────────────────┐
     │ Direct to User Registration  │    │ Informative Disqualification │
     │ & Launch Full Application    │    │ Summary & Alternative Grants │
     └──────────────────────────────┘    └──────────────────────────────┘

Unauthenticated (Guest) vs. Authenticated Discovery

• Unauthenticated (Guest User) Browsing: Prospective applicants, community advocates, researchers, and taxpayers can browse active, upcoming, and archived funding opportunities without logging in. Experience Cloud components leverage guest user profiles with read-only access to published FundingOpportunity records, honoring government sunshine and open-data transparency mandates.
• Faceted Search & Dynamic Filtering: The portal provides real-time filtering across multiple dimensions: funding domain (e.g., Healthcare, Transportation, Workforce Development), applicant entity eligibility, grant amount ranges, and remaining days until submission deadline.
• Authenticated Constituent Experience: Once an applicant decides to apply, they authenticate via a secure constituent login. Within the authenticated portal, users manage their organization profile, link authorized organization representatives (AORs), view in-flight drafts, and monitor post-award disbursements.

Pre-Eligibility Screening Pattern

A frequent pitfall in public sector grant management is administrative gridlock caused by hundreds of unqualified applicants submitting 50-page proposals, only to be rejected weeks later during initial triage. This wastes applicant resources and overwhelms agency staff.

To solve this, PSS implements an OmniStudio Pre-Eligibility Screening Screener:

1. Before creating a formal application record, the constituent engages with a lightweight, multi-step OmniScript wizard directly from the FundingOpportunity detail page.
2. The screener asks gating questions: Is your organization a registered 501(c)(3)? Do you possess an active Unique Entity Identifier (UEI) on SAM.gov? Does your proposed initiative operate in an eligible jurisdiction?
3. If the applicant fails a gating criterion, the screener provides an immediate, courteous disqualification explanation, preventing wasted effort.
4. If the applicant satisfies all gating rules, the screener presents a call-to-action to authenticate (or register), clones initial screener responses into a new IndividualApplication record, and launches the comprehensive intake workflow.

---

Standard Grantmaking Architecture vs. Legacy Packages

A critical topic on the AP-222 exam is understanding how modern Salesforce Grantmaking in Public Sector Solutions supersedes legacy architectures, specifically the open-source Outbound Funds Module (OFM) and legacy Nonprofit Success Pack (NPSP) extensions.

Historically, grants management on the Salesforce platform relied on managed packages with custom object schemas (prefixed with the outfund__ namespace). While functional, managed packages introduced schema silos, complex upgrades, and limited integration with core platform innovations.

Modern Salesforce Grantmaking re-architects grants management directly into the core CRM platform layer using standard objects.

Detailed Architectural Comparison

Why the Standard Object Model Matters for AP-222

1. Unified Application Architecture: In Public Sector Solutions, IndividualApplication is the universal container for business licenses, professional credentials, social program benefits, and grant requests. Agency caseworkers and compliance officers work across a single familiar data architecture.
2. Zero Namespace Friction: Core standard objects support native platform sharing rules, standard reporting types, Shield Platform Encryption, and OmniStudio Data Mappers without packaging constraints or namespace collisions.
3. Native Business Rules Engine (BRE) Integration: Standard FundingOpportunity and IndividualApplication records map seamlessly into BRE Expression Sets and Decision Matrices for automated eligibility and fee evaluation.
4. Agentforce Readiness: Standard Grantmaking objects map out-of-the-box to Standard Data Model Objects (DMOs) in Salesforce Data Cloud, allowing Agentforce autonomous agents to inspect grant guidelines, answer applicant queries, and verify compliance without custom data pipelines.

---

AP-222 Exam Strategy: Core Scenarios & Traps

• Scenario 1: Structuring Multi-Year Federal Grants with Annual Solicitations: When an exam question specifies that a state transportation authority receives an 8-year federal infrastructure grant and must release distinct competitive funding cycles each autumn with varying award limits, configure a single parent FundingProgram for the overarching federal appropriation, and create separate child FundingOpportunity records each year for the individual competitive cycles.
• Scenario 2: Triage of Ineligible Grant Applicants: If an agency is overwhelmed by hundreds of unqualified non-profit submissions, do not write custom validation rules on the submitted application object that fire upon save. Implement an unauthenticated OmniStudio pre-eligibility screener on Experience Cloud that evaluates gating criteria and prevents ineligible users from creating an IndividualApplication.
• Scenario 3: Legacy Package Replacement: If an exam prompt describes a public agency seeking to replace an older managed package (outfund__) to leverage Agentforce and Business Rules Engine, advise migrating to core standard Grantmaking objects (FundingProgram, FundingOpportunity, IndividualApplication, FundingAward, FundingDisbursement).