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.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
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
The Tasks page is the primary workspace for creating and managing tasks assigned to you or your team.All Tasks / My Tasks toggle
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.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:Basic Fields#
Basic Fields#
The Add Task form includes the main fields required to define the task, assign responsibility, and plan execution.
Title#
Use a clear and direct title that explains the required action.Confirm shipping readiness
Update phase production plan
Status#
Defines the current lifecycle stage of the task.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
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: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.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
If a task is expected to take 4 hours, enter 4 in the Estimated Hours field.
Priority#
Critical β Blocking work or affecting delivery
High β Important task with near deadline or operational impact
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
Assign To Me#
The Assign To Me option allows the current user to quickly assign the task to themselves.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#
Click More Options to display additional task fields.These fields are useful when the task requires more structure, collaboration, or planning control.
Flexible labels used for classification and filtering.Managed centrally in Settings
Used in grouping and swimlane views
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.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.Phase 01 Engineering Preparation
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.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.
Useful for defining the task sequence from the beginning
2.
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#
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.Start production planning
The predecessor task may be: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: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.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.
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.Material Preparation starts when Production Planning starts.
Shop Drawing Review starts when BOM Review starts.
Site Coordination starts when Shipping Planning starts.
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.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.
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.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.
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.
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.The current task starts 2 days after the predecessor task finishes.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.The current task can start 1 day before the predecessor task finishes.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.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.Release Phase 01 for production
Material availability checked
Each dependency can have its own: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#
The production team cannot start planning until engineering finishes the detailing package.Production planning for Phase 01
Production planning starts after detailing is completed.If the team needs one extra day for review, set Lag to:If planning can begin one day before detailing is fully finished, set Lead to:
Practical Example: Parallel Work#
Material preparation can start at the same time as production planning.Prepare material availability list
Production planning for Phase 01
Both tasks start together.
Practical Example: Finish Alignment#
QC documentation should be completed at the same time as final inspection.Complete QC documentation
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:Use Description to capture:β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:Status#
Defines the lifecycle stage of the task.Grouping and swimlane options
Workflow is configurable from Settings.
Priority#
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.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.
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:Resource planning accuracy
Assignees#
Users responsible for executing the task.Assignment rules are governed by:Department hierarchy (Default)
Or custom override (Not Default users)
Watchers#
Users who receive visibility and updates but are not responsible for execution.
Flexible labels used for classification and filtering.Managed centrally in Settings
Used in grouping and swimlane views
Parent Task & Sub Tasks#
Tasks can be structured hierarchically.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:This ensures tasks remain connected to production data and are fully traceable.
Attachments#
Upload files directly to tasks:
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.
Audit Logs#
Audit Logs track key task events such as: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
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.Supports grouping and swimlane configuration.
List View#
Tabular representation of tasks.Bulk actions (Edit, Archive, Delete)
Calendar View#
The Calendar View provides a time-based visualization of tasks, allowing teams to plan, track, and manage work based on due dates.Weekly and monthly planning
Identifying workload distribution
Monitoring upcoming and overdue tasks
πΉ 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)
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
Balance workload across teams
Conduct weekly planning meetings
Grouping & Swimlane Engine#
Task Manager supports flexible board configuration.Available grouping options include:Group by Priority
Swimlane by StatusGroup by Due Date
Swimlane by PriorityThis enables dynamic operational dashboards without modifying task data.
This page controls who can assign tasks to whom.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#
This supports cross-department collaboration when required.Task Manager β SettingsTask Workflow#
Defines lifecycle stages.To Do β In Progress β Done
Workflow directly impacts:
Create and manage task tags.Click Add Tag to create new classification labels.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.Links (Connected entities such as Projects)
Select one or multiple tasks
Perform archive management actions
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
4.
Confirm the action in the restore dialog
The selected tasks will return to the active Tasks workspace.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
β οΈ Important:
Deleting a task permanently removes it from the system and cannot be undone.Active Task
β
Archive
β
Restore β Returns to Tasks
Delete β Permanently removed
Task Manager β Notification SettingsThe 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.
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.
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.
Notification Categories#
Notification settings are grouped by activity type to make configuration easier.People#
Notifications related to task participants:
Collaboration#
Notifications related to collaborative actions:
Workflow Changes#
Notifications related to task lifecycle updates: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:Users can also choose the Reminder Channel, such as:These reminders help ensure that important deadlines are not missed.
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
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#