0.2 Planning and Scheduling Professional Roles and Competencies

0.2 Planning and Scheduling Professional Roles and Competencies

AACE lists RP 14R-90, Required Skills and Knowledge of Planning and Scheduling, among the recommended references supporting the PSP Body of Knowledge. As a Recommended Practice, it is technical guidance. It does not by itself rewrite a project contract, dictate one organization chart, or establish legal entitlement.

Planning and scheduling are connected but distinct

Planning determines what will be delivered and how the work can be executed. It includes understanding contract requirements, stakeholders, scope, goals, phases, work packages, methods, constructability, resources, estimate assumptions, interfaces, and technological sequence. Planning asks questions such as:

• What products and acceptance conditions define completion?
• Which work methods and work faces are feasible?
• Who supplies information, materials, access, approvals, and labor?
• What sequence follows from physical, regulatory, and operational constraints?
• Which assumptions and risks could change the plan?

Scheduling represents the plan in time. It defines measurable activities and milestones, assigns durations and calendars, connects relationship endpoints, calculates dates and float, loads cost or resources when required, records status, analyzes paths, and forecasts future events. Scheduling cannot repair an incomplete execution strategy merely by linking bars. Conversely, a plan that never becomes a time-phased model cannot show whether the proposed sequence meets dates or resource limits.

The distinction is analytical, not a rigid personnel rule. On a small project, one person may plan, schedule, update, and report. On a large program, planners, schedulers, estimators, cost engineers, risk analysts, field teams, and controls managers may divide the work. The organization should define responsibility, review, and approval authority for each deliverable.

Competency is integrated

A competent planning and scheduling professional connects several bodies of knowledge:

1. Scope and structure: trace requirements through the WBS, organization, cost accounts, work packages, and schedule coding.
2. Methods and resources: understand how design, procurement, construction, testing, and turnover are actually performed and supported.
3. Network modeling: apply activities, milestones, durations, calendars, relationships, lags, and constraints with a documented basis.
4. CPM analysis: calculate or interpret early and late dates, total and free float, longest or controlling paths, and milestone variance.
5. Maintenance and control: status actual work to a data date, revise remaining work, preserve baseline history, manage change, and produce current forecasts.
6. Cost, resource, and risk integration: connect quantities, productivity, crews, cost, uncertainty, and recovery actions without treating any one indicator as the whole project truth.
7. Communication: tailor reports to the decision, explain assumptions and limitations, and write a concise recommendation that a stakeholder can act on.

Software skill supports these competencies but does not replace them. A scheduler must understand why a date moved, which calendar or relationship controls it, whether the remaining work is feasible, and what evidence supports status. A colorful Gantt chart can still be technically weak.

Professional judgment and governance

The schedule may become a contract-required record, an internal control model, or evidence used in a dispute, depending on the project. Do not claim that every schedule is automatically a legally binding document. First identify the governing documents, approved status, intended use, and decision authority.

Likewise, float use and ownership depend on the contract and applicable law. The professional calculates and explains float transparently, identifies artificial constraints or unsupported logic, and avoids turning a scheduling convention into a legal conclusion. When management requests an earlier completion date, report the current forecast and develop feasible recovery alternatives with the responsible teams. Do not force a desired answer by hiding logic, changing the data date, or entering unsupported durations.

Ethical communication

AACE certificants are subject to AACE’s Canons of Ethics. Applied to planning and scheduling, ethical conduct includes honest representation of qualifications, objective use of records, disclosure of material assumptions and limitations, protection of confidential information, and avoidance of misleading technical statements. If evidence is uncertain, label the uncertainty. If an instruction would produce a false or deceptive schedule, document the concern and use the project’s escalation process.

The PSP perspective is therefore broader than CPM arithmetic. It combines execution knowledge, model discipline, current status, reasoned forecasting, stakeholder communication, and professional judgment.

Applied review: connect the role to an output

For each planning and scheduling deliverable, define who prepares it, who supplies inputs, who performs technical review, who approves it, and who receives it. Then define the evidence of completion. A planner may facilitate a method workshop, a scheduler may construct the network, and a superintendent may validate production and sequence; those responsibilities can overlap, but the approval and accountability path should not be ambiguous.

Use competency evidence rather than titles alone. Ask whether the practitioner can trace a milestone to scope and logic, explain calendar and constraint effects, reconcile estimate assumptions, validate status, forecast remaining work, and communicate uncertainty. On an exam scenario, choose the response that keeps technical findings objective, discloses assumptions, seeks input from responsible experts, and stays within the professional’s authority.