A technical lead and client representative review project acceptance and a system diagram
Updated: 16/11/2026
ING Broker editorial team

IT professional liability: contracts, delivery and client claims

IT professional liability concerns what happens when a client alleges harm connected with the service supplied. It is not the same assessment as insuring laptops or restoring your own systems after an attack. For a company in Moldova, preparation starts with actual services, the contract and evidence of delivery.

This material addresses software development, integration, administration and IT consulting businesses. It does not confirm a policy available for every activity, country or claim. A specialist reviews the legal aspects of a contract. The insurer confirms risk acceptance and insurance conditions, not an article or a screenshot of a quotation.

Describe activities, not only a business classification code

A company may develop applications, configure systems, migrate data and administer infrastructure. Do not describe these as though they create identical exposure. List the services actually supplied and projects important to the risk profile. Do not hide an activity merely because it rarely appears on invoices. A small share of revenue does not make its description unnecessary.

Separate your own product from services commissioned by a client and resale of licences. Explain who sets requirements and who controls production. Anonymous examples can serve an initial discussion without code or user data. Customer identities and sensitive records are shared only when necessary. Keep technical access outside the material used for a general commercial enquiry.

Compare the contract with the actual work

Place the quotation, requirements, contract and project amendments together. Which function was requested? Which deadline was agreed? Who approves changes? Informal messages can leave uncertainty if absent from project records. Ask for legal help interpreting obligations rather than assuming what an insurer would decide. The file should describe the agreement used in practice.

Do not automatically import clauses or promises from another company's contract. Liability limits, warranties and jurisdiction require review for the particular situation. An internet template is not proof of compliance in Moldova. For insurance assessment, present the version actually used, including relevant schedules, not an unused model that happens to appear more favourable.

Retain acceptance and change approvals

Document what was delivered and how the client confirmed its review. Acceptance of one stage is not acceptance of the entire project. For new requirements, record the effect on the work and who approved it. These details can help clarify a claim, but do not guarantee that every future complaint will be rejected.

Keep relevant tests, versions and important communications accessible to authorized recipients. Do not retrospectively alter records to conceal an error. Discuss uncertainties or known problems confidentially with the competent people. A new policy must not be presented as an automatic solution to an existing dispute. Preserve the actual sequence instead of adapting it to a preferred description.

Correcting the work differs from the harm claimed

Rewriting a function, refunding a fee and a client's alleged loss are different components. Do not automatically add them into one amount called an insured loss. Establish what the client requests, on which basis and with which supporting documents for each component. Read the policy against the nature of the actual cost, rather than the overall dispute alone.

A useful hypothetical review is a disputed data migration: what work was agreed, which copy existed, what was delivered and which consequence is alleged? This example is not a real claim and confirms no cover. It shows why a product name cannot replace checking the service and circumstances. Technical facts and commercial demands remain separately identifiable.

Foreign clients require distinct contractual review

Record clients' countries, the place of service and governing-law or court provisions where included in the contract. Do not assume global protection because services are delivered online. A territorial clause must be read with the other conditions and the confirmation needed for your company's work. The location of an online client is not the complete contractual picture.

A client's insurance requirement may specify limits or wording unavailable in the proposal under review. Compare the request with actual documents and mark differences. Do not sign a statement that every client condition is met when you hold only a preliminary quotation or verbal explanation. Keep the precise unanswered requirement visible before making that commercial commitment.

Identify subcontractors and insured persons separately

Explain who performs the work: employees, collaborators or other companies. Who coordinates testing and communicates directly with the client? A subcontract does not establish that the provider is included in your policy. Its insurance also does not confirm that all claims against your company will be taken over in full. Identify the real relationships before drawing conclusions.

Prepare collaboration models and the process used to review subcontracted deliverables. If responsibilities are unclear, request analysis before quotation. Do not describe an external team as employees to simplify a form. Assessment should reflect actual relationships and the services performed for clients, including the respective approval and delivery roles.

Cyber and professional liability raise different questions

If an incident affects your systems and then a client service, separate expenses and the people making demands. Internal restoration, technical advice and a liability claim are not automatically one category. The word cyber does not mean every professional error or contractual obligation is included. Ask which particular consequence each proposed document addresses.

