Governance, Ethics and Strategic Risk Engineering Leadership

Introduction

Risk engineering converts technical knowledge about buildings, processes, equipment, people and environments into decisions about loss prevention, insurance terms and organisational resilience. At an operational level, an engineer may inspect a sprinkler system, assess a combustible-load hazard or recommend business-continuity improvements. At a strategic level, however, the quality of that work depends on governance: who is authorised to decide, what evidence is required, how independence is protected, how recommendations are tracked, and how material issues reach senior management.

Governance is therefore not an administrative addition to risk engineering. It is the system through which technical judgement becomes consistent, accountable and defensible. Weak governance can cause technically competent work to produce poor insurance decisions. Examples include an inspection report based on obsolete drawings, an overdue high-priority recommendation, a conflicted vendor assessment, or an artificial intelligence output accepted without professional review.

This chapter examines governance, ethics, quality assurance, competency, vendor oversight, escalation and performance systems. It also considers regulation, environmental, social and governance (ESG) expectations, climate and catastrophe resilience, and the future capabilities required by insurers and risk owners.

Learning objectives

By the end of this chapter, the reader should be able to:

1. Explain the purpose and components of risk engineering governance.
2. Design quality-assurance, competency and escalation arrangements.
3. Evaluate conflicts of interest and professional accountability.
4. Establish effective controls over external engineers and vendors.
5. Select meaningful performance indicators for risk engineering.
6. Align engineering strategy with regulation, ESG, resilience and emerging insurance requirements.
7. Critically evaluate technology and artificial intelligence in technical risk decisions.

1. The strategic role of risk engineering governance

Governance is the allocation of authority, responsibility and oversight used to direct and control an organisation. In risk engineering it connects four elements:

• Purpose: the risk outcomes the function is expected to achieve;
• Authority: who may approve methods, ratings, recommendations and exceptions;
• Evidence: the information and technical basis required for decisions; and
• Accountability: how decisions, omissions and corrective actions are reviewed.

Governance differs from management. Management performs inspections, analyses hazards and closes recommendations. Governance sets the framework within which those activities are performed and assures the board, executive committee, regulator, reinsurer and policyholder that the framework is reliable.

A useful governance architecture has three lines of responsibility:

The model is not a substitute for professional judgement. It clarifies ownership and reduces the risk that everyone assumes another person is responsible.

1.1 Governance objectives

A mature system seeks to ensure that risk engineering is:

• Relevant: focused on hazards that can materially affect people, assets, liability or continuity;
• Consistent: using comparable definitions, rating criteria and documentation;
• Independent: resistant to commercial pressure and undisclosed interests;
• Proportionate: applying greater scrutiny to high-hazard or high-consequence risks;
• Traceable: retaining the evidence and reasoning behind important decisions;
• Responsive: escalating new information and overdue controls promptly; and
• Improving: learning from losses, near misses, complaints, audits and changing science.

Governance must not become bureaucracy. Excessive approval layers may delay urgent action and encourage superficial compliance. The appropriate principle is proportional control: the control effort should reflect the potential severity, uncertainty and reversibility of the decision.

2. A governance framework for risk engineering

An institutional framework normally contains the following instruments.

2.1 Policy and mandate

The risk engineering policy defines scope, objectives, minimum technical standards, reporting relationships and prohibited conduct. It should state whether the function serves underwriting, loss prevention, claims support, enterprise risk management, regulatory reporting, or all of these purposes. It should also distinguish advisory recommendations from binding risk acceptance decisions.

2.2 Standards and procedures

Standards translate policy into technical expectations. They may address inspection frequency, fire protection review, machinery integrity, natural-hazard assessment, environmental liability, construction risk, cyber-physical systems and business interruption. Procedures should identify required evidence, review points, report formats and records-retention periods.

Standards should be controlled documents. Each should have an owner, approval date, revision history, applicability statement and review trigger. A standard based on a particular jurisdiction, occupancy or technology must not be presented as universally applicable.

2.3 Decision rights

A decision-rights matrix should identify who may:

• classify a risk;
• approve a deviation from a technical standard;
• accept incomplete information;
• extend a recommendation deadline;
• appoint an external specialist;
• alter a risk score; and
• close a material recommendation.

The person who benefits commercially from a decision should not be the sole person authorised to validate its technical basis.

2.4 Risk information and records

