Common use of Incident Tracking Clause in Contracts

Incident Tracking. Every support incident is logged into our management system and given a unique incident number. This system tracks the history of each incident. The incident tracking number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident number, through the portal at Tyler’s website or by calling software support directly. Incident Priority Each incident is assigned a priority level, which corresponds to the client’s needs and deadlines. Tyler and the client will reasonably set the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client towards clearly understanding and communicating the importance of the issue and to describe generally expected response and resolution targets in the production environment only. References to a “confirmed support incident” mean that Tyler and the client have successfully validated the reported Defect/support incident. Priority Level Characteristics of Support Incident Resolution Targets 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business hour of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within one (1) business day. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of data. Tyler shall provide an initial response to Priority Level 2 incidents within four (4) business hours of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within ten (10) business days. For non-hosted customers, Tyler’s responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Level 2 incident that affects only one user or for which there is an existing circumvention procedure. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business day of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents without the need for a circumvention Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets procedure with the next published maintenance update or service pack, which shall occur at least monthly. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 4 Non- critical Support incident that causes failure of non-essential functionality or a cosmetic or other issue that does not qualify as any other Priority Level. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within two (2) business days of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents, as well as cosmetic issues, with a future version release. Remote Support Tool Some support calls may require further analysis of the client’s database, processes or setup to diagnose a problem or to assist with a question. Tyler will, at its discretion, use an industry-standard remote support tool. Tyler’s support team must have the ability to quickly connect to the client’s system and view the site’s setup, diagnose problems, or assist with screen navigation. More information about the remote support tool Tyler uses is available upon request. Exhibit D Exhibit D Third Party Terms We will make commercially reasonable efforts to minimize the need for you to rely on Third Party Software or Third Party Hardware in order to operate the Tyler Software. To the any such Third Party Product is required, you are responsible for purchasing, installing and configuring all Third Party Hardware and Third Party Software at your expense. We will make available a list of Third Party Software that will be required to load a new release of the Tyler Software, if any, as well as list of Third Party Software components that have been certified as compatible with the Tyler Software. We will have no liability for defects in the Third Party Hardware or Third Party Software. You are responsible for ensuring that you have current maintenance agreements with any Developers from whom you expect to receive maintenance and/or support on Third Party Software or Third Party Hardware. Exhibit E Exhibit E Statement of Work Exhibit E Statement of Work for Implementation of Tyler Jury Manager, Browser-based Jury Management System SaaS Implementation In Xxxxxxxxxx County, TX June 18, 2020 Tyler Technologies will implement Tyler Jury Manager in Xxxxxxxxxx County, TX under the following terms.

