Task Templates

The Task Templates feature inside Fabritec Task Manager allows teams to create reusable task workflows for activities that are repeated across multiple Projects, Buildings, or Phases.

Instead of recreating the same tasks manually each time, users can define a standard workflow once and apply it whenever the same operational process is required.

Using Task Templates, you can:

Create reusable task workflows

Apply templates to Projects, Buildings, or Phases

Create parent tasks and subtasks

Define assignees and watchers

Add tags and priorities

Configure start offsets and durations

Estimate the work hours required for each task

Create dependencies between related tasks

Calculate dates using calendar days or working days

Preview generated task dates before applying a template

Standardize repeated operational processes

Task Templates help teams reduce manual setup, improve consistency, clarify responsibility, and ensure that important execution steps are not missed.

Where to Find Task Templates

Navigate to:

Task Manager → Task Templates

The Task Templates page displays the reusable templates available to your organization.

From this page, authorized users can:

Search for templates

Filter available templates

Create a new template

Edit an existing template

Review template details

Apply a template to a Project, Building, or Phase

What Are Task Templates?

Task Templates are predefined task structures that generate live tasks automatically inside Fabritec.

Each template can contain:

Main tasks

Subtasks

Assignees

Watchers

Tags

Priority

Start Offset

Duration

Estimated Hours

Dependencies

Calendar-day or working-day scheduling logic

In simple terms:

A Task Template is a ready-made execution plan that can be applied to a Project, Building, or Phase.

For example, a Phase Revision Workflow template can include:

Create Revision

Import Phase Items

Upload Phase Drawings

Review Imported Items

Approve Revision

Release Phase for Production

When the template is applied, Fabritec creates these tasks automatically and links them to the selected Phase.

Why Task Templates Are Useful

Many operational activities follow the same steps across different projects.

Examples include:

New project kickoff

Project document collection

Engineering review

Building preparation

Phase revision preparation

Production release

Quality Control follow-up

Procurement follow-up

Shipping readiness

Site coordination

Without Task Templates, users may need to create the same tasks manually each time.

This can cause:

Missed activities

Inconsistent task names

Missing assignees

Unclear responsibility

Incorrect dates

Repeated administrative work

Different workflows between projects

Delays before execution begins

Task Templates solve this by creating a controlled and repeatable task structure.

Task Templates Page

The Task Templates page displays available templates as cards.

Each Template Card may display:

Template name

Description

Tags

Number of tasks

Offset unit

Applies to

Assignee or participant initials

Edit button

Apply button

The information shown on the card helps users understand the template before opening or applying it.

For example, a card may show that the template:

Contains 10 tasks

Uses Working Days

Applies to Projects

Includes Engineering and Planning tags

Assigns tasks to three users

Template Filters

Users can filter the template library using options such as:

All templates

Created by me

Recently used

These filters help users find the relevant template without reviewing the full library.

Search

Use the search field to find a template by name.

Examples:

New Project

Upload Documents

Building Preparation

Phase Revision

Production Release

Shipping Readiness

Use clear and specific template names so users can find the correct workflow quickly.

Creating a New Task Template

To create a new template:

Navigate to Task Manager → Task Templates

Click New Template

Enter the Template Name

Add a Description

Select Applies to

Select the Offset Unit

Add tasks and subtasks

Configure assignees, watchers, tags, and priorities

Define Start Offsets and Durations

10.

Add Estimated Hours where required

11.

Configure dependencies between related tasks

12.

Review the template in Grid View or Timeline View

13.

Click Save

New Template Page

The New Template page is where the reusable task workflow is designed.

The page includes:

Template Name

Description

Template Summary

Applies to

Offset Unit

View selector

Task Set

Save button

Cancel button

The Template Summary may display:

Number of tasks

Total template span

Number of assigned people

This gives users a quick overview of the workflow before saving it.

Template Name

The Template Name is the name displayed in the Task Templates library.

Use a clear name that explains the purpose of the workflow.

Recommended examples:

New Project Kickoff

Project Engineering Workflow

Project Document Collection

Building Preparation Workflow

Phase Revision Workflow

Production Release Checklist

Quality Inspection Follow-Up

Shipping Readiness Workflow

Avoid unclear names such as:

