Hi, Joe.

Here is one part of a conference report I did for my company upon
returning from this year's ARMA conference in Baltimore.  I found this
particular session very informative.

Session:  Creating a Global Retention Schedule for a Multinational
Company

Mark Weaver from the UK-based pharmaceutical company, AstraZeneca,
presented this session.  It began with very basic information (what is a
retention schedule and why have one?) and I almost switched sessions but
am glad I stayed.  He quickly got into the meat of his presentation by
using his company as the case study.  Mark outlined how AZ put together
a truly global retention schedule - a 3Y process!  He gave attendees
much food for thought:  centralized v. decentralized records,
functional/process-based v. departmental, using the consultation phase
to market RIM and raise visibility, performing a variation analysis of
all current schedules, and admonishing us to document the entire
development process.

Key take-aways:
*	A single schedule is the recommended final goal.
*	Cross-reference all retention requirements to avoid duplication.
*	Adopt highest level or standard.
*	Declare and manage local variations.
*	Be careful with time-based v. trigger/event-based disposition.
*	Destruction deviations should be approved by RIM; document the
reason for deviation.
*	Develop change control process for updates/changes to the
schedule.
*	Create Global Governance Group for ongoing retention schedule
management. 

You might want to look him up and contact him for more detailed info.
Hope this helps a bit.

Cheers,

Stephanie McCutcheon, CRM
Denver, Colorado

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]