Tasks
Tasks are freeform to-dos for your team. Use them to track follow-ups, internal actions, and lightweight work that does not warrant a full Job. Tasks are a CRM / project-management surface — they do not move money or affect job costing.
Key fields
Section titled “Key fields”| Field | Purpose |
|---|---|
| Title, Details | Short description and any additional context. |
| Status | open, in_progress, blocked, done, cancelled. |
| Priority | low, medium, high, urgent. Used for sorting and filtering. |
| Due Date | When the task is expected to be complete. |
| Assignee | The team member responsible. |
| Client, Client Contact | Optional. Link the task to a customer record for context. |
| Pipeline Deal | Optional. Attach the task to a forecast deal — useful for “send proposal”, “follow up”, etc. |
| Last Activity, Completed At | Timestamps used for sorting and reporting. |
Status transitions
Section titled “Status transitions”Status is user-driven — there is no approval workflow. Typical progression:
open→in_progresswhen someone starts the task.in_progress→blockedif it is waiting on someone or something.blocked→in_progresswhen unblocked.- Any state →
donewhen complete, orcancelledif no longer needed.
Completing a task also stamps the Completed At timestamp so you can report on throughput and cycle time.
Where tasks come from
Section titled “Where tasks come from”You can create a task directly from the Tasks list, or from inside a related record — a Client drawer, a Contact drawer, or a Pipeline deal — which seeds the link automatically.
No accounting impact
Section titled “No accounting impact”Tasks do not affect your accounts and do not roll into job profitability. If you need to log time against a piece of work, create a Timesheet entry on the relevant job instead.