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

<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd">
  <record>
    <leader>00000nab a2200000 i 4500</leader>
    <controlfield tag="001">MAP20071030044</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20080418122012.0</controlfield>
    <controlfield tag="007">hzruuu---uuuu</controlfield>
    <controlfield tag="008">980424e19970401usa||||    | |00010|eng d</controlfield>
    <datafield tag="040" ind1=" " ind2=" ">
      <subfield code="a">MAP</subfield>
      <subfield code="b">spa</subfield>
    </datafield>
    <datafield tag="084" ind1=" " ind2=" ">
      <subfield code="a">7</subfield>
    </datafield>
    <datafield tag="100" ind1="1" ind2=" ">
      <subfield code="0">MAPA20080004156</subfield>
      <subfield code="a">East, Tim</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">Proving your worth</subfield>
      <subfield code="b">: planning and publishing a risk management annual report</subfield>
      <subfield code="c">by Tim East</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">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</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080591182</subfield>
      <subfield code="a">Gerencia de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080545987</subfield>
      <subfield code="a">Anuarios</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080567057</subfield>
      <subfield code="a">Publicaciones</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080566852</subfield>
      <subfield code="a">Planificación</subfield>
    </datafield>
    <datafield tag="650" ind1="1" ind2="1">
      <subfield code="0">MAPA20080563608</subfield>
      <subfield code="a">Organización</subfield>
    </datafield>
    <datafield tag="740" ind1="0" ind2=" ">
      <subfield code="a">Risk management</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="t">Risk management</subfield>
      <subfield code="d">New York</subfield>
      <subfield code="g">nº 4, April 1997 ; p. 33-42</subfield>
    </datafield>
  </record>
</collection>