1. Community Development Platform
  2. Features
  3. Funding cases
Feature · Funding cases

Funding cases

Keep a request, its owner, program and current decision state in one case workspace.

OverviewMy funding cases
Community Development Platform · Funding cases

My funding cases

Funding cases

New
NumberSubjectStatusSubmitted dateOwner
FC-57533Draft fc-266Draft04 Oct
FC-55757Submitted fc-119Submitted11 Oct
FC-71813Verified fc-993Verified07 Oct
FC-44258Decided fc-632Decided05 Oct
FC-53210Delivered fc-738Delivered20 Oct
6 of 6 records
Draft fc-266Funding cases · FC-57533
Draft
Submitted date04 Oct
Example screen with sample data

What you can do

Move a request through a visible decision

The funding case is the central record for a request. It has a number, subject, submission date, status, organization, owner and program. Program Officer prepares it in Draft, then submits a specific revision for verification. The status path continues through Submitted, Verified, Decided and Delivered. Each state answers a different operational question: whether the case is ready for review, whether its evidence was checked, whether a decision was made and whether the approved action has a delivery trace.

The Funding Cases screen brings a status board and a selected case workspace together. Staff can examine state history, pending review decisions, the operation run and receipt trace, and the linked community needs while looking at the same case. This is useful when an owner needs to answer why a delivered case reached that point. The answer should follow the case’s revision and evidence, not an email summary.

How the work is organized

  • Preparation. Link the organization, owner and program and add the need and attachments that explain the request.
  • Revision. Record the current revision before sending it through validation and independent review.
  • State history. Retain the transition, actor and reason whenever the case’s status changes.

What to agree during setup

Define what makes a case ready to submit. The Program Officer should know which documents and need lines must be present for each program. Agree who checks the submission and who records the case decision after the independent review. The decision reason belongs with the case and the review decision belongs with the exact source revision. If a request is returned, the owner needs a clear correction path that keeps the earlier decision visible.

Choose how case numbers are assigned across organizations and programs. Use stable numbers when reconciling imports or discussing a case with a partner. A citizen reference or service code may help the team connect an outside intake channel, but it should not replace the case number in internal review. Test that a Program Officer sees only authorized organization work and an Independent Grant Reviewer cannot approve a revision they prepared.

Check the handoff on an actual case

Open a request for a local service project. The Program Officer selects the organization and program, adds the community need and a supporting document, then submits the case. The verifier checks the current revision; the independent reviewer records a decision with a reason. If approved, the authorized decision moves the case forward. Follow the state history back to the actor and revision. Reopen the case after a correction and confirm the earlier review and delivery receipt still appear as earlier evidence.

What your team sees

  • Funding status board — Cases grouped by Draft, Submitted, Verified, Decided and Delivered.
  • My funding cases — The owner’s current requests and submission dates.
  • Cases awaiting verification — Submitted requests ready for evidence checks.

Follow the work through

What it keeps track of

Data model
Funding cases
Funding requests, cases and awards submitted for a program.
Community needs
Community need, observation and line detail captured against a funding case.
Record attachments
Uploaded and verified supporting documents and source evidence.
Review decisions
Independent reviewer decisions recorded against an exact source revision.
State history
Immutable workflow-written status transition history for each case.

Who uses it

Permissions
Program Officer
Prepares and owns the case.
Independent Grant Reviewer
Decides on assigned revisions; Auditor checks the history.

Set up Community Development Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started