--- title: "Warn downstream owners before a change lands - Atlan MCP Cookbook" url: "https://atlan.com/mcp-cookbook/warn-downstream-owners-before-a-change-lands/" description: "Find every downstream consumer of a changing asset and warn their owners first." --- > Atlan is hosting Context Conference, bringing together the leaders and builders at the frontier of giving AI the context it needs to understand their business. It runs online on October 28, 2026, from 11:00 AM to 2:00 PM ET. Atlan co-founder Prukalpa Sankar opens and closes the day. Leaders from AstraZeneca, BNY and Verizon share why they invest in context and what they get from it. Registrants get early access to The AI Context Gap, a new study from MIT Technology Review Insights. Register: https://atlan.com/context-conference/ Recipe 7 in [The Atlan MCP Cookbook](https://atlan.com/mcp-cookbook/). Find every downstream consumer of a changing asset and warn their owners first. Use case: Change & fix data safely / Action: Make changes / Persona: AI Builder, Data Engineer / Effort: Moderate / Runs in: any AI tool Requires Atlan MCP connected to your AI tool: [set up Atlan MCP](https://docs.atlan.com/product/capabilities/atlan-ai/how-tos/remote-mcp-overview). ## 1. The task **Scenario.** Next week you are renaming customer_id to cust_id in dim_customers. Somewhere downstream, pipelines and dashboards read that column by name, and unless you warn them, they break quietly at 2am on release night. You want to find everyone affected and give them a week's notice. The ask: - Every downstream table and dashboard that uses the column, and their owners - A warning announcement on each - The change and the timeline spelled out Hero prompt: "The customer_id column in dim_customers is being renamed to cust_id next week. Find all downstream tables and dashboards that use it and add a warning announcement explaining the change and timeline." Step by step: 1. Find the changing asset and confirm what depends on it. Prompt: "The [column] in [table] is being renamed to [new name] next week - pull [table] and confirm it has downstream lineage." 2. Trace the downstream consumers. Prompt: "Trace the downstream tables and dashboards that use [table] - direct consumers first, then expand." 3. Resolve the owner of each impacted asset. Prompt: "For each downstream asset, show its owner (resolve the owning team where it's a group), so every warning reaches the right people." 4. Post a warning announcement on each impacted asset. Prompt: "Add a warning to each explaining the change from [column] to [new name] and the timeline." ## 2. What you'll give it Required context: - The asset and the change (customer_id to cust_id in dim_customers) - The timeline (next week, with a date) - Lineage populated, and permission to post announcements Optional context: - The migration guidance to include (what consumers should change and by when) - A cutoff, if you only want to warn assets touched in the last 90 days ## 3. What Atlan creates Outputs: - The full downstream consumer list for the changing column - The resolved owner of each impacted asset (the owning team where ownership is a group) - A warning announcement on each impacted table and dashboard - The change and the date, stated where each owner will see it **Summary.** The break is prevented instead of documented after the fact. Every owner in the path gets the same notice with the same deadline, on the asset they actually open. **Writes to Atlan.** Changed: a warning announcement on each impacted asset. Left untouched: the column, which you rename on your own schedule; this recipe only warns. ## 4. Follow-up prompts - **Give them the fix:** "Add a line to each announcement telling consumers to update to cust_id before the release date." - **Size the blast radius:** "Where usage data exists, rank the impacted assets by how heavily they're queried, so I warn the busiest ones first." - **Confirm before the change:** "A few days before the change, re-trace the downstream consumers and show which still have no warning announcement, so I can chase them." ## 5. Tips & troubleshooting **Cook's note.** Send it a week ahead. The point is to prevent the 2am break, not document it after. - Match the tool to the work. Run it where you can review the consumer list before it posts; a missed consumer is the whole risk, so check the list is complete. - Automate or chain it. Chain it to your PR flow: when a migration is merged, fire this recipe so the warnings post automatically with the release date. - Ask what it changed. Add "list every asset you posted a warning on." That list doubles as your notified-parties record. ## Related recipes - [See what a SQL change will break before you merge](https://atlan.com/mcp-cookbook/see-what-a-sql-change-will-break-before-you-merge/): Find every downstream consumer of a changed column or table before merging. - [Safely deprecate unused assets](https://atlan.com/mcp-cookbook/safely-deprecate-unused-assets/): Verify no active consumers exist, notify owners, then mark assets as deprecated. - [Triage a data-quality failure with full context](https://atlan.com/mcp-cookbook/triage-a-data-quality-failure-with-full-context/): Enrich quality failures with lineage, ownership, and downstream impact for faster triage. [Browse all recipes](https://atlan.com/mcp-cookbook/) / [Set up Atlan MCP](https://docs.atlan.com/product/capabilities/atlan-ai/how-tos/remote-mcp-overview)