A risk file should contain, as appropriate, the site description, occupancy, process information, plans, photographs, inspection date, data limitations, hazard analysis, safeguards, recommendations, responsible owner, due date, status and review evidence. Records should be sufficiently complete for an independent professional to understand what was known and why the decision was made.

Data lineage is especially important when information is transferred between inspection software, underwriting platforms, catastrophe models and dashboards. A false appearance of precision can arise when a database stores a numerical rating without preserving the assumptions behind it.

3. Professional ethics and accountability

Risk engineering has a public-interest dimension. Recommendations may affect life safety, environmental protection, availability of essential services and the solvency of insurers. Ethical practice therefore extends beyond satisfying an employer or client.

3.1 Core ethical principles

The following principles are widely relevant across professional engineering and insurance contexts:

• Competence: undertake work only within one’s education, training and experience, or obtain suitable assistance.
• Integrity: present evidence, assumptions, uncertainty and adverse findings honestly.
• Objectivity: avoid allowing commercial targets, personal relationships or preconceived views to distort judgement.
• Confidentiality: protect proprietary and personal information while complying with lawful disclosure duties.
• Fairness: apply criteria consistently and avoid discriminatory or arbitrary treatment.
• Public and environmental protection: give appropriate priority to life safety, pollution prevention and community consequences.
• Accountability: retain responsibility for professional conclusions, including conclusions assisted by software or consultants.

An ethical code is effective only when supported by reporting channels, protection against retaliation, investigation procedures and consequences for misconduct.

3.2 Conflicts of interest

A conflict exists when a personal, financial or organisational interest could improperly influence professional judgement, or could reasonably appear to do so. Conflicts may be actual, potential or perceived. Examples include an engineer assessing a facility owned by a close relative, accepting valuable hospitality from a protection-system contractor, receiving a bonus linked solely to premium growth, or reviewing work previously completed for a consulting client.

A practical conflict-management sequence is:

1. Identify the interest and the affected decision.
2. Disclose it promptly to the designated manager or ethics function.
3. Assess materiality, including appearance and stakeholder confidence.
4. Control it through recusal, independent review, restricted access or reassignment.
5. Record the decision and rationale.
6. Monitor whether the control remains effective.

Disclosure alone does not cure a serious conflict. In some circumstances withdrawal is required.

3.3 Professional dissent and escalation

An engineer should be able to challenge an underwriting decision, a client’s unsupported assurance or a manager’s request to soften a material finding. Escalation should be based on objective triggers rather than personal confrontation. Examples include imminent life-safety danger, suspected fraud, regulatory non-compliance, unreliable critical data, a material disagreement between experts, or an overdue recommendation whose risk has increased.

A sound escalation policy specifies time limits, decision levels, emergency routes and protection for good-faith reporting. It also distinguishes urgent notification from final technical determination: an initial alert may be issued before every fact is known, provided its provisional nature is stated.

4. Quality assurance and technical review

Quality assurance (QA) is the planned system for preventing defects; quality control (QC) is the inspection or testing of completed work. In risk engineering, both are necessary.

4.1 The quality cycle

A practical QA cycle is:

Plan → perform → review → correct → learn.

Planning identifies the applicable standard, competence requirement, scope, critical assumptions and independence needs. Performance gathers evidence and records limitations. Review tests technical reasoning, completeness and consistency. Correction addresses errors and communicates material changes. Learning updates training, standards, tools or controls.

4.2 Review methods

The intensity of review should reflect risk materiality. Methods include:

• Self-check: the engineer verifies required fields, calculations and evidence.
• Peer review: an appropriately competent colleague examines the work.
• Technical authority review: a specialist reviews complex or high-consequence matters.
• Independent validation: a reviewer not involved in the original work tests assumptions and conclusions.
• Thematic audit: a sample of files is examined for recurring weaknesses.

A checklist supports consistency but cannot replace expertise. Reviewers should ask whether the evidence supports the conclusion, whether important uncertainty is visible, and whether the recommendation is feasible and measurable.

4.3 Risk-based sampling

Suppose an organisation reviews a sample from each risk class. A simple monitoring rate can be expressed as:

where q is the review rate, nᵣ is the number of files reviewed and nₜ is the total population in the period. Both quantities are counts, so q is dimensionless and may be reported as a percentage. This measure describes coverage, not quality. A high review rate can coexist with poor review design.

For a high-hazard class, an organisation may require a higher q or review every material decision. The thresholds should be set by policy and validated against experience rather than selected merely for convenience.

