Proving your worth : planning and publishing a risk management annual report

<?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>Proving your worth</title>
<subTitle>: planning and publishing a risk management annual report</subTitle>
</titleInfo>
<titleInfo type="alternative">
<title>Risk management</title>
</titleInfo>
<name type="personal" usage="primary" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080004156">
<namePart>East, Tim</namePart>
<nameIdentifier>MAPA20080004156</nameIdentifier>
</name>
<typeOfResource>text</typeOfResource>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">usa</placeTerm>
</place>
<dateIssued encoding="marc">1997</dateIssued>
<issuance>serial</issuance>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">print</form>
<form authority="marccategory">microform</form>
</physicalDescription>
<abstract displayLabel="Summary">The main point to keep in mind in preparing a risk management annual report is to keep its focus narrow and make sure the message is concise. Therefore, there are a couple of things that the report will not try to accomplish. First, a report alone will never motivate or energize a leader of a business unit to support the risk management agenda. Second, the report will not communicate a great body of technical information or provide a vehicle for premium allocation. Those tasks are far better accomplished by other means such as a complete premium distribution plan geared toward financial controllers and accounting functions</abstract>
<note type="statement of responsibility">by Tim East</note>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080591182">
<topic>Gerencia de riesgos</topic>
</subject>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080545987">
<topic>Anuarios</topic>
</subject>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080567057">
<topic>Publicaciones</topic>
</subject>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080566852">
<topic>Planificación</topic>
</subject>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080563608">
<topic>Organización</topic>
</subject>
<classification authority="">7</classification>
<relatedItem type="host">
<titleInfo>
<title>Risk management</title>
</titleInfo>
<originInfo>
<publisher>New York</publisher>
</originInfo>
<part>
<text>nº 4, April 1997 ; p. 33-42</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">980424</recordCreationDate>
<recordChangeDate encoding="iso8601">20080418122012.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20071030044</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>