{"id":48,"date":"2013-10-30T07:54:48","date_gmt":"2013-10-30T13:54:48","guid":{"rendered":"http:\/\/ericlambert.net\/blog\/?p=48"},"modified":"2013-10-30T07:54:48","modified_gmt":"2013-10-30T13:54:48","slug":"feedback-on-feedback-clauses","status":"publish","type":"post","link":"https:\/\/ericlambert.net\/blog\/2013\/10\/30\/feedback-on-feedback-clauses\/","title":{"rendered":"Feedback on feedback clauses"},"content":{"rendered":"<p>A feedback clause generally gives a party a right and license to use ideas, comments, suggestions or similar feedback provided by the other party. Companies that offer products and services like these clauses because they allow the company way to learn information that can help them continue to improve their offerings.\u00a0 The standard argument in support of this type of clause is that it\u2019s important to a product or service provider to ensure that simply discussing products in development with a client does not jeopardize their ability to use information they learn during that discussion.\u00a0 While that\u2019s not unreasonable, there are a few different flavors of feedback clauses \u2013 the taste depends on which side of the fence you\u2019re on.<\/p>\n<p>As noted above, a typical feedback clause gives a party defines \u201cFeedback\u201d (e.g., any ideas, comments, suggestions or similar feedback provided by one party to the other); indicates that the provision of feedback is completely voluntary; and provides some grant of rights to the receiving party to use feedback.\u00a0 Think of this as the \u201cbase.\u201d\u00a0 There are things you can \u201cmix into\u201d the base to change or enhance it, including a <i>feedback trumps confidentiality <\/i>provision, a <i>feedback ownership<\/i> provision, and\/or a <i>feedback warranty<\/i> provision. If you\u2019re on the receiving end of feedback, these mix-ins may be worth considering adding into a base clause.\u00a0 If you are on the disclosing end, these may be real causes for concern.\u00a0 (If you\u2019d like a copy of my standard mix-in clauses, send me an email.)<\/p>\n<p><i>Feedback trumps confidentiality.<\/i>\u00a0 This mix-in states that any feedback provided, even if designated as confidential by the disclosing party, does not create any confidentiality obligation for the receiving party absent a separate written agreement, and the receiving party is free to use it the feedback without obligation or limitation.\u00a0 To the recipient, this ensures that any feedback can be freely used if provided by a recipient, regardless of confidentiality obligations under the Agreement.\u00a0 To the discloser, this can result in a \u201cback door\u201d around confidentiality.<\/p>\n<p><i>Feedback ownership.<\/i>\u00a0 This mix-in states that the disclosing party agrees to transfer all right, title and interest in and to feedback to the receiving Party.\u00a0 To the recipient, this ensures that they do not have to worry about creating derivative works of materials owned by a third party by using feedback.\u00a0 To the discloser, this can result in an inadvertent surrender of its own rights to any of its underlying proprietary information disclosed as feedback to a third party.<\/p>\n<p><i>Feedback warranty.<\/i>\u00a0 This mix-in is a warranty that the feedback does not infringe third party IP rights, is not subject to open source licensing obligations, and does not require payment of third party licensing fees.\u00a0 To the recipient, this can give some important protections if the recipient uses the feedback.\u00a0 To the discloser, this creates contractual representations for providing feedback, for which contractual damages may rise if the discloser breaches the warranty.<\/p>\n<p>Here is my own base feedback clause where I represent MyCo (I flip this around and add in mix-ins on a case-by-case basis if warranted).\u00a0 It requires designation of feedback as such, and protects confidential information if inadvertently provided with feedback:<\/p>\n<p>\u201cThe Parties acknowledge that MyCo may from time to time provide YourCo with ideas, comments, suggestions, or other feedback on the features or functionality of YourCo\u2019s product offerings which is designated by the disclosing party as \u201cFeedback\u201d in writing on any written feedback, or contemporaneously with disclosure if disclosed orally (collectively, \u201c<b>Feedback<\/b>\u201d).\u00a0 The Parties agree and acknowledge that any Feedback is provided voluntarily by MyCo.\u00a0 In the event MyCo provides YourCo with Feedback, MyCo hereby grants to YourCo a perpetual, royalty-free, worldwide right to use such Feedback for the limited purpose of improving and creating derivative works of YourCo\u2019s Products (notwithstanding the foregoing, the foregoing right shall not apply or extend to any portion of Feedback provided by MyCo which is MyCo\u2019s Confidential Information, MyCo Technology or MyCo Materials), and the obligations of confidentiality set forth in this Agreement shall supersede and have priority over any Feedback usage rights.\u201d<\/p>\n<p>Finally, one of the most important things you can do regarding feedback is educate your business teams on what to watch out for when sharing feedback with a contractual partner \u2013 as in many areas, sound business practices can go a long way towards ensuring reliance on the legal language never becomes a necessity.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A feedback clause generally gives a party a right and license to use ideas, comments, suggestions or similar feedback provided by the other party. Companies that offer products and services like these clauses because they allow the company way to &hellip; <a href=\"https:\/\/ericlambert.net\/blog\/2013\/10\/30\/feedback-on-feedback-clauses\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,4,7],"tags":[],"class_list":["post-48","post","type-post","status-publish","format-standard","hentry","category-drafting","category-legal","category-negotiation"],"_links":{"self":[{"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/posts\/48","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/comments?post=48"}],"version-history":[{"count":0,"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/posts\/48\/revisions"}],"wp:attachment":[{"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/media?parent=48"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/categories?post=48"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ericlambert.net\/blog\/wp-json\/wp\/v2\/tags?post=48"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}