4.4 Non-conformity and corrective action

A non-conformity is a failure to meet a defined requirement. It should be classified by impact, corrected by an accountable owner and closed only after evidence demonstrates completion. Repeated minor defects may indicate a systemic control failure and should not be dismissed individually.

Root-cause analysis should distinguish immediate cause, contributing conditions and systemic cause. For example, an incomplete inspection may be caused immediately by a missing photograph, contributed to by an unfamiliar site layout, and systemically caused by inadequate preparation time or poor form design.

5. Competency and professional development

Competence is more than possession of a qualification. It combines technical knowledge, practical experience, judgement, communication and ethical conduct.

A competency framework may cover:

Competency should be assessed against role requirements. A novice may work under supervision; an experienced engineer may lead complex assessments; a technical authority may approve methods and resolve disputes. A register should record qualifications, experience, training, authorisations and expiry dates.

Continuing professional development should combine formal learning with case review, field experience, peer discussion, incident investigation and feedback. Performance evaluation should not reward only the number of inspections completed. It should also consider the quality, usefulness and integrity of decisions.

6. Vendor and third-party oversight

External parties may perform inspections, modelling, laboratory testing, loss-control surveys, engineering design or remediation. Outsourcing activity does not outsource accountability. The insurer or risk owner remains responsible for selecting competent providers, defining scope and challenging outputs.

6.1 Due diligence

Before appointment, the organisation should assess:

• legal identity, ownership and financial stability;
• technical qualifications and relevant experience;
• professional registrations and insurance;
• independence and conflicts of interest;
• data-security and privacy controls;
• health, safety and environmental arrangements;
• subcontracting practices; and
• references and prior performance.

6.2 Contractual controls

A contract should define deliverables, methods, assumptions, access rights, reporting deadlines, confidentiality, intellectual property, audit rights, incident notification, correction obligations and liability allocation. It should require disclosure when the vendor lacks data or deviates from the agreed method.

Payment structures deserve attention. Payment solely for favourable findings or rapid closure can create a perverse incentive. Balanced arrangements may include payment for defined work products, independent quality measures and consequences for material defects.

6.3 Ongoing oversight

Vendor performance can be assessed through timeliness, technical-error rates, rework, recommendation usefulness, stakeholder feedback, audit findings and incident history. A vendor score should inform management but should not automatically replace professional evaluation. A technically difficult assignment may appropriately take longer than a routine one.

7. Escalation, incident management and learning

Escalation is a controlled movement of information and decision authority to a level able to act. A tiered system may include:

• Level 1: routine issue handled by the assigned engineer;
• Level 2: significant deviation or overdue action managed by a technical manager;
• Level 3: material safety, regulatory, reputational or accumulation issue reported to executive risk governance; and
• Emergency: immediate notification to designated leaders and emergency services where appropriate.

Triggers should be measurable where possible: for example, a critical safeguard unavailable, a recommendation overdue beyond a defined tolerance, a material change in occupancy, or a credible indication that reported controls do not exist.

Incident learning should include near misses. A loss is not the only evidence of a weak control; a near miss may reveal the same pathway before severe consequences occur. After-action reviews should ask what happened, what was expected, which barriers failed, why the failure was not detected earlier, and which changes will prevent recurrence.

8. Measuring performance without distorting behaviour

A balanced performance system combines leading and lagging indicators.

A useful indicator is the critical recommendation closure rate:

where c꜀ is the number of critical recommendations verified as completed by the measurement date and d꜀ is the number due by that date. The rate is meaningful only if “completed” means that evidence has been checked and the denominator includes all recommendations due. It should be supplemented by ageing, recurrence and residual-risk measures. Closing a recommendation administratively without reducing risk is a measurement failure.

Performance dashboards should show trends, data quality, material exceptions and confidence limitations. They should not conceal uncertainty behind a single composite score.

9. Regulation, ESG and resilience alignment

Risk engineering operates within a changing legal and supervisory environment. Relevant obligations may concern occupational safety, building and fire codes, environmental permits, hazardous substances, privacy, financial reporting, outsourcing, consumer protection and insurance governance. The applicable requirement depends on jurisdiction and business activity; professional judgement cannot substitute for legal advice.

Regulatory alignment requires a legal-obligation register, assigned owners, evidence of compliance, change monitoring and escalation of breaches. Technical recommendations should identify whether they are legally required, industry good practice, contractually required or risk-based enhancements. Confusing these categories can mislead decision-makers.

