diff --git a/prompts/weather/daily_report/daily_report.user.md b/prompts/weather/daily_report/daily_report.user.md
index 2587547..1bd0745 100644
--- a/prompts/weather/daily_report/daily_report.user.md
+++ b/prompts/weather/daily_report/daily_report.user.md
@@ -28,7 +28,7 @@ These products have already been filtered or matched to the forecast location. T
 
 - Active warnings are urgent and should dominate the lead and relevant sections.
 - Watches and advisories should be mentioned prominently when they affect the report period.
-- Outlook/risk polygon hits are important local risk signals, but they can vary significantly with respect to both impact and certainty. They should elevate the caveat, uncertainty, and ## What to Watch discussion without implying that severe weather is certain at the exact point.
+- Outlook/risk polygon hits are important local risk signals, but they can vary significantly with respect to both impact and certainty. Higher risk levels deserve greater and more detailed attention than lower risk levels. Outlook/risk polygons should elevate the caveat, uncertainty, and ## What to Watch discussion without necessarily implying that severe weather is certain at the exact point.
 - Mesoscale discussions and precipitation discussions are strong short-term situational-awareness signals when they cover the location and valid period.
 
 For the current schema, use `briefing.applicable_risk_products.alert_digest` and `briefing.metadata.alerts` to determine whether relevant local alerts exist. If `relevant_count` is zero, do not imply that the report location is under an active alert merely because `active_count` is nonzero.
@@ -51,9 +51,10 @@ Use `briefing.narrative_products` for meteorological context, prose framing, unc
 For the current schema:
 
 - Use `briefing.narrative_products.narrative_forecast.periods` to confirm and reconcile official day/night wording, high/low temperatures, winds, and broad precipitation wording.
-- Use `briefing.narrative_products.weather_story` for hazard type, broad geographic placement, and timing. Preserve spatial limits such as “north of I-70.” Do not mention URLs, image-download details, or internal fields.
+- Use `briefing.narrative_products.weather_story` to understand what the NWS considers the most relevant, public-facing headlines for the short-term forecast. Because the covered forecast area for this product is relatively large, be wary of discussion that relates to geographical areas outside the forecast location, and preserve spatial limits such as “north of I-70.”
 - Use `briefing.narrative_products.area_forecast_discussion.key_messages` and `briefing.narrative_products.area_forecast_discussion.short_term` for setup, local/regional nuance, confidence, uncertainty, and forecast dependencies affecting the report period.
 - Use `briefing.narrative_products.area_forecast_discussion.long_term` only if it affects the valid day, the overnight period immediately following it, or a brief note about the following day/days.
+- If `briefing.narrative_products.spc_convective_discussion.discussions` is present, use it to understand  and to provide context to the severe weather forecast. Because the covered forecast area for this product is relatively large, be wary of discussion that relates to geographical areas far from the forecast location, except as a discussion of the broader synoptic pattern.
 
 Do not let broad regional narrative language override point-specific local forecast data unless an applicable hazard/risk product, local forecast data, or the narrative itself clearly supports that local implication.