Collaborative Negotiation Sample Clauses
The Collaborative Negotiation clause establishes a process for parties to resolve disputes through open and cooperative discussions before pursuing formal legal action. Typically, this clause requires the parties to meet, share relevant information, and attempt to reach a mutually acceptable solution within a specified timeframe. Its core function is to encourage amicable resolution of disagreements, reducing the likelihood of costly and time-consuming litigation by fostering communication and problem-solving between the parties.
Collaborative Negotiation. A quorum shall exist when there are three members of each team present.
Collaborative Negotiation. The parties agree to work collaboratively and in good faith to negotiate a Network Administration Agreement under which UTOPIA will provide designated administration services for GSCA’s proposed broadband networks. It is anticipated that the draft Network Administration Agreement will be presented to the governing boards of GSCA and UTOPIA no later than December 31, 2022.
Collaborative Negotiation. Negotiation is not about contract language. It is about finding and defining the intersection of the parties’ interests. Finding the common interests and getting the deal right is the first step in negotiation. But in too many instances, contract language is exchanged before the key business issues are addressed, thus diverting attention away from the fundamental issues. Worse, the exchange of contract language may lock in terms that work against the parties' needs or preferences. The better practice is to follow the rule: deal first, language second.
1 Partner, ▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ LLP, San Francisco, California; Fellow, American College of Construction Lawyers; Honorary Member, AIACC; Steering Committee Member and Legal and Risk Chair, AIACC Integrated Project Delivery Taskforce. 2 This paper uses the term Integrated Project Delivery for projects where the key participants are involved from an early stage of design, the project is jointly managed by the project team, and risk and reward are shared based on project outcome. IPD is sometimes loosely used to describe projects that do not have these attributes, but use BIM or have pre-construction services. These are useful practices, but by themselves they are not IPD.