Incident Tracking. Every support incident is logged into our management system Tyler’s Customer Relationship Management System and given a unique incident number. This system tracks the history of each incident. The incident tracking number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident number, through the portal at Tyler’s website or by calling software support directly. Incident Priority Each incident is assigned a priority levelnumber, which corresponds to the client’s needs and deadlines. Tyler and the The client will is responsible for reasonably set setting the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client towards clearly understanding and communicating the importance of the issue and to describe generally expected response responses and resolution targets in the production environment only. References to a “confirmed support incident” mean that Tyler and the client have successfully validated the reported Defect/support incidentresolutions. Priority Level Characteristics of Support Incident Resolution Targets 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business hour of receipt of the support incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within one (1) business day. For non-non- hosted customers, Tyler’s responsibility for lost or corrupted data Data is limited to assisting the client in restoring its last available database. 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of dataData. Tyler shall provide an initial response to Priority Level 2 incidents within four (4) business hours of receipt of the support incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within ten (10) business days. For non-non- hosted customers, Tyler’s responsibility for loss or corrupted data Data is limited to assisting the client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Level 2 incident that affects only one user or for which there is an existing circumvention procedure. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business day of receipt of the support incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents without the need for a circumvention Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets procedure with the next published maintenance update or service pack, which shall occur at least monthly. For non-non- hosted customers, Tyler’s responsibility for lost or corrupted data Data is limited to assisting the client in restoring its last available database. 4 Non- critical Support incident that causes failure of non-essential functionality or a cosmetic or other issue that does not qualify as any other Priority Level. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within two (2) business days of receipt of the incidentdays. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents, as well as cosmetic issues, with a future version release. Remote Support Tool Some Incident Escalation Tyler Technology’s software support calls may require further analysis consists of the client’s database, processes or setup to diagnose a problem or to assist with a question. Tyler will, at its discretion, use an industry-standard remote support tool. Tyler’s support team must have the ability to quickly connect to the client’s system and view the site’s setup, diagnose problems, or assist with screen navigation. More information about the remote support tool Tyler uses is available upon request. Exhibit D Exhibit D Third Party Terms We will make commercially reasonable efforts to minimize the need for you to rely on Third Party Software or Third Party Hardware in order to operate the Tyler Software. To the any such Third Party Product is required, you are responsible for purchasing, installing and configuring all Third Party Hardware and Third Party Software at your expense. We will make available a list four levels of Third Party Software that will be required to load a new release of the Tyler Software, if any, as well as list of Third Party Software components that have been certified as compatible with the Tyler Software. We will have no liability for defects in the Third Party Hardware or Third Party Software. You are responsible for ensuring that you have current maintenance agreements with any Developers from whom you expect to receive maintenance and/or support on Third Party Software or Third Party Hardware. Exhibit E Exhibit E Statement of Work Exhibit E Statement of Work for Implementation of Tyler Jury Manager, Browser-based Jury Management System SaaS Implementation In Xxxxxxxxxx County, TX June 18, 2020 Tyler Technologies will implement Tyler Jury Manager in Xxxxxxxxxx County, TX under the following terms.personnel:

Incident Tracking. Every support incident is logged into our management system and given a unique incident number. This system tracks the history of each incident. The incident tracking number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident number, through the portal at Tyler’s website or by calling software support directly. Incident Priority Each incident is assigned a priority level, which corresponds to the client’s needs and deadlines. Tyler and the client will reasonably set the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client towards clearly understanding and communicating the importance of the issue and to describe generally expected response and resolution targets in the production environment only. References to a “confirmed support incident” mean that Tyler and the client have successfully validated the reported Defect/support incident. Priority Level Characteristics of Support Incident Resolution Targets 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business hour of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within one (1) business day. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of data. Tyler shall provide an initial response to Priority Level 2 incidents within four (4) business hours of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within ten (10) business days. For non-hosted customers, Tyler’s responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Level 2 incident that affects only one user or for which there is an existing circumvention procedure. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business day of receipt of the incident. Once the incident has Priority Level Characteristics of Support Incident Resolution Targets only one user or for which there is an existing circumvention procedure. been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents without the need for a circumvention Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets procedure with the next published maintenance update or service pack, which shall occur at least monthlyquarterly. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 4 Non- critical Support incident that causes failure of non-essential functionality or a cosmetic or other issue that does not qualify as any other Priority Level. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within two (2) business days of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents, as well as cosmetic issues, with a future version release. Remote Support Tool Some Incident Escalation Tyler Technologies’ software support calls may require further analysis consists of the client’s database, processes or setup to diagnose a problem or to assist with a question. Tyler will, at its discretion, use an industry-standard remote support tool. Tyler’s support team must have the ability to quickly connect to the client’s system and view the site’s setup, diagnose problems, or assist with screen navigation. More information about the remote support tool Tyler uses is available upon request. Exhibit D Exhibit D Third Party Terms We will make commercially reasonable efforts to minimize the need for you to rely on Third Party Software or Third Party Hardware in order to operate the Tyler Software. To the any such Third Party Product is required, you are responsible for purchasing, installing and configuring all Third Party Hardware and Third Party Software at your expense. We will make available a list of Third Party Software that will be required to load a new release of the Tyler Software, if any, as well as list of Third Party Software components that have been certified as compatible with the Tyler Software. We will have no liability for defects in the Third Party Hardware or Third Party Software. You are responsible for ensuring that you have current maintenance agreements with any Developers from whom you expect to receive maintenance and/or support on Third Party Software or Third Party Hardware. Exhibit E Exhibit E Statement of Work Exhibit E Statement of Work for Implementation of Tyler Jury Manager, Browser-based Jury Management System SaaS Implementation In Xxxxxxxxxx County, TX June 18, 2020 Tyler Technologies will implement Tyler Jury Manager in Xxxxxxxxxx County, TX under the following terms.following:

