At a glance
Understand the risk.
Ask the right questions.
Comprehensive IT Business Insurance starts with a clear picture of the work you perform, the responsibilities you accept and the events that could interrupt your business. This guide brings together common risks, insurance categories, practical documents and questions to discuss with your broker. Your business may need a different combination of covers or extensions from another business in the same industry.
Use the sections below to prepare for an insurance conversation in Perth, Sydney, Melbourne, Brisbane, Canberra or elsewhere in Australia. These examples are general information, not a recommendation that a particular policy is suitable for you. Your activities, locations, contracts and the applicable policy wording need to be considered together.
General information only. This does not take into account your objectives, financial situation or needs. Before acting, consider whether the information is appropriate for you. Cover is subject to insurer acceptance and the policy terms, conditions, limits and exclusions. Read the Financial Services Guide and the relevant PDS (where applicable) and/or policy wording before deciding.
01 / Understand your exposure
Common risks to consider.
- A deployment, code defect or integration issue causes a client’s system or website to fail.
- A vulnerability or credential compromise leads to unauthorised access or data loss.
- A customer alleges missed milestones, inadequate performance or failure to meet an SLA.
- An incident arising from the day-to-day activities of IT service providers leads to an allegation of injury, damage or financial loss.
- A contract, approval or record does not clearly document the responsibilities of IT service providers after a problem occurs.
- Software defects, configuration errors, failed integrations or service outages that affect a client’s operations.
02 / Connect risks with cover
Insurance commonly considered.
No single package suits every business. The descriptions below identify possible cover categories; each is subject to its own wording and underwriting.
may respond to covered allegations that professional services, advice, designs or omissions caused financial loss, subject to the insured services, retroactive date and claims-made notification requirements.
may assist with specified cyber incidents, privacy events, response costs and business interruption, depending on the event, security controls, sub-limits and exclusions.
may respond to certain third-party injury or property-damage allegations arising from business activities, subject to the insured activities and policy wording.
may cover specified buildings, contents, stock and equipment following insured events, subject to declared values, exclusions and settlement terms.
may assist with insured loss of gross profit or revenue and certain additional costs when a covered event triggers the policy, subject to the indemnity period and calculation basis.
may respond to certain directors and officers, employment-practices, statutory-liability or crime exposures where included, subject to policy terms and legal insurability.
A policy name does not establish that an activity or incident is insured. Review the insured business description, trigger, conditions, limits, excess and exclusions with your broker.
03 / A closer look at your business
Details worth discussing.
Describe the systems you control
An IT business should explain the boundary between advice, implementation and ongoing operation. A developer building a brochure website has a different exposure from a managed service provider administering client networks or a software vendor hosting business critical transactions. List the services delivered, the industries served and the largest client dependencies. Include hosting, cloud administration, data migration, cybersecurity work, integrations and automated processes where relevant. If the business can change a customer’s live environment or access privileged accounts, explain the approval and access model. An insurer needs more than a broad description such as computer services.
Review where one mistake could affect several customers. Shared hosting, a common deployment tool or a central remote management platform can create an accumulation of loss. Record how backups are separated, restoration is checked and emergency access is controlled. Describe subcontractors and third party platforms that provide material parts of the service. These facts help distinguish a professional error from a cyber event, though one incident may involve both. Ask how the policies interact where a faulty release causes downtime and a compromised account is also suspected. Coverage should be assessed from the actual wording rather than the product name.
Bring service promises into the review
Supply representative statements of work, support agreements and service level commitments. Pay particular attention to uptime promises, credits, unlimited indemnities, security guarantees and the customer’s right to recover lost revenue. Obligations accepted in a contract can be broader than the liability a policy is designed to insure. Ask whether the definition of professional services includes every revenue stream and whether intellectual property allegations or loss of client data are addressed. Overseas customers and contracts governed outside Australia deserve specific discussion, especially where the chosen policy places limits on territorial or jurisdictional scope.
Maintain records of client acceptance, test results and approved changes. For migrations, record what data was in scope, which backups were available and who confirmed completion. For ongoing support, preserve the ticket history and agreed responsibilities for patching, licensing and third party subscriptions. Cyber proposals should describe actual controls, not an intended future state. If a control cannot be applied consistently across older systems, explain the exception. Check how incident response costs, dependent service provider outages, funds transfer fraud and contractual service credits are treated; these are separate questions even when they arise from the same outage.
Prepare for a multi-client incident
Create a response plan that assigns technical containment, client communication and insurer contact to named roles. Keep access to the plan and relevant contact details outside the systems most likely to fail. Preserve logs and deployment records before restoration overwrites evidence. A clean rebuild may be technically sensible, but the sequence should allow investigation where practical. Record when each client was affected and restored, and separate incident response costs from ordinary support work. Notify potential claims promptly through the agreed process, including a customer’s allegation that a release or recommendation caused financial loss.
At renewal, review growth in hosted sites, managed devices, recurring revenue and customer concentration. New use of automation or artificial intelligence may change the service scope and the approvals needed before output reaches a client. Revisit the cost and time required to restore the largest environment, not just a small test account. Check that the insured entity matches the entity signing contracts and that acquired products or trading names are declared. A coordinated professional indemnity and cyber review can reveal gaps between client promises, operational control and policy triggers before a difficult incident makes those boundaries urgent.
04 / Put it in context
What an incident might look like.
Hypothetical examples only. These are not BAU client stories or predictions of a claim outcome.
A deployment, code defect or integration issue causes a client’s system or website to fail. The affected party seeks compensation, defence costs or rectification expenses. Whether any policy responds would depend on the allegations, insured activities, policy trigger, exclusions, excess and limit.
A vulnerability or credential compromise leads to unauthorised access or data loss. The event also interrupts normal trading or creates additional expense. Property, liability, professional, cyber or interruption cover may be relevant only where the facts satisfy the applicable wording.
A few minutes. A different perspective.
Put your thinking
into practice.
Three situations for comprehensive it business businesses. Choose a practical next step, then explore why the details matter.
A learning activity with hypothetical situations. It is not a risk assessment, personal advice or a prediction of insurance cover.
What would you do next?
Work through the facts, the records and the questions you would take to your broker. There is no time limit.
05 / Prepare for the conversation
Bring the details.
Make the discussion useful.
Documents and contracts
- Software development agreements, statements of work and acceptance records.
- Security architecture, testing, change-control and incident records.
- Master services agreements, statements of work, software licences and acceptable-use terms.
- Service-level agreements, hosting terms, data-processing agreements and privacy policies.
- Subcontractor, cloud-provider, payment-provider and reseller agreements.
- Security policies, incident-response plans, backup records and change-control procedures.
Questions to ask before choosing cover
- Are all products and services—development, hosting, support, data processing, consulting and managed services—listed?
- What uptime commitments, warranties, indemnities and liability caps appear in customer contracts?
- Does cyber cover include incident response, privacy liability, business interruption and social-engineering losses?
- How are open-source software, subcontractors, cloud providers and offshore development teams treated?
- Do the policy territory and jurisdiction match where customers, users and data are located?
06 / Know the limitations
What may not be covered.
The following are examples only, not a complete exclusion list. Product terms vary, and the applicable PDS and/or policy wording must be checked.
- Guaranteed performance, liquidated damages, service credits or contractual penalties unless specifically accepted.
- Known vulnerabilities, incidents or circumstances that pre-date cover or were not disclosed when required.
- Patent infringement and some intellectual-property disputes, which may require specialist cover.
- Failure to maintain minimum security controls, backups, patching or multi-factor authentication where policy conditions apply.
- Loss caused solely by supplier failure where dependent-business-interruption or contingent cover is absent.
07 / Questions, explained
Frequently asked questions.
What insurance do IT service providers commonly consider?
Depending on their activities, assets, staff and contracts, IT service providers may consider Professional indemnity insurance, Cyber insurance, Public and products liability insurance. Other policies or extensions may also be relevant. No single list is suitable for every business, and availability is subject to insurer appetite and underwriting.
Would insurance automatically respond if a deployment, code defect or integration issue causes a client’s system or website to fail?
Not automatically. A claim outcome depends on the actual facts, the policy period, insured activities, definitions, exclusions, conditions, excesses, sub-limits and notification requirements. The relevant wording should be reviewed before relying on cover.
What information is usually needed to obtain a quote for Comprehensive IT Business Insurance?
Insurers commonly request turnover or revenue, payroll, staff and contractor numbers, locations, claims or complaints history, and the exact activities to be insured, plus services provided, contract limits, data volumes, security controls, hosting arrangements and overseas customers. Complete and accurate disclosure helps the insurer assess the risk, but it does not guarantee that cover will be offered or that a future claim will be accepted.
08 / Keep exploring
Connect the wider picture.
Read about the primary insurance categories and clarify the terms used in policy discussions. A link does not mean a product is suitable for your business.
Useful insurance terms
Official guidance
Local understanding. National reach.
Across Australia.
Connected to your business.
Based in Osborne Park, Western Australia, and supporting businesses nationally. These are service areas, not separate BAU offices. State and territory requirements can differ.
WAWestern Australia+
Perth, Bunbury, Mandurah, Rockingham and Kalgoorlie.
NSWNew South Wales+
Sydney, Newcastle, Central Coast, Wollongong and Maitland.
VICVictoria+
Melbourne, Geelong, Ballarat, Bendigo and Shepparton.
QLDQueensland+
Brisbane, Gold Coast, Sunshine Coast, Townsville and Cairns.
SASouth Australia+
Adelaide, Mount Gambier, Whyalla, Gawler and Port Pirie.
TASTasmania+
Hobart, Launceston, Devonport, Burnie and Ulverstone.
ACTAustralian Capital Territory+
Canberra, Gungahlin, Tuggeranong, Belconnen and Woden Valley.
NTNorthern Territory+
Darwin, Palmerston, Alice Springs, Katherine and Nhulunbuy.
Let’s start with your business
A clearer conversation
about your insurance.
Tell us what you do, what has changed and what you need to understand.
Speak with BAU Risk
Request a callback.
Tell us about your business and the cover questions you would like to discuss.
Before sharing personal information, read our privacy information.