What are projects and campaigns?

A project is a named body of work inside one team, with a lead, dates, and tasks under it. A campaign sits above projects and spans teams. If What are tasks? answers "what am I doing today", this section answers "what are we working towards".

Projects live in the Work area of the menu, under Work › Departments and then the team they belong to. Campaigns come together on Work › Roadmap.

Fairgreen Golf Co. runs a campaign called Autumn drop. Under it sit a Marketing project for the shoot and the emails, and a Production project for the sampling and the factory dates.

What does a project give you that a task list does not?

Four things, each the answer to a question somebody asks in a Monday meeting.

• A lead. One named person accountable, set separately from who is assigned the tasks.
• Dates. A Start and a Target, which is what puts the project on the roadmap as a bar.
• Milestones. Dated checkpoints inside the project, so "samples approved" is visible without being somebody's to-do.
• Progress. A live count of scope against completed, with a percentage bar and open-task counts per person, worked out from the tasks and their subtasks rather than typed in.

A project also gets its own Overview, List, Board and Calendar tabs, so the team working in it has everything in one place.

Why does a campaign exist above that?

Because the work of a launch does not sit in one team, and no single project can hold it.

The Autumn drop needs Marketing, Production and Warehouse. Each of those wants its own project with its own lead and its own board, and the person running the launch needs to see all three on one timeline.

That is what a campaign is: the band across the roadmap that the separate projects hang from. A project points at one campaign, and a campaign spans as many teams as it needs. Your workspace may use its own word for a campaign; Settings › Terminology shows both.

When would you use each one?

Start a project when a piece of work has several tasks, a person accountable for it, and an end. "Autumn lookbook shoot" is a project. "Book the studio" is a task inside it.

Start a campaign when two or more teams are working towards the same date. When only one team is involved, a project on its own is enough.

Use a cycle when you want a stretch of time rather than a body of work. A cycle is a named, dated container that cuts across every team and project at once, which is a different shape from both. See How to set up and work in cycles.

What is something else better for?

• Work that comes round again, like a weekly stock count, is a repeating task rather than a project. See How to make a task repeat.
• A thing you are tracking rather than a body of work you are doing is a record. See What is an Object?.
• A plan of what goes out and when, before any of it is real work, lives on a project's Overview as planned items. See How to plan what goes out and when.

Read this section in order

How to start a project is the place to begin, and covers the properties that matter on day one. How to add and reschedule milestones adds the checkpoints, and How to plan what goes out and when lays out what the project will publish or ship.

How to set up a campaign is worth reading once you have more than one team working towards a date. How to use the roadmap is where all of it comes together on one timeline, and it is the screen most people end up living in.

How to set up and work in cycles covers the fortnightly rhythm that runs across all of it. When a project is finished, How to archive, restore or delete a project covers putting it away.