diff --git a/merge-queue/using-the-queue/monitor-queue-status.md b/merge-queue/using-the-queue/monitor-queue-status.md
index 8f10e481..65df778d 100644
--- a/merge-queue/using-the-queue/monitor-queue-status.md
+++ b/merge-queue/using-the-queue/monitor-queue-status.md
@@ -47,6 +47,23 @@ The view of all current PRs being tested by Trunk Merge Queue and their respecti
 
 You can click on any shown PR to navigate to the details page for that PR.
 
+#### Impacted targets in the graph
+
+When running in [Parallel mode](../optimizations/parallel-queues/), the graph view shows impacted targets information to help you understand why PRs are grouped or ordered the way they are.
+
+* **Per-PR tooltips**: Hover over a PR node to see which targets that PR impacts.
+* **Overlapping targets on edges**: Use the **Show impacted targets** toggle to display which targets overlap between connected PRs. Overlapping targets explain why PRs are in the same testing sequence — PRs with shared targets must test together.
+
+This is useful for debugging unexpected queue ordering or understanding why specific PRs are batched together.
+
+#### Impacted targets on the PR detail page
+
+On any PR's detail page, click **View impacted targets** to see the full list of uploaded targets. The modal shows one of three states:
+
+* **IMPACTS\_ALL**: The PR impacts all targets, so no parallel optimization is possible.
+* **Specific targets**: A list of each target the PR impacts.
+* **No targets uploaded**: No targets were provided, so the PR is treated as IMPACTS\_ALL for safety.
+
 ### Health view
 
 Select a period of time to inspect using the **Period** dropdown (default 7 days) and a **Granularity** (defaults  to daily) of queue metrics