Fabritec Docs
English
  • English
  • Arabic
Learning Center
Support CenterChangelog
Learning Center
Support CenterChangelog
English
  • English
  • Arabic
English
  • English
  • Arabic
  1. Menu
  • Introductions
  • Installing Fabritec as a Desktop or Mobile App
  • Notification Settings and Push Notifications
  • Connecting Fabritec with AI Assistants: Claude AI and ChatGPT
  • Fabritec Production Setup & User Management
    • Production Setup
      • Production Stages
      • WorkStations
      • Categories
      • Routes
      • Labour Titles
      • Shifts
      • Labours
      • Labour Group
    • User Management
      • Roles
      • Departments
      • Users
      • Logs
    • Settings
      • Company Profile
      • Preferences
      • License Info
      • Settings
  • General
    • Home
    • Customers
    • Dashboards
    • Reports
    • User Profile & Change Language
    • Projects
      • Create New Project
      • Overview
      • Details
      • Buildings
      • Documents
      • Messages
      • Phases
      • Phases Explorer
      • Revisions: Bulk Paint Update & Selective Item Deletion
      • Phases Explorer: Manual Item Entry, Drawing Validation, and Smart Allocation
      • Routing Setup
      • Tracking
      • Quality Control
      • Shipping Status
      • Shipping
      • Erection
  • Menu
    • Folder Structure
    • Task Manager
    • Task Templates & Schedule View
    • Production Page
    • Revert & Refabricate Items in Production
    • Quality Control
    • Shipping Yard
    • Shipping Calendar
  • Fabritec Workflow
    • Fabritec Project Lifecycle workflow
    • Fabritec Dashboards and Reports workflow
    • Production Setup & User Management Workflow
  1. Menu

Task Manager

The Task Manager is a centralized operational module inside Fabritec that enables teams to create, assign, track, and control tasks with full structural governance and traceability.
Unlike generic task tools, Task Manager is built to align with Fabritec’s department hierarchy, project structure, and production workflow, ensuring that tasks are not isolated activities but structured operational actions connected to real manufacturing data.
image.png
Using Task Manager, you can:
Create structured tasks with defined workflow stages
Assign tasks according to department hierarchy rules
Override assignment rules when business needs require it
Track work visually using Kanban or operationally using List
Configure task workflow statuses
Manage classification tags
Link tasks to Projects, Buildings, Phases, and Phase Items
Track comments, time logs, and audit history
Define task start dates, due dates, and estimated hours - Create parent tasks and sub tasks - Set dependencies between related tasks - Control dependency logic using relationship types, lead, and lag
Task Manager ensures clarity, accountability, and cross-department coordination across engineering, production, QC, and planning teams.

πŸ“ Where to Find Task Manager
Navigate to:
Task Manager β†’ Tasks
Task Manager contains four main pages:
Tasks – Execution workspace for creating, assigning, and tracking tasks
Schedule – Time-based task schedule view
Members – Assignment governance
Settings – Workflow and tags configuration
Archive – Manage archived tasks
Notification Settings – Manage task notification preferences
Task Templates – Create reusable task structures

Tasks Page#

The Tasks page is the primary workspace for creating and managing tasks assigned to you or your team.
At the top of the page:
Add Task
Search Tasks
All Tasks / My Tasks toggle
View selector:
Kanban
Calendar (Time-based task planning view)
List
You can transfer task cards between them using drag and drop.

βž• Creating a Task#

Click Add Task to open the task creation panel.
image.png
The updated Add Task form allows users to create tasks with planning details, ownership, classification, collaboration visibility, and dependency rules from the same panel.
Tasks can still be created with minimal information and enriched later. However, users can now add more planning information during creation, including:
Start Date
Due Date
Estimated Hours
Priority
Assignees
Tags
Watchers
Parent Task
Dependencies
Description

Basic Fields#

Basic Fields#

The Add Task form includes the main fields required to define the task, assign responsibility, and plan execution.

Title#

The task name.
Use a clear and direct title that explains the required action.
Examples:
Prepare cutting list
Review shop drawings
Inspect welding stage
Confirm shipping readiness
Update phase production plan

Status#

Defines the current lifecycle stage of the task.
Default workflow:
To Do
In Progress
Done
The selected status controls where the task appears in the Kanban board and how it is grouped in task views.
Workflow statuses can be configured from:
Task Manager β†’ Settings

Start Date#

