That's a pretty short timeline for a policy that affects the entire
organization and contains many regulatory and legal risks.

Policy development is the foundation of your IS and RIM strategies.
All other processes usually proceed the guidelines and rules set forth
in the corporate policies. As a consultant who assists organization in
developing corporate policies around ESI and communication systems, I
have a base template that is over 50 pages and covers a majority of
the rule making subject matters. Even with this extensive template, I
find that only 20-30% of the content is used in my clients implemented
policies. Policy development is so integral to each company and must
be suited to each specific organization with support from senior level
management and backed with legal review.

I don't want to continue to put a gray cloud over your task, so I will
leave you with one recommendation that most companies fail to address
in policy development: Enforcement. Don't write anything in the policy
you cant enforce, monitor or provide training for. Failure to enforce
your policy will expose your organization to unnecessary risks.

Take a few seconds to review current litigation's and look for how
many times the ruling party has place sanctions or expanded Discovery
in litigation due to mistakes in the creation and implementation of
corporate policy.

I would address your legal counsel and have them raise the red flag.

-----
Robert Kleppen
Seattle, WA
206-979-3365



On 8/12/07, Lynette Yohn <[log in to unmask]> wrote:
> Greetings,
>
> Does anyone currently have an e-mail policy that you would be willing to
> share with me?  Until very recently, our corporate e-mail policy was
> maintained by our IS division.  However, due to the importance e-mail has
> gained in recent years, I find it necessary to address e-mail retention
> and archiving in a separate policy.
>
> I appreciate any help you can provide and the sooner the better.  I just
> received the assignment and have 1 week to complete.
>
> Lynnette
>
> Lynnette S. Yohn
> Blue Cross Blue Shield of Minnesota
> Records Management Specialist
> (651)662-6617
> (651)629-3162 - Pager
>
> "Be kinder than necessary, for everyone you meet is
> fighting some kind of battle."
>
>
> ----------------------------
> Important news about email communications:
>
> If our business rules identify sensitive information, you will receive a ZixMail Secure Message with a link to view your message. First-time recipients will be asked to create a password before they are granted access. To learn more about ZixMail, ZixCorp Secure Email Message Center, and other ZixCorp offerings, please go to http://userawareness.zixcorp.com/secure4/index.php
> ----------------------------
>
> The information contained in this communication may be confidential, and is intended only for the use of the recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have
> any questions concerning this message, please contact the sender.
>
> Unencrypted, unauthenticated Internet e-mail is inherently insecure. Internet messages may be corrupted or incomplete, or may incorrectly identify the sender.
>
> 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]
>


-- 
Robert Kleppen
Big Imperative - Consultant
PH:206-979-3365
[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]