Tasks

Find it: Left nav → Tasks · Who can use it: Org Admins and Development Associates create and manage tasks. Committee chairs and members see the tasks in their scope and can complete, reopen or cancel tasks assigned to them. Board Viewers see tasks read-only.

The three views

Tasks opens on Open. Switch views with the tabs at the top; each tab shows its exact count.

• Open — the work still to do, and the default. Overdue tasks come first (flagged in red), then tasks due today, then upcoming tasks by due date, then tasks with no due date.
• Recently completed — tasks finished in the last 30 days, newest first. A short window for reviewing what got done.
• History — tasks completed more than 30 days ago, older completed tasks, and cancelled or snoozed tasks, newest first. Tasks completed before this view existed show Completion date unavailable: their completion time was never recorded, so none is invented.

Each row shows the task's title and type, the donor it's tied to (a link to their profile), who it's assigned to, and its due date — or, in Recently completed and History, its completion date. Cancelled tasks are marked Cancelled and snoozed tasks Snoozed.

Filtering and pages

• Narrow any view by due date (overdue, due today, upcoming, no due date), task type, or Assigned to me, or search task titles. Filters stay applied as you switch views and pages; Clear filters resets them.
• A donor profile's View tasks link opens Tasks filtered to that donor.
• Each page shows 50 tasks. Use Previous and Next to move through the rest; the count above the buttons tells you where you are.

How to create a task

1. Click New task in the page header.
2. Enter a Title (for example, "Call to thank for last gift").
3. Pick a Type: Call, Meeting, Thank-you, Cultivation, Solicitation, Follow-up, or Other.
4. Optionally set a Due date.
5. Click Create task. If you created it from a donor's profile, it's automatically linked to that donor and assigned to you.

Complete, reopen or cancel

• Complete moves an open task to Recently completed and records when it was finished. Completing it again doesn't change that date.
• Reopen puts a completed, cancelled or snoozed task back in Open and clears its completion date. A snoozed task can only be reopened from here, not completed or cancelled directly.
• Cancel is for work that no longer needs doing. The task isn't deleted: it moves to History, where you can find it and reopen it. Nothing is permanently lost.
• Assign to me appears on open tasks that have no assignee, for Org Admins and Development Associates. It makes you the assignee. A task that already has an assignee isn't changed. Every task in the first 30-day work plan needs an assignee (see Getting started).

How tasks connect to your pipeline

• Tasks are the day-to-day counterpart to a donor's Next Action date — the pipeline-discipline field that keeps a donor from going cold. Setting a next action on a donor and creating a task to do it work hand in hand.
• The Action Plan can turn a group's recommended next steps into tasks here — up to 25 at a time, for exactly the donors it lists, never twice for the same work. Today can do the same for a recommendation you accept.

How the AI agent layer works your tasks

An AI agent can help clear this queue, but how much it's allowed to do depends on the task — never on how busy you are. Every task type carries an execution class that sets a ceiling on agent involvement:

• Human-only — the donor-facing, judgment-heavy work: calls, meetings, cultivation, and any ask. An agent may add prep notes, but it can never complete one of these for you.
• Agent-preparable — the agent drafts the work (an email, a follow-up) and leaves it for you to review, edit, and approve. Nothing reaches a donor until you say so.
• Agent-executable — routine, low-risk chores the agent can finish end-to-end: thank-yous to your lowest-tier donors, gift-receipt delivery, creating reminder and follow-up tasks, record hygiene (duplicate flags, missing-field nudges), reassigning stale tasks, and keeping next-action dates current. None of these solicit anyone.

What actually happens is governed by a per-organization autonomy dial with four settings — off, suggest, prepare, and auto — set separately for each task type by an admin in Settings. The default is Prepare: agents draft, you approve. Nothing sends on its own until an admin deliberately switches a task type to Auto, and only the agent-executable types can be switched at all.

Two guarantees hold no matter how the dial is set:

• Asks are never auto-completed. A solicitation is always human work.
• Agents never bypass the OK-to-ask engine. The same timing and stewardship rules that block you from a premature ask block the agent too — there is no back door.

See Ai agents for the full picture of what the agents do and how to supervise them.

Good to know

• Tasks keep every Tier A–D donor moving with a clear next step — an empty Open view means nothing is queued, not that everything's done.
• A task without a due date can't be overdue; it appears at the end of Open.
• "Today" and "overdue" follow the calendar date in UTC.