Content-Type: text/html

Fair enough. That said, given any requirement for users to interact with
their potential records from a classification and declaration perspective,
why are the three zones described any worse than any other approach that
uses *more* folders - or sub-folders and sub-sub-folders? In other words,
how should an organization and its users manage emails that rise to the
level of records? 

If it's inbox or RM repository, I don't think that users will take the time
to do it as they are received or acted on, meaning that they stay in the
inbox. At some point then they either have to go to other folders in the
inbox (same problem you describe), to the repository (same problem I
describe), keep them essentially forever, or apply an automated cleanup
every X number of days, weeks, or months, with the same risk of deleting
stuff that should have been saved. 

What about using the three-zone approach with rules that ping the user
whenever a message is within 5, 15, or 30 days of being deleted? And yes,
this could be applied to just the inbox or to the myriad folders as well,
but I think it's too complex for the multiple folders and the rules could be
overwhelming for the volume in the inbox that represents everything
received. 

Regards, and hope to see many of you in Las Vegas next week, 

Jesse Wilkins
<a href="/cgi-bin/wa?LOGON=A3%3Dind0810B%26L%3DRECMGMT-L%26E%3D7bit%26P%3D239856%26B%3D--%26T%3Dtext%252Fplain%3B%2520charset%3Dus-ascii" >[log in to unmask]</a> 

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact <a href="/cgi-bin/wa?LOGON=A3%3Dind0810B%26L%3DRECMGMT-L%26E%3D7bit%26P%3D239856%26B%3D--%26T%3Dtext%252Fplain%3B%2520charset%3Dus-ascii" >[log in to unmask]</a> 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:<a href="/cgi-bin/wa?LOGON=A3%3Dind0810B%26L%3DRECMGMT-L%26E%3D7bit%26P%3D239856%26B%3D--%26T%3Dtext%252Fplain%3B%2520charset%3Dus-ascii" >[log in to unmask]</a>