For prevention, discuss access, change review and testing of sensitive operations with technical staff. These measures do not replace insurance analysis. They help describe real processes and reduce reliance on general explanations. State only controls that already exist and have been checked, not features planned for a later stage. Plans should remain labelled as plans.

A claim needs a timeline

Keep the first communication date, complaint subject and relevant documents. Separate what the client says from what the technical team has verified. Follow the notification procedure of any potentially relevant policy and seek guidance. Do not promise payment, admit liability or commit to a particular lawyer on behalf of the insurer. Those are not conclusions a sales response can establish.

Do not publish client messages, personal information or vulnerability details to prove your position. Work with legal and technical specialists through suitable channels. Reviewing a file and commercial communication are different activities. A calm, documented and checked response is more useful than an immediate conclusion about coverage. Preserve the documents needed to support that response.

Check a change requested after acceptance

A client may request a function change after accepting the initial stage. Keep the request, impact analysis and extra-work approval. Do not assume the old acceptance also describes the new configuration. Separating versions and requirements helps establish facts later, but does not determine legal responsibility for a disputed outcome. Record both stages rather than silently replacing the first.

If a change affects important data or processes, arrange appropriate checks with the technical team in a safe environment. Do not use real personal data in a public demonstration or execute financial transactions merely for an editorial test. Document what was checked and the test's limitations. A partial check must not be called a complete product or security audit.

A client requirement is not an insurance certificate

The client may require evidence before signing. Compare the requirement with what the received documents actually confirm. An application, preliminary calculation and issued policy are different stages. Do not send a statement of complete protection solely because you began speaking to an adviser or received a product name. The statement must have an actual documentary basis.

Ask who can issue the requested evidence and what it can contain. Do not alter an insurer's document to match the client's preferred commercial wording. Seek review of any difference and disclose it transparently. The broker can help clarify the position, but its own text cannot convert an unaccepted condition into confirmed protection.

A fee and a claimed amount are different assessment bases

An IT contract value describes part of a commercial relationship, not every exposure alleged by a client. Prepare requested activities, revenues and project information without inventing a maximum loss. For an internal scenario, explain what stops, which data exists and which cost is estimated. Distinguish the assumption from a documented amount or one already demanded.

When comparing proposals, ask about the proposed limit and any limits for cost categories. Check whether expenses use one shared limit or receive separate treatment under the documents. Another company's quotation does not provide the answer. Discuss your actual activities, agreements and accepted conditions without general promises about price or compensation.

A checklist for the IT business manager

Check whether documents describe current services and real collaborations. A commercial portfolio may contain historical projects that no longer define the business. Separate completed, ongoing and planned activities. Explain each category and period so an example is not mistaken for work already accepted or tested. A current description matters more than a convenient old presentation.

  • Actual services and delivery to the client.
  • Contracts used and approval of project changes.
  • Testing, acceptance and maintenance records.
  • Subcontractors and their real responsibilities.
  • Relevant countries and client requirements.
  • Known circumstances and unresolved questions.

Use the sheet at renewal, updating significant changes. If a new service begins, do not assume it fits the old description. Request review before making promises to clients. A clear working file helps comparison and communication, but replaces neither the insurance contract, legal advice nor the insurer's decision on an individual claim.

Frequently asked questions about IT liability

Is every programming error compensated?

No general confirmation exists. Check the accepted activity, demand, relevant dates and contract conditions. Correcting your own code is not automatically an insured loss.

Can we buy a policy after receiving a complaint?

Do not present purchase as a remedy for a known case. Disclose circumstances accurately and request review of applicable periods and conditions. Issuance alone does not establish acceptance of that claim.

What supports a useful comparison?

Actual services, requested revenue categories, countries, agreements and delivery processes. Compare premium with limits, excess and exclusions. Do not send code or credentials through public forms.

Next step

Request a conversation with ING Broker to check assessment and intermediation possibilities. The broker explains options; risk acceptance, conditions and claims handling belong to the insurer under the contract. This material does not confirm product availability or coverage of a particular case.

Related reading: Errors and omissions: distinct questions to check.

Sources and information limits

The Romanian original records source consultation on 9 November 2026. The translation revision date does not mean the sources have been checked again. Preparation lists are editorial recommendations, not policy conditions. Cited product examples belong to their providers, not ING Broker offers. Legal obligations and individual circumstances require specialist verification.

IT professional liabilityMoldova