Cross-plan dependency governance Cross-plan dependencies, finally under control.
CrossLink watches the dependencies that cross your Microsoft Planner Premium plans and turns every upstream slip into a small, reviewable decision — never a surprise cascade.
An upstream slip is news, not an order.
Big programs are never one plan.
Your clinical operations plan depends on a date in manufacturing; regulatory depends on a date in yours. When one team moves, everyone downstream needs to decide whether to move with it.
The wrong fix: native cross-project links auto-cascade. One team's slip silently rewrites your schedule — so managers stop linking plans altogether, and lose the visibility they needed most.
Propose, don't cascade.
Link a giver to a getter
Right-click across two plans to connect a giver (provides the date) to a getter (depends on it). Starts in step — no noise at creation.
CrossLink watches for drift
When a giver moves, CrossLink detects it automatically against live plan data — no plan open, nothing to trigger. The getter gets flagged.
You accept — or you don't
Each slip surfaces as a proposal. Your date changes only when you accept — the change becomes a conversation between teams, not a cascade.
See it happen in the real product
A giver slips, the proposal appears, one click accepts it. Click to enlarge.
Key features
Propose-and-accept governance
Upstream changes never auto-update your plan. Every slip is a reviewable decision.
The cross-plan drift view
One screen shows every link you're monitoring. Your morning check-in is a single glance.
Giver / getter language
Plain program-management terms: this task gives a date, that task gets it.
A timeline for many plans
Select the plans you care about, see their tasks and cross-links together.
History on every link
Each link remembers how its dates moved, so you see the drift, not just the current state.
No client, no polling
Detection runs against your Dataverse data directly — no open windows, no manual refresh.
Proven thinking, built for Planner Premium.
Accept-don't-cascade, the give/get language, the "show me everything I'm monitoring" view — ideas refined over years of managing cross-plan dependencies in regulated, milestone-driven programs, built natively for Microsoft Planner Premium on the Power Platform.
The program manager who lives across plans — monitoring dozens of cross-plan dependencies from the program view, not any single plan. Built for multi-team programs in regulated, milestone-driven industries: pharma, biotech, hardware, infrastructure.
An upstream slip is news, not an order. Program managers need to see it, understand its impact, and decide — not have their schedule quietly rewritten for them. From the plain giver/getter language to the single cross-plan view to the accept-don't-cascade model, every part of CrossLink keeps the program manager in control of their own plan.
What you need to get started
CrossLink works with the Microsoft tools your program managers already use.
Microsoft Planner Premium
If your teams plan their work in Planner Premium, you're ready — CrossLink layers directly on top of the plans you already have.
One-click install
No new platform to adopt, no data migration. CrossLink installs alongside your existing plans from Microsoft Marketplace.
Built for your Microsoft cloud
CrossLink runs on the Power Platform, inside your own environment — your program data never leaves Microsoft's cloud.
Frequently asked questions
Does CrossLink change my dates automatically?
No. That's the whole point. Inside a single plan, Planner reschedules for you — CrossLink never touches your dates across a plan boundary without your explicit acceptance.
Do I need to keep plans open for it to work?
No. Detection runs against your data directly, whether or not anyone has a plan open.
Can I link two tasks in the same plan?
You can, but CrossLink will warn you — Planner's own built-in dependencies usually serve you better within a single plan. CrossLink is built for the links that cross plans.
How is this different from Planner's built-in dependencies?
Planner's dependencies work beautifully inside a single plan, and reschedule automatically as they should. CrossLink handles the links that cross plan boundaries — where automatic rescheduling is the wrong behavior — by turning each upstream change into a decision you approve, not a cascade you never saw.