This contract document is also included in the discounted Proposal Kit Professional bundle. Order and download for $199.
The original US Web Development Contract has been edited by an attorney in Canada to conform to Canadian law. Edit as needed to create your starting contract for your business. Each client may require modifications to the standard contract which you will need to deal with on a per-project basis. You may use the various contracts and agreements as starting points for use in other countries. You will need to have your own attorney review and edit the contracts for use in other countries and states where the standard pre-written versions will not be applicable. If you find an attorney who wants to redo everything from scratch their own way, consider getting a second opinion, unless you are in a country where US, English or Canadian law do not apply.

There is an alternate version of this contract which is more client-centered (however with minimal ownership rights for the developer).

There is also a short form (2 page) version available.
Document Length: 8 Pages
Business proposal example I have found

your contracts very useful and have used them as part of doing business. The web site contracts worked really great as I had to present them to a clients attorney and he found them to be very concise and accurate."

John Sanders
Inbox-Media, Inc.
The actual document is delivered in the retail products as an editable template.
Produced by:
Proposal Kit
Category:
Software > Computer Software > Business & Productivity Software
Price:
$199 USD
 
 
Proposal Kit reviews4.9 stars, based on over 700 reviews
Web Development Contract (Developer Centered) (Canada)
Disclaimers: Proposal Kit, Inc. makes no warranty and accepts no responsibility for suitability of any materials to licensees business. Proposal Kit, Inc. assumes no responsibility or liability for errors or inaccuracies. Licensee accepts all responsibility for results obtained. Information included is not legal advice. Use of any supplied materials constitutes acceptance and understanding of these disclaimers.

How do you write a Web Development Contract (Developer Centered) (Canada) document?

WEB SITE DEVELOPMENT AGREEMENT the Agreement THIS AGREEMENT is made this current day day of current month current year Between company name hereinafter referred to as the Developers company name hereinafter referred to as the Customer

Recitals WHEREAS the Developers have experience and expertise in the development of web sites; AND WHEREAS the Customer agrees to have the Developers develop web site for it; AND WHEREAS the Developers agrees to develop the Customers web site on the terms and conditions set forth herein the Web Site NOW THEREFORE in consideration of the mutual promises and covenants hereinafter set out the parties agree as follows. 1. Interpretation. 1 Definitions. As used herein the following terms shall have the following meanings; a Customer shall mean company name

b Developers shall mean company name c Material shall mean all of the Developers and third parties material described in Schedule C. d Specifications shall mean for the purpose of each separate contract the specifications as set out and agreed to by the parties and any amendments thereto as attached hereto as Schedule B. e Web Site shall mean the web site developed according to the Specifications. f Web Site Milestone shall mean milestone in the development of the Web Site as set out in the Specifications and Payment Terms. 1 Schedules. The following are the Schedules attached hereto and are incorporated by reference into this agreement. Schedule Payment Terms and other conditions for the development of the Web Site.

Schedule Specifications that are applicable to the Web Site. Schedule List of material owned by Developer and third parties. Schedule Addresses specified for the parties to this Agreement. 1 Invalidity of Provisions. Save and except for any provisions or covenants contained herein which are fundamental to the subject matter of this Agreement including without limitation those that relate to the payment of monies the invalidity or unenforceability of any provision or covenant hereof or herein contained shall not affect the validity or enforceability of any other provision or covenant hereof or herein contained and any invalid provision or covenant will be deemed to be severable. 1 Headings. The insertion of headings is included solely for convenience and reference and is not intended to affect the construction or interpretation of this Agreement nor are the headings intended to be full or accurate descriptions of the contents hereof.

