1. Community Development Platform
  2. Features
  3. Independent review
Feature · Independent review

Independent review

Put a named reviewer decision and reason against the exact case revision.

OverviewPending review decisions
Community Development Platform · Independent review

Pending review decisions

Approval conditions

New
ParentSource revisionDecisionReviewerEvidence reference
FC-74384190PendingER-693
FC-38883850PendingER-957
FC-10155580PendingER-169
FC-82908790PendingER-256
FC-79546330PendingER-955
6 of 6 records
ER-693Review decisions · RD-77771
Pending
ParentFC-74384
Source revision190
Example screen with sample data

What you can do

Make the review independent and specific

A review decision points to a funding case and its source revision. The Independent Grant Reviewer records the decision, date, reason and evidence reference. Pending, Approved, Returned and Rejected are distinct outcomes. A return asks for correction while rejection records a negative decision for that revision. Keeping the revision with the decision protects the team from treating an approval of an earlier case version as approval of a changed request.

The reviewer sees the case’s community needs, attached evidence and state history alongside the pending decision. They can compare the submitted request with the selected program and the evidence available at validation. The reviewer should be a different person from the Program Officer who prepared the revision. That separation matters most when the request is urgent and the same team is under pressure to move it quickly.

How the work is organized

  • Assignment. A pending decision names the case, reviewer and source revision to be assessed.
  • Evidence. The reviewer checks the need lines and attachments used to justify the requested outcome.
  • Decision. Approval, return or rejection carries a date and reason that remain attached to the reviewed revision.

What to agree during setup

Agree who may serve as an Independent Grant Reviewer for each organization and program. Define the evidence needed for review, including how a verified attachment is identified. The Program Officer can prepare attachments and needs; the reviewer records the decision. Test the direct record permissions as well as the Funding Cases screen, because hiding a button alone does not protect the decision table.

Set a clear rule for a returned request. The Program Officer should revise the case and submit a successor revision; the earlier returned decision stays in history. Decide whether a rejected request can be reconsidered under a new revision or must begin as a separate case, and apply that policy consistently. The case’s current status and the decision outcome should be read together rather than treated as interchangeable fields.

Check the handoff on an actual case

Take a case that asks to fund a public gathering space. Have the Program Officer submit a revision with two community needs and a verified document. Assign an Independent Grant Reviewer who did not prepare it. The reviewer opens the pending decision, checks the program policy reference and the evidence, then returns the case with a concrete reason. After the officer corrects one need, inspect both revisions. The returned decision should still refer to the first revision; a new review must address the changed version. Repeat with an approval and check that the decision has the right reviewer and date.

What your team sees

  • Pending review decisions — Assigned case revisions awaiting an independent decision.
  • Review decision history — Approved, returned and rejected decisions with reason and date.
  • Unverified attachments — Documents that need checking before the reviewer relies on them.

Follow the work through

Read review and decision for the approval handoff and correction and follow-up for returned work.

What it keeps track of

Data model
Review decisions
Independent reviewer decisions recorded against an exact source revision.
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.
State history
Immutable workflow-written status transition history for each case.
Team members
Staff, program officers, reviewers and assigned team members.

Who uses it

Permissions
Independent Grant Reviewer
Records decisions.
Program Officer
Prepares and corrects cases; Auditor reads the evidence trail.

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