exception handling

[brianwgray at gmail.com (Brian Gray)]

    A cheap and simple, short term solution (depending on your email
infrastructure) may be something like a change management email group that
dumps to a public folder (restricted view / post permissions of course).
Once an address is configured you can then send a standardized (by you)
email listing your changes, to what, and why the changes were made to your
address and then it is time stamped and lists who made the change it's
backed up with the rest of your email system. This makes them search-able as
well. A similar scheme could be done within something like Microsoft Share
point which would also add revision control etc.

In any event, a few searches on the interwebs for "change management
control" will start throwing all kinds of ideas your way.

On Mon, Jan 5, 2009 at 10:24 PM, Mike Patterson <mike.patterson at unb.ca>wrote:

> Don Berry wrote on 1/5/09 7:11 PM:
> > Paper?
> >
> > That way you have the signatures of the responsible managers on file. If
> an
> > exception that they allowed has a business impact, then they are on the
> hook
> > for it.
>
> It's just me and my manager.  No worries there.
>
> Mike
>
> --
> A file that big?
> It might be very useful.
> But now it is gone.
>  _______________________________________________
> Pauldotcom mailing list
> Pauldotcom at mail.pauldotcom.com
> http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
> Main Web Site: http://pauldotcom.com



-- 
-Brian W. Gray
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.pauldotcom.com/pipermail/pauldotcom/attachments/20090106/a4df1a50/attachment.htm