Legal Contract Templates Reprint Rights Agreement

How do you write a Reprint Rights Agreement document?

REPRINT RIGHTS AGREEMENT DATE. current date Order #. WorkOrder Job Job title of signator authorized signature or signer. Insert the Job Description Here I the undersigned being duly authorized and having the right to grant reproduction rights to company name do hereby request that company name reprint the following materials as described below. In consideration of the agreement by company name to reproduce or reprint the materials agree to the following terms and conditions. Nothing in the works and materials listed above and or submitted to company name for reprint contains any content that infringes or violates any intellectual property rights of any third party or author. Further nothing contained within the work or materials or any part or operation of the materials will cause the use reproduction resale or transfer of the rights to the materials to infringe upon the intellectual property rights of any third party.

Nothing in the works and materials will result in the violation of any local state federal international or any other jurisdiction under which the reproduction or reprinting of such materials would constitute an unlawful civil or criminal offense. company name has no obligation to review edit censor or otherwise certify the materials to ensure they comply with applicable law. I hereby release and discharge company name and its agents representatives and assigns from any and all claims and demands arising out of or in connection with the reprint of the materials including without limitation any and all claims for copyright or trademark violation invasion of privacy right of publicity slander libel or defamation. further agree to defend company name for all liabilities damages judgments costs or expenses arising out of company name being made part of any claim arising out of the reproduction and reprinting of the materials listed above. Signature. Printed Name. Company. Job title of signator authorized signature or signer. Dated. Note all fields are required to be completed.

Writing the Syndication Contract document (alternate or related contract document)

SYNDICATION AGREEMENT THIS AGREEMENT is made this current day day of current month current year by and between company name Company and company name Syndicatee The purpose of this Agreement hereafter referred to as the Agreement is to define long term contract arrangement under which Syndicatee will provide Syndication services on behalf of Company. As service the standard Syndication agreement with Company is provided below. 1. Definitions. Content shall mean all code that Company makes available to Syndicatee under this Agreement. Content includes but is not limited to. computer source code text articles utilities graphics logos and all other content made available or directly provided to Syndicatee by Company. Company Branding shall mean all logos graphics and content provided to Syndicatee that contains Company Trademarks Servicemarks or other content that cannot be edited or altered in any format by Syndicatee.

2. Grant of Rights. Subject to the terms and conditions of this Agreement Company grants Syndicatee non exclusive right to display on its web site all content made available to Syndicatee by Company. 3. Representation. Syndicatee shall maintain sales office for product promotion and is responsible for all costs incurred for the promotion and sale of Company products and services. Syndicatee shall conduct business in its own name and shall not represent itself as an employee or agent of Company. Prospects may be registered with Company and will be protected for days. This protection may be renewed at Companys discretion for further days. 4. Restrictions. End user pricing and Syndicatee compensation are outlined in Exhibit attached and are subject to change at the sole discretion of Company.

5. Compensation. Terms of payment are C. O. D. unless credit approval has been granted by Company. If credit approval has been granted credit terms are net days upon receipt of invoice. Company reserves the right to revoke any credit extended if payment is in arrears or delinquent for more than days. 6. Nondisclosure. Proprietary information exchanged hereforth shall be treated as such by Syndicatee and held in the strictest of confidence. This information shall include but is not limited to the provisions outlined in this Agreement product and services information pricing source code company practices methodology and procedures. Syndicatee further agrees not to edit alter distribute decompose disassemble decode or reverse engineer any Company content delivered to Syndicatee or any portion thereof without prior written approval of Company. 7. Transfer of Rights. Syndicatee may not assign or transfer this Agreement in whole or in part without the prior written consent of Company. Syndicatee may not sublicense any of the content to any third party unless otherwise agreed upon in writing by Company. Examples of improper sublicensing include but are not limited to. contractors affiliates partners web site visitors or any other third party to whom Syndicatee transfers or allows the transfer of Company content. In the event that Syndicatee contemplates whole or partial sale of its business ownership change or change in its jurisdiction Syndicatee shall notify Company by email facsimile or email no less than sixty days prior to the effective date of the event.

