Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / The update cycle: checks, narrative, review and submittals

The update cycle: checks, narrative, review and submittals

Run each schedule update as a reviewed period. Open it at a new data date, record progress, run eight update checks, write the narrative, route it through multi-step review, accept the update of record and send a schedule submittal package.

On this page

Most contracts ask for a schedule update every month: progress to a new data date, a narrative, and a file the owner’s scheduler can review. The Updates page (Schedule › Update › Updates) runs that cycle as one reviewed record per update period. An accepted update becomes the update of record, a fixed point that later forensic analysis can rely on.

Every step needs Schedule admin on the project.

The cycle

Schedule update status flowAn update is Open while progress is recorded and checks run. Submit for review moves it to Submitted. A reviewer can request a revision, which moves it to Revision requested; the scheduler re-runs the checks and submits it again. The final approval moves it to Approved, the update of record. Open, Submitted and Revision requested updates can be withdrawn with a reason.submitapproverequest revisionresubmitOpenSchedulerSubmittedReviewersApprovedUpdate of recordRevision requestedWithdrawn
Schedule update statuses in the app

An update can also be withdrawn, with a reason, at any point before approval. Only one update can be in progress (open, submitted or revision requested) on a project at a time.

  1. Open update. Choose the new data date. It can’t be earlier than the current data date, and it must be later than the last update that wasn’t withdrawn. The name defaults to Update N · date. Baseline for slip defaults to the same baseline as the previous update. Opening drafts a new version from the current plan.
  2. Record progress. Use the Planner, where Progress Spotlight and Update Progress can fill the period in as planned for you to correct, Field progress (from daily logs) or the touch view. The period length is up to you. Monthly is typical, but nothing enforces an interval.
  3. Run the checks. The eight update checks run against the plan as it stands. Each check passes, warns, fails or is skipped, and lists up to 200 activities. The evidence is stored with a digest.
  4. Write the narrative. Fill the six sections. Fill empty from checks and Replace with draft start you off from the check evidence.
  5. Submit for review. Choose reviewers or a workflow template. You must submit with the latest check run, on a plan that hasn’t changed since. Failed checks block submission unless you acknowledge them.
  6. Review. Reviewers compare the submission with the previous accepted update, comment, and respond.
  7. Accept. The final approval makes the submission the update of record. It can’t be changed afterwards.

Once an update is approved, the Updates page offers Store period performance. It records the accepted version’s actual units and cost into a financial period that ended by the update’s data date. See Period performance and earned value.

The eight update checks

Check What it looks for
DCMA 14-point health The health assessment on the updated plan.
Out-of-sequence progress Work started before its predecessors allow.
Actuals after the data date Actual dates recorded in the future.
Progress not reported Activities the previous accepted update forecast to start by this data date that report no actual start. Skipped on the first update.
Changes since the last accepted update Logic, duration, constraint and calendar edits.
Baseline slip Finish movement against the chosen baseline. It fails above 30 calendar days by default.
Critical path change Activities joining or leaving the critical path.
Float erosion Activities that lost float, from 5 working days by default.

The narrative

Six sections, each required and up to 20,000 characters: Critical path, Progress this period, Delays and slippage, Schedule changes, Risks and float and Mitigation and recovery. The narrative is frozen with each submission, so a revision round never rewrites what a reviewer already read. If the schedule assistant is turned on, it can also draft a narrative from the saved data for you to edit.

Review

  • Reviewers: up to 25, each with a group number and a role. Approvers decide. Reviewers (informational) can comment but never decide. At least one approver is required. Groups proceed in sequence, so you can run the project team’s review before the owner’s. You can also start from a workflow template.
  • Reviewers must be active project members with Schedule admin. Nobody can review their own submission.
  • Compare. The review page compares the submission with the previous accepted update, or with the baseline for the first update. It’s sorted into logic, duration, constraint, calendar and progress changes, retroactive changes to actual dates, and added and removed activities.
  • Comments can be general or pinned to an activity (up to 4,000 characters), and can be resolved. Everyone involved is notified, and every transition is audited.
  • Respond with Approve, Approve as noted or Request revision. A revision request needs a comment.

