Nonprofit Participant Follow-Up And Referral Tracking Template: Fields, Statuses, and Rules

The most useful nonprofit participant follow-up and referral tracking template is a small operating record. It should answer what is happening, who owns it, what evidence exists, and when the next decision occurs. This structure works in a spreadsheet, database, or focused application.

Recommended record fields

| Field | Why it exists | Update point | |---|---|---| | Program and participant ID | Prevents the record from depending on memory or an inbox search | Record the follow-up commitment | | Follow-up purpose | Prevents the record from depending on memory or an inbox search | Confirm consent and preferred contact | | Consent boundary | Prevents the record from depending on memory or an inbox search | Assign the action | | Preferred channel | Prevents the record from depending on memory or an inbox search | Complete or coordinate the follow-up | | Owner | Prevents the record from depending on memory or an inbox search | Record the outcome and next review | | Due date | Prevents the record from depending on memory or an inbox search | Record the follow-up commitment | | Referral or action | Prevents the record from depending on memory or an inbox search | Confirm consent and preferred contact | | Attempt outcome | Prevents the record from depending on memory or an inbox search | Assign the action | | Next date | Prevents the record from depending on memory or an inbox search | Complete or coordinate the follow-up | | Closed reason | Prevents the record from depending on memory or an inbox search | Record the outcome and next review |

Suggested statuses

Use workflow statuses that describe reality: Record The Follow Up Commitment → Confirm Consent And Preferred Contact → Assign The Action → Complete Or Coordinate The Follow Up → Record The Outcome And Next Review. Add Waiting only when you also capture a waiting reason and review date. Add Closed—Not Completed when an item legitimately ends without the desired outcome.

Follow-up rules

• When a promised follow-up date arrives, assign a next action and review date.
• When a referral has no confirmation by its review date, assign a next action and review date.
• When staff ownership or participant contact preference changes, assign a next action and review date.

Avoid reminders with no stop condition. A rule should say when it starts, who receives it, what counts as a response, and when a person should take over.

Example records

• A participant requests a resource list by text after a workshop
• A referral is sent but the partner cannot reach the participant
• A staff member leaves with open check-ins assigned

For each example, write the current status, next action, owner, and supporting evidence. This makes the template testable with real work rather than idealized sample data.

Quality-control rules

• Collect only information needed for the action
• Consent and contact preferences control outreach
• Referral sent and referral connected are separate outcomes
• Supervisors can reassign open commitments without exposing unnecessary detail

Before adding automation, run the template manually for a week. Remove ambiguous fields and confirm that two different users classify the same situation the same way. Consistency matters more than having a long form.

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.