The Start Date defines when the task is planned to begin.
This field is optional, but it is useful when the task needs to be planned before the due date.
Use Start Date when you need to:
Plan when engineering, production, QC, or shipping work should begin
Coordinate work across multiple teams
Track tasks that require preparation time
Build a realistic task sequence with dependencies
Avoid starting dependent tasks too early
Example:
A task called Prepare fabrication drawings may start before its final due date to give the engineering team enough time to complete the work.

Due Date#

The Due Date defines the expected deadline for completing the task.
The due date is optional and uses a calendar picker.
Due Date supports grouping into:
Overdue
Due Today
This Week
Later
No Due Date
Use Due Date when the task is connected to a project milestone, production deadline, QC inspection, shipping date, or internal follow-up.

Estimated Hours#

The Estimated Hours field allows users to define the expected effort required to complete the task.
This field helps teams compare planned effort against actual work logs.
Use Estimated Hours to:
Estimate how much time the task should take
Support workload planning
Help managers understand team capacity
Compare estimated work with logged work
Improve planning accuracy over time
Example:
If a task is expected to take 4 hours, enter 4 in the Estimated Hours field.

Priority#

Indicates urgency level:
Very Low
Low
Normal
High
Critical
Priority affects:
Card visibility
Grouping
Filtering
Operational planning
Recommended usage:
Critical – Blocking work or affecting delivery
High – Important task with near deadline or operational impact
Normal – Standard task
Low / Very Low – Non-urgent follow-up or improvement task

Assignees#

Users responsible for executing the task.
Assignment rules are governed by:
Department hierarchy by default
Or custom override through the Members page
Supports multi-select.

Assign To Me#

The Assign To Me option allows the current user to quickly assign the task to themselves.
This is useful when:
The user is creating a task for their own work
A supervisor wants to quickly record a task they will handle
A user wants to take ownership without searching the assignee list
More Options:
image.png

More Options#

Click More Options to display additional task fields.
More Options includes:
Tags
Watchers
Parent Task
Dependencies
Description
These fields are useful when the task requires more structure, collaboration, or planning control.

Tags#

Flexible labels used for classification and filtering.
Tags are:
Multi-select
Optional
Managed centrally in Settings
Used in grouping and swimlane views
Examples:
Engineering
Urgent
QC
Shipping
Rework
Client Request
Internal Follow-up
Use tags for classification, not lifecycle status.

Watchers#

Users who receive visibility and updates but are not responsible for execution.
Watchers are useful when someone needs to stay informed without being assigned to complete the task.
Examples:
A project manager watches an engineering task
A QC manager watches a rework task
A shipping coordinator watches a production readiness task
A department head watches a critical delay task

Parent Task#

The Parent Task field allows the task to be linked under a higher-level task.
This helps structure large work into smaller actionable tasks.
Example:
Parent Task:
Phase 01 Engineering Preparation
Sub tasks:
Prepare shop drawings
Review BOM
Confirm paint system
Submit drawings for approval
Use Parent Task when a task is part of a larger work package.

Task Dependencies#

Task Manager now supports Task Dependencies, allowing users to define relationships between tasks.
A dependency means one task is connected to another task in a planned sequence.
This is especially useful for project-based manufacturing workflows where one activity depends on another before it can start, finish, or progress correctly.
Examples:
Detailing must finish before production planning starts
Material preparation must start before cutting starts
QC review must finish before shipping confirmation finishes
Fabrication work cannot start until drawings are approved
Dependencies help teams move from simple task tracking to structured operational planning.

Where Dependencies Appear#

Dependencies can be managed in two places:
1.
Add Task form
When creating a new task
Useful for defining the task sequence from the beginning
2.
Task Details panel
After the task has already been created
Useful for updating task relationships as project conditions change
This allows users to adjust planning logic without recreating tasks.

Dependency Fields#

The Dependencies section includes:
Predecessor Task
Dependency Type
Lead / Lag Value
Add Dependency button
Existing dependency list

Predecessor Task#

The Predecessor Task is the task that the current task depends on.
Select the task that must happen before, start with, finish with, or control the timing of the current task.
Example:
If the current task is:
Start production planning
The predecessor task may be:
Finish drawing review
This means production planning depends on drawing review.

Dependency Type#

The dependency type defines the relationship between the predecessor task and the current task.
Available dependency types:
Finish to Start
Start to Start
Finish to Finish
Start to Finish
Each type controls how the timing of one task relates to another.