Forensic series

Accepted updates of record form a forensic series ordered by data date. From the Updates page, Windows analysis → opens Schedule › Analyze › Forensics with the last 12 updates as windows, so the delay analysis runs on exactly what was accepted, not on whatever versions happened to be saved.

Modified or recreated updates (MIP 3.5)

When the updates of record can’t be used as they are, for example because progress was never statused or logic was missing, choose the modified or recreated method. It runs the same bifurcated windows as MIP 3.4 over updates you supply. For each one you declare its provenance (contemporaneous, modified by the analyst or recreated by the analyst) and keep a modification register: what changed, before and after, the authority that permits it, and why. The register is part of the report and its evidence manifest. The tool doesn’t recreate an update for you; you supply the recreated version. See windows analysis.

Pacing

In a concurrency analysis you can add pacing claims: one delay (the paced delay) was a deliberate response to another (the parent). Test 1 is computed from the chronology and, when you name both activities, their relative total float in an optional context version. Tests 2 and 3, including contemporaneous evidence of intent, are your evidence. The analysis records the tests and doesn’t produce a verdict. See pacing.

Prospective time impact analysis

A what-if impact on a change event is a quick estimate. A formal time extension request uses a prospective TIA with owner review, under AACE RP 52R-06. Open Schedule › Analyze › Forensics › Prospective time impact analysis.

  1. Submit a fragnet. A Schedule admin (with edit access to the change event, when one is linked) describes the delay events: duration, the activity each delays, optional onset, stated responsibility, basis and source documents, plus any extra links and a narrative of every change made to the update. Choose the contract’s time unit (work or calendar days) and list dates already awarded. The fragnet goes into the update in effect: the last approved update period statused on or before the delay start. It’s refused if no approved update qualifies, or if it names activities that aren’t in that update.
  2. Review. Another Schedule admin, acting as the owner’s reviewer, records a review note. Nobody can review their own submission.
  3. Decide. The reviewer accepts the fragnet, or rejects it with a reason. A rejected fragnet is resubmitted as a new analysis.
  4. Analyse. Only an accepted fragnet is analysed, on the update in effect and the later approved updates. The report is kept, immutable, with its evidence manifest and linked to the analysis. Large networks run as a background job. If the standard refuses the analysis, the refusal is reported by category and nothing is kept.

The fragnet and every submitted input are fixed once submitted, review and decision are final, and the history is append-only. Every step is audited on the analysis and on the linked change event. A prospective TIA isn’t one of the RP 29R-03 methods of implementation, so its report carries no MIP, and it says that entitlement is a question for the contract.

Schedule submittal packages

A schedule submittal packages an update or a baseline for the owner. It’s a separate record from construction submittals.

  1. Build package. Choose the subject: a submitted or approved update (the latest round or a chosen one), or a named baseline. Choose P6 XER, P6 XML or both, and add an optional cover note.
  2. Check the files. An update package holds the export, the narrative, a health-and-checks summary and a compare CSV. A baseline package holds the export, the cover note, a health summary and a compare against the previous baseline. Every file is pinned to one version, can’t be changed afterwards, and carries a SHA-256 digest.
  3. Distribute. Send it once, by email through the Emails tool, to project users and external addresses (up to 50 of each in To and CC). Recipients get sign-in download links. To resubmit, build a new package.
  4. Record the response. Enter Approved, Approved as noted, Revise and resubmit or Rejected, the response date and notes. A response is recorded once.
  • Mistake: Editing the plan after running the checks

    In the app: Submission needs the latest check run on an unchanged plan. Re-run the checks after any edit.

  • Mistake: Acknowledging failed checks without explaining them

    In the app: Use the narrative’s Schedule changes and Delays sections to say why each failure is acceptable.

  • Mistake: Distributing a package, then editing the narrative

    In the app: Packages are immutable and sent once. Build a new package from the revised submission.

Limits

  • The prospective TIA doesn’t re-status an update for you. Supply the re-statused update as an approved update period.
  • The owner’s reviewer is any other Schedule admin; there’s no separate owner role yet.
  • An accepted TIA’s days aren’t carried to the change order automatically.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file