Test

Template 1

Tasks

New Template

Workflow

A clear name helps users select the correct template and reduces the risk of applying the wrong process.

Description

The Description explains when and why the template should be used.

A good description should clarify:

The operational situation

The expected workflow

The entity to which it should be applied

The intended result

Example:

Use this template when starting a new project to assign kickoff activities, collect project documents, prepare drawings, assign the project team, and begin the initial planning workflow.

Another example:

Use this template when preparing a new Phase revision. It includes item import, drawing upload, quantity review, approval, and production release activities.

Descriptions are especially important when the organization has several templates with similar names.

Applies To

The Applies to field defines the operational entity that will receive the generated tasks.

Available options include:

Project

Building

Phase

This setting determines what the user must select when applying the template.

Project

Select Project when the template contains activities related to the full project.

Project templates can be used for:

Reviewing the contract

Uploading project documents

Assigning the project team

Reviewing the Scope of Work

Preparing the project schedule

Preparing general arrangement drawings

Planning procurement activities

Coordinating project-wide approvals

Example template:

New Project Kickoff

Possible tasks:

Review Contract

Upload Project Documents

Assign Project Team

Confirm Scope of Work

Prepare Initial Schedule

Prepare GA Drawings

Building

Select Building when the workflow must be repeated for a specific Building inside a Project.

Building templates can be used for:

Reviewing the building model

Extracting the building BOM

Confirming building quantities

Preparing the building phase plan

Reviewing the shipping sequence

Confirming delivery requirements

Preparing building-specific documents

Example template:

Building Preparation Workflow

Possible tasks:

Review Building Model

Confirm Building Information

Extract Building BOM

Prepare Phase Breakdown

Review Shipping Sequence

Confirm Site Requirements

Phase

Select Phase when the workflow applies to a specific project Phase.

Phase templates can be used for:

Creating a revision

Importing items

Uploading drawings

Reviewing imported data

Approving the revision

Releasing the Phase for production

Following up Quality Control

Preparing packing lists

Confirming shipping readiness

Example template:

Phase Revision Workflow

Possible tasks:

Create Revision

Import Phase Items

Upload Phase Drawings

Review Imported Items

Approve Revision

Release Phase for Production

Offset Unit

The Offset Unit defines how Fabritec calculates the generated task dates.

Available options include:

Calendar Days

Working Days

The selected Offset Unit applies to the Start Offset, Duration, and generated task schedule.

Calendar Days

Calendar Days count every day continuously.

This includes:

Working days

Weekends

Non-working days

Example:

Template Start Date: June 20

Task Start Offset: 2

Generated Start Date: June 22

Calendar Days can be used for:

Client deadlines

Fixed calendar commitments

General follow-up activities

External review periods

Calendar-based approval windows

Working Days

Working Days count only the organization’s configured working days.

Non-working days are excluded from the date calculation.

Working Days are normally more appropriate for internal operational workflows such as:

Engineering

Planning

Procurement

Production preparation

Quality Control

Shipping preparation

Internal approvals

Example:

If a template starts on the last working day of the week and the next day is not a company working day, the following task will be scheduled on the next available working day.

Working Days help create a more realistic execution schedule.

Template Views

Inside the New Template or Edit Template page, users can switch between:

Grid View

Timeline View

Both views display the same template structure but support different review activities.

Grid View

Grid View displays the template tasks in a table.

Use Grid View to manage:

Task names

Assignees

Watchers

Tags

Start Offsets

Durations

Priorities

Task order

Subtasks

Grid View is normally the most efficient view for creating or editing the task structure.

Timeline View

Timeline View displays template tasks visually across a planned timeline.

The Template Timeline is calculated using:

Start Offset

Duration

Task hierarchy

Subtask timing

Use Timeline View to review:

Task sequence

Task duration

Task overlap

Subtask timing

Overall template span

Assignee distribution

Timeline View helps identify scheduling problems before the template is saved or applied.

For example, it may reveal that:

Two tasks overlap unexpectedly

A task begins too early

A task has an unrealistic duration

A dependent task is scheduled before its predecessor

The complete workflow takes longer than expected

Task Set

The Task Set is the main section where the template workflow is created.

From the Task Set, users can:

