Skip to content
Kairos OneBook a demo
Menu
Intermediate · 3 min read

Status and update a P6 schedule

Collect defensible actuals, reforecast remaining work, advance the data date, calculate, compare, and publish a complete update record.

Working definition

A professional update is a controlled evidence cycle. Start from the prior accepted native file, establish the reporting cutoff, collect field-verified actual starts and finishes, reforecast remaining durations and logic, record approved changes, run the schedule with controlled options, compare with the prior update and baseline, and publish the native file with its narrative and logs.

Version scope

Desktop P6 Professional workflow. Menu labels are aligned with Oracle’s current Version 26 help; older 24.x deployments may show minor wording or privilege differences.

Key takeaways

  • Begin from the prior accepted native file and a defined cutoff.
  • Record evidence-based actuals and reforecast remaining duration independently.
  • Publish the native file, schedule log, comparison, narrative, and change record together.
01

Status is not percent complete alone

For each activity, determine whether it started, finished, remains in progress, or has not started. Record actual dates, remaining duration, physical or units progress where applicable, and a current estimate of the remaining sequence. A percentage without remaining-time judgment does not produce a credible forecast.

02

Reconcile every class of change

Separate progress from revisions to logic, calendars, durations, scope, constraints, codes, and resources. The update narrative and change register should explain why each material edit occurred and whether it was approved.

Run a defensible periodic update

The order matters because advancing the data date before status collection can make errors harder to see.

Menu path: Project > Activities > Status, then Tools > Schedule (F9)

Before you start

  • Prior accepted native file
  • Approved reporting cutoff
  • Field status records
  • Change and delay registers
  • Controlled update layout

  1. Create the working copy

    Copy the prior accepted update into a controlled working location and record its checksum or source ID.

    Verify: The source file can be restored exactly.

  2. Collect and validate status

    Confirm actual starts, actual finishes, remaining durations, physical or units progress, suspensions, and forecast handoffs with responsible field staff.

    Verify: Each material actual date and progress claim has a supporting record.

  3. Enter actuals and remaining work

    Use Activity Details > Status and the controlled update layout to enter status without overwriting unrelated fields.

    Verify: Completed, in-progress, and not-started activities are internally consistent.

  4. Record authorized revisions

    Enter approved logic, calendar, duration, code, scope, or constraint changes and log each revision separately from progress.

    Verify: The change register reconciles to the edited fields.

  5. Advance the data date and schedule

    Set the approved cutoff, run F9 with controlled options, and save the log.

    Verify: No invalid progress remains on the wrong side of the data date without disposition.

  6. Compare and challenge

    Compare with the prior update and baseline; trace critical and near-critical path movement, float consumption, milestone variance, and new exceptions.

    Verify: Every material change is progress-driven, revision-driven, or explicitly unresolved.

  7. Publish the update package

    Retain the native file, XER if required, schedule log, narrative, change register, quality report, and approval disposition.

    Verify: A reviewer can reproduce the calculation and understand the period without private oral context.

    Field-ready control

    Monthly P6 update package

    • Prior accepted source preserved
    • Cutoff and data date match
    • Actuals supported
    • Remaining durations reforecast
    • Revisions separately logged
    • F9 options and log retained
    • Prior-update and baseline comparisons complete
    • Narrative reconciles to native file
    • Native submission and review disposition retained

    Common questions

    Should remaining duration be calculated from percent complete?

    Not by default. Remaining duration is a forecast of time still required. It should be informed by work remaining, productivity, resources, access, and calendar conditions.

    Sources and scope

    Follow the reference trail.

    This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.

    Updating ProjectsOracle · checked 2026-08-01Update progress for individual activitiesOracle · checked 2026-08-01Primavera P6 Professional User Guide, Version 26Oracle · checked 2026-08-01Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01