Tasks

A task is a discrete unit of work inside an engagement (or, less commonly, a firm-level admin task not tied to any engagement). Most tasks auto-generate from pipeline stage templates. You can also add ad-hoc tasks manually.

Tasks have a type, a status, an assignee, a due date, and (optionally) a “waiting on” reason.

Where to find tasks

The Tasks page has two views: List and Board.

Using the list view

A sortable table with one task per row:

• Title
• Engagement (with client)
• Type (Collect, Prepare, Review, …)
• Status
• Assignee
• Due date
• Stage (which engagement stage this task belongs to)

Filterable, sortable, supports bulk actions (select rows → bulk reassign or set status).

Using the board view

Kanban-style with status columns (To do / In progress / Completed). Drag cards between columns to update status.

The 13 task types

Type is mostly metadata for filtering and reporting — it doesn’t change behavior. Pick the closest match.

The 5 statuses

Completed, Cancelled, and Not applicable all count as “done” for stage-gate evaluation — none of them block stage advancement.

The “waiting on” flag

When a task is To do or In progress, it can have a Waiting on label:

The waiting-on flag is for status reporting — the Tasks page lets you filter to “tasks I’m waiting on client for” so you can prioritize the right follow-ups. It doesn’t auto-create a blocker (use Blockers for that).

Auto-generated tasks (stage templates)

When an engagement enters a stage, Assure Pro creates tasks from the stage’s task templates.

Each template defines:

• A task title (with merge variables resolved).
• A type.
• An assignee role (preparer, reviewer, or partner) — resolved to the actual user from the engagement’s assignments.
• A default due-date offset from stage entry (or from engagement due date).
• Whether the task is required for advance (gates the stage in strict mode).

Example: the Tax pipeline’s In prep stage might have these templates:

When an engagement moves into In prep, those four tasks are created, assigned, and given due dates relative to stage entry.

Adding a manual task

Click + Add task anywhere a task list appears.

The dialog asks:

Click Add. The task appears in the task list immediately.

Completing a task

Three ways:

When you complete a task:

• Status changes to Completed.
• The completion is logged in the activity timeline.
• If the stage’s gate fires (all required tasks now complete, no blockers, auto-advance condition met), the engagement auto-advances.
• The engagement’s task-progress bar updates on the kanban card.

Bulk task actions

In the Tasks page list view, select multiple rows (checkboxes). The Task bulk bar appears at the bottom with:

• Set status — mark many tasks as Completed, Not applicable, or Cancelled.
• Reassign — change assignee on many tasks at once.
• Set due date — bulk reschedule.
• Delete — remove tasks (use sparingly — completed tasks shouldn’t be deleted).

The Tasks page (cross-engagement)

The dedicated Tasks page (sidebar) shows tasks across all engagements. Filters:

The default view is “what’s on my plate right now” — To do plus In progress tasks assigned to me.

Saved views are supported — for example, “Waiting on client” filters to status = To do, waiting on = Client.

Working in the task detail page

Click any task to open its detail page. Sections:

• Header — title, status, type, engagement, client, stage, assignee, due date.
• Description — free-form. Editable.
• Activity — timeline of changes (status, assignee, due date).
• Comments — threaded discussion (rare for tasks — most discussion lives at the engagement level).
• Subtasks — optional checklist within the task.

Keyboard shortcuts

Common patterns

”I want a task that isn’t tied to a stage”

Most stage-template tasks belong to a stage. Manual tasks don’t have to — create with stage = “(none)”. They appear in the engagement’s task list under “Unassigned to stage” and don’t gate any stage moves.

”I want a recurring task across many engagements”

Set up a stage template in the Pipeline builder — the template generates the task on every engagement that enters the stage. Pure manual tasks don’t recur.

”I want a task that’s actually a checklist”

Use the subtasks field on the task detail page. A task can have many subtasks; the parent task is complete when all subtasks are complete (or you can mark it complete manually).

”Tasks that span engagements”

Tasks belong to one engagement (or none). For work that crosses engagements (for example, “Reconcile inter-company eliminations between holding co and operating co”), create the task on the engagement it primarily lives on and add a comment linking to the related engagement.

Permissions

Next

• Custom pipelines — defining stage task templates.
• Stages & gates — how required tasks gate stage advancement.
• The engagement detail page — the Tasks section on an engagement.