Skip to content
Kairos OneBook a demo
Menu
Advanced · 2 min read

Baseline review and acceptance playbook

Gate scope, logic, calendars, durations, contract dates, resources, quality, narrative, and approval before freezing the plan of record.

Working definition

Baseline acceptance is a decision workflow, not a schedule-health score. The reviewer first establishes submission completeness and lineage, then tests contract alignment, scope coverage, execution logic, duration and calendar basis, resource feasibility, calculation settings, and quality exceptions. Comments are resolved with evidence before the approved native file is frozen and assigned.

Key takeaways

  • Review schedule inputs before relying on calculated outputs.
  • Resolve comments against the native file and cited evidence.
  • Freeze the exact accepted file and preserve the full decision trail.
01

Review in dependency order

Do not start with float thresholds. Confirm file identity and contract dates, then scope and WBS, calendars and durations, logic and constraints, resources and risk, and only then calculated paths and quality metrics. Downstream metrics are not trustworthy when upstream inputs are wrong.

02

Acceptance needs a durable record

Retain the submission, checks, comments, responses, revisions, meeting decisions, final native file, schedule log, basis memorandum, and formal disposition. Make clear whether the action is approval, acceptance, no objection, or review only under the contract.

Run a controlled baseline acceptance

Separate completeness, technical credibility, and contractual disposition into explicit gates.

Before you start

    1. Intake and preserve

      Record project ID, filename, native format, checksum, submission date, version, data date, narrative, basis, reports, and required attachments.

      Verify: The exact submission can be reproduced.

    2. Check contract and scope

      Reconcile milestones, calendars, WBS, deliverables, procurement, submittals, testing, commissioning, turnover, and closeout.

      Verify: All required scope and dates are represented.

    3. Review the model

      Evaluate durations, resources, logic, lags, constraints, codes, options, float, longest and near-critical paths, and schedule risk.

      Verify: The plan is buildable and calculation settings are disclosed.

    4. Issue and resolve comments

      Tie each comment to an activity, field, clause, source, required action, owner, and status.

      Verify: Every closed comment has evidence in the revised native file or an accepted disposition.

    5. Approve and freeze

      Issue the contractual disposition, retain the final package, create and assign the P6 baseline, and restrict changes.

      Verify: Displayed baseline dates reconcile to the exact accepted file.

      Field-ready control

      Baseline acceptance gate

      • Complete native submission
      • Contract milestones reconciled
      • Full lifecycle scope
      • Calendar and duration basis
      • Complete defensible logic
      • Constraints and options disclosed
      • Resources and risk addressed
      • Quality exceptions dispositioned
      • Comments closed with evidence
      • Exact approved file frozen and assigned

      Common questions

      Does acceptance mean the owner guarantees the contractor’s means and methods?

      The contractual meaning depends on the agreement. The disposition should be worded consistently with the contract and should not imply a responsibility transfer that was not intended.

      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.

      Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01UFGS 01 32 01.00 10: Project ScheduleWhole Building Design Guide / U.S. Department of Defense · checked 2026-08-01Recommended PracticesAACE International · checked 2026-08-01