Documentation > Documentation > Craftly Workspace > Tasks & Operations > Tasks

Tasks

Craftly Workspace provides a structured system for issuing, distributing, executing, and submitting official company tasks.

A task in Craftly is not simply a personal to do item. It represents actual work assigned by the organization, with a clear source, responsible person, expected outcome, and submission process.

Craftly uses two primary ways to distribute official tasks:

  • Notice Board
  • Command Chain

But What Is the Command Chain?

The Command Chain is Craftly's hierarchical communication and task distribution system.

It is the structured path through which official commands, instructions, and tasks move through the organization.

The hierarchy follows:

Chairman → CEO → C-Suite → Senior → Junior → Executive

A command can originate at a higher level and be passed down through the appropriate organizational levels until it reaches the person responsible for carrying out the work.

Each level is responsible for passing relevant work to the appropriate people under its responsibility.

The Command Chain therefore provides a clear relationship between:

Who issued the command → Who received it → Who is responsible → Who executes it

This keeps organizational communication structured and prevents official tasks from being distributed randomly or without accountability.

How Tasks Are Assigned

Craftly uses two official channels for distributing tasks.

1. Notice Board

The Notice Board is used when an official task needs to be announced to a department, unit, group, or the wider organization.

A task posted on the Notice Board contains the necessary instructions and expectations so that the responsible members can understand what needs to be done.

The Notice Board works as a centralized location for officially published organizational tasks and notices.

2. Command Chain

Tasks can also be assigned directly through the Command Chain.

In this case, the task follows the organization's hierarchy and is passed from the appropriate leadership level to the people responsible for executing it.

For example:

CEO → C-Suites → Senior → Junior → Executive

A leader does not need to send the task to everyone. They pass it through the appropriate organizational structure until it reaches the person or team responsible for the work.

This makes the Command Chain the primary mechanism for hierarchical task delegation and execution.

Executing a Task

Once a member receives an official task, they are responsible for completing it according to the instructions provided.

The member should understand:

  • What needs to be done
  • Why it needs to be done
  • What output is expected
  • When it needs to be completed
  • Who is responsible for the task

A task remains an active responsibility until the required work has been completed and submitted.

Task Submission

Once the work is completed, the member can submit the result through the Task Submission system.

A member can submit up to 5 files per task.

Supported formats include:

  • Images / Photos
  • PDF
  • Text
  • JSON
  • CSV

This allows different types of work to be submitted in the format that best represents the actual result.

For example:

Task Assigned
↓
Work Completed
↓
Output / Evidence Prepared
↓
Task Submission
↓
Submitted Work Recorded

The submission should represent the actual output of the assigned task, rather than simply indicating that the task was completed.

What If You Cannot Complete a Task?

Sometimes a member may be unable to complete an assigned task because of a technical problem, lack of information, insufficient resources, or another blocker.

In that situation, the member should not silently leave the task incomplete.

Instead, they should contact their Unit Leader and explain the situation.

They should communicate:

  • Why the task could not be completed
  • What problem occurred
  • What is currently blocking the work
  • What kind of help or resources are needed

The Unit Leader can then determine the appropriate next step.

The process becomes:

Task Assigned
↓
Work Begins
↓
Problem Occurs
↓
Member Contacts Unit Leader
↓
Problem Identified
↓
Support / Resolution
↓
Work Continues

This makes problems visible to the organization instead of allowing incomplete work to disappear without explanation.

The Complete Task Flow

The complete Craftly task system can be understood as:

Task Issued
↓
Notice Board or Command Chain
↓
Task Assigned to Responsible Member
↓
Task Execution
↓
Completed?
If Yes
Prepare Output
↓
Task Submission
↓
Upload up to 5 Files
↓
Task Completed / Recorded
If No
Identify Blocker
↓
Contact Unit Leader
↓
Resolve the Problem
↓
Continue the Task

Why Craftly Uses This System

The purpose of the Task and Command Chain system is to make organizational work clear, traceable, and accountable.

Every official task should have:

  • A clear source
  • A defined path
  • A responsible person
  • A specific expected outcome
  • A way to submit the result
  • A clear escalation path when something goes wrong

This creates a simple principle:

Commands should have a clear path. Work should have a clear owner. Completed work should have a verifiable submission. Problems should have a clear path to resolution.

That is how Craftly Workspace turns organizational instructions into structured, accountable execution.

Access ControlTask Assignment