8. Change Control


8. Change Control

If the vendor will be providing implementation services, the license agreement should address the change control and change order procedure. Generally speaking, the longer a project is anticipated to last, the more likely changes will be required. The contract should have a defined procedure that addresses the mechanism for either party proposing changes to the scope; documenting the impact of those changes on the contract price, schedule, personnel or other aspect of the contract; and accepting or modifying the change in scope. A very basic change order provision is shown below.

Example Provision:

start example
  1. Change Orders. Either party may submit a written change request to the other party for consideration. On receiving each change request, the parties shall meet and confer regarding the request, the availability of Vendor's staff, cost of any changes, and any impact the change will have on project scheduling and product warranties or other obligations under this Agreement. If the parties agree to the change, the written change order will be signed by both parties and attached as an exhibit to this Agreement.

end example




Software Agreements Line by Line. How to Understand & Change Software Licenses & Contracts to Fit Your Needs
Software Agreements Line by Line. How to Understand & Change Software Licenses & Contracts to Fit Your Needs
ISBN: 1587623692
EAN: N/A
Year: 2004
Pages: 56

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net