01What it is
Tasks is the register of work in two scopes: site tasks belong to a project on a site, and object service tasks are pinned directly to an object you only service. A task has a start, a duration in days, estimated hours, a priority and an assignee.
The assignee is a crew or a person: a crew when a team does the work, a person when one individual is responsible. That decides which conflict the schedule shows. An undated task does not stand anywhere in time, so it clashes with nothing.
The states are: to do, in progress, for approval, done and blocked. Blocking requires a sentence about what the task is waiting for.
- WHO AND WHEN
- A crew or a person, a start and a duration.
- CHECKLIST
- A required item blocks closing.
- PROOF OF COMPLETION
- A photo or a document for work that gets covered up.
02What it is for
Work split between people
Every task has an assignee, an area and a date.
Delays and blocks in view
Tiles count late, blocked and unassigned tasks.
Proof a week later
A task that requires proof closes only after a photo or a document is uploaded.
Consistent quality
A checklist template loads ready-made points, for example for a works handover or fire-stop penetrations.
03Main options
The task card has tabs: Overview, Dependencies, Checklist, Proof of completion and Task events. The four used most often are described below.
Task plan and state
Start, end, duration, assignee and the deadline of the project the task belongs to.
- Change the state from the card menu
- Block task with the reason it is waiting
- The number of ticked checklist items
What has to come first
This is where schedule conflicts come from.
- Finish › start, start › start, finish › finish
- What must come before and what waits for this task
- No dependency to another site and no closed loops
Points to tick off
A required item blocks closing the task.
- Load from a checklist template
- Points from the template are added as required
- Templates suggested by the type of work
A photo or a document in the task
For work that gets covered up, this is the only way to show anything a week later.
- A photo or a document attached to the task
- A task that requires proof does not close without it
- Task events show state changes and added proof
04Tasks step by step
- STEP 1Open Modules › People and planning › Tasks and choose New task.
- STEP 2Enter the title, choose the project (or the object in the Object service scope) and the area, for example floor 3.
- STEP 3Choose a crew or a person, set the start, duration and priority. For work that gets covered up, tick Requires proof of completion.
- STEP 1On the task list switch the layout to the board. The columns are task states.
- STEP 2Move a card to another state with Move to.
- STEP 3The done column shows tasks from the last 14 days; older ones are on the list.
- STEP 1On the task card choose Block task.
- STEP 2Write one sentence on what the work is waiting for. The manager and the crew will see it.
- STEP 1Open the task card and the Checklist tab.
- STEP 2Choose a template and load it. The points are added to the list as required.
05Actions
The most common tasks around tasks.
New task
Work to be done with an assignee and a date.
Schedule
The task chart and conflicts.
Block task
With the reason it is waiting.
Checklist
Points from a template or your own.
Proof of completion
A photo or a document in the task.
Time filter
Late, next 7 days or undated.
06What it connects to
Choose a module to see how it uses tasks.
Schedule
Dated tasks build the schedule chart and its conflicts.
Go to the topicScheduleObjects
Object service tasks are pinned directly to an object.
Go to the topicObjectsChecklist templates
Checklist templates are loaded on the task card.
Go to the topicChecklist templatesTimesheets
An attendance entry can point at the task that was worked on.
Go to the topicTimesheets