Legal Contract Templates Project Consulting Override

How do you write a Project Consulting Override document?

company name Project Consulting Override company name address address city state or province zip or postal code Phone. phone number Fax. fax number DATE. current date Order contract reference number

Customer. company name address address city state or province zip or postal code Phone. phone number Fax. fax number For. General Description of Project Deliverables

company name arrives at its consulting solutions using the best available science company name experience and marketing practices. Before continuing any additional work for the benefit of the Customer Customer acknowledges that it has received the following consulting and recommendations concerning the development of the project from company name and has requested that company name implement solution other than what was recommended by company name. Further company name understands that any estimates provided to them prior to the date on this agreement may require revisions and or adjustments to the pricing based on the different solutions chosen by company name. Please initial the following sections which detail the projects deliverables contracted between company name and company name and sign the Acceptance of Agreement at the bottom of this document. Initials Description of Recommendation Recommendation description here

Recommendation description here Recommendation description here Recommendation description here Recommendation description here ACCEPTANCE OF AGREEMENT. I certify that have read and understand the above Project Consulting Override from company name and that all questions or concerns that may have regarding the above have been adequately answered by company name to company names satisfaction. further certify and release company name from any damages whether direct or indirect as well as any obligation or duty to correct problems arising out of or contributed to by company names decision to implement solution or strategy other than that which was suggested by company name while acting as consultant to company name unless otherwise agreed upon in writing. I understand that by signing this agreement release company name from any and all liability tort or claim concerning this change to the project. Customers signature Title Date

Companys signature Title Date

How to write my Contract Change Form (During Development) document (alternate or related contract document)

company name Contract Addendum company name address address

city state or province zip or postal code Phone phone number Fax fax number DATE. current date Order contract reference number Bill To. company name address address

city state or province zip or postal code Phone phone number Fax fax number For. Invoice. Product and or Service Addendum. Contract #contract reference number Additional Services The following is request to amend the previous established and contracted relationship between company name and company name and is to act as an addendum to any existing contract or relationship established between the two parties. Authorized changes may also impact delivery dates and milestones. The undersigned party desires company name to provide the following additional goods and services. Total. Delivery Date Milestone Impact. Entire Agreement. This Agreement contains the entire Agreement between the parties relating to the subject matter hereof and supersedes any and all prior agreements or understandings written or oral between the parties related to the subject matter hereof. No modification of this Agreement shall be valid unless made in writing and signed by both of the parties hereto.

Binding Effect. This Agreement shall be binding upon and inure to the benefit of Customer and Developers and their respective successors and assigns provided that Developers may not assign any of his obligations under this Agreement without Customers prior written consent. PAYMENT TERMS. Net days. 1. 5% Interest monthly on accounts past due days. ACCEPTANCE OF AGREEMENT. The above prices specifications and conditions are hereby accepted. The designer is authorized to execute the project or provide software as outlined in this Agreement. Payment will be made as proposed above. Customers signature Title Date Developers signature Title Date

How do you write a Milestone Waiver Agreement document? (example of another included contract document)

company name Milestone Waiver Agreement address address city state or province zip or postal code Phone phone number DATE. current date Order WorkOrder

Client. company name city state or province zip or postal code Phone phone number For. Description of project milestone deliverable to be waived This agreement entered into by and between company name and company name hereby amends agreement WorkOrder as follows.

company name agrees to waive the following milestone and deliveribles and release company name from any further contractual obligation. Initials Description of Waived Milestone Description of Project Milestone Deliverable to be waived Insert Milestone number here Insert rights and remedies and any information pertaining to alteration of payments concerning this milestone or deliverables Description of Project Milestone Deliverable to be waived Insert Milestone number here Insert rights and remedies and any information pertaining to alteration of payments concerning this milestone or deliverables Description of Project Milestone Deliverable to be waived Insert Milestone number here Insert rights and remedies and any information pertaining to alteration of payments concerning this milestone or deliverables Description of Project Milestone Deliverable to be waived Insert Milestone number here Insert rights and remedies and any information pertaining to alteration of payments concerning this milestone or deliverables Description of Project Milestone Deliverable to be waived Insert Milestone number here Insert rights and remedies and any information pertaining to alteration of payments concerning this milestone or deliverables ACCEPTANCE OF AGREEMENT. I certify that the aforementioned milestones and or deliverables required under the agreement listed on this document have hereby been waived and release company name from any requirement to demonstrate deliver or otherwise complete to my satisfaction in order to fulfill the terms and conditions in aforementioned agreement #. Clients signature

Writing the Software Requirements Specifications document (example of another included contract document)

Software Requirements Specification SRS THE SRS PROJECT DOCUMENT TITLE Author Title company name

current date Document Version Control Information V 1. 0 1. Introduction. 1 Purpose of This Document. Insert the purpose of this document and its intended audience. 1 Scope of Document. Insert description of the scope of this Software Requirement Specification

1. 21 Scope Constraints. Insert constraints such as schedules costs interactions overview or any other information relevant to the construction of the development requirements. 1 Overview. Insert an overview or brief description of the product software or other desired end result. 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. 2. General Description. 2 Product Functions.