Dependency Relationship Types#

1. Finish to Start#

Finish to Start means the current task should start after the predecessor task finishes.
This is the most common dependency type.
Use it when one task cannot begin until another task is completed.
Example:
Drawing Approval must finish before Production Release starts.
Cutting List Preparation must finish before Cutting Operation starts.
QC Inspection must finish before Shipping Preparation starts.
Practical meaning:
Task B starts only after Task A finishes.

2. Start to Start#

Start to Start means the current task should start when the predecessor task starts.
Use it when two tasks need to begin at the same time or in close coordination.
Example:
Material Preparation starts when Production Planning starts.
Shop Drawing Review starts when BOM Review starts.
Site Coordination starts when Shipping Planning starts.
Practical meaning:
Task B starts when Task A starts.

3. Finish to Finish#

Finish to Finish means the current task should finish when the predecessor task finishes.
Use it when two activities must be completed together or aligned at the end.
Example:
Packing List Preparation should finish when Shipping Readiness Review finishes.
QC Documentation should finish when Final Inspection finishes.
Client Progress Update should finish when Internal Weekly Review finishes.
Practical meaning:
Task B finishes when Task A finishes.

4. Start to Finish#

Start to Finish means the current task should finish when the predecessor task starts.
This is less common, but useful in handover situations.
Example:
Temporary manual follow-up finishes when system-based tracking starts.
Old coordination process finishes when new task workflow starts.
Backup monitoring task finishes when main responsible task starts.
Practical meaning:
Task B finishes when Task A starts.

Lead and Lag Control#

The dependency section includes a numeric field used to control timing between dependent tasks.
This value supports:
Positive values
Negative values
Zero

Positive Value: Lag#

A positive value creates a delay after the dependency point.
Use a positive value when the current task should wait before starting or finishing.
Example:
Dependency type:
Finish to Start
Lag value:
2
Meaning:
The current task starts 2 days after the predecessor task finishes.
Use lag when:
A review buffer is required
Material needs time to arrive
Drawings need internal approval after completion
QC results need time before the next step
A task should not start immediately after the previous task

Negative Value: Lead#

A negative value creates overlap with the predecessor task.
Use a negative value when the current task can start or finish before the predecessor is fully complete.
Example:
Dependency type:
Finish to Start
Lead value:
-1
Meaning:
The current task can start 1 day before the predecessor task finishes.
Use lead when:
Work can overlap safely
Planning can begin before approval is fully complete
Shipping preparation can begin before production is fully finished
Teams need to compress the schedule without losing control

Zero Value: No Delay or Overlap#

A value of 0 means there is no delay or overlap.
The dependency applies directly based on the selected dependency type.
Example:
Dependency type:
Finish to Start
Value:
0
Meaning:
The current task starts immediately after the predecessor task finishes.

Adding Multiple Dependencies#

The + button allows users to add dependency rows.
This means one task can depend on more than one predecessor task.
Example:
Task:
Release Phase 01 for production
May depend on:
Drawing review completed
BOM confirmed
Material availability checked
QC requirements reviewed
Each dependency can have its own:
Predecessor task
Relationship type
Lead or lag value
This gives teams more accurate control over complex task sequences.

Dependency Notes#

The system displays guidance under the dependency fields:
Use a positive value for lag, which delays the task after the dependency point.
Use a negative value for lead, which lets the task overlap the predecessor.
Use 0 for no delay or overlap.
If no dependency is added, the task remains independent.

Practical Example: Production Planning Dependency#

Scenario:
The production team cannot start planning until engineering finishes the detailing package.
Current Task:
Production planning for Phase 01
Predecessor Task:
Detailing of Phase 01
Dependency Type:
Finish to Start
Lag:
0
Meaning:
Production planning starts after detailing is completed.
If the team needs one extra day for review, set Lag to:
1
If planning can begin one day before detailing is fully finished, set Lead to:
-1

Practical Example: Parallel Work#

Scenario:
Material preparation can start at the same time as production planning.
Current Task:
Prepare material availability list
Predecessor Task:
Production planning for Phase 01
Dependency Type:
Start to Start
Value:
0
Meaning:
Both tasks start together.

Practical Example: Finish Alignment#

