diff --git a/backend/app/agents/brand_agent.py b/backend/app/agents/brand_agent.py
index df32eb0..efba634 100755
--- a/backend/app/agents/brand_agent.py
+++ b/backend/app/agents/brand_agent.py
@@ -129,7 +129,9 @@ Analyze the uploaded proof against the {brand} brand specification above, checki
 
 7. **Accessibility**: Check for legible font sizes, proper contrast, and appropriate use of special typography elements per guidelines.
 
-Provide your analysis as a JSON object. Be specific about any issues found and reference the relevant guideline sections.
+Provide your analysis as a JSON object. Be specific about any issues found.
+
+IMPORTANT: Do NOT include page numbers, document names, or source citations in your feedback (e.g., no "Page 10", "per Page 12", "Social Media Guidelines Page 8"). All feedback must be self-contained and directly actionable without requiring users to look up external references.
 
 RAG Status Guidelines:
 - **Green**: Fully compliant with brand guidelines, no issues
diff --git a/backend/app/agents/channel_best_practices_agent.py b/backend/app/agents/channel_best_practices_agent.py
index 0417d53..811cfd6 100644
--- a/backend/app/agents/channel_best_practices_agent.py
+++ b/backend/app/agents/channel_best_practices_agent.py
@@ -122,7 +122,9 @@ Analyze the uploaded proof for adherence to channel best practices, checking:
    - Are touch targets appropriately sized?
    - Does it account for thumb-zone navigation?
 
-Provide your analysis as a JSON object. Be specific about any issues found and reference the relevant guideline sections.
+Provide your analysis as a JSON object. Be specific about any issues found.
+
+IMPORTANT: Do NOT include page numbers, document names, or source citations in your feedback (e.g., no "Page 10", "per Page 12", "Social Media Guidelines Page 8"). All feedback must be self-contained and directly actionable without requiring users to look up external references.
 
 RAG Status Guidelines:
 - **Green**: Fully aligned with best practices, optimized for the channel
diff --git a/backend/app/agents/channel_tech_specs_agent.py b/backend/app/agents/channel_tech_specs_agent.py
index 338d925..7e6cb3e 100644
--- a/backend/app/agents/channel_tech_specs_agent.py
+++ b/backend/app/agents/channel_tech_specs_agent.py
@@ -128,7 +128,9 @@ Analyze the uploaded proof for technical specification compliance, checking:
    - Video/animation format requirements (if applicable)
    - Frame rate and duration limits (if applicable)
 
-Provide your analysis as a JSON object. Be specific about any technical issues and reference the relevant specification.
+Provide your analysis as a JSON object. Be specific about any technical issues found.
+
+IMPORTANT: Do NOT include page numbers, document names, or source citations in your feedback (e.g., no "Page 10", "per Page 12", "Digital Guidelines Page 8"). All feedback must be self-contained and directly actionable without requiring users to look up external references.
 
 RAG Status Guidelines:
 - **Green**: Fully compliant with all technical specifications
diff --git a/backend/app/agents/lead_agent.py b/backend/app/agents/lead_agent.py
index df51e61..1fb39ce 100755
--- a/backend/app/agents/lead_agent.py
+++ b/backend/app/agents/lead_agent.py
@@ -145,6 +145,7 @@ Your summary should:
 - Start with a one-line verdict statement
 - List key issues as bullet points (max 3-5 bullets)
 - Each bullet: one sentence, actionable
+- Do NOT include page numbers, document names, or source citations. Keep all feedback self-contained and actionable.
 - For 'Passed': briefly note any amber items in 1-2 bullets
 {revision_context}
 Here are the specialist reviews:
diff --git a/backend/app/agents/legal_agent.py b/backend/app/agents/legal_agent.py
index d34cbc5..cc4ef54 100755
--- a/backend/app/agents/legal_agent.py
+++ b/backend/app/agents/legal_agent.py
@@ -146,6 +146,7 @@ If the proof is nonsensical, not a marketing material, or cannot be analyzed, se
 - Keep feedback brief and scannable
 - Use bullet points for each finding
 - Each bullet should be one actionable sentence
+- Do NOT include page numbers, document names, or source citations (e.g., no "Page 10", "per the Legal Guidelines"). Feedback must be self-contained and actionable.
 - Start with the issue, then the requirement
 - Example: "Missing APR disclaimer - add representative APR per FCA requirements"
 """