business risk management reporting as a follow up to the meeting with aa on friday , april 14 , richard and i
discussed with aa ( sorrells , grutzmacher and brown ) how the monthly brm
controller ' s meeting deliverables and database deliverables should be
prepared . the proposal i think we should recommend to aa is the following :
opening and closing meeting with front line managers and discussion of all
items , regardless of priority ratings ( high , medium , low )
report generated to the business risk managers at the monthly controller
meeting in the " project doorstep " style , incorporating existing controls and
observations / action steps to be taken on the critical issues ( those with a
high rating ) and identify responsible person ( s ) and target date
follow up matrix report relating to the specific project audited in the
manner consistent with the brm database indicating priority ratings ( the high
issues should match the issues reported in the monthly controller meetings )
eliminate the summary report that has typically be presented at the monthly
controller meetings
once the " project doorstep " style report presented by aa is received at the
monthly controller meeting , compliance will input the issues into the second
database to enable the reminder notifications to be sent to the person ( s )
responsible for the action step . in addition , a monthly progress report will
be generated from compliance to the business risk managers to show the
critical ( high ) issues and implementation detail , if any .
it will be imperative that aa issue final reports on the projects immediately
after they have been completed and deliver the matrix within two ( 2 ) weeks
after the monthly controller meetings to compliance for inputting to the brm
database . if this information is not received within the two week time
period , compliance will notify the brm ' s and aa of the deficiency .
it will also be necessary for you , the business risk managers , to notify your
front line personnel that they will be receiving the email notifications on
action plans with specific target dates and with the expectation that the
responsible persons will be expected to respond to the email with the status
report of the issue .
if you are in agreement with this reporting plan , please indicate so in a
return email message to me and i will coordinate all responses and
communicate this to aa . i feel that this process will provide the brm ' s the
necessary information that you have indicated you want to hear in the
controller ' s meetings , including the candid discussions as well as provide
compliance with the necessary information to maintain the database so the
information is available for the corporate needs .
if you have any questions , please do not hesitate to call me at 31939 . thank
you for your attention . donna lowry
business risk management reporting
as a follow up to the meeting with aa on friday , april 14 , richard and i
discussed with aa ( sorrells , grutzmacher and brown ) how the monthly brm
controller ' s meeting deliverables and database deliverables should be
prepared . the proposal i think we should recommend to aa is the following :
opening and closing meeting with front line managers and discussion of all
items , regardless of priority ratings ( high , medium , low )
report generated to the business risk managers at the monthly controller
meeting in the " project doorstep " style , incorporating existing controls and
observations / action steps to be taken on the critical issues ( those with a
high rating ) and identify responsible person ( s ) and target date
follow up matrix report relating to the specific project audited in the
manner consistent with the brm database indicating priority ratings ( the high
issues should match the issues reported in the monthly controller meetings )
eliminate the summary report that has typically be presented at the monthly
controller meetings
once the " project doorstep " style report presented by aa is received at the
monthly controller meeting , compliance will input the issues into the second
database to enable the reminder notifications to be sent to the person ( s )
responsible for the action step . in addition , a monthly progress report will
be generated from compliance to the business risk managers to show the
critical ( high ) issues and implementation detail , if any .
it will be imperative that aa issue final reports on the projects immediately
after they have been completed and deliver the matrix within two ( 2 ) weeks
after the monthly controller meetings to compliance for inputting to the brm
database . if this information is not received within the two week time
period , compliance will notify the brm ' s and aa of the deficiency .
it will also be necessary for you , the business risk managers , to notify your
front line personnel that they will be receiving the email notifications on
action plans with specific target dates and with the expectation that the
responsible persons will be expected to respond to the email with the status
report of the issue .
if you are in agreement with this reporting plan , please indicate so in a
return email message to me and i will coordinate all responses and
communicate this to aa . i feel that this process will provide the brm ' s the
necessary information that you have indicated you want to hear in the
controller ' s meetings , including the candid discussions as well as provide
compliance with the necessary information to maintain the database so the
information is available for the corporate needs .
if you have any questions , please do not hesitate to call me at 31939 . thank
you for your attention . donna lowry