1 Dollars. All amounts referenced herein shall mean currency of Canada. 2. Term. Except for the obligations of the parties that shall survive completion of the development work of the Web Site by the Developers unless terminated earlier in accordance with the termination and default provisions in the Agreement the term of this Agreement shall be for the duration of the works to be completed as referenced herein and the Web Site is delivered to the Customer for its use. Agreement changes must be approved by both parties in writing and will be considered addendums to the Agreement. The Agreement shall be deemed terminated when an Acceptance form is signed by both parties. 3. Compensation Contract Price. 3 Upon the execution of this Agreement the Customer agrees that it shall pay to the Developers the agreed upon sum of Insert Total Payment Amount in cash bank draft certified funds or credit card payment as applicable which is agreed and understood to be non refundable in the event of termination or cancellation of this Agreement consideration referred to in this section is for the Developers initial development proposal and other preparatory works which is agreed to by the parties as necessary to this Agreement of which said amount upon completion of the Web Site shall represent partial payment towards the total contract amount.

3 Upon the Developers completing each Web Site Milestone the Customer shall pay to the Developers such amount representing percentage of the total contract price as specified in Schedule and thereafter in the same percentage at each Milestone as set out in the Schedule to this Agreement. 3 In the event that the Customer fails to make any of the scheduled Web Site Milestone payments by the deadlines set forth in Schedule the Developers reserve the sole and exclusive right but are not obligated to retain all monies paid to date without refund and all Materials related to the development of the Web Site notwithstanding the Web Site has not been completed and to pursue any and all legal and other remedies at its disposal including but not limited to the following. a to terminate the Agreement and retain all monies paid to date b to pull disable disassemble block or otherwise make unusable the Web Site and associated links without notice to the Customer and to retain full and complete ownership thereof c to transfer the Web Site contents to another Customer for valuable consideration

d to commence legal action for damages and or injunctive relief and all legal costs on solicitor and customer basis and e to charge the Customer interest at rate of 2% per month or 26. 8% per year on amounts outstanding. 4. Terms and Conditions. 4 Development of Web Site. The Developers agree to develop the Web Site according to the terms listed in Schedule attached hereto.

4 Specifications. The Developers agree to develop the Web Site pursuant to the specifications set forth in Schedule attached hereto the Specifications 4 Delivery of Web Site. The Developers will use commercially reasonable efforts and reasonable diligence in the development of the Web Site and endeavor to deliver to the Customer Web Site in accordance with the Specifications by delivery date. Notwithstanding the aforesaid delivery date the Customer acknowledges and agrees that this delivery deadline and the corresponding progress payments thereto as listed in Schedule are estimates and are not time of the essence required delivery dates. Where commercially reasonable the Customer and the Developers will revise delivery schedules acknowledged by the parties in writing. 4 Proprietary Ownership Rights. The Customer agrees that the Web Site is and remains the exclusive property of the Developers and that the Developers shall retain title to and hold all rights and interest in and to all software developed by the Developers and the Web Site and copies thereof as may be applicable notwithstanding the granting of any license in respect of the use thereof. The Customer acknowledges that it receives no title or ownership rights in or to any of the intellectual property rights in the software. Specifically but without limitation the Customer agrees that the Developers shall hold all right title and interest in and to.

a all text graphics animation audio components and digital components of the Web Site the Content b all interfaces navigational devices menus menu structures or arrangements icons help and other operational instructions software and all other components of any source or object computer code that comprises the Web Site c all literal and non literal expressions of ideas that operate cause create direct manipulate access or otherwise affect the Content and d all copyrights patents trade secrets and other intellectual or industrial property rights in the Web Site or any component or characteristic thereof. The Customer further agrees that it shall not do anything that may infringe upon or in any way undermine Developers right title and interest in the Web Site as described in this paragraph. The Customer shall retain all of its intellectual property rights in any text images or other components it provides to the Developers for use in the Web Site. The Customer shall hold the copyright for the agreed upon version of the Web Site as delivered and the Customers copyright notice may be displayed in the completed Web Site upon receipt of payment by the Developers of all amounts due and owing to the Developers under this Agreement. 4 Confidentiality. Without limiting the above the Customer and the Developers acknowledge and agree that the Specifications and all other documents and information related to the development of the Web Site provided by the Developers the Confidential Information are confidential and constitutes valuable trade secrets of the Developers. The Customer shall keep the Confidential Information in confidence and shall not at any time during or after the term of this Agreement without the Developers prior written consent disclose or otherwise make available to anyone either directly or indirectly all or any part of the Confidential Information. Excluded from the Confidential Information definition is anything that can be seen by the public on the Web Site when each page of the Web Site is first accessed. The performance by the Customer of the foregoing obligations is condition to the Developers developing the Web Site for the Customer and the use thereof by the Customer. 5. Limited Warranty and Limitation on Damages.

