Watershed
AI / ML EngineerAppliedAug 6, 2026

Refine supplier evidence requests for edit-free sends

Faster supplier outreach can lose value when requests do not reflect what is already known.

Teams often need specificity without creating duplicate work or overreaching for evidence.

Suppliers will help, but they stop responding when our asks look like we didn’t read what they sent.

Heidi Roux · Scope 3 Reporting Lead

Coordinates supplier data collection for a public company with a large procurement footprint.

What pulls against what

  • specific requests vs. supplier fatigue
  • retrieval breadth vs. data permissions
  • automation speed vs. reviewer confidence
  • collection throughput vs. evidence adequacy

What is at stake

Irrelevant requests consume reviewer time and weaken supplier participation. Better grounded drafting can improve primary-data collection before reporting deadlines

Why Watershed

At Watershed, supplier engagement often determines whether Scope 3 reporting becomes more specific over time.

Written for

LLM systems engineerretrieval engineerapplied ML product builder

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.