Nonprofit Participant Follow-Up And Referral Tracking Checklist for Small Nonprofit Direct-Service And Program Teams

A checklist for nonprofit participant follow-up and referral tracking should prevent missing decisions, not merely prove that somebody clicked boxes. The checklist below is designed for small nonprofit direct-service and program teams and centers on one result: every consented program follow-up reaches a documented next step or closed reason without unnecessary data collection.

Before the work starts

• Confirm Program and participant ID
• Confirm Follow-up purpose
• Confirm Consent boundary
• Confirm Preferred channel
• Confirm Owner

Also name the owner and the expected completion condition. If either is unknown, the work is not ready to enter the active queue.

While the work is moving

• Update Record the follow-up commitment
• Update Confirm consent and preferred contact
• Update Assign the action
• Update Complete or coordinate the follow-up
• Update Record the outcome and next review

Every update should change a decision. Notes such as “followed up” are weak unless they also include the channel, result, next date, and owner.

Before marking it complete

• Verify Due date
• Verify Referral or action
• Verify Attempt outcome
• Verify Next date
• Verify Closed reason

Confirm that the actual outcome—not just an activity—has been recorded. If the process ended early, use a closed reason rather than deleting the record.

Copy-and-paste weekly review

• [ ] Review records where a promised follow-up date arrives

• [ ] Review records where a referral has no confirmation by its review date

• [ ] Review records where staff ownership or participant contact preference changes

• [ ] Check for recording more personal detail than the workflow needs

• [ ] Check for using message sent as the completion outcome

• [ ] Check for failing to distinguish referral made from referral connected

• [ ] Check for leaving overdue records ownerless after staff changes

Make the checklist measurable

Choose one metric before the next cycle. Good options for this workflow are On-time follow-up rate, Connection rate, Closed-reason completeness. A checklist that never changes a metric or prevents a known failure mode is probably administrative overhead.

Assign ownership and escalation

Put one role—not a group—next to every item that can remain open. Define a backup owner and an escalation time for work that affects a customer, client, participant, or delivery promise. During review, separate not started, waiting on someone, and failed validation; those states need different actions. If a checklist item repeatedly waits on the same dependency, redesign the intake or handoff instead of adding more reminder boxes.

Next step

Explore the Participant Follow-Up Queue workflow concept and record whether this is painful enough to justify a focused tool.

For the adjacent workflow, see Grant Evidence Organizer.