The Developers warrant the Web Site will conform to the Specifications as set out herein for period of days from acceptance. If the Web Site does not materially conform to the Specifications the Developers shall be responsible to correct the Web Site without unreasonable delay at the Developers sole expense and without charge to the Customer to bring the Web Site into material conformance with the Specifications. This warranty shall be the exclusive warranty available to the Customer in respect of the Web Site conforming to the Specifications regardless of whether any remedy set forth herein fails of its essential purpose or otherwise. The Customer hereby waives any other warranty condition or representation express or implied statutory or otherwise including without limitation any implied warranties of merchantability and fitness for particular purpose. The Customer acknowledges that the Developers do not represent or warrant that the Web Site will work on all platforms or that the Web Site will be error free or that the Developers will be able to achieve fixes or workarounds for every problem or error discovered. The Customer acknowledges that the Developers are not responsible for the results obtained by the Customer on the Web Site. Under no circumstance will the Developers be liable to the Customer for any claim for damages of any kind direct or indirect special incidental consequential punitive or tort damages including negligence whether resulting from loss of use delay of delivery loss of data loss of anticipated profits loss of business non operation or increased expense of operation or otherwise and agrees that its sole and exclusive remedy for damages either in contract or tort is the return of the consideration paid to Developers as set forth in Schedule and in no event shall the Developers total cumulative liability hereunder from all causes of action of any kind exceed the total amount paid by the Customer to the Developers. The Customer further agrees to indemnify the Developers from and against any loss claim liability damage cost or expense including legal fees payable to any person or entity arising out of the use of the Web Site. 6. Independent Contractor. The Developers agree that they are retained as independent contractors and not as employees associates joint venture partners or legal representatives of the Customer. It is the intention of the parties that the Developers will be fully responsible for payment of all withholding taxes including but not limited to; their own provincial and federal income taxes Canada Pension Plan on all compensation earned and paid under this Agreement. The parties agree that the Customer will not withhold or pay any income tax Workers Compensation Board Assessments contributions or any other similar charges in respect of the Developers personnel and any other payroll taxes on the Developers behalf. The Developers understand and agree that they will not be entitled to any employee benefits that the Customer provides for its employees generally or to any statutory employment benefits including without limitation company pension plans profit sharing plans workers compensation or employment insurance. The Developers agree to indemnify the Customer for any and all claims made by any lawful government authority for all statutory withholding taxes and deductions not paid by the Developers and claimed against the Customer for monies paid pursuant to this Agreement and remitted thereto by the Customer to such authority or claims against the Customer from the Developers partners associates and employees. 7. Equipment. The Customer agrees to make available to the Developers for the Developers use in performing the services required by this Agreement such items of hardware and software as the Customer and the Developers may agree are reasonably necessary for such purpose. 8. General Provisions. 8 Entire Agreement. This Agreement constitutes the entire agreement between the parties pertaining to the subject matter hereof and supersedes all prior agreements understandings negotiations and discussions whether oral or written of the parties and there are no warranties representations or other agreements between the parties in connection with the subject matter except as specifically set out herein. No supplement modification amendment waiver or termination of this agreement will be valid or binding unless executed in writing by the parties.

How do you write a Software Testing Plan document? (alternate or related contract document)

Software Testing Plan STP THE STP PROJECT DOCMENT TITLE Author Title company name current date

Document Version Control Information V 1. 0 1. Introduction 1 Purpose of this document Objectives Insert the purpose of this document its objectives and its intended audience. 1 Scope of document

