1. Binders & ECF Laura Bramble (Catlin) May 2009

2. Binders and ECF What is in scope? What is out of scope? Co-lead claims 60 – 80% of binder contracts

3. What changes have been requested? Usability issues Co-lead claims Agreement parties Net settlement Binders and ECF

4. How will these be resolved? Initial investigation completed Prototype (September – December 2009) Initially develop using storyboards Develop working application Process extensive variety of binder cases via prototype Review outcome of prototyping Binders and ECF

5. Critical dependencies (must be delivered prior to or as part of binders solution) Broker claim entry – new user interface Claims workflow triggers (CWT) &/or new carrier user interface including writeback Claims database – available as full operational datastore Access control database – supporting inputs from sources other than CLASS New version of LIMCLM for binder brokers only (minor change & not mandatory) Non critical dependencies – preferably implemented but not essential Document file viewer (although significant impact on usability if not included) ACORD broker input and response Translation from LIMCLM to ACORD There may be other potential dependencies which emerge during prototype stage Binders and ECF

6. Tentative Dates Binders and ECF