Incident Tracking. Every support incident is logged into our management system Xxxxx’x Customer Relationship Management System and given a unique incident case number. This system tracks the history of each incident. The incident tracking case number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident case number, through the portal at Tyler’s website Xxxxx’x Customer Portal or by calling software support directly. Incident Priority Each incident is assigned a priority level, which corresponds to the clientClient’s needs and deadlinesneeds. Tyler Xxxxx and the client Client will reasonably set the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client Client towards clearly understanding and communicating the importance of the issue and to describe generally expected response and resolution targets in the production environment only. References to a “confirmed support incident” mean that Tyler Xxxxx and the client Client have successfully validated the reported Defect/support incident. Priority Level Characteristics of Support Incident Resolution Targets Targets* 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler Xxxxx shall provide an initial response to Priority Xxxxx 0 Level 1 incidents within one (1) business hour of receipt of the incident. Once the incident has been confirmed, Tyler Xxxxx shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within one (1) business day. For non-hosted customers, Tyler’s Xxxxx’x responsibility for lost or corrupted data is limited to assisting the client Client in restoring its last available database. Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets* 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of data. Tyler Xxxxx shall provide an initial response to Priority Level 2 incidents within four (4) business hours of receipt of the incident. Once the incident has been confirmed, Tyler Xxxxx shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within ten (10) business days. For non-hosted customers, Tyler’s Xxxxx’x responsibility for loss or corrupted data is limited to assisting the client Client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Level 2 incident that affects only one user or for which there is an existing circumvention procedure. Tyler Xxxxx shall provide an initial response to Priority Xxxxx 0 Level 3 incidents within one (1) business day of receipt of the incident. Once the incident has been confirmed, Tyler Xxxxx shall use commercially reasonable efforts to resolve such support incidents without the need for a circumvention Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets procedure with the next published maintenance update or service pack, which shall occur at least monthlyquarterly. For non-hosted customers, Tyler’s Xxxxx’x responsibility for lost or corrupted data is limited to assisting the client Client in restoring its last available database. 4 Non- critical Support incident that causes failure of non-essential functionality or a cosmetic or other issue that does not qualify as any other Priority Level. Tyler Xxxxx shall provide an initial response to Priority Xxxxx 0 Level 4 incidents within two (2) business days of receipt of the incident. Once the incident has been confirmed, Tyler Xxxxx shall use commercially reasonable efforts to resolve such support incidents, as well as cosmetic issues, with a future version release. Remote Support Tool Some support calls *Response and Resolution Targets may require further analysis differ by product or business need Incident Escalation If Xxxxx is unable to resolve any priority level 1 or 2 defect as listed above or the priority of an issue has elevated since initiation, you may escalate the client’s database, processes or setup to diagnose a problem or to assist with a question. Tyler will, at its discretion, use an industry-standard remote support tool. Tyler’s support team must have the ability to quickly connect incident to the client’s system and view the site’s setup, diagnose problems, or assist with screen navigation. More information about the remote support tool Tyler uses is available upon request. Exhibit D Exhibit D Third Party Terms We will make commercially reasonable efforts to minimize the need for you to rely on Third Party Software or Third Party Hardware in order to operate the Tyler Software. To the any such Third Party Product is required, you are responsible for purchasing, installing and configuring all Third Party Hardware and Third Party Software at your expense. We will make available a list of Third Party Software that will be required to load a new release of the Tyler Software, if anyappropriate resource, as well as list of Third Party Software components that have been certified as compatible outlined by each product support team. The corresponding resource will meet with you and any Xxxxx staff to establish a mutually agreeable plan for addressing the Tyler Software. We will have no liability for defects in the Third Party Hardware or Third Party Software. You are responsible for ensuring that you have current maintenance agreements with any Developers from whom you expect to receive maintenance and/or support on Third Party Software or Third Party Hardware. Exhibit E Exhibit E Statement of Work Exhibit E Statement of Work for Implementation of Tyler Jury Manager, Browser-based Jury Management System SaaS Implementation In Xxxxxxxxxx County, TX June 18, 2020 Tyler Technologies will implement Tyler Jury Manager in Xxxxxxxxxx County, TX under the following termsdefect.