Insert description of the scope of this Software Testing Plan 1. 21 Scope Constraints Insert constraints such as schedules costs interactions overview or any other information relevant to the testing of the development requirements. 1 Overview Insert an overview or brief description of the product software or other desired end result that is being tested under this Software Testing Plan. 1 Business Context Insert an overview of the business or organization desiring the development of this project. Include the business or organizations mission statement and its organizational goals and objectives. Note. If you have already completed Software Requirements Specification the majority of this material is copied verbatim from that document. The purpose of this preamble is to familiarize staff recently attached to the testing portion of project who may not have been present or involved with earlier stages of the project. 1 Testing Strategy

Insert general overview of the strategy and plan for meeting the testing deliverables. Describe the levels of testing that will need to take place and the type of testing activities. more detailed outline will be provided further on in this document. If there are specific tests that need to follow their own STP you can describe them in an additional document separate from this main document. A Testing Strategy Outline will include. * The individual items to be tested * The purpose for testing those items * The individual features to be tested * The individual features NOT to be tested * The managerial and technical approach to testing * The criteria for pass and failure of testing * The individual roles or responsibilities of participants in testing

* The milestones and deliverables required for testing * The schedules and timelines for individual tests or the Software Testing Plan as whole * The risk assumptions and constraints placed upon the Software Testing Plan. 1 References and Reference Material Insert list of all reference documents and other materials related to the Software Testing Plan. References will often include but are not limited to. * Software Requirements Specifications

* Software Development Plan * Software Quality Assurance Plan * Software Management Plan * Project Outline and Management Plan 1 Documentation Items Insert references to documentation including but not limited to. * Software Requirements Specification SRS * Software Design Specification SDS

* Software Development Plan SDP * Software Installation Guide * Software Users Guide * Software Features Guide * Software Bug Error Correction or Defect Removal Guide 2. Items to be Tested 2 Program Modules Insert description of the testing to be performed for each module that the software contains.

2 Job Control Procedures Insert description of the procedures to be followed for testing the job control language JCL including scheduling for production control and all job sequencing. This section should include all the relationships between the above mentioned items in the Program Modules section. 2 User Procedures Insert description of the testing to be conducted on user documentation and support resources online or printed to ensure that they are complete and comprehensive. 2 Operator Procedures Insert description of the testing procedures to be conducted to ensure that the software can be run and supported within production environment as intended and that any Help Desk or other support services outlined in the plan can be verified as effective and meeting the intended support outcomes as outlined in the goal of the Software Testing Plan. 2 Features to be Tested

Insert the objectives and requirements for features that are being tested in this Software Testing Plan. 2 Features Not to be Tested Insert the objectives and requirements for features that are NOT being tested in this Software Testing Plan 3 Approach Insert the objectives and requirements for the overall approach to testing. The approach should cover such major tasks as the identification of time estimates for each element of the Software Testing Plan. Identify the different types of testing and describe their testing methods and the criteria for evaluating such testing. Your Software Testing Plan may contain several different approaches for certain elements. 3 Component Testing Insert the objectives and requirements to verify the implementation integrity and functionality for single unit component module or group of individual software elements or components. Component Testing is performed to verify that the individual component or group of components is complete and functioning as intended. 3 Integration Testing Insert the objectives and requirements to verify the implementation integrity and functionality for combined units such as individual software units components or group of individual software elements or components that has been combined with hardware elements. Integration testing is important to ensure that the software is functional as whole within the environment it is intended to run. The Integration Testing is performed to ensure that all operational requirements are met.

3 Conversion Testing Insert the objectives and requirements for testing that all historical data elements convert or are compatible with the new system. Conversion testing is required only if the software is an upgrade of an older system or will use or manipulate data from other systems. 3 Job Stream Testing Insert the objectives and requirements for testing that the software operates correctly in the production environment. 3 Interface Testing Insert the objectives and requirements for testing that the software operates correctly with all user interface and input systems. 3 Recovery Testing Insert the objectives and requirements for testing that the softwares recovery and restore operations function correctly and all backup systems and procedures work as intended in the production environment. 3 Performance Testing