Add tasks

Create subtasks

Reorder tasks

Define assignees

Add watchers

Add tags

Set priorities

Configure Start Offsets

Configure Durations

Open detailed task settings

Add dependencies

The Task Set determines exactly what Fabritec will generate when the template is applied.

Adding a Task

Click Add Task to create a new task row.

Each task can include:

Task Name

Assignees

Watchers

Tags

Start Offset

Duration

Priority

Use action-based task names that clearly describe the required work.

Recommended examples:

Review Contract

Upload Project Documents

Prepare GA Drawings

Extract Material Takeoff

Create Purchase Request

Import Phase Items

Upload Phase Drawings

Review BOM

Release Phase for Production

Prepare Packing List

Avoid task names that do not explain the required action, such as:

Contract

Documents

Drawings

Review

Production

Subtasks

Fabritec supports creating Subtasks inside a Task Template.

Subtasks divide a larger activity into smaller and more manageable steps.

Example: Upload Project Documents

Parent Task

Upload Project Documents

Subtasks

Upload Contract

Upload Drawings

Upload BOQ

Upload Technical Specifications

Upload Customer Correspondence

Example: Prepare Phase Revision

Parent Task

Prepare Phase Revision

Subtasks

Create Revision

Import Items

Upload Drawings

Upload Supporting Files

Review Quantities

Confirm Revision Data

Subtasks are useful when:

Several activities contribute to one main result

Different users are responsible for parts of the same work package

Progress needs to be tracked in more detail

A checklist is too simple for the required workflow

Assignees

Assignees are the users responsible for performing the generated task.

Examples:

Task	Suggested Assignee
Prepare GA Drawings	Design Engineer
Extract Material Takeoff	Planning Engineer
Create Purchase Request	Procurement Engineer
Release Phase for Production	Production Manager
Inspect Final Welding	QC Inspector
Prepare Packing List	Shipping Coordinator

Assign tasks to the role or user who is accountable for completing the activity.

Avoid assigning every task to the same user unless that user is genuinely responsible for the complete workflow.

Watchers

Watchers are users who need visibility into the task but are not responsible for completing it.

Watchers can monitor:

Status changes

Comments

Attachments

Progress

Completion

Delays

Examples of watchers include:

Project Manager

Planning Manager

QC Manager

Shipping Manager

Department Manager

Operations Manager

For example:

The Design Engineer may be the Assignee for Prepare GA Drawings

The Project Manager may be added as a Watcher

This keeps responsibility clear while maintaining management visibility.

Tags

Tags classify tasks and support easier filtering.

Examples:

Engineering

Planning

Procurement

Production

Shipping

Erection

Client Approval

Internal Review

Documents

Tags should describe the task category or operational area.

Do not use tags as substitutes for task statuses.

For example:

Use the tag Engineering to classify the task

Use the task status to show whether it is To Do, In Progress, or Done

Start Offset

The Start Offset defines when a task should begin relative to the selected Template Start Date.

It is not a fixed calendar date.

Example:

Template Start Date: June 20

Task	Start Offset	Generated Start Date
Review Contract	0	June 20
Upload Documents	1	June 21
Prepare Drawings	2	June 22

Because Start Offset is relative, the same template can be reused with different Start Dates.

Understanding Start Offset

A Start Offset of:

0 means the task starts on the Template Start Date

1 means the task starts one offset unit later

2 means the task starts two offset units later

The actual generated date depends on whether the template uses:

Calendar Days

Working Days

Duration

The Duration defines how long the task is expected to remain active.

Example:

Task: Prepare GA Drawings

Start Offset: 1

Duration: 5

This means:

Prepare GA Drawings begins one day after the Template Start Date and continues for five days.

Duration helps Fabritec calculate the generated task Due Date.

Use realistic durations based on:

The task scope

Available resources

Approval requirements

Historical execution time

Operational complexity

Avoid giving every task the same duration unless the activities genuinely require the same amount of time.

Priority

The Priority field defines the urgency and operational importance of the generated task.

Available priority levels may include:

Very Low

Low

Normal

High

Critical

Recommended usage:

Priority	Recommended Usage
Critical	The task blocks execution or directly affects delivery
High	The task has significant operational impact
Normal	Standard operational activity
Low	Non-urgent follow-up
Very Low	Optional or long-term improvement activity

