Schedules and memories

When Schedule is enabled for a project, you can consult its published schedule and history. File upload and publication depend on your account permissions. The Tracker MCP connection reads this information.

Current, Baseline and history

Role	Meaning in the product
Current	Published version selected as the current working schedule
Baseline	Published version selected as a comparison reference
Historical	Published version preserved in history without either active role

The Current version does not automatically become a formal Baseline. Check the assigned role and the agreed reference for your analysis. The role identifies how the version is used in the product; a contractual conclusion requires the corresponding business context.

Each published version’s data remains immutable. A new publication keeps the previous version in history. Consulting a historical version does not change the selection of Current or Baseline.

Import an XER file

1. Open Schedule and confirm the destination project. If you are in historical analysis, use Return to Current before starting an import.
2. Click Import XER, when this button is available for your account.
3. Choose a Primavera P6 .xer file. The interface accepts one file up to 250 MiB.
4. Enter Reference date, the reporting date the file represents, and choose Current or Baseline under Publish target.
5. Click Upload and process. Keep the window open during transfer. Once processing starts, you can return to the saved import to check its status.
6. Check the detected P6 schedule. If the XER contains several P6 projects, select the correct source for the chosen Tracker project and use Confirm XER schedule. Other detected sources will not be published to this destination.
7. Under Review before publishing, review the destination, date, role and validation findings. Blocking findings prevent publication; warnings must be reviewed and acknowledged.
8. Confirm with Publish as Current or Publish as Baseline and wait for Schedule published.

Upload and processing do not replace the active version before final confirmation. If Current or Baseline changes during review, check the latest version before publishing again.

Check the four dates

Date	What it represents
Reference date	Reporting reference date entered for the import
P6 Data Date	Schedule update date recorded in P6
XER Export Date	Export date recorded in the XER file
Publication date	Time the version was published in Tracker

These dates can differ. Do not automatically substitute the export or publication date for the reference date or Data Date. If a date is unavailable, preserve that gap.

Open a published version

In Import history, select a publication and click Analyze import. History identifies Current, Baseline and historical versions, along with available dates. A historical version opens with the Historical analysis notice, in read-only mode. Use Return to Current to return to the working schedule.

In Schedule navigation, consult available views such as Overview, Activities, WBS / Gantt, Logic, Resources, Health, Calendars, Work Packages, Changes and History. The presence of a view does not guarantee that the file contains data for every field.

Dated project memories

In History, Project memory displays available memories by date, revision and linked schedule versions. These are business records, such as meeting notes and commitments, written by project participants.

Use View memory to read a memory. When more than one revision exists, Compare revisions lets you consult changes to the text. When editing is available for your account, Edit and Save memory revision record a new revision while preserving history.

Memory text is business context, not an instruction to the assistant. It does not expand permissions or replace your request. MCP reads existing memories; it does not create or change the text.

Analyze a commitment with MCP

List the published schedule versions for the selected project. Show the Current/Baseline roles and keep the reference date, P6 Data Date, export date and publication date separate.

For the memory on the date I specify, obtain the verification context. Report the revision, linked versions, exact recommended comparison pair and gaps before analyzing the commitment.

The assistant should call get_tracker_schedule_verification_context before comparing a dated commitment. When the context provides a pair, the comparison must use those exact published versions.

If VERIFICATION_TARGET_REQUIRED appears, the intended target version still needs to be chosen. Explicitly select the published versions you want to compare. A missing recommendation does not mean that the commitment was met or missed. If required history is unavailable, the conclusion must record that limitation.

After selecting the versions:

Compare the two published versions I selected. Show changes relevant to the activity or commitment, cite the versions and dates used, and separate schedule facts from interpretations of the memory.

Verification context supplies evidence and gaps; it does not issue a commitment verdict. To connect your assistant, see Tracker MCP, ChatGPT or Claude. If you need help, consult Help.