Whether a baseline is approved, accepted, or deemed accepted, and what that status means, depends on the governing contract and law. This guide is technical education, not legal advice.
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.
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.
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.
Implied acceptance of a baseline schedule
Implied or deemed acceptance describes a baseline treated as accepted without a written approval. Deemed acceptance usually comes from contract wording, such as a stated review period after which a submission is treated as accepted. Implied acceptance is argued from conduct, such as both parties measuring progress, pricing changes, or processing payment against the submitted schedule for months without objection.
Whether a baseline was accepted, and what acceptance means, depends on the contract terms and the governing law. Before the review starts, the owner-side team should know what its contract says about review periods, the effect of silence, any link between progress payment and an accepted schedule, and whether review or acceptance shifts responsibility.
The practical risk is an unclear record. Teams commonly reduce it by responding within the review period even when the review is incomplete, issuing a written disposition against the exact revision, stating in writing when an unaccepted schedule is used only for interim reporting, and making sure payment processing does not by itself signal acceptance.
This section is general information about schedule-review practice, not legal advice. The effect of silence, use, or payment on a baseline depends on your contract terms and the governing law; ask your contract administrator or counsel how they apply to your project.
Run a controlled baseline acceptance
Separate completeness, technical credibility, and contractual disposition into explicit gates.
Before you start
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.
Check contract and scope
Reconcile milestones, calendars, WBS, deliverables, procurement, submittals, testing, commissioning, turnover, and closeout.
Verify: All required scope and dates are represented.
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.
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.
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.
Can a baseline schedule be accepted without a written approval?
Some contracts treat a submission as accepted if no response is made within a stated period, and acceptance is sometimes argued from the parties’ conduct. The answer depends on the contract and the governing law, which is why the review record should show a timely written disposition on the exact revision.
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