Use Critical priority carefully.

If too many tasks are marked as Critical, users will not be able to distinguish the work that genuinely requires immediate attention.

Task Details Inside a Template

Opening a task inside the template displays the Task Details window.

The Task Details window may include:

Title

Description

Assignees

Watchers

Tags

Priority

Start Offset

Duration

Estimated Hours

Dependencies

Use this window when the task requires more information than can be configured directly from the Grid View.

Task Description

The Description field stores detailed instructions for the task.

Use the Description to define:

Scope

Required documents

Review instructions

Acceptance criteria

Internal notes

Production requirements

Quality requirements

Expected output

Example:

Review all Phase 01 drawings and confirm that the latest approved revision is available before importing items into the Phase revision.

Another example:

Confirm that all completed items have passed the required Quality Control inspections before preparing the packing list.

A clear description reduces dependency on verbal explanations after the template is applied.

Estimated Hours

The Estimated Hours field defines the expected work effort required to complete the task.

Example:

Task: Prepare GA Drawings

Estimated Hours: 16

Estimated Hours can help teams:

Estimate workload

Understand expected effort

Compare planned effort with actual work logs

Improve future planning

Support resource and capacity discussions

Identify tasks with unrealistic schedules

Estimated Hours and Duration represent different concepts.

Duration defines the calendar or working-day span

Estimated Hours defines the expected effort

For example, a task may have:

Duration: 3 working days

Estimated Hours: 8 hours

This means the team expects eight hours of work to be completed within a three-day period.

Dependencies in Task Templates

Task Templates support Dependencies between tasks.

A dependency connects one task to another in a planned sequence.

Dependencies help teams avoid starting or completing work before the required predecessor activity is ready.

Examples:

Drawing Review must finish before Production Release starts

Material Estimation must finish before Purchase Request preparation starts

Final Inspection must finish before Shipping Preparation finishes

Phase Revision Approval must finish before Production Release starts

Dependency Fields

The Dependencies section may include:

Predecessor

Dependency Type

Lag or Lead

Add button

Existing dependency list

Predecessor

The Predecessor is the task that controls the timing relationship.

Example:

Current Task:

Create Purchase Request

Predecessor:

Estimate Materials

This means the timing of Create Purchase Request is linked to Estimate Materials.

Dependency Types

Available dependency types include:

FS: Finish to Start

SS: Start to Start

FF: Finish to Finish

SF: Start to Finish

FS: Finish to Start

The current task starts after the predecessor finishes.

Example:

Estimate Materials starts after Prepare GA Drawings finishes.

This is the most common dependency type.

Use it for sequential activities where one task must be completed before the next task can begin.

SS: Start to Start

The current task starts when the predecessor starts.

Example:

Prepare Procurement Plan starts when Material Estimation starts.

Use this dependency when two activities can begin at the same time.

FF: Finish to Finish

The current task finishes when the predecessor finishes.

Example:

QC Documentation finishes with Final Inspection.

Use this dependency when two activities must be completed together.

SF: Start to Finish

The current task finishes when the predecessor starts.

This dependency type is less common.

It may be used for special handover or shift-transition workflows where the completion of one task depends on the start of another.

Use SF dependencies only when the operational relationship is clear.

Lag and Lead

The Lag / Lead value adjusts the timing between dependent tasks.

Positive value = Lag

Negative value = Lead

Zero = No additional delay or overlap

Lag Example

Dependency Type: Finish to Start
Lag: 2 days

Meaning:

The current task begins two days after the predecessor finishes.

Example:

Predecessor: Approve Revision

Current Task: Release Phase for Production

Lag: 1 working day

The production release task begins one working day after approval.

Lead Example

Dependency Type: Finish to Start
Lead: -1 day

Meaning:

The current task can begin one day before the predecessor finishes.

Lead creates an overlap between tasks.

Use lead only when:

The overlap is operationally safe

The current task does not require the predecessor to be fully complete

The responsible teams understand the relationship

Partial predecessor output is sufficient

Reviewing a Template Before Saving

Before saving a Task Template, confirm:

The Template Name is clear

The Description explains when to use it