ESG should be integrated into engineering analysis rather than treated as a public-relations label:

• Environmental: climate hazards, pollution pathways, energy transition, water stress, biodiversity and waste.
• Social: worker safety, community exposure, vulnerable populations, human rights in supply chains and access to essential services.
• Governance: accountability, anti-corruption, data integrity, ethical procurement and transparent decision-making.

Resilience is the capacity to anticipate, withstand, respond to and recover from disruptive events while adapting to change. A resilient assessment considers not only physical damage but also dependencies: utilities, transport, suppliers, information technology, personnel and emergency services.

Climate analysis should distinguish hazard, exposure and vulnerability. A facility may face increasing flood hazard, but loss depends additionally on its location, elevation, barriers, equipment placement, warning time, maintenance and recovery capability. Scenario analysis should state time horizon, climate assumptions, adaptation measures and uncertainty. It should not be presented as a precise prediction.

10. Technology and artificial intelligence

Digital inspection platforms, sensors, geospatial data, drones, remote surveys and predictive analytics can improve coverage and consistency. Artificial intelligence may assist with document classification, image screening, anomaly detection, report drafting and prioritisation.

However, risks include biased training data, automation bias, poor explainability, cyber compromise, privacy breaches, model drift and false confidence. Human accountability remains essential for decisions affecting safety, coverage, pricing or regulatory compliance.

A governance approach for AI should include:

1. a defined purpose and acceptable-use boundary;
2. data provenance, quality and permission checks;
3. validation against representative cases;
4. performance monitoring for error and bias;
5. human review proportionate to consequence;
6. secure access, logging and change control; and
7. a process for contesting or correcting outputs.

An AI-generated recommendation is evidence to evaluate, not professional approval. If the system cannot show the basis of a material conclusion, the organisation should limit its use or obtain independent corroboration.

11. Strategic leadership and future capability

Strategic risk engineering leadership involves translating technical uncertainty into choices about capital, capacity, underwriting appetite, service models and organisational resilience. Leaders must communicate in two directions: they must preserve technical integrity when speaking to executives, and explain commercial consequences when speaking to engineers.

Important leadership practices include:

• establishing a clear risk-engineering vision linked to enterprise strategy;
• maintaining constructive challenge between engineering and underwriting;
• investing in scarce technical and digital capabilities;
• using lessons from claims and near misses to revise prevention priorities;
• designing succession and knowledge-transfer arrangements;
• engaging regulators, clients, brokers, reinsurers and communities appropriately; and
• preparing for emerging risks such as autonomous systems, battery energy storage, supply-chain concentration, extreme weather and interconnected infrastructure.

Future insurance requirements are likely to place greater emphasis on continuous risk information, demonstrable resilience, transparent models, climate-related disclosure, cyber-physical security and evidence that recommendations produce real risk reduction. The strategic response is not to collect unlimited data. It is to identify decision-critical information, improve its reliability and use it under explicit governance.

Applied case: Northshore Chemicals illustrative case

Background

Northshore Chemicals operates a solvent-blending plant near a river and supplies several regional manufacturers. Its insurer uses an external engineering firm for annual surveys. The underwriting team is under pressure to renew capacity before the survey report is complete.

Problem

The previous report rated solvent storage as adequately protected. A new site manager informs the engineer that storage volume has increased, a foam system has been partly isolated for maintenance, and a major customer depends on Northshore’s output. The external firm also provides design services to Northshore and has not disclosed this relationship. A dashboard shows 92% recommendation closure, but several closures were based only on management declarations.

Analysis

The issue is simultaneously technical, ethical and governance-related. The changed storage profile may invalidate the previous assessment. Isolation of protection is a potentially critical impairment. The consulting relationship creates at least a perceived conflict and may be an actual conflict if the firm benefits from recommending its own design work. The closure metric lacks verification and therefore overstates control effectiveness. River proximity also raises environmental and business-interruption consequences.

Approach and solution

The insurer’s risk engineering leader should immediately record a provisional escalation and inform underwriting that the prior rating is not reliable for the changed conditions. A competent independent engineer should review storage, detection, suppression, drainage, ignition control, emergency response and impairment management. The plant should provide a documented interim impairment plan, including compensating measures and a restoration deadline.