Insert description of the functionality of the product. 2 Similar System Information. Insert description of the relationship between this product and any other product or product ; whether the product shall be stand alone product or whether the product shall be used as component or to support another program or programs. This section is intended to discuss the relationships between the above mentioned items. 2 User Characteristics. Insert description of the characteristics of the typical user or user community that this product serves or will serve. Include features that the user or user community currently uses or expects. Include current relevant features and describe the expected experience level and familiarity with similar software systems applications or other programs and program use. 2 User Problem Statement.

Insert user problem statement that describes the essential problem currently being faced by the intended user community. 2 User Objectives. Insert the objectives and requirements for the product from the users perspective. The user objectives section may also include wish list of features or functionality that the user want and how that relates to the business context 2 General Constraints. Insert the general constraints placed upon the developers including hardware requirements schedule requirements industry protocols or standards to be met or any other constraint placed upon the development of the product. 3. Functional Requirements. This section describes the functional requirements ranked in order of importance. Here you will describe what the product must accomplish; what other component requirements must accomplish; the requirements for Interface Scalability Performance Compatibility or other components of the product; and how the product fulfills these requirements. Each functional requirement should be specified in format similar to the following. Functional Requirement #1 Name

3 Description. complete description of the functional requirement. 3 Criticality. description of how critical this functional requirement is to the overall product. 3 Technical Issues. description of issues related to the design development or integration of this functional requirement. 3 Cost Summary and Schedules. description of the costs and timelines associated with this functional requirement.

3 Risks. description of the risks and possible circumstances under which this functional requirement may not be able to be met. Include provisions the developers must take in order to overcome this risk. 3 Dependencies with other requirements. description of the various interactions between this requirement and other functional requirements. Here you will insert statements concerning the impact of these dependencies and the impact on the ranking of requirements. Functional Requirement #2 Name Repeat the section above for more requirements. 4. Interface Requirements. This section describes both how the product will interface with other software products or dependencies or with end users for input and output.

4 User Interfaces. Describes how this the end user interfaces with the product. 4. Graphical User Interface GUI. Describes the graphical user interface or whether another system is required to provide the GUI. Include mock ups or screenshots of the user interface features. Describe all navigation systems hierarchy of menus sub menus buttons and all other relevant GUI features of the product. 4. Command Line Interface CLI. Describes the command line interface if present. For each command description of all arguments and example values and invocations should be provided. 4. Application Programming Interface API. Describes the application programming interface if present. For each public interface function the name arguments return values examples of invocation and interactions with other functions should be provided.

4. Debugging and Diagnostics. Describes the process required for the product to return troubleshooting debugging or other diagnostic data and feedback. 4 Hardware Interfaces. description of all interfaces to hardware or hardware devices. 4 Communications Interfaces.

description of all communication and network interfaces. 4 Software Interfaces. description of all software interfaces. 5. Performance Requirements. Insert specific performance requirements. 6. Design Constraints. Insert specific design constraints including compliance with specific standards and constraints on design due to hardware limitations.

7. Other Non Functional Attributes. A description of other non functional attributes required by the product. Examples. 7 Security. Insert the attributes description here. 7 Binary Compatibility. Insert the attributes description here.

7 Reliability. Insert the attributes description here. 7 Maintainability. Insert the attributes description here. 7 Portability. Insert the attributes description here.

7 Extensibility. Insert the attributes description here. 7 Reusability. Insert the attributes description here. 7 Application Compatibility. Insert the attributes description here.

7 Resource Utilization. Insert the attributes description here. 7. 10 Serviceability. Insert the attributes description here. 8. Preliminary Object Oriented Domain Analysis. A description or list of the fundamental objects required to be modeled within the product in order to satisfy its requirements. The goal is to create structural view on the requirements and how they may be satisfied. This section deals primarily with higher level programming and functional requirements AND may be safely omitted for projects not concerned with Object Oriented Domain Analysis OODA. This section should not be removed from your SRS Document. Instead you should include an entry such as. No Object Oriented Domain Analysis Requirement. 8 Inheritance Relationships.

description of primary inheritance hierarchy. Include diagrams graphs or other UML examples to further illustrate such relationships. 8 Class descriptions. description of each class identified during the OODA. Include more detailed description of each class. The description of each class should be organized as follows. 8. Insert the Class name identifier 8. 2. Abstract or Concrete. Indicates whether this class is abstract designed only as parent from which subclasses may be derived or concrete suitable to be instantiated.

8. 2. List of Superclasses. Lists the class from which another class subclass inherits. 8. 2. List of Subclasses. Lists the class that is derived from base class by inheritance. The new class contains all the features of the base class but may have new features added or existing features redefined. 8. 2. Purpose. Lists the purpose of the class. 8. 2. Collaborations. Lists the names of each class that this class must interact with and how it must interact in order to accomplish its purpose. 8. 2. Attributes.