Applies to is correct

The correct Offset Unit is selected

All required tasks are included

Task names are action-based

Assignees are appropriate

Watchers have been added where needed

Tags are consistent

Priorities are realistic

Start Offsets are correct

Durations are realistic

Estimated Hours are reasonable

Dependencies represent real operational relationships

Subtasks are positioned under the correct parent task

The Timeline View displays the intended sequence

After completing the review, click Save.

Applying a Task Template

After creating a template, users can apply it from the Task Templates page.

To apply a template:

Navigate to Task Manager → Task Templates

Find the required template

Click Apply

Select the target Project, Building, or Phase

Select the Start Date

Review the Schedule Preview

Click Apply

Fabritec then creates the tasks automatically.

Apply Task Template Window

The Apply task template window displays the template information before tasks are generated.

The window may include:

Template Name

Description

Number of tasks

Applies to

Offset Unit

Target selector

Start Date

Schedule Preview

Apply button

Cancel button

Review this information carefully before creating the tasks.

Selecting the Target

The target selector depends on the template’s Applies to setting.

Project template → Select a Project

Building template → Select a Building

Phase template → Select a Phase

This ensures the generated tasks are linked to the correct operational entity.

For example:

A Project Kickoff template should be applied to the relevant Project

A Building Preparation template should be applied to the relevant Building

A Phase Revision template should be applied to the relevant Phase

Start Date

The Start Date is the date Fabritec uses to calculate the generated task dates.

Fabritec combines:

The selected Start Date

Each task’s Start Offset

Each task’s Duration

The selected Offset Unit

Any configured dependencies

Example:

Start Date: June 20

Task	Start Offset	Generated Start Date
Review Contract	0	June 20
Upload Documents	1	June 21
Prepare Drawings	2	June 22

If the template uses Working Days, non-working days are excluded.

If the template uses Calendar Days, all days are included.

Schedule Preview

Before the tasks are created, Fabritec displays a Schedule Preview.

The preview can be shown using:

Days

Dates

Days

The Days view displays each task according to its position inside the template.

Example:

Day 0

Day 1

Day 2

Day 5

This is useful for reviewing the template’s relative schedule.

Dates

The Dates view displays the actual generated dates based on the selected Start Date.

This is useful for confirming:

Start Dates

Due Dates

Working-day calculations

Weekend handling

Task overlap

Overall schedule span

Always review the Schedule Preview before clicking Apply.

After the tasks are created, changing the template does not automatically rebuild the already-generated tasks.

What Happens After Applying the Template?

After clicking Apply, Fabritec creates real tasks inside Task Manager.

The generated tasks can include:

Status

Priority

Assignees

Watchers

Tags

Start Date

Due Date

Description

Estimated Hours

Comments

Attachments

Work Logs

Audit Logs

Dependencies

Entity linking

Notifications

Archive controls

The tasks can then be managed using the standard Task Manager features.

Task Templates do not create static checklists.

They create live operational tasks that can be assigned, updated, discussed, monitored, and completed.

Practical Example: New Project Kickoff Template

Template Name

New Project Kickoff

Description

Use this template when creating a new Project to review the commercial scope, collect documentation, assign the Project team, and begin engineering and planning activities.

Applies To

Project

Offset Unit

Working Days

Tasks

Task	Assignee	Start Offset	Duration	Priority
Review Contract	Project Manager	0	1	High
Upload Project Documents	Document Controller	0	2	Normal
Assign Project Team	Project Manager	1	1	High
Prepare GA Drawings	Design Engineer	2	5	High
Estimate Materials	Planning Engineer	7	2	Normal
Create Purchase Request	Procurement Engineer	9	1	Normal

Dependencies

Estimate Materials depends on Prepare GA Drawings

Create Purchase Request depends on Estimate Materials

Result

When the template is applied, Fabritec creates the kickoff tasks with:

Planned dates

Assignees

Priorities

Durations

Dependencies

Project linking

The Project team can begin execution without rebuilding the workflow manually.

Practical Example: Phase Revision Workflow

Template Name

Phase Revision Workflow

Description

Use this template when preparing a new Phase revision, from revision creation and item import through approval and production release.

Applies To

Phase

Offset Unit

Working Days

