Tasks

A task serves two purposes: it’s a unit of work that can be assigned and tracked using standard task management features, and it’s also a form submission that collects rich data about that unit of work.

Overview

Tasks are the fundamental unit of work in ChronoFlow. Each task represents a specific piece of work that needs to be done, but tasks are more than just to-do items—they’re also rich data containers that collect structured information about the work being performed.

Task as Unit of Work

As a unit of work, a task can be managed using standard task management features:

• Assignment: Tasks can be assigned to specific users or team members
• Priority: Tasks can be prioritized to indicate urgency or importance
• Status: Tasks have statuses (new, in progress, completed, etc.) to track progress
• Due Date: Tasks can have due dates to indicate when work should be completed
• Tracking: Tasks can be tracked through workflows and processes

This makes tasks work like traditional task management items, allowing teams to organize, prioritize, and track their work.

Task as Form Submission

A task is also a form submission. According to what fields are applied in the hierarchy above it (space, folder, and list levels), those fields become the “form” for the task.

When you create or work on a task, you’re filling out a form that’s dynamically constructed from:

• Fields assigned at the space level
• Fields assigned at the folder level (if the task’s list is in a folder)
• Fields assigned at the list level

This form determines what information needs to be collected for that task. For more details on how fields are inherited, see the Fields documentation.

Task as Rich Data Container

Because tasks inherit fields from the hierarchy above them, each task becomes a rich data container that collects structured information about the unit of work it represents.

For example, a task might collect:

• Standard task management data (priority, status, due date, assignee)
• Organization-level data (like a Student ID, if that field is assigned)
• Space-level data (department-specific information)
• Folder-level data (workflow-specific information)
• List-level data (kind-specific information)

This combination of task management features and structured data collection makes tasks powerful tools for both managing work and collecting the information needed to complete that work.

Tasks in Lists

Tasks exist within lists. All tasks in a list are instances of the same kind of work, which means they share:

• The same list-level fields
• The same structure and data requirements
• The same workflows (if any)

When you view a list, you see all current tasks of that kind, each with its own data and status.

Creating and Managing Tasks

Tasks can be created:

• Manually by users
• Automatically through workflows
• As part of a process or sequence

Once created, tasks can be:

• Assigned to team members
• Updated with data through the form
• Tracked through status changes
• Moved through workflows
• Completed when the work is done

The combination of task management capabilities and rich data collection makes tasks the central mechanism for both organizing work and collecting the information needed to complete it.