Incident Tracking. Every support incident is logged into our management system and given a unique incident number. This system tracks the history of each incident. The incident tracking number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident number, through the portal at Tyler’s website or by calling software support directly. Incident Priority Each incident is assigned a priority level, which corresponds to the client’s needs and deadlines. Tyler and the client will reasonably set the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client towards clearly understanding and communicating the importance of the issue and to describe generally expected response and resolution targets in the production environment only. References to a “confirmed support incident” mean that Tyler and the client have successfully validated the reported Defect/support incident. Priority Level Characteristics of Support Incident Resolution Targets 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business hour of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within one (1) business day. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of data. Tyler shall provide an initial response to Priority Level 2 incidents within four (4) business hours of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within ten (10) business days. For non-hosted customers, Tyler’s responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Level 2 incident that affects only one user or for which there is an existing circumvention procedure. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business day of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents without the need for a circumvention Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets procedure with the next published maintenance update or service pack, which shall occur at least monthly. For non-non- hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 4 Non- critical Support incident that causes failure of non-non- essential functionality or a cosmetic or other issue that does not qualify as any other Priority Level. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within two (2) business days of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents, as well as cosmetic issues, with a future version release. Remote Support Tool Some Incident Escalation Tyler Technologies’ software support calls may require further analysis consists of the client’s database, processes or setup to diagnose a problem or to assist with a question. Tyler will, at its discretion, use an industry-standard remote support tool. Tyler’s support team must have the ability to quickly connect to the client’s system and view the site’s setup, diagnose problems, or assist with screen navigation. More information about the remote support tool Tyler uses is available upon request. Exhibit D Exhibit D Third Party Terms We will make commercially reasonable efforts to minimize the need for you to rely on Third Party Software or Third Party Hardware in order to operate the Tyler Software. To the any such Third Party Product is required, you are responsible for purchasing, installing and configuring all Third Party Hardware and Third Party Software at your expense. We will make available a list three types of Third Party Software that will be required to load a new release of the Tyler Software, if any, as well as list of Third Party Software components that have been certified as compatible with the Tyler Software. We will have no liability for defects in the Third Party Hardware or Third Party Software. You are responsible for ensuring that you have current maintenance agreements with any Developers from whom you expect to receive maintenance and/or support on Third Party Software or Third Party Hardware. Exhibit E Exhibit E Statement of Work Exhibit E Statement of Work for Implementation of Tyler Jury Manager, Browser-based Jury Management System SaaS Implementation In Xxxxxxxxxx County, TX June 18, 2020 Tyler Technologies will implement Tyler Jury Manager in Xxxxxxxxxx County, TX under the following terms.personnel:

