# Using Pollination for demonstrating WELL compliance

**URL:** <https://discourse.pollination.solutions/t/using-pollination-for-demonstrating-well-compliance/3701>\
**Category:** Recipes\
**Tags:** feature-request\
**Created:** [March 1, 2024, 8:23pm UTC](https://discourse.pollination.solutions/t/using-pollination-for-demonstrating-well-compliance/3701 "2024-03-01T20:23:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![adaversa](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/adaversa/32/7271_2.png) [@adaversa](https://discourse.pollination.solutions/u/adaversa)\
**Post date:** [March 1, 2024, 8:23pm UTC](https://discourse.pollination.solutions/t/using-pollination-for-demonstrating-well-compliance/3701/1 "2024-03-01T20:23:57Z")

</div>

@mikkel we are also looking to use Pollination for demonstrating WELL compliance. I appreciate the idea to provide recipe inputs but hardcode to zero credits.

Would it be easier to clone the daylight-option-one recipe, modify hardcoded thresholds but do not expose them, and issue a WELL v2 L01 recipe?

Within grasshopper (and running the recipe locally) am I able to modify the script with the WELL values?

Thank you!

---

<div class="post-metadata">

**Author:** ![mikkel](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/mikkel/32/5920_2.png) [@mikkel](https://discourse.pollination.solutions/u/mikkel)\
**Post date:** [March 7, 2024, 6:07pm UTC](https://discourse.pollination.solutions/t/using-pollination-for-demonstrating-well-compliance/3701/2 "2024-03-07T18:07:59Z")

</div>

Hi @adaversa (and @jroberts),

Please forget what I said above about exposing extra inputs to `leed-daylight-option-one` and hardcoding the credits if you change the thresholds.

The better solution is to create a new recipe tailored to WELL (v2 L01). As far as I can tell, the procedure is the same as `leed-daylight-option-one`, the only difference being the thresholds, or you can choose Annex A of CEN 17037:2018. We already have the post-processing for both of these so it is just a matter of putting together a new recipe using parts from existing recipes.

 ![image](https://discourse.pollination.cloud/uploads/default/original/2X/4/45c859239fb2a1299fcae59a34bfb03a479fbd8a.png)

> **[WELL Standard](https://v2.wellcertified.com/en/wellv2/light/feature/1)**
>
> \## Build Setup

> [@adaversa](#):
>
> Within grasshopper (and running the recipe locally) am I able to modify the script with the WELL values?

No, that is not possible.

---

<div class="post-metadata">

**Author:** ![jroberts](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/jroberts/32/9861_2.png) [@jroberts](https://discourse.pollination.solutions/u/jroberts)\
**Post date:** [March 8, 2024, 9:34am UTC](https://discourse.pollination.solutions/t/using-pollination-for-demonstrating-well-compliance/3701/3 "2024-03-08T09:34:57Z")

</div>

Hi @mikkel,

That sounds like a good and reasonably pain-free solution!  
Note that WELL L01 is a precondition, but there are also optimisation credits available under L06, but this uses sDA\_300/50%, so we could just use the `leed-daylight-one` recipe for this, or this part of that recipe could be copied and pasted into the new WELL recipe for L01 and L06? Not sure what the cleanest solution is.

 ![image](https://discourse.pollination.cloud/uploads/default/original/2X/d/d0a9eed6148b163a53b3754077a2fada2823fbbc.png)

Thank you!

---

<div class="post-metadata">

**Author:** ![mostapha](https://discourse.pollination.solutions/user_avatar/discourse.pollination.solutions/mostapha/32/5761_2.png) [@mostapha](https://discourse.pollination.solutions/u/mostapha)\
**Post date:** [March 8, 2024, 8:43pm UTC](https://discourse.pollination.solutions/t/using-pollination-for-demonstrating-well-compliance/3701/4 "2024-03-08T20:43:13Z")

</div>

Assigned @mikkel on March 8, 2024, 8:43pm UTC