Negotiating Supplier Penalties and IP Rights
Alex Vance and Sam Brooks reconvene to finalize a contract for robotic arms, addressing late delivery penalties and intellectual property ownership. They discuss compromise terms for liquidated damages, force majeure clauses, and shared software licensing.
What you’ll be able to do
- Identify and negotiate specific contractual terms such as penalty rates and force majeure clauses.
- Articulate concerns regarding intellectual property rights and shared licensing models for custom software.
- Define service-level agreements (SLAs) including response times, support guarantees, and monitoring protocols.
- Establish protocols for software updates, testing, and continuous improvement through quarterly reviews.
Dialogue
Beginner version
Alex Vance
Sam Brooks, thanks for meeting again. We agree on most things. But we need to clear up a few details before we sign.
Sam Brooks
Of course. Let’s go through each point step by step.
Alex Vance
First, we want a stronger rule for late delivery. Late robots will delay our project. We propose a 1% penalty per week. The max is 10%.
Sam Brooks
I understand. We usually limit penalties to 5%. How about 0.75% per week? The max will be 7%. Can we add a rule for force majeure events?
Alex Vance
Yes, but be clear. No normal price changes. If force majeure happens, tell us right away. Follow the escalation plan.
Sam Brooks
Agreed. We will add an escalation process with names and response times. We will send updates every two weeks.
Alex Vance
Perfect. Next, the new software. Our IT team is worried. We want shared ownership of the middleware. We need to let other branches use it.
Sam Brooks
That is complex. We normally keep full ownership. But we can agree to shared rights. You can use and change the software in your group.
Alex Vance
Good. We do not want to renegotiate for future changes inside our company.
Sam Brooks
Understood. I will speak with our legal team. I will update the contract.
Alex Vance
Great. Now, the service-level agreement. We like the 48-hour response time. But for serious problems, we need 24-hour on-site support. We also want help to monitor the system.
Sam Brooks
We can do that. For critical issues, we offer 24-hour support. We will give you a hotline and a support manager. We will add a system to warn us both.
Alex Vance
Excellent. Another point is software updates. We want 30 days’ notice for planned updates. Tell us immediately for urgent security updates. We want to test updates. We need a way to undo them.
Sam Brooks
No problem. We will include a clear update plan. Our technical team will help during testing.
Alex Vance
Finally, we want to meet every three months. We will check service quality, deliveries, and risks. We want a plan for improvements.
Sam Brooks
That works well. We will suggest KPIs like uptime and response speed. We can add workshops for improvements.
Alex Vance
Perfect. Can you send the new contract by Friday? Then we can do a final review.
Sam Brooks
Yes, of course. I will make sure our legal and operations teams include everything.
Alex Vance
Thank you, Sam Brooks. Once we approve, we will send the letter of credit and confirm the plan.
Sam Brooks
That sounds great. I look forward to completing this deal, Alex Vance.
Alex Vance
Me too, Sam Brooks. Thanks for working closely with us.
Intermediate version
Alex Vance
Sam Brooks, thanks for meeting again. After going over the draft with our legal and purchasing teams, we agree on most things. But there are still a few important details we need to clear up before we sign.
Sam Brooks
Of course, happy to help. Let’s go through each point step by step.
Alex Vance
First, we want a stronger rule for late delivery. If the robots arrive late, our automation project will be delayed, and this will affect our customers. We propose a penalty of 1% of the order value for each week of delay, up to 10%.
Sam Brooks
I understand. Normally, we limit penalties to 5%. But we can meet halfway-how about 0.75% per week, up to a maximum of 7%? Also, can we add a rule for force majeure events, like big problems in the global supply chain that we can’t control?
Alex Vance
Yes, but we need to be clear. The rule should not include things like normal price changes for materials. Also, if force majeure happens, you must tell us right away and follow an escalation plan to fix the issue.
Sam Brooks
Agreed. We will add a clear escalation process, with names and response times for each contact. We will also send progress updates every two weeks during key parts of the project.
Alex Vance
Perfect. Next, we need to talk about the new software you will make for us. Our IT team is worried about future changes. We want to share ownership of the special middleware or API tools you develop for this project. We also need the right to let our other company branches use them.
Sam Brooks
That is a bit more complex. We normally keep full ownership of our software, but we can agree to shared rights. This will let you use and change the software within your group of companies.
Alex Vance
Good. We also want to make sure we don’t need to renegotiate if we make future changes inside our company.
Sam Brooks
Understood. I will speak with our legal team and update the contract with the right language.
Alex Vance
Great. Now, for the service-level agreement. We like the 48-hour response time for non-urgent problems, but for serious problems that stop production, we need a 24-hour on-site support guarantee. Also, we would like your company to help us monitor the system to catch problems early.
Sam Brooks
We can do that. For critical issues, we can offer 24-hour support. We will also give you a hotline and a special support manager just for your project. For monitoring, we can add a system that warns us both when there are early signs of a problem.
Alex Vance
Excellent. Another point is software updates. We want at least 30 days’ notice for planned updates, and we want to be told immediately for urgent security updates. We also want to test updates with you before they go live and have a way to undo them if needed.
Sam Brooks
No problem. We will include a clear update plan with testing and rollback steps. Our technical team will also help during the testing phase.
Alex Vance
Finally, we would like to meet every three months during the first year to check how things are going, service quality, deliveries, and any risks. We also want to include a plan to make improvements over time.
Sam Brooks
That works well. We will also suggest KPIs, such as equipment uptime, service response speed, and spare parts availability. For improvements, we can add workshops to review lessons learned.
Alex Vance
Perfect. Can you send us a new version of the contract with all these points by Friday? Then we can do our final review.
Sam Brooks
Certainly. I will ensure our legal and operations teams incorporate all the agreed points.
Alex Vance
Thank you, Sam Brooks. Once we approve the contract, we will send the letter of credit and confirm the production plan.
Sam Brooks
That sounds excellent. I am eager to finalise this agreement, Alex Vance.
Alex Vance
Me too, Sam Brooks. Thanks for working closely with us on this.
Advanced version
Alex Vance
Sam Brooks, thank you for reconvening. Having reviewed the draft with our legal and procurement departments, we are largely in agreement. However, a few critical stipulations require resolution prior to execution.
Sam Brooks
Certainly. I am amenable to addressing these systematically.
Alex Vance
To commence, we require a more robust clause governing late deliveries. Delays in the robot shipments will inevitably derail our automation timeline, thereby impacting our client commitments. We propose a penalty equivalent to 1% of the order value per week of delay, capped at 10%.
Sam Brooks
I appreciate your position. Typically, we cap penalties at 5%. However, I am willing to compromise-how about 0.75% per week, with a maximum ceiling of 7%? Furthermore, could we incorporate a force majeure provision, accounting for uncontrollable disruptions within the global supply chain?
Alex Vance
Agreed, provided the definition is precise. It must exclude routine material cost fluctuations. Additionally, should a force majeure event occur, you must notify us immediately and activate an escalation protocol to mitigate the impact.
Sam Brooks
Understood. We will establish a clear escalation matrix, specifying contacts and response timelines. We will also provide bi-weekly progress updates during critical project phases.
Alex Vance
Excellent. Moving on to the proprietary software you will develop for us. Our IT department has expressed concerns regarding future modifications. We seek shared ownership of the custom middleware or API tools developed for this project, along with the right to deploy them across our corporate affiliates.
Sam Brooks
That introduces some complexity. While we typically retain full IP rights, we can agree to a shared licensing model. This would permit your group to utilize and modify the software within your corporate structure.
Alex Vance
Good. We also need assurance that internal corporate restructuring will not necessitate renegotiation.
Sam Brooks
Noted. I will consult our legal counsel to ensure the contract language accommodates this.
Alex Vance
Moving forward, regarding the Service Level Agreement. We are satisfied with the 48-hour response time for non-critical issues, but for production-stopping emergencies, we require a 24-hour on-site support guarantee. Additionally, we would appreciate your assistance in proactive system monitoring to identify anomalies early.
Sam Brooks
We can accommodate that. For critical incidents, we will provide 24-hour support. We will also assign a dedicated support manager and establish a priority hotline for your project. Regarding monitoring, we can implement an alert system that notifies both parties of early warning signs.
Alex Vance
Superb. Another consideration is software updates. We require a minimum of 30 days’ notice for scheduled updates and immediate notification for urgent security patches. We also need the ability to test updates in a sandbox environment before deployment and a rollback procedure in case of failure.
Sam Brooks
No issue. We will draft a comprehensive update protocol, including testing and rollback steps. Our technical team will also support the testing phase.
Alex Vance
Finally, we propose quarterly review meetings during the first year to assess service quality, delivery performance, and risk mitigation. We also want a framework for continuous improvement.
Sam Brooks
That aligns well. We will propose KPIs, such as equipment uptime, service response efficiency, and spare parts availability. For continuous improvement, we can schedule workshops to review lessons learned.
Alex Vance
Perfect. Could you circulate a revised contract incorporating these terms by Friday? We can then conduct our final review.
Sam Brooks
Certainly. I will ensure our legal and operations teams incorporate all these points.
Alex Vance
Thank you, Sam Brooks. Upon approval, we will issue the letter of credit and confirm the production schedule.
Sam Brooks
That sounds excellent. I look forward to finalizing this agreement, Alex Vance.
Alex Vance
Likewise, Sam Brooks. I appreciate your close collaboration on this matter.
Check your understanding
1. What service-level guarantees does Alex Vance request for production-halting incidents?
Show answer
Alex Vance requests a 24-hour on-site support guarantee for production-stopping emergencies, as opposed to the 48-hour response time for non-critical issues.
2. How does Sam Brooks address the request for proactive monitoring and predictive maintenance?
Show answer
Sam Brooks agrees to implement an alert system that notifies both parties of early warning signs to identify anomalies.
3. What protocol does Alex Vance suggest regarding software updates and joint validation?
Show answer
Alex Vance requires a minimum of 30 days’ notice for scheduled updates and immediate notification for urgent security patches. They also require the ability to test updates in a sandbox environment before deployment and a rollback procedure in case of failure.
Grammar practice (mixed)
Tenses
Alex Vance ___ the contract revisions with his legal team yesterday.
Show answer & why
reviewed · 💡 The specific past time marker 'yesterday' requires the simple past tense to describe a completed action.
Prepositionsself-check
Sam Brooks insisted ___ including proactive monitoring in the service agreement.
Show answer & why
on · 💡 The verb 'insist' is standardly followed by the preposition 'on' when indicating the subject of the insistence.
Conditionalsself-check
If the IT team ___ joint ownership of the middleware, future integrations will be easier.
Show answer & why
retains · 💡 This is a first conditional sentence describing a likely future result, so the 'if' clause requires the simple present tense.
Tenses
Typically, we ____ penalties at 5%.
Show answer & why
cap · 💡 The sentence describes a general business practice, requiring the simple present tense for the subject 'we'.
Prepositionsself-check
Sam Brooks: I appreciate your position. Typically, we cap penalties ____ 5%.
Show answer & why
at · 💡 The preposition 'at' is used to specify a precise level or amount, such as a percentage cap.
Verb formsself-check
Alex Vance: Agreed, ____ the definition is precise. It must exclude routine material cost fluctuations.
Show answer & why
provided · 💡 'Provided' is used as a conjunction meaning 'if' or 'on the condition that'. It is the standard formal usage in business contracts.
Grammar in contextself-check
Sam Brooks: Understood. We will establish a clear escalation matrix, specifying contacts and response timelines. We will also provide bi-weekly progress updates during ____ critical project phases.
Show answer & why
the · 💡 The definite article 'the' is used because 'critical project phases' refers to specific phases previously implied or known in the context of the agreement.
Discussion (practise speaking)
How do you balance strict penalty clauses with maintaining a positive vendor relationship?
🤔 Think about a time you had to negotiate terms that felt too harsh.
Show sample answer
- Focus on mutual benefit rather than punishment.
- Include clear communication channels for disputes.
- Consider the long-term value of the partnership.
Ask Phil: Role-play negotiating a penalty clause with a difficult supplier.
What steps should be taken to ensure a force majeure clause is effective and fair?
🤔 Consider how unexpected events like natural disasters impact your industry.
Show sample answer
- Define specific events that qualify as force majeure.
- Exclude routine market fluctuations.
- Require immediate notification and mitigation efforts.
Ask Phil: Discuss how to define force majeure in a global supply chain context.
How can a company protect its intellectual property while allowing a vendor to develop custom software?
🤔 Think about how you handle IP in your current projects.
Show sample answer
- Negotiate shared ownership or licensing rights.
- Specify usage rights for corporate affiliates.
- Ensure the contract language prevents future renegotiation.
Ask Phil: Practice explaining the need for shared IP rights to a vendor.
Why is it important to include proactive monitoring and regular review meetings in an SLA?
🤔 Reflect on how often you review service quality with your partners.
Show sample answer
- It helps identify issues before they become critical.
- Regular meetings ensure alignment on performance metrics.
- It fosters continuous improvement and trust.
Ask Phil: Explain the benefits of proactive monitoring to a skeptical client.
Vocabulary
- reconvening
- ↗
reveal definition
Meeting again after a previous session. “Sam Brooks, thank you for reconvening.” - critical stipulations
- ↗
reveal definition
Important conditions that must be met. “However, a few critical stipulations require resolution prior to execution.” - amenable to
- ↗
reveal definition
Willing to consider or agree to something. “I am amenable to addressing these systematically.” - robust clause
- ↗
reveal definition
A strong and detailed contract section. “we require a more robust clause governing late deliveries.” - force majeure provision
- ↗
reveal definition
A contract term for uncontrollable external events. “could we incorporate a force majeure provision, accounting for uncontrollable disruptions within the global supply chain?” - escalation protocol
- ↗
reveal definition
A defined process for handling serious issues. “activate an escalation protocol to mitigate the impact.” - proprietary software
- ↗
reveal definition
Software owned by a specific company. “Moving on to the proprietary software you will develop for us.” - ↗
reveal definition
An agreement allowing multiple parties to use software. “we can agree to a shared licensing model.” - production-stopping emergencies
- ↗
reveal definition
Critical issues that halt all work. “for production-stopping emergencies, we require a 24-hour on-site support guarantee.” - rollback procedure
- ↗
reveal definition
A plan to revert software to a previous state. “a rollback procedure in case of failure.”
Key phrases (useful expressions from the dialogue)
- prior to execution Before the agreement is officially signed or started.
- addressing these systematically Handling issues in a structured and organized way.
- uncontrollable disruptions Events that cannot be managed or predicted by the parties.
- mitigate the impact To reduce the negative effects of a problem.
- corporate restructuring Changes in the organization structure of a company.
- lessons learned Insights gained from past experiences to improve future actions.
More Negotiation lessons
Annual Trade Negotiation Closing the Deal
One week after their first annual negotiation meeting, Alex Vance and Sam Brooks meet again to finish the agre…
Defending Supplier Contracts Against Competitor Bids
A supplier addresses a client's consideration of switching to a competitor offering lower prices and better te…
Finalizing Contract Terms and Dispute Resolution
Two business representatives discuss and finalize the terms of a legal agreement, including dispute resolution…
Negotiating Exclusive Licensing Terms for APAC E-Commerce Expansion
Verolane Group VP Elena Vance negotiates an exclusive online licensing deal with Brankside Holdings VP Marcus …
Negotiating Infrastructure Cost Allocation in Development Project
Two business representatives discuss cost-sharing for public amenities in a major urban development project. T…
Negotiating Sustainable Snack Launch and Delivery Terms
Alex Vance and Sam Brooks meet to finalize details for launching healthy snacks in Brankside Holdings stores. …
Keep going
Practise this scenario live with Phil, and get a personalised lesson built from your own mistakes. Interactive in the browser, with a booklet to keep.
Book a lesson with Phil