Incident Tracking. Every support incident is logged into our management system and given a unique incident number. This system tracks the history of each incident. The incident tracking number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident number, through the portal at Tyler’s Xxxxx’x website or by calling software support directly. Incident Priority Each incident is assigned a priority level, which corresponds to the client’s needs and deadlines. Tyler Xxxxx and the client will reasonably set the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client towards clearly understanding and communicating the importance of the issue and to describe generally expected response and resolution targets in the production environment only. References to a “confirmed support incident” mean that Tyler Xxxxx and the client have successfully validated the reported Defect/support incident. Priority Level Characteristics of Support Incident Resolution Targets 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler Xxxxx shall provide an initial response to Priority complete application failure or Xxxxx 0 incidents within one (1) business hour of application unavailability; (b) receipt of the incident. Once the incident has been application failure or unavailability in confirmed, Tyler Xxxxx shall use commercially 1 one or more of the client’s remote reasonable efforts to resolve such support Critical location; or (c) systemic loss of incidents or provide a circumvention procedure multiple essential system functions. within one (1) business day. For non-hosted customers, Tyler’s Xxxxx’x responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of data. Tyler Xxxxx shall provide an initial response to Priority repeated, consistent failure of Level 2 incidents within four (4) business hours of essential functionality affecting more receipt of the incident. Once the incident has been than one user or (b) loss or corruption confirmed, Tyler Xxxxx shall use commercially 2 of data. reasonable efforts to resolve such support High incidents or provide a circumvention procedure within ten (10) business days. For non-hosted customers, Tyler’s Xxxxx’x responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Level 2 incident that affects only one user or for which there is an existing circumvention procedure. Tyler Xxxxx shall provide an initial response to Priority existing circumvention procedure, or Xxxxx 0 incidents within one (1) business day of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents without the need for a circumvention Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets procedure with the next published maintenance update or service pack, which shall occur at least monthly. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 4 Non- critical Support incident that causes failure of non-essential functionality or a cosmetic or other issue that does not qualify as any other Priority Level. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within two (2) business days of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents, as well as cosmetic issues, with a future version release. Remote Support Tool Some support calls may require further analysis of the client’s database, processes or setup to diagnose a problem or to assist with a question. Tyler will, at its discretion, use an industry-standard remote support tool. Tyler’s support team must have the ability to quickly connect to the client’s system and view the site’s setup, diagnose problems, or assist with screen navigation. More information about the remote support tool Tyler uses is available upon request. Exhibit D Exhibit D Third Party Terms We will make commercially reasonable efforts to minimize the need for you to rely on Third Party Software or Third Party Hardware in order to operate the Tyler Software. To the any such Third Party Product is required, you are responsible for purchasing, installing and configuring all Third Party Hardware and Third Party Software at your expense. We will make available a list of Third Party Software that will be required to load a new release of the Tyler Software, if any, as well as list of Third Party Software components that have been certified as compatible with the Tyler Software. We will have no liability for defects in the Third Party Hardware or Third Party Software. You are responsible for ensuring that you have current maintenance agreements with any Developers from whom you expect to receive maintenance and/or support on Third Party Software or Third Party Hardware. Exhibit E Exhibit E Statement of Work Exhibit E Statement of Work for Implementation of Tyler Jury Manager, Browser-based Jury Management System SaaS Implementation In Xxxxxxxxxx County, TX June 18, 2020 Tyler Technologies will implement Tyler Jury Manager in Xxxxxxxxxx County, TX under the following terms.of

Incident Tracking. Every support incident is logged into our management system and given a unique incident number. This system tracks the history of each incident. The incident tracking number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident number, through the portal at Tyler’s website or by calling software support directly. Incident Priority Each incident is assigned a priority level, which corresponds to the client’s needs and deadlines. Tyler and the client will reasonably set the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client towards clearly understanding and communicating the importance of the issue and to describe generally expected response and resolution targets in the production environment only. References to a “confirmed support incident” mean that Tyler and the client have successfully validated the reported Defect/support incident. Priority Level Characteristics of Support Incident Resolution Targets 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler shall provide an initial response to Priority complete application failure or Xxxxx 0 incidents within one (1) business hour of application unavailability; (b) receipt of the incident. Once the incident has been application failure or unavailability in confirmed, Tyler shall use commercially 1 one or more of the client’s remote reasonable efforts to resolve such support Critical location; or (c) systemic loss of incidents or provide a circumvention procedure multiple essential system functions. within one (1) business day. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of data. Tyler shall provide an initial response to Priority repeated, consistent failure of Level 2 incidents within four (4) business hours of essential functionality affecting more receipt of the incident. Once the incident has been than one user or (b) loss or corruption confirmed, Tyler shall use commercially 2 of data. reasonable efforts to resolve such support High incidents or provide a circumvention procedure within ten (10) business days. For non-hosted customers, Tyler’s responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Level 2 incident that affects only one user or for which there is an existing circumvention procedure. Tyler shall provide an initial response to Priority existing circumvention procedure, or Xxxxx 0 incidents within one (1) business day of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents without the need for a circumvention Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets procedure with the next published maintenance update or service pack, which shall occur at least monthly. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 4 Non- critical Support incident that causes failure of non-essential functionality or a cosmetic or other issue that does not qualify as any other Priority Level. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within two (2) business days of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents, as well as cosmetic issues, with a future version release. Remote Support Tool Some support calls may require further analysis of the client’s database, processes or setup to diagnose a problem or to assist with a question. Tyler will, at its discretion, use an industry-standard remote support tool. Tyler’s support team must have the ability to quickly connect to the client’s system and view the site’s setup, diagnose problems, or assist with screen navigation. More information about the remote support tool Tyler uses is available upon request. Exhibit D Exhibit D Third Party Terms We will make commercially reasonable efforts to minimize the need for you to rely on Third Party Software or Third Party Hardware in order to operate the Tyler Software. To the any such Third Party Product is required, you are responsible for purchasing, installing and configuring all Third Party Hardware and Third Party Software at your expense. We will make available a list of Third Party Software that will be required to load a new release of the Tyler Software, if any, as well as list of Third Party Software components that have been certified as compatible with the Tyler Software. We will have no liability for defects in the Third Party Hardware or Third Party Software. You are responsible for ensuring that you have current maintenance agreements with any Developers from whom you expect to receive maintenance and/or support on Third Party Software or Third Party Hardware. Exhibit E Exhibit E Statement of Work Exhibit E Statement of Work for Implementation of Tyler Jury Manager, Browser-based Jury Management System SaaS Implementation In Xxxxxxxxxx County, TX June 18, 2020 Tyler Technologies will implement Tyler Jury Manager in Xxxxxxxxxx County, TX under the following terms.of

