dont' always agree with Chris but in this case I must. documentation must be
built into the business process so that reports are produced with ease.
creating the list (and it could just as easily be a database query versus a
paper printout) shouldn't be onerous.

the recent appeals court decision concerning the Rambus patent litigation
would seem to indicate that having such documentation would be more helpful
than harmful. but maybe Messrs Isaza and Montana can way in at some point on
this

peterk

On Mon, May 16, 2011 at 12:17 PM, Chris Flynn <[log in to unmask]> wrote:

> Well as you are all aware I would never disagree with Bill, or say he is
> wrong but.... .
>
> I tend towards the other side of the coin. Build the required documentation
> into your work process. Most of the folder names will already exist in a
> structure. leverage your work. Generate box lists. Track what you have,
> where it is and when you dispose of it. If you can't support it in an audit
> then hopefully you can resolve any shortcoming in the process. As for who,
> what where when and why, that is what policy and procedure are for and one
> reason we have a job.
>
>


-- 
Peter Kurilecz CRM CA
[log in to unmask]
Richmond, Va
http://twitter.com/RAINbyte
http://tech.groups.yahoo.com/group/RAINbyte/
http://paper.li/RAINbyte/rainbyte
Information not relevant for my reply has been deleted to reduce the
electronic footprint and to save the sanity of digest subscribers

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]