3.6 Stakeholder Feedback and Types of Schedules

3.6 Stakeholder Feedback and Types of Schedules

The schedule converts a cross-functional plan into dates. Stakeholder feedback supplies information no single planner can own: engineering release strategy, vendor lead time, field means and methods, owner access, permit status, test sequence, resource availability, and acceptance criteria.

Structured feedback

Use workshops and review cycles with defined inputs. Ask each discipline to validate:

• scope and activity list;
• physical and preferential logic;
• quantities, production rates, and durations;
• calendars, shifts, and access;
• resource availability and shared constraints;
• milestones and handoffs;
• risks, assumptions, and opportunities; and
• reporting and acceptance needs.

Record comment, disposition, owner, and date. A workshop does not authorize an undocumented scope or baseline change.

Types by purpose

These products can coexist. The hierarchy should define which model calculates dates and how summaries roll up.

Do not confuse type with format

A Gantt/bar chart is a display of activities over time. It may present a CPM model or a simple list with no logic. A network diagram displays relationships. CPM is a calculation method. “Level 2” or “Level 3” describes relative detail under an adopted classification, not a universal file type.

An executive milestone view can be generated from the same CPM source as a detailed control report. Manually retyping milestone dates into slides breaks traceability and can leave leadership viewing stale forecasts.

Select fit-for-purpose detail

The right level supports the decision and update cycle. A five-year master schedule should not contain every daily crew task, while a two-week lookahead needs readiness detail that the control schedule may not. The lookahead should reconcile to the control schedule unless an approved field change is being processed.

Feedback during updates

During execution, field, vendor, designer, owner, and commissioning feedback updates actual status and remaining plan. Validate actual dates and independently estimate remaining duration. Distinguish:

• actual progress;
• revised execution logic;
• approved scope change;
• proposed recovery; and
• stakeholder target.

Mixing them can make the current schedule appear on time by rewriting history.

Example

The control schedule shows equipment delivery, installation, testing, and turnover. Procurement maintains detailed vendor steps; commissioning maintains test procedures; the executive report shows only delivery and operational milestones. All three products should share the same current interface dates. If the vendor schedule slips, the change flows through the control schedule before the executive summary is updated.

Quality questions

• Does each product have a defined purpose and owner?
• Are data dates and source models identified?
• Can every summary date be traced to detailed logic?
• Are near-term plans consistent with remaining durations and constraints?
• Is stakeholder feedback documented and dispositioned?

Good schedule architecture provides different views of one integrated plan rather than competing versions of the truth.

Applied review: select the model for the decision

Schedule type and level should follow purpose. A milestone schedule communicates key commitments. A summary schedule supports management decisions across phases or packages. A control schedule coordinates measurable work and interfaces. A detailed short-term schedule supports field execution. These views should reconcile to a controlled source, but they need not show identical granularity. Adding thousands of activities does not make a schedule more useful if the audience cannot act on the information.

Stakeholder feedback helps define both content and presentation. Ask what decisions the user makes, how often information changes, what lead time is needed, and which exceptions require escalation. Translate valid needs into coding, milestones, reports, or detail. Reject requests that would create conflicting status, duplicate models, or misleading precision, and explain the alternative that preserves control.

Feedback continues after issue. Track whether reports reveal the intended trends and whether field teams can update the selected detail reliably. If a detailed model cannot be statused with objective evidence, reconsider the decomposition or progress rules. In exam questions, match the schedule to its decision horizon and audience while preserving traceability. A presentation view may filter and summarize; it should not rewrite actual dates or omit a material driver simply to create a favorable picture.