Tasks

Tasks are the cross-functional accountability layer in Tempr.

Open The Task List

Open /tasks to view your queue.

Users with broader permissions may be able to switch between:

• mine
• all

They may also filter by task status or assignee.

Task States

Task status is managed separately from project or lead state. Common task views include:

• pending
• open
• cleared
• completed
• active

What Tasks Are For

Use tasks when there is a specific person who needs to do a specific thing next.

Good examples:

• collect missing project information
• follow up on an overdue customer decision
• resolve an operational blocker before scheduling
• verify accounting or sync cleanup

What Tasks Are Not For

Tasks are not a replacement for:

• customer records
• project comments
• lead qualification state
• work-order completion

Those records should still reflect the business truth. Tasks simply track the next accountable action.

Manual Completion

Some tasks can be completed manually, while others depend on automation rules that only allow completion under specific conditions. If you cannot clear a task directly, check whether it is automation-backed and whether another record state must change first.

Best Practices

• keep task notes short but actionable
• use comments when the receiving user needs context
• complete the task only after the underlying business action is truly done
• prefer assigning one clear owner instead of leaving follow-up work implied