CRM Follow-Up Review Template

Weekly pipeline review.

Nonprofit development follow-up where a connected CRM remains the donor system of record.

Daily stale lead or deal checks.

Missing owner, stage, note, or follow-up reviews.

CRM actions that should be previewed before they run.

HubSpot contacts, companies, deals, tickets, owners, and metadata where authorized.

Slack, Asana, Trello, Calendar, or Knowledge context that explains recent work.

Saved CRM dashboard questions.

Approval rules for supported CRM changes.

Records that need attention.

Plain-language explanation of why each item was flagged.

Draft notes, tasks, or updates where supported.

A review queue before approved changes execute.

Choose the CRM objects and owners in scope.

Define what counts as stale, missing, or ready for review.

Connect supporting work context if CRM records depend on project or team activity.

Run the review in read-only mode first.

Add approved CRM actions after the team trusts the recommendations.

Require review before notes, stages, owners, associations, or tasks change.

Keep donor and participant judgment with nonprofit staff; a stale-record rule is not a relationship decision.

Show the reason for each proposed update.

Start with internal notes and tasks before external communication.

Keep CRM access tied to authorized teams and workflows.