Documenting Defects Clause Samples

The 'Documenting Defects' clause establishes the requirement for parties to formally record and report any defects identified in goods, services, or works provided under the contract. Typically, this involves specifying the process for notifying the other party of a defect, including the format, timeframe, and necessary supporting information such as photographs or detailed descriptions. By clearly outlining how defects should be documented, this clause ensures that issues are promptly and accurately communicated, which helps facilitate timely resolution and reduces disputes over the existence or nature of defects.
POPULAR SAMPLE Copied 1 times
Documenting Defects. Purchaser must document all Defects in writing with sufficient information to recreate the Defect or otherwise clearly and convincingly document or evidence its occurrence, including, but not limited to, the operating environment, data set, user, or any other such information that Tyler may reasonably request. Purchaser shall deliver such information to Tyler concurrently with its notification to Tyler of a Defect. Purchaser shall use all reasonable efforts to eliminate any non-application related issues prior to its notification to Tyler of such Defect, including, but not limited to, issues related to the network, user training, Purchaser-produced extensions, and data problems not caused by the Licensed Software. Any technical or other issue for which Purchaser requests services, but which is not a Documented Defect, shall be treated as a request for other services and governed by Section 4.
View SourceView Similar (2)
Documenting Defects. End User must document all Defects in writing with sufficient information to recreate the Defect or otherwise clearly and convincingly document or evidence its occurrence, including, but not limited to, the operating environment, data set, user, or any other such information that Tyler may reasonably request. End User shall deliver such information to Tyler concurrently with its notification to Tyler of a Defect. End User shall use all reasonable efforts to eliminate any non-application related issues prior to its notification to Tyler of such Defect, including, but not limited to, issues related to the network, user training, End User- produced extensions, and data problems not caused by the Licensed Software. Any technical or other issue for which End User requests services, but which is not a Documented Defect, shall be treated as a request for other services and governed by Section 4.
View Source
Documenting Defects. End User must document all Defects in writing with sufficient information to recreate the Defect or otherwise clearly and convincingly document or evidence its occurrence, including, but not limited to, the operating environment, data set, user, or any other such (a) ▇▇▇▇▇ shall provide End User with procedures for contacting support staff during normal business hours (8:30 a.m. to 5:00 p.m., Central Time, Monday through Friday, excluding national holidays) for reporting Documented Defects. ▇▇▇▇▇ shall assist End User in the diagnosis of any Documented Defect, including the assigned Service Level and ▇▇▇▇▇’▇ tracking number. (b) For each reported Documented Defect, ▇▇▇▇▇ shall assign appropriate personnel to diagnose and correct the Documented Defect, and where appropriate, identify Circumvention Procedures. ▇▇▇▇▇’▇ initial response shall include an acknowledgement of notice of the Documented Defect, confirmation that ▇▇▇▇▇ has received sufficient information concerning the Documented Defect, and an action plan for resolving the Documented Defect and avoiding further deleterious consequences of the Documented Defect.
View Source

Related to Documenting Defects

  • Reportable Events Involving the ▇▇▇▇▇ Law Notwithstanding the reporting requirements outlined above, any Reportable Event that involves solely a probable violation of section 1877 of the Social Security Act, 42 U.S.C. §1395nn (the ▇▇▇▇▇ Law) should be submitted by Practitioner to CMS through the self-referral disclosure protocol (SRDP), with a copy to the OIG. If Practitioner identifies a probable violation of the ▇▇▇▇▇ Law and repays the applicable Overpayment directly to the CMS contractor, then Practitioner is not required by this Section III.G to submit the Reportable Event to CMS through the SRDP.

  • LIABILITY FOR FAILURE TO COMPLETE TRANSACTIONS If We do not

  • Our Liability for Failure to Complete Transactions If we do not properly complete a transaction from your Card on time or in the correct amount according to our Agreement with you, we will be liable for your losses or damages. However, there are some exceptions. We will not be liable, for instance:

  • Cost of remedying Defects Any repair or rectification undertaken in accordance with the provisions of Clause 17.2, including any additional testing, shall be carried out by the Contractor at its own risk and cost, to the extent that such rectification or repair is attributable to: (a) the design of the Project; (b) Plant, Materials or workmanship not being in accordance with this Agreement and the Specifications and Standards; (c) improper maintenance during construction of the Project Highway by the Contractor; and/ or (d) failure by the Contractor to comply with any other obligation under this Agreement.

  • DEFECT LIABILITY It is agreed that in case any structural defect or any other defect in workmanship, quality or provision of services or any other obligations of the Promoter as per the agreement for sale relating to such development is brought to the notice of the Promoter within a period of 5 (five) years by the Allottee from the date of handing over possession, it shall be the duty of the Promoter to rectify such defects without further charge, within 30 (thirty) days, and in the event of Promoter's failure to rectify such defects within such time, the aggrieved Allottees shall be entitled to receive appropriate compensation in the manner as provided under the Act.