Tasks

Task	Assignee	Start Offset	Duration	Priority
Create Revision	Planning Engineer	0	1	High
Import Phase Items	Planning Engineer	0	1	High
Upload Phase Drawings	Document Controller	1	2	High
Review Imported Items	Planning Manager	2	1	Normal
Approve Revision	Project Manager	3	1	High
Release Phase for Production	Production Manager	4	1	Critical

Dependencies

Upload Phase Drawings depends on Import Phase Items

Review Imported Items depends on Upload Phase Drawings

Approve Revision depends on Review Imported Items

Release Phase for Production depends on Approve Revision

Result

The Phase team receives a complete workflow for:

Preparing the revision

Reviewing imported data

Controlling approval

Releasing the correct Phase information to production

Practical Example: Building Preparation Workflow

Template Name

Building Preparation Workflow

Applies To

Building

Offset Unit

Working Days

Tasks

Task	Assignee	Start Offset	Duration	Priority
Review Building Model	Design Engineer	0	2	High
Confirm Building Quantities	Planning Engineer	2	1	High
Extract Building BOM	Planning Engineer	3	2	Normal
Prepare Phase Breakdown	Project Manager	5	2	High
Review Shipping Sequence	Shipping Coordinator	7	1	Normal
Confirm Site Requirements	Project Manager	8	1	Normal

Result

The selected Building receives a controlled preparation workflow covering engineering, planning, and shipping coordination.

Common Use Cases

New Project Kickoff

Use a Project template when a new Project begins.

Typical tasks:

Review Contract

Upload Project Documents

Confirm Scope of Work

Assign Project Team

Prepare Project Schedule

Prepare Initial Drawings

Project Document Collection

Use a Project template to collect the documents required before engineering or planning begins.

Typical tasks:

Upload Contract

Upload BOQ

Upload Drawings

Upload Specifications

Review Customer Documents

Confirm Missing Information

Building Preparation

Use a Building template when each Building requires its own preparation process.

Typical tasks:

Review Building Model

Extract Building BOM

Confirm Building Quantities

Prepare Phase Plan

Review Shipping Sequence

Confirm Site Requirements

Phase Revision Preparation

Use a Phase template when preparing a new revision.

Typical tasks:

Create Revision

Import Items

Upload Drawings

Upload Supporting Files

Review Quantities

Approve Revision

Production Release Checklist

Use a Phase template before releasing work to production.

Typical tasks:

Confirm Revision Approval

Validate BOM

Confirm Latest Drawings

Review Quality Requirements

Confirm Routing

Confirm Production Readiness

Release Phase for Production

Quality Control Follow-Up

Use a Phase template when Quality Control activities require structured follow-up.

Typical tasks:

Confirm Inspection Requirements

Review Pending Inspections

Complete Dimensional Inspection

Review Welding Inspection

Record Rework

Confirm Final Approval

Shipping Readiness

Use a Project or Phase template to prepare work for dispatch.

Typical tasks:

Review Completed Items

Confirm Quality Approval

Prepare Packing List

Confirm Loading Requirements

Review Shipping Sequence

Coordinate Dispatch Date

Template Governance

Task Templates support stronger task-management governance by providing a consistent structure for repeated work.

Reusable Execution Structures

Templates ensure that teams follow the same workflow each time the same operational process occurs.

Entity-Based Planning

Templates can be linked to:

Projects

Buildings

Phases

This keeps tasks connected to the correct operational context.

Standard Responsibility

Templates can define assignees and watchers in advance.

This reduces uncertainty about who is responsible for each activity.

Consistent Scheduling

Start Offsets, Durations, and Offset Units create a repeatable scheduling method.

Controlled Dependencies

Dependencies maintain the planned sequence between related tasks.

Reduced Manual Setup

Users do not need to recreate repeated tasks, assignments, priorities, and dates manually.

This supports:

Consistent task creation

Clearer responsibility

Faster workflow setup

Stronger execution control

Better coordination

Reduced missed activities

Important Considerations

Confirm that the template Applies to the correct entity type before saving it.

Review user assignments regularly when team responsibilities change.

Do not add dependencies unless a real timing relationship exists.

Use Working Days for internal execution workflows when company calendars must be respected.

