> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trybrink.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule

> Import P6 schedules, read them as a Gantt chart, and see exactly what moved between revisions

The **Schedule** page turns your Primavera P6 exports into a Gantt chart you can read without opening P6 — and, once you've uploaded more than one revision, into a record of what changed between them.

## Getting a schedule into Brink

Schedules come from **Primavera P6 XER exports**.

<Steps>
  <Step title="Pick the project">
    Set your active project first, from the project switcher in the top bar.
    Schedules belong to a project — that's what lets Brink diff each new export
    against that project's history.
  </Step>

  <Step title="Upload the XER">
    Go to the [Documents](/features/documents) page, click **Upload files**, and
    choose your `.xer` export. Brink recognises it and routes it into the
    schedule pipeline rather than the normal document flow.
  </Step>

  <Step title="Open the Schedule page">
    Your latest snapshot renders as a Gantt chart. Upload the next export the
    same way and it becomes the new latest snapshot, diffed against the one
    before it.
  </Step>
</Steps>

<Note>
  Re-uploading an export that's byte-for-byte identical to the previous one
  doesn't create a new snapshot — nothing changed, so there's nothing to diff.
</Note>

If nothing has been uploaded yet, the page reads: *"No schedule ingested yet. Upload a P6 XER export from the Documents page to see it here."*

## Reading the chart

Activities are grouped by **WBS**. Each row shows the activity's code and name on the left and its bar on the timeline, with the date range and either **critical** or its remaining float called out beside the bar.

The legend explains the colours:

| Swatch                  | Meaning                                                         |
| ----------------------- | --------------------------------------------------------------- |
| **Current**             | The activity as it stands in the latest export.                 |
| **Moved this revision** | This activity's dates changed since the previous export.        |
| **Critical (0 float)**  | The activity is on the critical path.                           |
| **Previous revision**   | The ghost bar — where this activity sat in the previous export. |
| **Today**               | Today's date marker.                                            |

<Tip>
  **Ghost bars are the point.** Once you have two or more exports, every
  activity that moved is drawn twice — once where it is now, once where it used
  to be. Slip is something you see rather than something you have to hunt for.
</Tip>

## Expand for the full picture

Click the chart, or the **Expand** button in the header, for a near-fullscreen view at a fixed day scale with a sticky activity column. Four summary cards sit above it:

* **Range** — the schedule's first start to its last finish
* **Span** — total days
* **WBS groups** — how many groups the schedule is broken into
* **Critical** — how many activities sit on the critical path

Press **Escape** or click the backdrop to close it.

## What changed between revisions

Each new export is compared against the previous one, and the differences are flagged as findings — worst first — and surfaced on your [Daily](/features/daily) page under **On the schedule**, as a banner reading *"schedule revision flagged — N findings (M high) in the export file"*.

Brink looks for:

| Finding              | What it means                                                                               |
| -------------------- | ------------------------------------------------------------------------------------------- |
| **Activity removed** | An activity in the previous export is gone from this one.                                   |
| **Activity added**   | An activity that wasn't there before.                                                       |
| **Dates shifted**    | The finish moved — with how many days, in which direction, and both dates.                  |
| **Duration changed** | The original duration grew or shrank, with the before and after.                            |
| **Float eroded**     | Total float fell, with the before and after.                                                |
| **Calendar swapped** | The activity was moved to a different calendar — the same work on a different working week. |
| **Lag changed**      | The lag on a logic tie was changed, including into negative lag.                            |

<Warning>
  Calendar swaps, shrunk durations, and negative lag are flagged **high** for a
  reason: they move a finish date without any activity visibly moving. They're
  the changes a Gantt chart alone won't show you.
</Warning>

## Schedule on the Daily page

The **On the schedule** section of the [Daily](/features/daily) page shows the activities landing in the day or week you're looking at, each tagged **Schedule** with its project, WBS, and finish date, flagged **critical** or with its remaining float — along with the revision banners described above.

## Which day is "today"?

Schedule days follow the **jobsite's** calendar, not your browser's. That comes from the [project's site timezone](/workspace/projects#site-timezone), falling back to your [organization's default](/workspace/organizations#timezone). When the two differ, a **Site time: …** badge appears in the page header so you know which clock the days are being counted on.

## Asking about the schedule

Schedule data is part of your company brain, so you can ask about it directly in [Chat](/features/assistant):

* *"Which activities slipped in the latest schedule revision?"*
* *"What's on the critical path in the next 30 days?"*
* *"Show me activities with negative float"*