business risk management reporting follow meeting aa friday april 14 richard discussed aa sorrells grutzmacher brown monthly brm controller meeting deliverables database deliverables prepared proposal think recommend aa following opening closing meeting front line managers discussion items regardless priority ratings high medium low report generated business risk managers monthly controller meeting project doorstep style incorporating existing controls observations action steps taken critical issues high rating identify responsible person target date follow matrix report relating specific project audited manner consistent brm database indicating priority ratings high issues match issues reported monthly controller meetings eliminate summary report typically presented monthly controller meetings project doorstep style report presented aa received monthly controller meeting compliance input issues second database enable reminder notifications sent person responsible action step addition monthly progress report generated compliance business risk managers show critical high issues implementation detail imperative aa issue final reports projects immediately completed deliver matrix within two 2 weeks monthly controller meetings compliance inputting brm database information received within two week time period compliance notify brm aa deficiency also necessary business risk managers notify front line personnel receiving email notifications action plans specific target dates expectation responsible persons expected respond email status report issue agreement reporting plan please indicate return email message coordinate responses communicate aa feel process provide brm necessary information indicated want hear controller meetings including candid discussions well provide compliance necessary information maintain database information available corporate needs questions please hesitate call 31939 thank attention donna lowry