The external firm must disclose its design relationship. Pending conflict review, it should not be the sole party validating the protection adequacy. The recommendation register should separate “management states complete” from “independently verified complete.” Underwriting, engineering and claims representatives should assess accumulation and business-interruption dependency. Environmental specialists should examine spill containment and river-protection measures.

Outcome

The independent review finds that storage configuration changed beyond the assumptions of the prior report and that the isolated foam zone lacks adequate compensating controls. Renewal is not automatically declined; instead, capacity and terms are made conditional on immediate impairment controls, verified restoration, a staged storage redesign and tested business-continuity arrangements. The vendor is retained for limited technical work under enhanced disclosure and independent review.

Learning points

1. A historical rating is not transferable when exposure or safeguards change.
2. Commercial urgency does not remove the duty to escalate material uncertainty.
3. Vendor competence and independence must both be assessed.
4. Recommendation closure requires evidence, not assertion.
5. Environmental, continuity and insurance consequences may arise from the same physical hazard.
6. Governance creates the conditions in which technical expertise can influence decisions.

Challenges and limitations

Governance systems face practical limitations. Small organisations may lack separate technical, compliance and audit teams, requiring compensating reviews or external assurance. International insurers must reconcile different legal regimes and technical standards. Quantitative indicators can encourage gaming, while qualitative judgement can be criticised as inconsistent. Climate projections and catastrophe models contain structural and data uncertainty. Independent review also has a cost and may delay decisions.

These limitations do not justify abandoning governance. They require transparent assumptions, proportional controls, documented exceptions and periodic evaluation of whether controls improve outcomes. A mature organisation can state what it does not know, why the uncertainty matters and what action will reduce it.

Best-practice design principles

A high-performing risk engineering function generally:

1. links technical work to explicit risk and insurance decisions;
2. assigns authority and accountability clearly;
3. applies independent review to material judgements;
4. protects professional dissent and manages conflicts;
5. verifies recommendation implementation;
6. supervises vendors throughout the relationship;
7. measures quality and outcomes, not activity alone;
8. integrates legal, ESG and resilience considerations;
9. governs digital and AI tools through validation and human oversight; and
10. learns systematically from losses, near misses, audits and stakeholder feedback.

Chapter Summary

Risk engineering governance is the framework that makes technical decisions reliable, consistent, independent and accountable. It includes policy, standards, decision rights, records, quality assurance, competency management, vendor oversight, escalation and performance measurement. Ethical practice requires competence, integrity, objectivity, confidentiality, fairness and attention to public and environmental protection. Conflicts must be identified, disclosed, assessed, controlled and documented; disclosure alone may not be sufficient.

Quality assurance should use risk-based peer review, independent validation, corrective action and learning. Competency frameworks must cover engineering, insurance, communication, governance, digital capability and resilience. Outsourced work requires due diligence, clear contracts, conflict controls and ongoing performance review. Dashboards should combine leading and lagging indicators and avoid rewarding superficial closure.

Regulatory, ESG and resilience considerations should be integrated into hazard and consequence analysis. Technology and AI can improve coverage and decision support, but they introduce data, bias, security and accountability risks. Strategic leaders must connect engineering evidence with underwriting, capital, claims and organisational resilience while preserving professional independence and making uncertainty visible.

Key Terms

Governance: The system for directing, controlling and overseeing an organisation.

Risk engineering: The application of engineering knowledge to identify, evaluate and reduce insurable and operational risks.

Accountability: The obligation to explain decisions, accept responsibility and remedy failures.

Quality assurance: Planned activities intended to prevent defects and ensure reliable processes.

Quality control: Examination or testing of completed work to identify defects.

Competency: The combination of knowledge, skill, experience, judgement and ethical conduct required for a role.

Conflict of interest: An actual, potential or perceived interest that may improperly influence judgement.

Professional dissent: A reasoned challenge to a decision or practice on technical, ethical or safety grounds.

Escalation: Movement of information and decision authority to a level able to respond effectively.

Vendor oversight: Governance of external providers from selection through performance review and termination.

Recommendation closure: Verified completion of an action intended to reduce identified risk.

Risk appetite: The type and level of risk an organisation is willing to retain or pursue.

Residual risk: Risk remaining after controls and mitigation measures are applied.

Resilience: Capacity to anticipate, withstand, respond to, recover from and adapt to disruption.

ESG: Environmental, social and governance considerations affecting organisational conduct and risk.

Data lineage: The traceable history of data origin, transformation, use and ownership.