Scenario:
QC documentation should be completed at the same time as final inspection.
Current Task:
Complete QC documentation
Predecessor Task:
Final inspection
Dependency Type:
Finish to Finish
Value:
0
Meaning:
QC documentation and final inspection finish together.

Description#

The Description field allows users to add detailed instructions or notes.
The description editor supports rich text formatting, including:
Bold
Italic
Underline
Paragraph formatting
Lists
Links
Undo / redo
Use Description to capture:
Task scope
Instructions
Acceptance criteria
Notes for assignees
Required documents
Production or QC context
Example:
β€œReview all Phase 01 shop drawings and confirm that the latest approved revision is ready before releasing the task to production planning.”

Task Details & Fields#

Opening a task displays a structured task panel.click on the card to open its details.
The updated Task Details panel gives clearer visibility into the full task structure, including planning fields, ownership, collaboration, work tracking, and dependency controls.
The Task Details panel includes:
Description
Attachments
Task Link
Comments
Work Logs
Audit Logs
Status
Priority
Start Date
Due Date
Estimated Hours
Assignees
Watchers
Tags
Parent Task
Reporter
Sub Tasks
Total Log Time
Dependencies
image.png

Status#

Defines the lifecycle stage of the task.
Default workflow:
To Do
In Progress
Done
Status controls:
Kanban columns
Status dropdown
Grouping and swimlane options
Workflow is configurable from Settings.

Priority#

Indicates urgency level:
Very Low
Low
Normal
High
Critical
Priority affects:
Card visibility
Grouping
Filtering
Operational planning

Start Date#

The Start Date shows when the task is planned to begin.
Inside the Task Details panel, users can update the Start Date if the task schedule changes.
This is useful when:
Work is postponed
A task needs to start earlier
A dependency affects the task timeline
Planning dates need to be adjusted during execution

Due Date#

Optional deadline using a calendar picker.
Supports grouping into:
Overdue
Due Today
This Week
Later
No Due Date

Estimated Hours#

Estimated Hours defines the planned effort for completing the task.
This helps compare planned work against actual logged time.
Use Estimated Hours together with Work Logs to understand:
Planned effort
Actual effort
Task overruns
Resource planning accuracy
Team workload

Assignees#

Users responsible for executing the task.
Assignment rules are governed by:
Department hierarchy (Default)
Or custom override (Not Default users)
Supports multi-select.

Watchers#

Users who receive visibility and updates but are not responsible for execution.

Tags#

Flexible labels used for classification and filtering.
Tags are:
Multi-select
Optional
Managed centrally in Settings
Used in grouping and swimlane views

Parent Task & Sub Tasks#

Tasks can be structured hierarchically.
Assign a Parent Task
Create Sub Tasks
Useful for breaking large operations into smaller actionable items.

Reporter#

The Reporter field shows the user who created or reported the task.
This helps identify who initiated the task and who may need to be contacted for clarification.

Task Link (Entity Linking)#

Tasks can be linked to Fabritec entities:
Project
Building
Phase
Phase Item
This ensures tasks remain connected to production data and are fully traceable.

Attachments#

Upload files directly to tasks:
Drawings
Inspection reports
Photos
Supporting documents

Comments#

The Comments tab allows team coordination and discussion.

Work Logs#

The Work Logs tab allows time tracking for tasks.
Supports accountability and future reporting.

Total Log Time#

The Total Log Time field displays the total amount of time recorded against the task through Work Logs.
This helps compare:
Estimated Hours
Actual logged time
Execution effort
Team productivity

Audit Logs#

Audit Logs track key task events such as:
Task creation
Status updates
Assignment changes
Field modifications
Priority changes
Start date changes
Due date changes
Estimated hours changes
Dependency changes
Task link changes
Ensures traceability and controlled operations.

Dependencies in Task Details#

Dependencies can also be viewed and updated from inside the Task Details panel.
This allows users to adjust task relationships after the task is created.
Inside Task Details, users can:
Select a predecessor task
Choose the dependency type
Set lead or lag value
Add the dependency using the + button
Review existing dependencies
This is useful when project conditions change and task sequencing needs to be updated without recreating the task.

Task Views#

Kanban View#

Visual board organized by workflow stages.
Displays:
Title
Tags
Due date
Priority
Linked entities
Assignees
Supports grouping and swimlane configuration.

List View#

Tabular representation of tasks.
Columns include:
Title
Status
Priority
Tags
Links
Assignees
Supports:
Search
Filtering
Column control
Bulk actions (Edit, Archive, Delete)

