# NEC3: Response to an early warning

**URL:** <https://reachback.builtintelligence.com/t/nec3-response-to-an-early-warning/3373>\
**Category:** NEC3 and NEC4 Contracts\
**Created:** [14 April 2015 19:28 UTC](https://reachback.builtintelligence.com/t/nec3-response-to-an-early-warning/3373 "2015-04-14T19:28:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Barry\_Trebes](https://dub1.discourse-cdn.com/flex013/user_avatar/reachback.builtintelligence.com/barry_trebes/32/517_2.png) [@Barry\_Trebes](https://reachback.builtintelligence.com/u/Barry_Trebes)\
**Post date:** [17 April 2015 15:29 UTC](https://reachback.builtintelligence.com/t/nec3-response-to-an-early-warning/3373/3 "2015-04-17T15:29:42Z")

</div>

Would like to reinforce Glenn’s response by saying that the entire purpose of Early warnings is to avoid, mitigate or reduce potential risks. Issuing an early warning is a positive pro-active action. Much can be lost in translation in written communications and that is why it is good to discuss early warnings in a risk reduction meeting face to face to understand the risk.

---

_[View the full topic](https://reachback.builtintelligence.com/t/nec3-response-to-an-early-warning/3373)._
