1. Community Development Platform
  2. Features
  3. Follow-up and corrections
Feature · Follow-up and corrections

Follow-up and corrections

Assign unresolved work while retaining earlier decisions and delivery evidence.

OverviewMy follow-up actions
Community Development Platform · Follow-up and corrections

My follow-up actions

Follow up actions

New
SourceTitleDue dateStatusResolution
FC-25275Open fua-32618 OctOpenRSL-727
FC-58394In progress fua-59105 OctIn progressRSL-158
FC-95705Completed fua-38112 OctCompletedRSL-405
FC-50317Cancelled fua-88606 OctOpenRSL-189
FC-11084Open fua-61711 OctIn progressRSL-527
6 of 6 records
Open fua-326Follow up actions · FUA-87112
Open
SourceFC-25275
Due date18 Oct
ResolutionRSL-727
Example screen with sample data

What you can do

Give unresolved work an owner

Follow-up actions attach to a funding case and an assigned team member. Each action has a title, due date, status, completion date and resolution. Open and in progress make outstanding work visible; Completed records what closed it, while Cancelled distinguishes work the team chose not to perform. The action can cover a missing document, a returned review, a delivery exception or a correction to an executed revision. An owner and due date keep it from disappearing into case notes.

Corrections need more care after a case has been delivered. The case has a revision and status history, and the review decision records the exact revision approved. Operation runs and receipts retain the result of the earlier executed action. When a later revision supersedes a delivered one, the team needs a successor review and an explicit compensating follow-up action. That preserves what happened first while making the next obligation visible.

How the work is organized

  • Assignment. Give each action a team member and due date, linked to the affected case.
  • Resolution. Record the completed work and resolution rather than silently removing the action.
  • Correction. Keep earlier state transitions, decisions and receipts attached to their original revision.

What to agree during setup

Define which issues require a follow-up action and who may close one. A Program Officer can manage follow-up records; the assigned team member should provide the resolution. Agree when a correction changes the case’s source revision and when a separate case is more appropriate. If an outside delivery was executed, name the person who checks whether a compensating action is needed and what evidence will close it.

Use the state history to explain status movement. Its actor, time, revision, operation key and reason help an Auditor reconstruct the sequence. Keep a returned review decision with its original revision when the owner resubmits. A successor decision must be independent, even if the correction seems small. Test that a later edit cannot make an old approval appear current.

Check the handoff on an actual case

Imagine a facility grant was delivered, then the team finds that the approved quantity was wrong. The Program Officer records a correction and assigns a follow-up action for the external adjustment. The earlier receipt remains attached to the executed revision. A reviewer assesses the successor revision and records a new decision with a reason. The team closes the follow-up only after the correction is reconciled and the resolution is documented. The Auditor should be able to read the original decision, original delivery and later correction in order.

What your team sees

  • Open follow-up actions — Assigned outstanding work with due dates and case links.
  • My follow-up actions — Work assigned to the current team member.
  • Review decision history — Earlier decisions by revision for comparison during correction.

Follow the work through

Use correction and follow-up for the repair path and review and decision for renewed approval.

What it keeps track of

Data model
Follow up actions
Assigned outstanding actions, corrections and outstanding requests for a case.
Funding cases
Funding requests, cases and awards submitted for a program.
State history
Immutable workflow-written status transition history for each case.
Review decisions
Independent reviewer decisions recorded against an exact source revision.
Operation runs
Workflow-maintained execution runs with operation key, input hash and persisted result reference.
Operation receipts
Ordered steps inside an operation run with input, output and external receipt state.
Team members
Staff, program officers, reviewers and assigned team members.

Who uses it

Permissions
Program Officer
Manages correction work.
Independent Grant Reviewer
Decides on the successor revision; Auditor checks the retained 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