Model risk: The possibility that a model is unsuitable, incorrectly implemented or misinterpreted.

Automation bias: The tendency to place excessive confidence in automated outputs.

Technical authority: A person authorised to approve methods, resolve complex issues or validate high-consequence work.

Three lines model: A structure distinguishing operational management, risk oversight and independent assurance.

Review Questions

Short Answer Questions

1. What is the difference between governance and management in risk engineering?
2. Why is disclosure of a conflict of interest not always sufficient?
3. Distinguish quality assurance from quality control.
4. Identify two leading and two lagging risk engineering indicators.
5. Why must AI-assisted engineering decisions retain human accountability?

Long Answer Questions

1. Explain how a three-lines governance model can be applied to an insurer’s risk engineering function.
2. Discuss the elements of an effective competency and continuing professional development framework.
3. Evaluate the ethical responsibilities of a risk engineer facing commercial pressure to soften a material finding.
4. Design a vendor oversight process covering due diligence, contracting, monitoring and corrective action.
5. Explain how ESG and resilience considerations can be integrated into property and liability risk engineering.

Analytical / Application Questions

1. A high-hazard site reports that all critical recommendations are closed, but provides no verification evidence. Design an assurance and escalation response, including appropriate performance measures.
2. An engineering consultancy both assesses a facility and sells the recommended protection system. Analyse the conflict and propose controls that preserve decision integrity.
3. A flood-exposed manufacturer has reliable physical safeguards but depends on one transport route and one specialist supplier. Develop a governance-informed resilience assessment and explain how the results should influence insurance strategy.

Multiple Choice Questions with Answers

Question 1

Which governance component primarily defines who may approve a technical deviation?

A. Decision-rights matrix

B. Marketing plan

C. Claims reserve schedule

D. Training attendance record

Correct Answer: A. Decision-rights matrix

Question 2

Which action is most appropriate when a serious conflict of interest is identified?

A. Ignore it if the report is technically detailed

B. Disclose it and assess controls such as recusal or reassignment

C. Accept gifts to ensure cooperation

D. Allow the conflicted person to perform the sole independent review

Correct Answer: B. Disclose it and assess controls such as recusal or reassignment

Question 3

Quality assurance is best described as:

A. Only testing completed reports

B. Planned activities intended to prevent defects

C. A method for increasing inspection volume

D. A replacement for professional competence

Correct Answer: B. Planned activities intended to prevent defects

Question 4

In the formula q = nᵣ ÷ nₜ, what does nᵣ represent?

A. The total risk population

B. The number of files reviewed

C. The number of recommendations overdue

D. The number of vendors appointed

Correct Answer: B. The number of files reviewed

Question 5

Which statement about outsourcing risk engineering work is correct?

A. Outsourcing transfers all accountability to the vendor

B. Vendor selection is unnecessary if the vendor is inexpensive

C. The organisation remains responsible for oversight and challenging outputs

D. A contract eliminates the need for quality review

Correct Answer: C. The organisation remains responsible for oversight and challenging outputs

Question 6

Why can a high recommendation-closure rate be misleading?

A. Closure rates are always irrelevant

B. Recommendations may be marked closed without verified risk reduction

C. Critical recommendations never need deadlines

D. A high rate proves that all hazards are eliminated

Correct Answer: B. Recommendations may be marked closed without verified risk reduction

Question 7

Which is a leading indicator of risk engineering performance?

A. Historical insured losses

B. Past catastrophe claims

C. Training completion or review coverage

D. Prior-year litigation cost

Correct Answer: C. Training completion or review coverage

Question 8

What is automation bias?

A. A legal requirement to automate every inspection

B. The tendency to place excessive confidence in automated outputs

C. A method for calculating flood depth

D. A control that guarantees unbiased data

Correct Answer: B. The tendency to place excessive confidence in automated outputs

Question 9

In the Northshore Chemicals case, why was the prior risk rating unreliable?

A. The insurer changed its logo

B. Exposure and protection conditions had changed

C. The site had no business interruption exposure

D. The external engineer had completed training

Correct Answer: B. Exposure and protection conditions had changed

Question 10

Which statement best describes resilience?

A. The elimination of every possible hazard

B. The capacity to anticipate, withstand, respond to, recover from and adapt to disruption

C. The ability to maximise premium without review

D. A substitute for regulatory compliance

Correct Answer: B. The capacity to anticipate, withstand, respond to, recover from and adapt to disruption