Re: Requests for changes in documentation

["Rick Henkel" <rickhenkel -at- yahoo -dot- com>]

We used a form at my last job, and it worked very well. We typically got
hundreds every month from clients and from internal personnel--that may
sound like a lot, but we probably had over 50,000 pages of documentation we
maintained.

Here are the fields we included on our form:

* Manual affected
* Revision date on page in question (to make sure they have the latest
revision)
* Pages (the page number where they found the problem)
* A check box indicating whether they attached the pages and marked the area
of concern
* "Describe Concern and Correct Processing"
* "Liability Impact/Client Risk"
* The name of the person we could get more technical info from

That worked really well for us.

Seems to me that it's possible to make that form a PDF, and the user can
then somehow fill it out and send it directly to your Web site if you use
PDF interactive forms. Maybe that would work for you.

Rick



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

Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**New Dates!!** San Francisco (Apr 16-17), San Jose (Mar 29-30)
http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.

IPCC 01, the IEEE International Professional Communication Conference,
October 24-27, 2001 at historic La Fonda in Santa Fe, New Mexico, USA.
CALL FOR PAPERS OPEN UNTIL MARCH 15.  http://ieeepcs.org/2001/

---
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.