On this page
A baseline submission establishes the reference plan the team intends to manage against. Its value comes from an understandable sequence, credible assumptions and a clear submission history. A large activity count or attractive Gantt chart cannot substitute for those things.
Begin with the governing requirements
Create a requirement register before building the transmittal. Record the incorporated specification and edition, amendments, milestone dates, required file format, software requirements, narrative contents and review process. For a deadline, capture its starting event and whether its units are business, working or calendar days.
“Due after notice” is not precise enough. Identify which notice, who received it and the recorded receipt date. Confirm the contractual counting convention rather than applying a familiar deadline from another project.
- 01PreserveOriginal file + issue date
- 02CorroborateDaily records + notices
- 03ExplainCause + affected work
- 04ReviewAssumptions + decisions
Assemble one coherent package
| Package item | What the reviewer should be able to establish |
|---|---|
| Native schedule and requested exports | Which network and version produced the submission |
| Narrative | How the team intends to build the job and what assumptions remain |
| Calendar and settings record | When work can happen and how the schedule was calculated |
| Milestone and interface list | Which handoffs, access dates and approvals matter |
| Assumption and exception register | Which inputs need confirmation or acceptance |
| Transmittal and revision index | When the package was sent and what changed |
The GAO Schedule Assessment Guide is a useful reference for assessing schedule quality. Its guidance helps structure a review; the submission obligations still come from the project’s governing documents.
Test the construction story
Walk the plan with the superintendent and trade leads. Does procurement precede installation? Is time available for review and resubmission? Are temporary works, testing, commissioning and turnover visible? Do crew assumptions match the planned work fronts?
For a fictional equipment package, an installation activity alone is insufficient. The plan may need design release, submittal review, fabrication, delivery, access preparation, installation, testing and energization. The specific decomposition should follow the project, not a universal template.
Check that the completion milestone is driven by the intended scope. A disconnected closeout activity can disappear from the apparent critical path even though the owner requires it before handover.
Keep acceptance and revision distinct
Record the review status exactly: submitted, returned with comments, revised, accepted or another status defined by the project. Preserve the response and the version it addresses. Do not describe a submission as accepted merely because it was uploaded.
When responding to comments, provide a disposition register with the action taken, affected activity IDs and any explanation for an unchanged item. Retain prior versions so later variance reporting has a trustworthy reference.
Next, prepare the monthly narrative and follow the audit checklist. The resource library connects baseline preparation to ongoing project controls and the os.construction workflow.
Share this article