Home › Forums › Show & Tell › How BrightLeaf Giving runs fiscal sponsorship on Gravity Forms

How BrightLeaf Giving runs fiscal sponsorship on Gravity Forms

Tags: case-study

The problem. BrightLeaf Giving hosts charitable programs under a fiscal sponsor: community support funds, social impact campaigns and education funds. Every program needs an application, a review, donation tracking, disbursement requests and a dashboard for the person running it. We didn't want a separate app for each of those.

Who uses it. Program managers, our review team and finance. Our forms hold about 17,800 active entries, and the Master Ledger form alone records about 150 funding, disbursal and fee transactions a month.

The stack. One WordPress multisite. Gravity Forms for every intake, Gravity Flow for reviews and disbursement approvals, GravityView for the dashboards. Every money figure on a dashboard is a GravityOps Global Variable, defined once and reused wherever it appears. New programs watch a short training video in a GravityOps Multi Media field before their dashboard opens, and an AI review step reads each application before a person does.

The data flow.

  1. A program manager applies through a Gravity Form.
  2. Gravity Flow routes the application to review, then to approval.
  3. Every funding, disbursal and fee transaction lands as an entry in one Master Ledger form.
  4. Disbursement requests are Gravity Flow approvals before any money moves.
  5. Each program's dashboard is a GravityView over those same entries, so there's no second system to keep in sync.

What we'd change. The ledger has no Refund transaction type. We book refunds as a negative Fee with "REFUND" in the description. It works, but refund reporting becomes a text search, and we'd add a proper type if we built it again.

Ask us anything about the setup.

<p><strong>The problem.</strong> BrightLeaf Giving hosts charitable programs under a fiscal sponsor: community support funds, social impact campaigns and education funds. Every program needs an application, a review, donation tracking, disbursement requests and a dashboard for the person running it. We didn't want a separate app for each of those.</p><p><strong>Who uses it.</strong> Program managers, our review team and finance. Our forms hold about 17,800 active entries, and the Master Ledger form alone records about 150 funding, disbursal and fee transactions a month.</p><p><strong>The stack.</strong> One WordPress multisite. Gravity Forms for every intake, Gravity Flow for reviews and disbursement approvals, GravityView for the dashboards. Every money figure on a dashboard is a GravityOps Global Variable, defined once and reused wherever it appears. New programs watch a short training video in a GravityOps Multi Media field before their dashboard opens, and an AI review step reads each application before a person does.</p><p><strong>The data flow.</strong></p><ol><li>A program manager applies through a Gravity Form.</li><li>Gravity Flow routes the application to review, then to approval.</li><li>Every funding, disbursal and fee transaction lands as an entry in one Master Ledger form.</li><li>Disbursement requests are Gravity Flow approvals before any money moves.</li><li>Each program's dashboard is a GravityView over those same entries, so there's no second system to keep in sync.</li></ol><p><strong>What we'd change.</strong> The ledger has no Refund transaction type. We book refunds as a negative Fee with &quot;REFUND&quot; in the description. It works, but refund reporting becomes a text search, and we'd add a proper type if we built it again.</p><p>Ask us anything about the setup.</p>

Leave a Reply

This topic is locked. No more replies are allowed.

Log in or create an account to reply.