Training is conversational and context-specific or audience-specific
whereas policy is a document with precise verbiage to articulate general
rules. I'd start with nailing the verbiage in policy (or procedures
document) before subsequently interpreting it in training sessions.

I sort of pepper the entire RM policy document with all the ideas discussed
in this email thread so far, for example,

   - in the introduction section,   ....'Records Retention Schedule
   dictates how long records are kept before they are destroyed. The only
   exception is a Legal Hold.'
   - in the 'roles & resp.' section, being specific about resp. of various
   employee roles for things like review & creation of retention schedule,
   audit of timely destruction, guidance in destroying, each person's role
   within the legal hold process. Specific 'roles' include RM, RM Committee,
   Law Dept, IT Dept. and others
   - a separate section on the purpose of the retention schedule - briefly
   touching on how it is created, how classes are determined, how review
   process is done etc ('briefly' because this is a policy not a procedures
   document)
   - a whole section on record destruction i.e '  Records may not be
   destroyed before their retention period has expired' 'Records may not be
   kept longer than their retention period, unless...' ' A Legal Hold
   extends the retention period of Records for the duration of the Legal Hold'

   - a separate section on Legal Hold (again, policy rules, not procedures
   details)



-- 
Maureen Cusack
San Francisco, CA
[log in to unmask]

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]