Planning is the connective tissue of every project discipline. Engineering deliverables, contract awards, interface handovers, construction packages, commissioning windows — none of it works in isolation. A good schedule is where they all meet, calibrated by standard strings, milestones, and S-curves that have been earned the hard way over many projects.
Most disciplines on a major capital project quietly resolve to the same handful of questions: when does this start, when does it finish, what does it depend on, and who else is waiting on it? That is a planning conversation — even when nobody calls it one.
The schedule will contain activities that look exactly like CPDS contract-development steps. It will contain milestones that mirror the interface register. It will carry the engineering deliverable cadence and the construction sequencing in the same place. Planning is the only discipline that touches all of them.
That is also why bad planning is so destructive. A weak schedule fragments the rest of the project's controls; a strong one stitches them together.
CPDS activities — contract development steps appear as a standard schedule string per major package.
Interface milestones — every entry in the interface register should map to a schedule milestone with a forecast date.
Engineering deliverables — IFR / IFC dates anchor procurement, vendor data, and construction.
Procurement & vendor data — PO award, mob, and certified VDR feed every downstream discipline.
Construction & commissioning — handover sequences, system-by-system, with their own milestone strings.
The single most under-used technique in capital project planning is the standard string: a reusable sequence of activities with consistent naming, consistent logic, and consistent calendars — but with durations tuned to the specific package. A pump skid, a pressure vessel, and a structural steel package all share the same string shape: SoW → ITT → Bid Eval → RFA → PO → Mob → IFC → Fab → Deliver. Only the durations change.
Comparable across packages — variance reads make sense because the activities are the same.
Faster planning — the planner replicates a string, not 40 individual activities.
Auditable — reviewers can challenge a duration without re-litigating the structure.
Activity codes drift over time — every package ends up with its own naming.
Durations get copied wholesale rather than tuned — strings become unrealistic.
Strings get hidden inside summary bars — the structure is there, but invisible to reviewers.
The CPDS app codifies the contract-development string — the durations to argue over, in one place.
The Interfaces app codifies the handover milestones that anchor every string to its neighbours.
The XER Reader lets you check whether the standard strings actually made it into the schedule.
A schedule with no milestones is a schedule no executive will read. Milestones turn thousands of activities into a sentence the rest of the project can quote. They also happen to be the natural meeting point between the schedule and the interface register — every interface handover should appear as a milestone, and vice versa.
An S-Curve is the integral of activity progress over time. Plotted alongside its baseline, it is the most compact and honest summary a project can produce. AACE RP 14R-90 and RP 29R-03 both rely on S-Curve reads as the first-pass diagnostic for whether a schedule is on plan.
TASKRSRC and calendar data.A schedule on its own only tells you where the project thinks it is. A variance report tells you where it has moved — and that's where the conversation with the planner becomes productive. AACE RP 29R-03 and RP 38R-06 treat baseline comparison as the foundational forensic technique.
AACE International is the authoritative source for planning, scheduling, and EVM Recommended Practices. The four below are the core reads.
Each of the other chapters in this Learn series has a planning shadow.
The XER Reader puts these concepts in front of you against an actual P6 export — WBS, S-curves, baseline variance, and logic checks, in your browser.