bf3dd902-03fd-4c12-9686-3ef2bfa923d7.png#

Calendar View#

The Calendar View provides a time-based visualization of tasks, allowing teams to plan, track, and manage work based on due dates.
It is ideal for:
Deadline tracking
Weekly and monthly planning
Identifying workload distribution
Monitoring upcoming and overdue tasks
cd49bb38-4ea0-4b20-b25d-9ba86b717551.png

πŸ”Ή How It Works#

Tasks are displayed on the calendar based on their Due Date.
Each task appears on its scheduled date
Multiple tasks can exist on the same day
Tasks without a due date are not shown in the calendar

πŸ”Ή Calendar Navigation#

You can easily navigate through time using:
Month selector (e.g., April 2026)
Previous / Next arrows
Today shortcut to jump to the current date

πŸ”Ή View Modes#

Calendar supports multiple time views:
Day View – Focus on a single day
Week View – Plan short-term activities
Month View – High-level planning and overview

πŸ”Ή Task Interaction#

From the Calendar View, you can:
Click on a task to open full details
View task status and priority at a glance
Identify overloaded days or gaps in planning

You can also create tasks directly from the Tasks page while using Calendar View.#

πŸ”Ή Waiting List Panel#

The Waiting List panel on the right displays tasks that are not currently scheduled or need attention.
Helps track pending or unplanned tasks
Provides quick access without leaving the calendar view

πŸ’‘ When to Use Calendar View#

Use Calendar View when you need to:
Plan production or operational tasks over time
Ensure deadlines are met
Balance workload across teams
Conduct weekly planning meetings

Grouping & Swimlane Engine#

Task Manager supports flexible board configuration.
You can define:
Group By (Columns)
Swimlane By (Rows)
Available grouping options include:
Status
Priority
Due Date
Examples:
Group by Priority
Swimlane by Status
Group by Due Date
Swimlane by Priority
This enables dynamic operational dashboards without modifying task data.

Members Page#

Navigate to:
Task Manager β†’ Members
This page controls who can assign tasks to whom.

6264819a-ed9b-496c-81a0-031f1b78d203.png#

Default Mode#

When a user is marked as Default:
Task assignment follows department hierarchy rules.
Users can assign tasks to users at the same level or below.

Not Default Mode#

When marked as Not Default:
Assignment hierarchy is overridden.
Admin can manually select allowed assignees.

Manage Custom User#

Includes:
User selector
Assignees multi-select
Save action
This supports cross-department collaboration when required.

eef940da-095a-4b5d-a66b-de636b466bca.png#

Settings Page#

Navigate to:
Task Manager β†’ Settings
This page controls:
Task Workflow
Tags

99374ed4-aa13-43aa-b2cc-b606ef2032e2.png#

Task Workflow#

Defines lifecycle stages.
Default:
To Do β†’ In Progress β†’ Done
Admin can:
Add new statuses
Reorder statuses
Modify naming
89cc671e-12e6-43d0-bae3-61f2081f269a.png
Workflow directly impacts:
Kanban columns
Status dropdown
Reporting and filtering

Tags Management#

Create and manage task tags.
Tags table shows:
Name
Tasks Count
Edit
Delete
Click Add Tag to create new classification labels.

8357d42a-bdfa-4a09-b1c2-b5e3bcfac126.png
Tags are immediately available in task forms and filters.#

Archive Page#

Navigate to:
Task Manager β†’ Archive
The Archive page stores tasks that have been archived from the Tasks workspace.
Archived tasks are not active but remain saved in the system for reference, recovery, or permanent removal.
This helps teams keep the active task workspace organized while preserving operational history.

Archived Tasks Table#

The Archive page displays archived tasks in a tabular list view.
Columns include:
Title
Status
Priority
Tags
Links (Connected entities such as Projects)
Assignees
Due Date
Users can:
Search archived tasks
Select one or multiple tasks
Perform archive management actions
1716112b-64b0-4008-99dd-0e60d88f8107.png

Restoring Archived Tasks#

Archived tasks can be restored if they need to become active again.

Steps#

1.
Navigate to Task Manager β†’ Archive
2.
Select one or more archived tasks
3.
Click Restore
4.
Confirm the action in the restore dialog
The selected tasks will return to the active Tasks workspace.
e27337c0-fc8a-4009-b217-acbe27d5f55d.png

