Skip to content
4Fleet

Create and track an operational task

Create one assigned task with a due date, add its working detail, and move it to completion from the Tasks workspace.

How-to · 6 min · Operators · Reviewed 30 Jul 2026

Goal

Create one task that has a clear owner and due date, then track it to completion without relying on an informal note.

Prerequisites

  • Your role can create tasks.
  • The intended assignee is an active user or driver in the company.
  • You know the concrete outcome, priority, and due time.

Steps

  1. Open Tasks and select New Task.
  2. In Create New Task, write an action-based title, such as "Confirm pickup sign for BK-104".
  3. Add the details needed to complete the work. Link the relevant booking, client, or operational context when the form offers it.
  4. Select the priority, category, assignee, due date, and due time.
  5. Select Create Task.
  6. Open the task and add subtasks when the work needs a short checklist.
  7. Add comments or attachments to the same task instead of creating parallel notes.
  8. Move the task through the available statuses as work progresses, or use the board to drag it to the correct column.
  9. Confirm completion only after the outcome is real. Completing a task records task state; it does not replace the underlying booking, invoice, or customer action.
  10. For work that genuinely repeats, create a user-managed recurring task template and verify its next generated occurrence.

Expected result

The task appears in Tasks with the correct assignee, due time, and context, and its activity shows a clear path to completion.

Troubleshooting

  • The task is missing: clear filters and search, then check the current list or board status.
  • The assignee cannot see it: confirm the active user or driver link and whether the task is driver-facing.
  • A due task is not on Calendar: confirm that it has a valid due date and refresh both Tasks and Calendar.
  • A recurring template creates nothing: confirm that it is a user-created active template with a valid next run. Do not expect undocumented system templates.
  • A booking checklist does not send messages automatically: treat booking packs as checklists unless a separate, verified automation owns the external action.
  • A payment-overdue task was expected: verify the invoice reminder workflow separately. Do not rely on a task rule unless the generated task is visible.

Related articles

Was this article helpful?