Sarbane Oxley process and procedure documentation: how granular?

["Suzanne Pyle" <suzpyle -at- hotmail -dot- com>]

Although it may be too early to tell, has anyone figured out how much detail 
to include when producing process/procedure documentation for the Section 
404 Sarbane Oxley requirements? My only frame of reference is the ISO 
documentation requirements which pretty much follow a standard format.

Haven't seen much out on the Web that talks about what the Sarbane Oxley 
documentation should or could look like; instead, there seems to be more 
discussion around the realization that documentation in general is 
necessary, and not all the bells and whistles for automating every process 
within an organization.

If you're in the middle of a Sarbane Oxley project, I'd be curious to know 
what experience you've got on determining how detailed to get when 
documenting the organization's processes and procedures?

Suzanne

_________________________________________________________________
Cell phone ?switch? rules are taking effect ? find out more here. 
http://special.msn.com/msnbc/consumeradvocate.armx


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ROBOHELP FOR FRAMEMAKER TRIAL NOW AVAILABLE!

RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.  
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for 
competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.