Lists each attribute associated with each instance of this class and indicates examples of possible values or range of values. 8. 2. Operations. Lists each operation able to be invoked upon instances of this class. 8. 2. Constraints. Lists the constraints and restrictions upon the behavior of instances of this class. 9. Operational Scenarios. description of the various scenarios that an end user may experience when using the product under certain conditions or situations. Scenarios are not considered to be functional requirements rather they are used to help set parameters and expectations for the use of the product under these conditions or situations. 10. Preliminary Schedule.

description of the project schedule and timeline for completion. The project plan should include all major tasks who is responsible for the completion of such tasks what the interdependencies of each task are and what the start and completion of each task will be. You should also include vendor information and requirements of such that affect the schedule and timeline. 11. Preliminary Budget. description of the cost summary and an attachment of the initial line item and itemized budget for the project. 12. Appendices. A description of all other supporting information for understanding these requirements. All SRS documents require the following two appendices. 12 Definitions Acronyms Abbreviations.

description of the definitions of important terms abbreviations and acronyms. May also include Glossary. 12 References. listing of all citations to all documents and meetings referenced or used in the preparation of this requirements document. Customer Initials Developers Initials

How do you write a Project Additional Expense Form document? (example of another included contract document)

company name Project Additional Expense Form company name address address city state or province zip or postal code Phone. phone number Fax. fax number DATE. current date

Order contract reference number Customer. company name address address city state or province zip or postal code Phone. phone number Fax. fax number For. General Description of Project Scope Pursuant to Insert related clause in your original contract of our services contract the following is an accounting of the additional hours and costs that were outside of the original scope of work Specifications or that represent change requests to the original bid amount. Hours Cost Description of Additional Labor or Materials

Insert additional cost here. ACCEPTANCE OF ADDITIONAL EXPENSES. I certify that have read and understand the above project expenses presented by company name and approve of them. company name may add these to their final project billing. Customers signature Title Date

Writing the Contract Specifications Definitions document (example of another included contract document)

Specification Definitions Example attachment defining specification definitions for web site project Standard Page. * Uses our pre existing page templates completely custom pages will require more time. * Page body contains up to unique static GIF or JPG images requiring minimal work including but not limited to. scanning sizing cropping editing compressing. * to browser screens of text when viewed at 640x480 screen resolution. * Up to hyperlinks not including the page header and trailer site navigation hyperlinks * Includes the addition of basic navigation systems built into each page. Creation of the graphical menu bar with image slicing and rollovers is rolled into the base price per page. Keyword Splash Page.

* copy of the primary splash page that is tailored to specific key word of phrase. E commerce Solutions. * Level 1. Flat text file non interactive. * Level 2. page interactive form using email. * Level 3. Multi page interactive forms using email and or data files * Level 4. Multi page interactive forms using real time credit card processing. Level and allow for shopping cart product purchasing on any pages. Common Navigation Systems.

1. Graphical navigation bar with rollovers at head of each page. 2. Page header text navigation bar under the graphical navigation bar. 3. Text navigation bar at bottom of each page. 4. Site map page. 5. Help page. 6. Quick guide page.

7. Automated search component. 8. Index pages page of simple links to sub pages within the site 9. List traversal of series pages pages designed to be read one after the other 10. Hyperlinks to other pages. 11. Shallow tree 4 clicks max.

12. Consistent navigation across all pages.

How to write my Project Change Request Form (During Maintenance) document (example of another included contract document)

company name Change Order company name address address city state or province zip or postal code Phone phone number Fax fax number DATE. current date

Order contract reference number Bill To. company name address address city state or province zip or postal code Phone phone number Fax fax number For.

Invoice. Product and or Service Billing. Hourly. hourly rate Fixed Rate. FixedRate Other.

Please provide detailed description of the changes that you would like made to your project. Be as specific as possible. Provide the exact page frame location on the page frame and what corrections need to be made. To avoid duplication and confusion please list all of your corrections on this form. You may attach additional forms as necessary. Agreements PAYMENT TERMS. Net days. 1. 5% Interest monthly on accounts past due days. ACCEPTANCE OF AGREEMENT. The above prices specifications and conditions are hereby accepted. The designer is authorized to execute the project or provide software as outlined in this Agreement. Payment will be made as proposed above. Clients signature Title

Writing the Project Contract Acceptance Signoff Form document (example of another included contract document)

company name Project Acceptance Signoff address address city state or province zip or postal code Phone phone number DATE. current date Order WorkOrder Client.

company name city state or province zip or postal code Phone phone number For. General Description of Project Deliverables Please initial the following sections which detail the projects deliverables contracted between company name and company name and sign the Acceptance of Agreement at the bottom of this document. Initials Description of Completed Milestone Acceptance of Milestone #1 description here

Acceptance of Milestone #2 description here Acceptance of Milestone #3 description here Acceptance of Milestone #n description here Acceptance of Project per Contract Specifications. ACCEPTANCE OF AGREEMENT. I certify that have received the above project deliverables from company name and that the deliverables listed above have been demonstrated delivered or otherwise completed to my satisfaction. Best Practice Note. If billing by credit card the above line should include permission to charge their credit card. This helps reduce your chargeback exposure. Example. Florentine Design Group LLC may now charge the final installment of 390 to AMEX ************345 for completion of the project.

Clients signature