8. Term of Agreement. The term of this Agreement is twelve months from the date of execution by Company. This Agreement shall be continuously renewed every twelve months unless Syndicatee notifies Company in writing thirty days prior to the expiration date. 9. Termination. Company may terminate this Agreement at its sole discretion upon the occurrence of one or more of the following events. failure to comply with any provisions of the Agreement upon receipt of written notice from Company of said failure appointment of Receiver or upon the filing of any application by Syndicatee seeking relief from creditors upon mutual agreement in writing by Company and Syndicatee. 10. Disputes. If legal proceedings are commenced to resolve dispute arising out of or relating to this Agreement the prevailing party shall be entitled to recover all costs legal fees and expert witness fees as well as any costs or legal fees in connection with any appeals. 11. Indemnification. Syndicatee shall indemnify and hold Company harmless from and against any and all claims judgments awards costs expenses damages and liabilities including reasonable attorney fees of whatsoever kind and nature that may be asserted granted or imposed against Company directly or indirectly arising from or in connection with Syndicatees marketing or support services of the product or services or the unauthorized representation of the product and services or any breach of this Agreement by Syndicatee.

12. Limited Warranty. Companys only responsibility to Syndicatee concerning content tolls utilities or other materials made available under this Agreement will be to use reasonable efforts consistent with industry standards to cure any defects errors or omissions brought to Companys attention. 13. Force Majeure. Neither party shall be held responsible for delay or failure in performance hereunder caused by acts of nature strikes embargoes fires war or other causes beyond their reasonable control. 14. Binding Effect.

If any provision of this Agreement is held to be unenforceable the enforceability of the remaining provisions shall in no way be affected or impaired thereby. This agreement and any disputes arising hereunder shall be governed by the laws of state or province state without regard to conflicts of law principles. failure by any party to exercise or delay in exercising right or power conferred upon it in this Agreement shall not operate as waiver of any such right or power. The parties represent and warrant that on the date first written above they are authorized to enter into this Agreement in its entirety and duly bind their respective principals by their signatures below. EXECUTED as of the date first written above. company name By signator authorized signature or signer. Job title of signator authorized signature or signer.

Date when the contact was signed company name By signator authorized signature or signer. Job title of signator authorized signature or signer. Date when the contact was signed

Syndicatee Initials Company Initials

How to write my Photo Reprint Rights Agreement document (alternate or related contract document)

PHOTO REPRINT RIGHTS RELEASE DATE. current date Order #. WorkOrder Job Job title of signator authorized signature or signer. Insert Job Description here Photographer or Agency Name. company name address address city state or province zip or postal code Phone. phone number Photo Description. Format Provided. I the undersigned being duly authorized and having the right to grant reproduction rights to do hereby request you reprint the following materials as described below.

Authorized Signature. Date when the contact was signed Job title of signator authorized signature or signer. Note all fields are required to be completed.

How do you write a Permission to Reprint Testimonial Agreement document? (example of another included contract document)

PERMISSION TO QUOTE Declarations company name Grantee is requesting permission from contract first name contract last name Author for the right to reprint reproduce and republish the following Testimonial the Material for use in Insert Reprint Location Advertising Broadcasting Publishing by the Grantee. Agreements Permission is granted to Grantee for non exclusive world rights in all languages for use of the material listed below received in the format of Testimonial by contract first name contract last name Author and for any promotional or subsidiary usage future revisions and future editions of the same. Material. Include the full quote to be used. Insert full text of quote to be reprinted here. Contribution credits will read as follows.

Examples. Dr. John Doe Title Imaginary University In witness whereof the parties have executed this Agreement this current day day of current month current year. Author. Job title of signator authorized signature or signer. Grantee.

Job title of signator authorized signature or signer.

How to write my Permission to Link Agreement document (example of another included contract document)

PERMISSION TO LINK company name Grantor has Web site located at web site domain URL Grantors Web site web site URL Grantee has Web site located at Grantees Web site Agreements 1 Grantor hereby grants Grantee permission to provide hypertext link from Grantees Web site to the home page of Grantors Web site. 2 Neither party shall be liable to the other party for the content of its Web site or links on its Web site to other Web sites. 3 Grantee acknowledges that Grantor may terminate this Permission at any time with or without cause by giving notice to Grantee. Grantee must remove the hypertext link to Grantees Web site within days days of receiving such notice.

4 This Agreement is governed by the laws of the State of state or province excluding its conflict of laws principles. 5 This Agreement is the entire understanding between the parties relating to the link referenced here and supersedes all prior or contemporaneous understandings whether written or oral. In witness whereof the parties have executed this Agreement this current day day of current month current year. Grantor Job title of signator authorized signature or signer. Grantee Job title of signator authorized signature or signer.

Writing the Software Testing Plan document (example of another included 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