Use Calendar Days for commitments that continue across weekends or non-working days.

Review generated dates before applying the template.

Avoid creating very large templates when the workflow can be divided into smaller, focused templates.

Update templates when the organization’s standard operating process changes.

Changes to a template affect future applications, not tasks that were already generated.

⭐ Best Practices

Use clear and specific template names

Write descriptions that explain when the template should be used

Select Applies to carefully

Use Project templates for project-wide workflows

Use Building templates for building-specific activities

Use Phase templates for revision, production, QC, and shipping workflows

Use Working Days for operational execution

Use Calendar Days for fixed calendar commitments

Keep task names action-based

Use subtasks for detailed work packages

Assign responsible users from the beginning

Add watchers only when they require visibility

Use tags for classification

Set realistic priorities

Define realistic Start Offsets and Durations

Add Estimated Hours where workload planning is important

Use dependencies only when tasks have a real sequence

Review Timeline View before saving

Review Schedule Preview before applying

Update templates when the standard workflow changes

Archive or stop using duplicate and outdated templates

Reports – Analyze production performance

Dashboards – Track daily productivity trends

Shifts – Manage worker schedules

Labours – Assign and manage factory workers

Where to Find Task Templates#

What Are Task Templates?#

Why Task Templates Are Useful#

Task Templates Page#

Template Filters#

Search#

Creating a New Task Template#

New Template Page#

Template Name#

Description#

Applies To#

Project#

Building#

Phase#

Offset Unit#

Calendar Days#

Working Days#

Template Views#

Grid View#

Timeline View#

Task Set#

Adding a Task#

Subtasks#

Example: Upload Project Documents#

Parent Task#

Subtasks#

Example: Prepare Phase Revision#

Parent Task#

Subtasks#

Assignees#

Watchers#

Tags#

Start Offset#

Understanding Start Offset#

Duration#

Priority#

Task Details Inside a Template#

Task Description#

Estimated Hours#

Dependencies in Task Templates#

Dependency Fields#

Predecessor#

Dependency Types#

FS: Finish to Start#

SS: Start to Start#

FF: Finish to Finish#

SF: Start to Finish#

Lag and Lead#

Lag Example#

Lead Example#

Reviewing a Template Before Saving#

Applying a Task Template#

Apply Task Template Window#

Selecting the Target#

Start Date#

Schedule Preview#

Days#

Dates#

What Happens After Applying the Template?#

Practical Example: New Project Kickoff Template#

Template Name#

Description#

Applies To#

Offset Unit#

Tasks#

Dependencies#

Result#

Practical Example: Phase Revision Workflow#

Template Name#

Description#

Applies To#

Offset Unit#

Tasks#

Dependencies#

Result#

Practical Example: Building Preparation Workflow#

Template Name#

Applies To#

Offset Unit#

Where to Find Task Templates

What Are Task Templates?

Why Task Templates Are Useful

Task Templates Page

Template Filters

Search

Creating a New Task Template

New Template Page

Template Name

Description

Applies To

Project

Building

Phase

Offset Unit

Calendar Days

Working Days

Template Views

Grid View

Timeline View

Task Set

Adding a Task

Subtasks

Example: Upload Project Documents

Parent Task

Subtasks

Example: Prepare Phase Revision

Parent Task

Subtasks

Assignees

Watchers

Tags

Start Offset

Understanding Start Offset

Duration

Priority

Task Details Inside a Template

Task Description

Estimated Hours

Dependencies in Task Templates

Dependency Fields

Predecessor

Dependency Types

FS: Finish to Start

SS: Start to Start

FF: Finish to Finish

SF: Start to Finish

Lag and Lead

Lag Example

Lead Example

Reviewing a Template Before Saving

Applying a Task Template

Apply Task Template Window

Selecting the Target

Start Date

Schedule Preview

Days

Dates

What Happens After Applying the Template?

Practical Example: New Project Kickoff Template

Template Name

Description

Applies To

Offset Unit

Tasks

Dependencies

Result

Practical Example: Phase Revision Workflow

Template Name

Description

Applies To

Offset Unit

Tasks

Dependencies

Result

Practical Example: Building Preparation Workflow

Template Name

Applies To

Offset Unit

Tasks