Insert the objectives and requirements for testing that the software operates correctly in regards to normal operation response and execution times scalability portability and all other performance requirements within the production environment. 3 Regression Testing Insert the objectives and requirements for testing that any changes applied to the software do not affect functions previously tested. 3 Acceptance Testing Insert the objectives and requirements for testing that the software or system meets all criteria and deliverables. The Acceptance Testing is important to ensure that all requirements are met and that all components modules hardware requirements and recovery and restore operations function in the production environment and that plan exists to demonstrate such functionality for customer. 3. 10 Alpha Beta and Release Candidate RC Testing Insert the objectives and requirements for testing that will be done by customer to verify that the software meets all deliverables and requirements from the Software Requirements Specifications SRS or the Software Development Plan SDP and to detect any errors bugs or defects in the software.

4. Pass and Failure Criteria This section describes the criteria to determine whether specific item has passed or failed particular test. 4 Criteria for Suspension This section will describe the criteria for suspending an individual element or group of elements for particular testing activity. 4 Criteria for Resumption of Testing This section will describe the criteria for resuming testing for an individual element or group of elements that has been previously suspended. 4 Criteria for Approval of Testing This section will describe the criteria for acceptance and approval for an individual element or group of elements.

5. Testing Process and Methods Insert the specific testing process and methods to be used in performing each testing activity. In this section you will describe and define each type of test that the Software Testing Plan contains. You may attach additional exhibits to this section if your testing plan requires them. 6. Test Deliverables Insert the specific deliverables and documents that are to be delivered from the testing process. Test deliverables may include incremental data or data derived from incomplete tests. Typical test deliverables include but are not limited to. * Individual Test Element or Module Summary Reports * Group Element or Module Summary Reports * Individual and Combined Test Logs

* Test Metrics and Benchmark Reports * Test Input and Output Reports * Test Incident Reports 7. Testing Task and Requirements List A description of tasks and the skills required for performing testing as part of the deliverables.

Examples. 7 Task Name Insert description here. 7 Responsibility for Task Insert description here. 7 Resources Required for Task Insert description here. 7 Schedule or Timeline for Task Insert description here.

8. Testing Hardware and Environmental Requirements List A description of the hardware and environmental requirements for performing testing as part of the deliverables. Examples. 8 Hardware Requirement Name Insert description here. 8 Software Requirement Name Insert description here. 8 Security Resources Requirement Name Insert description here.

8 Specific Tools Requirement Name Insert description here. 8 Specific Documentation Requirement Name Insert description here. 8 Specific Risks and Assumptions Insert description here. Focus on restraints such as resource availability time constraints staff and developer availability and all other external factors that can influence testing.

8. 61 Risk and Assumption Contingency Plan Insert description of the contingency plan for each item listed above. 9. Change Request and Management A description of the Software Testing Plan change request and change management procedure. Describe the process that must be followed for submission review and authorization for all requests for change to the Software Testing Plan or any change to any part of the deliverables. 10. Approval for Software Testing Plan A description of the personnel authorized to approve the Software Testing Plan. Their Name Title and signature must accompany this document.

approved approver Title Date when the contact was signed approved approver Title Date when the contact was signed

approved approver Title Date when the contact was signed approved approver Title Date when the contact was signed 11. Appendices A description of all other supporting information required for the understanding and execution of the Software Testing plan and requirements. All Software Testing Plan documents require the following two appendices.

11 Definitions Acronyms Abbreviations A description of the definition of important terms abbreviations and acronyms. This may also include Glossary of terms. 11 References A listing of all citations to all documents and meetings referenced or used in the preparation of this Software Testing Plan and testing requirements document. Customer Initials Developer Initials

A Document from Contract Pack

The editable Web Development Contract (Developer Centered) (Canada) template - complete with the actual formatting and layout is available in the retail Contract Packs.
Proposal Kit on BBB
Proposal Kit
Proposal Kit on FaceBook
Create winning business proposals & contracts with minimal effort and cost. Downloadable proposal software, proposal templates, legal contracts and sample proposals.
© 1997 - 2018, Proposal Kit, Inc. All rights reserved.
Proposal Kit

Create winning business proposals & contracts with minimal effort and cost. Proposal software, proposal templates, legal contracts and sample proposals.