a little clarification. I dislike ACT+x retention periods when the trigger
event is not defined. Rather than see ACT+X in a schedule I would much
prefer to see explicit trigger events such as Contract
expired/terminated/cancelled + X. that is more easily understood than is
ACT+X
having worked with a major ERMS for the past 8 years I'm always looking for
trigger events that can be automated by a feed from another business
system. For example I would look for a feed from the HRIS system to
provide me with an employee's termination date or a contract management
system to tell me when the contract ended.
I think BillR and I are in violent agreement ;-)
On Mon, Jul 1, 2013 at 4:07 PM, Roach, Bill <[log in to unmask]> wrote:
>
>
> I do not share Peter's distaste for ACT+ timeframes. My experience is
> that managing a collection of related records with a single ACT+ timeframe
> is much easier than trying to manage the retention of each individual item
> in the collection independently. This is especially true if the trigger
> can be automated or if data from an existing business system can be used to
> initiate disposal.
>
--
Peter Kurilecz CRM CA
[log in to unmask]
Richmond, Va
http://twitter.com/RAINbytehttp://tech.groups.yahoo.com/group/RAINbyte/http://paper.li/RAINbyte/rainbytehttp://pinterest.com/pakurilecz/archives/http://pinterest.com/pakurilecz/records-management/http://www.linkedin.com/in/peterakurilecz
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]
