How to Review a Feedback License That Assigns Customer Ideas

An ops lead at a 22-person UK agency is about to accept a SaaS MSA — a master services agreement the vendor hangs order forms on — whose Feedback sentence irrevocably assigns every suggestion and Customer Input, including the roadmap. Sales calls it standard. Knowing how to review a feedback license assignment of customer ideas means you freeze that sentence, lock a product-only definition, read the verb, then narrow, swap to a disclaimer, or delete.

On 8 September 2026, Reza (Ops) has Finance’s yes on a US project-ops SaaS. Clause 8.4 owns ‘Customer Input’ related to our Services, even if designated confidential, and irrevocably assigns it. Last Thursday the AE sat in a roadmap call. Delivery sketched a 2027 client-portal workflow. AE Slack: “standard feedback — we just need to ship your ideas.” Go-live is Wednesday.

Typical mistake: treating the heading as stationery. The costly risk is not a bug-report box. Common Paper CSA 2.1 §1.4 (accessed 8 September 2026) is a lightweight use-right, not an assignment. Commentary: many customers bristle at seeing an assignment. Reza’s paper is the Language Library swap plus the Law Insider tripwire: vendor owns Customer Input even if designated confidential.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

How do “suggestions and ideas” swallow your roadmap?

Search the packet — MSA plus order form plus any Cover Page Other Changes — for feedback, suggestions, ideas, Customer Input, assign, and irrevocable. Write the list. A High sentence names suggestions or Customer Input related to our Services, then owns or assigns them. That list is meant to catch “your tool should do X.” Over-broad drafts catch the roadmap.

See the packet freeze walk. Brian Heller (accessed 8 September 2026): intended object is “your tool should do X”; over-broad drafts include the customer’s roadmap. Last Thursday’s Slack sits inside the net if the paper says “related to our Services.” If the next sentence is improve / enhance / train on Customer Content, that is vendor AI training rights — then return. Feedback is not training-on-customer-data. Do: write the list. Don’t: treat “suggestions and ideas” as stationery.

What to lock in a product-only definition — not your business plans

Undefined Feedback, ideas, related offerings, or related to our Services pulls in agency business plans. Define Feedback only as a suggestion for improving the vendor’s existing products that are the subject of this agreement. Expressly exclude confidential information, customer data, general business ideas, and the customer’s workflows or roadmap.

For example, a crash on their button is the intended object. A “fix” that describes your 2027 client-portal build is a roadmap dump — out of scope unless written, marked, and accepted. GC AI (accessed 8 September 2026): a grant of “all suggestions, ideas, and improvements” can reach further than either side intended. Tighten Common Paper’s “related offerings.” Do: write vendor’s existing product. Don’t: leave “ideas” undefined.

What does a licence versus assignment of unknown IP actually move?

Write the verb. A licence is a use-right. An assignment transfers title. Both can cast a shadow over future IP the staff have not invented yet. Treat assignment as High. United Kingdom copyright protects the expression of a work, not the idea behind it — so “own the idea” is the wrong ask.

Market colour — not Reza’s statute — is a non-exclusive, perpetual, royalty-free licence. Morgan Lewis / NLR (2017 structure): assignment can make the discloser lose what they dumped as feedback. David Tollen (5 December 2023): a short grant can be read as rights in related patents later created — interpretation #3. GOV.UK IPO and Pinsent Out-Law (21 June 2024): copyright protects expression, not ideas. The clause is not void. Residuals — unaided memory — are a different sentence. Do: refuse assignment; if they insist on a use-right, keep it non-exclusive and product-only. Don’t: treat licence and assignment as the same paper.

Which carve-out keeps confidential information and customer data out of the grant?

A sentence that says Feedback is not Confidential Information, even if designated confidential, punches through the confidentiality clause. Demand a carve-out that survives. Marking Slack confidential does not save a roadmap if the paper already punched through. Feedback must not include client files, personal data, or the agency roadmap.

High sentence from the Tollen 2024 sample: Feedback will not be considered Customer’s Confidential Information. Same punch as Law Insider’s “even if designated confidential.” Buyer do: the confidentiality / NDA — non-disclosure — block still governs Feedback that includes Customer Data. Align the DPA — the data processing agreement — so a support dump cannot be re-labelled Feedback. In practice, Reza’s Slack stamp is worthless here. Do: write a carve-out that survives. Don’t: bank on the stamp.

When to prefer a feedback disclaimer over a grant

The vendor wants to ship product suggestions without a later “you stole my idea” claim. That does not require ownership of unknown IP. Offer a feedback disclaimer instead of a grant: nothing restricts their use of suggestions about their products; confidentiality still governs customer confidential information; no licence or assignment of future IP.

Tollen’s mechanic — paraphrase, not a Checkory clause — is the buyer counter. Morgan Lewis (20 August 2025) treats a disclaimer as a middle ground without a formal licence or assignment. A disclaimer that voids confidentiality for any Customer Input is not enough. Offer delete first (Heller); disclaimer second; a narrow licence third. Do: swap the grant once Feedback is product-only. Don’t: accept a second assignment dressed as “standard language.”

How do you narrow, swap to a disclaimer, or delete?

Confirm the sentence is Feedback and ideas, not a training paragraph. Then narrow the definition and the verb, swap the grant for a disclaimer, or delete. Walk if they refuse an irrevocable assignment plus a confidential punch-through after last week’s roadmap call.

Success bar before you sign: fill that one-page checklist — packet hits → product-only Y/N → licence or assignment? → CI / customer-data carve-out Y/N → disclaimer offered? → narrow / disclaimer / delete — and point to one sentence that pauses Wednesday. “We don’t train on your data” is not that sentence. A Slack stamp is not that sentence on Reza’s paper.

Copy the live Feedback sentence into the same packet log. Tell Delivery what must not go in a ticket until the paper matches. Owner = Reza or a named deputy. Escalate the assignment plus the confidential punch-through to counsel — a qualified solicitor for England and Wales — if they will not move. Optional: a Checkory first-pass — a first machine pass that extracts clauses before a human reads every page — on the same MSA PDF, then a human opens every High flag — a high-severity hit a human must verify.