Horizontal Schedule Integration
EVM Terms
Reviewed by forProject Technology - updated Sep 2026
Quick definition: Horizontal Schedule Integration means Work Packages and tasks are logically sequenced and linked to their interdependencies across the same level of the schedule, including hand-offs between different teams.
Horizontal integration focuses on how Work Packages, Planning Packages, and lower-level tasks connect to one another through dependencies and constraints — including "hand-offs" of products between different Integrated Product Teams. This logical linking lets a schedule show how a delay in one task will ripple forward into the tasks and milestones that depend on it.
Why it matters
Without horizontal integration, a schedule is just a list of dates rather than a true network schedule — it can't show how a slip in one area will actually impact downstream work. Because it captures these cross-team hand-offs and dependencies, it's essential for realistically forecasting schedule impacts across an Integrated Master Schedule.
Also known as
N/A
Used in
Integrated Master Schedule development and analysis; evaluating schedule impacts across Integrated Product Teams
See also
FAQ
How is Horizontal Schedule Integration different from Vertical Schedule Integration?
Horizontal integration links dependencies across work at the same level, including across different teams; Vertical Schedule Integration ties schedule detail consistently up and down between summary and detailed levels.
Why does Horizontal Schedule Integration matter for teams working on different parts of a project?
It captures the "hand-offs" between Integrated Product Teams, so a schedule can show how a delay in one team's deliverable will impact the team waiting to receive it.
Definition maintained by forProject Technology.
© 2026 forProject Technology, Inc.
© 2026 forProject Technology, Inc.
