Skip to content
Search

How baselines work

A baseline is a copy of the items a list or a Gantt showed when the baseline was captured. For each item it keeps the type, the parent, the title and the value of every number, date and tracked-time field. After capture, only the name of a baseline can change. Later edits to the items never reach the copy, so it keeps showing the plan as it was.

A capture takes the items the view shows at that moment, after its filters. It holds up to 10,000 items. That limit also counts the sub-items a capture keeps but the view does not show. The new baseline is named with a number and the date of the capture.

A Gantt inside an item’s page has no saved view of its own. Its baseline is recorded against that item, and the list marks it Item.

The baseline is shared. Everyone allowed to read baselines can compare against it. Which baseline a person compares against is that person’s own choice, kept for this view in this browser. Two people on one view can compare against different baselines.

  • The finish alone decides the color. An item that starts later but finishes on the same day is on plan.
  • Distances are counted in calendar days, not working days.
  • A red or green end on the ghost covers how far the finish moved.
  • An item with no finish date, now or in the baseline, is shown as on plan.
  • The comparison reads the Gantt’s date fields as they are set now. Change those fields, and the ghosts move to the values the new fields had at capture. This works because a baseline keeps every date value.
  • A parent’s ghost covers what its items spanned at capture, under the parents they had then.

Pointing at a ghost also lists other changes: the fields that changed, a new parent and a new type.

The baseline columns and the change tags read the same copy the ghosts show. Every number, date and tracked-time field has a Baseline · ‹field› column and a Δ ‹field› column, in a list and in a Gantt table.

  • A parent’s baseline value is its own captured value when it has one. Otherwise it comes from its captured sub-items, by the same rule that gives the live value.
  • A tracked-time baseline adds the item’s own time to the time below it, as the live cell does.
  • In a view nested with Tree by, each baseline value is the item’s own captured value, and tracked time shows no delta.
  • A date delta counts calendar days from the baseline to the live date. A positive number means later.
  • A change tag sits right after the value. In a number or tracked-time column every row keeps the same space for it at the end, so the values stay lined up. A later date, and more tracked time, Duration or Estimate, is amber; earlier or less is green. Any other number is gray. A cell showing a rolled-down value gets no tag.
  • An added item has no value in these columns.

A capture stores only number, date and tracked-time values. A change to any other field, such as a status, is not compared. A capture can also hold sub-items the view did not show, only so a parent’s value can be worked out. They are never counted as added or removed.

Formulas, filters and cards cannot read these values. They show one value per item for everyone, and the baseline is each person’s own choice.

An item the view shows now but the baseline does not hold is added. It is drawn blue, with a sparkle icon by its title.

An item the baseline holds but the view no longer shows is removed. It has no row. The Baseline page names it with one of two reasons: deleted, or no longer in this view, for example because a filter now hides it.

Under the list, the Baseline page counts what slipped, came in early, stayed on plan, was added and was removed. It names up to eight of the removed items.

The list offers the baselines that belong to this part of your organization:

  • baselines from this view, and from the other views in its project, where the project is the nearest folder above the view in the sidebar;
  • item baselines whose item the page belongs to, or whose item holds everything the view shows. A view across several projects, such as a portfolio, offers no project’s item baselines: each holds one project, so every other project would show as added. Capture a baseline from that view instead.

Other baselines stay reachable through the search field above the list, which shows at most 20 matches. The baseline you compare against always stays in the list, marked with a check. Most of the time it sits in its usual group. A baseline the list would otherwise leave out, such as one found through the search, sits under Comparing against at the top instead.

An item baseline whose item was deleted shows Root item deleted. Nobody can compare against it until the item is restored from the trash.

In the roles every organization starts with, Administrator and Collaborator can capture and compare. Reader can compare, but not capture. A custom role gets the same choices from its baseline permissions. See Roles and permissions.

Only the person who captured a baseline, or an Administrator, can rename or delete it. Deleting a baseline stops the comparison for everyone using it.

The dates are in March 2026. Build is captured from Monday 9 to Friday 13 March. Later, its finish moves to Wednesday 18 March.

  1. Compare against the baseline. The Build bar turns red.
  2. Under the bar, the gray ghost covers 9 to 13 March. A red end runs from 13 to 18 March.
  3. Point at the ghost. It shows both date ranges and finish +5 calendar days.