Charting the evolving role and authority of the CRO : 2016 North American insurance CRO survey

<?xml version="1.0" encoding="UTF-8"?><modsCollection xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-8.xsd">
<mods version="3.8">
<titleInfo>
<title>Charting the evolving role and authority of the CRO</title>
<subTitle>: 2016 North American insurance CRO survey</subTitle>
</titleInfo>
<name type="corporate" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080438654">
<namePart>Ernst & Young</namePart>
<nameIdentifier>MAPA20080438654</nameIdentifier>
</name>
<typeOfResource>text</typeOfResource>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">gbr</placeTerm>
</place>
<issuance>monographic</issuance>
<place>
<placeTerm type="text">Nueva York [etc.]</placeTerm>
</place>
<publisher>Ernst & Young LLP</publisher>
<dateIssued>2016</dateIssued>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">electronic</form>
<extent>26 p.</extent>
</physicalDescription>
<abstract displayLabel="Summary">Results from EY¿s sixth annual survey of North American insurance CROs provide an overview of current ERM capabilities, practices and organizations. They also provide a view into the variety of ERM frameworks across the insurance sector. This year¿s survey revealed a spectrum of maturity levels of ERM programs  with some very impressive frameworks that are integral to and influential in how the business is run, to others that are limited in scope and formality. To a degree, this variety reflects the inclusion of a broader and more diverse group of participants in the 2016 survey compared with past years.
The survey also clarifies the role that companies expect CROs to perform. Where ERM structures are advanced, CROs are very senior officers and participate in decision-making at the highest levels of the organization. At the other end of the continuum, the survey included several insurers that do not have a single, titled CRO role, though there may be an officer leading ERM efforts. More robust ERM programs have typically been in place for a few years and are now fully embedded as part of routine business operations, while late adopters struggle to define the ideal role, structure and prominence of their risk teams.
Interestingly, despite the varying levels of sophistication and formality, all survey respondents felt their organizations have adequate processes to manage the risks to their business. In some cases, EY analysis reveals a degree of complacency where risk management capabilities do not seem sufficiently developed. There are just as many examples, however, where risks are very effectively monitored, controlled and mitigated without the recognizable or formalized superstructure that is often associated with modern ERM.</abstract>
<targetAudience authority="marctarget">specialized</targetAudience>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080550592">
<topic>Encuestas</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080591182">
<topic>Gerencia de riesgos</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080591199">
<topic>Gerentes de riesgos</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080557515">
<topic>Cibernética</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080590567">
<topic>Empresas de seguros</topic>
</subject>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20090036062">
<geographic>Norteamérica</geographic>
</subject>
<classification authority="">7</classification>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">170602</recordCreationDate>
<recordChangeDate encoding="iso8601">20170602122254.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20170017813</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>