Incident Tracking. Every support incident is logged into our management system and given a unique incident number. This system tracks the history of each incident. The incident tracking number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident number, through the portal at Tyler’s website or by calling software support directly. Incident Priority Each incident is assigned a priority level, which corresponds to the client’s needs and deadlines. Tyler and the client will reasonably set the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client towards clearly understanding and communicating the importance of the issue and to describe generally expected response and resolution targets in the production environment only. References to a “confirmed support incident” mean that Tyler and the client have successfully validated the reported Defect/support incident. Priority Level Characteristics of Support Incident Resolution Targets 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business hour of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within one (1) business day. For non-hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of data. Tyler shall provide an initial response to Priority Level 2 incidents within four (4) business hours of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within ten (10) business days. For non-hosted customers, Tyler’s responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Level 2 incident that affects only one user or for which there is an existing circumvention procedure. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business day of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents without the need for a circumvention Exhibit C Schedule 1 Priority Level Characteristics of Support Incident Resolution Targets procedure with the next published maintenance update or service pack, which shall occur at least monthly. For non-hosted customers, Tyler’s Priority Level Characteristics of Support Incident Resolution Targets responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 4 Non- critical Support incident that causes failure of non-essential functionality or a cosmetic or other issue that does not qualify as any other Priority Level. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within two (2) business days of receipt of the incident. Once the incident has been confirmed, Tyler shall use commercially reasonable efforts to resolve such support incidents, as well as cosmetic issues, with a future version release. Remote Support Tool Some support calls may require further analysis of the client’s database, processes or setup to diagnose a problem or to assist with a question. Tyler will, at its discretion, use an industry-standard remote support tool. Tyler’s support team must have the ability to quickly connect to the client’s system and view the site’s setup, diagnose problems, or assist with screen navigation. More information about the remote support tool Tyler uses is available upon request. Exhibit D Exhibit D Third Party Terms We will make commercially reasonable efforts to minimize the need for you to rely on Third Party Software or Third Party Hardware in order to operate the Tyler Software. To the any such Third Party Product is required, you are responsible for purchasing, installing and configuring all Third Party Hardware and Third Party Software at your expense. We will make available a list of Third Party Software that will be required to load a new release of the Tyler Software, if any, as well as list of Third Party Software components that have been certified as compatible with the Tyler Software. We will have no liability for defects in the Third Party Hardware or Third Party Software. You are responsible for ensuring that you have current maintenance agreements with any Developers from whom you expect to receive maintenance and/or support on Third Party Software or Third Party Hardware. Exhibit E Exhibit E Statement of Work Exhibit E Statement of Work for Implementation of Tyler Jury Manager, Browser-based Jury Management System SaaS Implementation In Xxxxxxxxxx County, TX June 18, 2020 Tyler Technologies will implement Tyler Jury Manager in Xxxxxxxxxx County, TX under the following terms.