Make dependencies visible early

Coordination sequence, not a permit procedure

When work packages share people, access, services, suppliers, or timing, record the dependency in the authorized system and identify the owner roles that need to coordinate. A coordination note is not a permit, authorization, or substitute for an approved local requirement.

For permit, safety-critical, regulated, or site-specific questions, consult the applicable approved local reference and route unresolved questions to the designated trained role.

Coordinate an interface

Use the local authorized process for records and decisions

  1. 1

    Identify affected parties

    Name the work packages, area owner roles, suppliers, and shifts that share the dependency.

  2. 2

    Record the dependency

    Enter the coordination detail in the authorized system of record, not only in an informal note or this example site.

  3. 3

    Consult the approved local reference

    Use the applicable, current local permit or other controlled reference for requirements; this page does not state those requirements.

  4. 4

    Hand off unresolved questions

    Take open questions to the designated trained role or decision owner through the local escalation route.

Completed fictional interface example

A coordination dependency example, not a permit record or work authorization.

Dependency Affected roles Planning handoff Open question route
A supplier delivery and maintenance work are planned around the same shared access window. Maintenance planner; supplier coordinator; area operations lead The shutdown coordinator records the timing dependency in the authorized planning system and brings affected roles into the interface review. Permit or site-specific questions go to the designated local trained role using the approved local reference.