Projects

Planning & delivery

Turn a plan into finished work. Break the work into items, organize it on boards and sprints, schedule it on the timeline, and balance the team's workload.

βœ… WorkπŸƒ SprintsπŸ“ FormsπŸ“ˆ TimelineπŸ‘₯ Workload
Two colleagues arranging connected task cards on a shared board.

Work: the heart of every project

The Work module holds every work item in the project: tasks, bugs, deliverables, and whatever else your team tracks. Show the same items as a board, a list, or a table, whichever suits the job.

Drag a card to change its status. The list, timeline, and reports update at the same time.

What a work item holds

Who and when

Assignee, priority, start and due dates, and an estimate.

Detail

Description, subtasks, and your team's custom fields.

Conversation

Comments, @mentions, and attached files.

Dependencies

Links that control the order of the work.

Each project can define its own types (for example Task, Bug, or Deliverable) and statuses. Every status belongs to one of four groups (to do, in progress, done, or cancelled), so reports stay consistent across projects. Save your favorite filters and layouts as saved views.

Dependencies in plain words

A dependency says how one item has to wait for another. There are four kinds:

TypeMeansExample
Finish β†’ Start (FS)B can start only after A finishes.Install after delivery.
Start β†’ Start (SS)B can start only after A starts.Testing starts once building starts.
Finish β†’ Finish (FF)B can finish only after A finishes.Documentation finishes after development.
Start β†’ Finish (SF)B can finish only after A starts.The old shift ends once the new shift starts.

Sprints

If your team works in short cycles, use Sprints. A sprint has a goal and a date window. Items not yet in a sprint wait in the backlog. A sprint does not copy the items: it groups the same work items you see on the board.

Intake forms

Use Forms to collect requests in a consistent way, such as IT requests, change ideas, or site reports. Every submission becomes a work item automatically. The submissions view shows who answered, when, and which work item was created.

Project automations

Let the project handle routine follow-ups for you. Each rule is when this happens β†’ if these conditions are true β†’ do this.

A rule can start when…Example action
an item's status changesNotify the reviewer when an item moves to Review.
an item is assignedAdd a comment with the team checklist.
an item is created, including from a formSet a priority and put it in the current sprint.
a due date is approachingRemind the assignee.
Automations are safe by design

A rule runs as its owner and can only do what that owner is allowed to do. Rules cannot trigger themselves in an endless loop.

Work-item templates

The project's Templates tab stores repeatable work, such as a release checklist or a site-visit routine. Create the work from a template instead of retyping it.

Timeline (Gantt)

Timeline shows the same work items as bars on a calendar, with the dependencies between them.

Red bars are on the critical path. Grey lines show the approved plan, so you can see slip at a glance.
  • Critical path. These items have no slack. If one is late, the whole project is late.
  • Reschedule with confidence. Move an item and the items that depend on it move too.
  • Baselines. Freeze the approved schedule as a baseline. From then on, the timeline shows how far each start and finish has slipped against it.
Moving a task never rewrites the baseline

A new baseline is an approved decision and goes through a change request. Day-to-day moves only change the live plan.

Products

Products lists the things the project must deliver, such as a trained team, an installed network, or a signed manual. Each product records its purpose, what it is made of, where it comes from, its quality criteria, and how quality will be checked. Work items and quality checklists can point to a product.

A product describes what you deliver. Work items describe how you get there. That is why they are kept separate.

Workload

Workload compares the team's capacity with the demand from assigned work, so you can spot overloaded people early. It also records each person's skills and cost rates.

Try "what if" safely

Create a named scenario to see how a different assignment would change the load. Real assignments stay as they are until you choose to apply the scenario.

Project docs

The project's Docs tab keeps meeting minutes, designs, and how-to notes next to the work. It uses the same editor as the company-wide Docs library.