Planning Interlock

What is a Planning Interlock?

A planning interlock is an explicit agreement between teams, made during planning, about the work one team will do for another and when. It turns hidden cross-team dependencies into written commitments that both sides sign up to.

Updated November 2026 · 2 min read


How interlocks work

In large organizations, few goals can be met by one team alone. A product launch may need work from platform, security, legal and marketing. During planning, the team that needs something asks the team that can provide it. If both agree, they record an interlock: what will be delivered, by when, and who owns it on each side. The term is widely used in large technology companies, often alongside OKRs.

ElementWhat it recordsExample
Requesting teamWho needs the workMobile app team
Providing teamWho will do itIdentity platform team
CommitmentWhat exactly will be deliveredPasskey sign-in API, production-ready
DateWhen it is needed and promisedEnd of week 6
OwnersA named person on each sideTwo engineering managers
StatusAgreed, at risk, delivered or droppedAgreed

Interlocks vs dependencies

A dependency is a fact: team A needs something from team B. An interlock is a decision about that dependency: team B has agreed to provide it, with a date. Unmanaged dependencies cause surprises late in the quarter. Interlocks force the conversation early, during planning, while it is still possible to change scope or timing. They are a practical form of dependency management.

An example

During quarterly planning, a payments team lists five things it needs from other teams. Three providing teams agree and record interlocks. The fourth, data engineering, says it has no capacity this quarter, so the payments team drops the related key result instead of discovering the gap in week 10. The fifth request goes to the quarterly planning review, where leaders decide which team's priorities give way. At each OKR check-in, both teams update the status of their interlocks.

Making interlocks work

  • Collect requests before planning so providing teams can size them
  • Require a yes or a no; "we'll try" is not an interlock
  • Count accepted interlocks against the providing team's capacity
  • Track them in one shared place, visible to both sides and to leaders
  • Review interlock status at regular syncs and escalate early when one slips

Interlocks at scale

In a company with hundreds of teams, interlocks can number in the thousands each quarter. Most organizations keep them manageable by only recording interlocks above a size threshold, grouping them by program, and reviewing the riskiest ones in the operating rhythm rather than all of them. A simple view of who depends on whom also shows which teams are overloaded with requests.

Common pitfalls

Interlocks fail when providing teams accept every request to avoid conflict, then miss most of them. They also fail when the list grows so long that no one reviews it. A high number of interlocks can be a sign that teams are not organized around the work, which Team Topologies and similar approaches try to address. In SAFe, the same need is met during big room planning, where dependencies are drawn on a program board.

Frequently asked questions

What does interlock mean in planning?

An interlock is a commitment between two teams, agreed during planning, that one will deliver specific work the other depends on, by a set date. It records what is needed, who provides it, when, and who owns it on each side. The word is common in large technology companies that plan quarterly.

How are interlocks different from OKRs?

OKRs describe what a team wants to achieve. Interlocks describe what a team needs from others to achieve it, and what it has promised in return. Many organizations link the two: a key result is only accepted if the interlocks it depends on are agreed. Both are reviewed at the same OKR check-ins.

What happens when an interlock is missed?

The requesting team should hear about it as early as possible, ideally at a regular sync rather than at the deadline. Both teams then agree a recovery plan, a smaller scope or a new date. If they cannot agree, the issue goes to the leaders who own both teams' priorities. Missed interlocks are worth reviewing at quarter end to improve planning.