036ac29c-dc4f-4e93-8d70-81fc8f33e77b.png#

Permanently Deleting Archived Tasks#

Archived tasks can also be permanently removed from the system.

Steps#

1.
Navigate to Task Manager β†’ Archive
2.
Select the tasks you want to delete
3.
Click Delete
4.
Confirm the deletion
⚠️ Important:
Deleting a task permanently removes it from the system and cannot be undone.

8c1b6a9e-5224-4741-bede-841d920e8473.png#

Active Task
↓
Archive
↓
Restore β†’ Returns to Tasks
Delete β†’ Permanently removed

Notification Settings#

Navigate to:
Task Manager β†’ Notification Settings
The Notification Settings page allows users to control how they receive notifications related to task activities.
Fabritec automatically sends notifications when important task events occur, ensuring users stay informed about updates that affect their work.
Examples of events that trigger notifications include:
When a task is created and assigned to a user
When a user is added or removed as an assignee
When a user is added or removed as a watcher
When comments, attachments, or work logs are added
When key task fields such as status, priority, or due date change
When a task is archived, restored, or deleted
Users can customize how these notifications are delivered.
03225b8c-b838-4ed8-8562-05fc9a41dbbc.png

Notification Presets#

Fabritec provides preset notification configurations that users can quickly apply.
Available presets include:
None – No notifications
Standard – Default recommended settings
Minimal – Only critical notifications
Verbose – Notifications for most task events
Custom – Fully customizable notification rules
When Custom is selected, each notification event can be configured individually.
f63bbce8-6fb1-4ef3-948d-45f3376598f3.png

Notification Channels#

Each event can be configured to notify users through different channels.
Available channels include:
None – No notification is sent
In-App – Notification appears inside the Fabritec interface
Email – Notification is sent to the user's email
In-App & Email – Notification is sent through both channels
This flexibility allows users to balance visibility and notification frequency.
7079bb1a-12a3-4eb4-bf06-4c9652455ba4.png

Notification Categories#

Notification settings are grouped by activity type to make configuration easier.

People#

Notifications related to task participants:
Assignee add/remove
Watcher add/remove
Reporter change

Collaboration#

Notifications related to collaborative actions:
Comments
Worklogs
Attachments

Workflow Changes#

Notifications related to task lifecycle updates:
Status
Priority
Due Date
Archive
Restore
Delete
Title changes
These notifications help teams stay aware of operational changes that affect task execution.

Due Date Reminders#

Users can configure reminder notifications for task deadlines.
Reminder options include:
7 Days Before
3 Days Before
2 Days Before
1 Day Before
Same Day at 8:00 AM
Same Day at 12:00 PM
Users can also choose the Reminder Channel, such as:
In-App
Email
In-App & Email
These reminders help ensure that important deadlines are not missed.
WhatsApp Image 2026-03-12 at 12.28.36 PM.jpeg

Saving Notification Preferences#

After configuring the desired settings:
1.
Click Save at the top of the page.
2.
The selected notification preferences will be applied to your account.
Each user can configure their own notification settings independently.

Governance Model Summary#

Task Manager is built on four structural pillars:
1.
Workflow Control – Defines task lifecycle
2.
Assignment Governance – Controls responsibility boundaries
3.
Flexible Classification – Enables operational categorization
4.
Dependency Planning – Controls task sequencing and execution relationships
This ensures:
Structured execution
Controlled collaboration
Cross-functional visibility
Full operational traceability
Better planning between dependent activities
Stronger control over task timing and handoffs

⭐ Best Practices#

Add Start Date when the task has planned execution timing
Add Due Date when the task has a clear deadline
Use Estimated Hours to support workload planning
Use Parent Task and Sub Tasks for large work packages
Use Dependencies when tasks must follow a sequence
Use Finish to Start for most sequential tasks
Use Start to Start for parallel tasks that should begin together
Use Finish to Finish when two tasks must finish together
Use positive lag values when a waiting period is needed
Use negative lead values only when overlap is operationally safe
Avoid unnecessary dependencies that make task planning too complex
Review dependencies when project priorities or dates change

πŸ”— Related Articles#

Reports – Analyze production performance
Dashboards – Track daily productivity trends
Shifts – Manage worker schedules
Labours – Assign and manage factory workers
Modified atΒ 2026-06-21 10:59:39
Previous
Folder Structure
Next
Task Templates & Schedule View
Built with