TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
At 08:28 28/07/98 -0800, Nancy Hitchcox wrote:
>I would like to hear from editors who allow authors to work in a document
>throughout the publication process. I edit proposals and am finding that,
>more and more, subject matter experts (the authors) want to continue
>working in the document (on a shared file server) until just before it goes
>to Repro. I feel we have to find a way to accommodate their needs and
>still maintain control over the document. We are using MS Word Office 98
>and have considered having them work with revisions turned on, but haven't
>worked out the logistics. Any ideas out there?
We had the same problem - the software used to edited the last minute and
we either couldn't put the changes in anymore because the documents were
already off to the printer or being proof-read or we didn't find out about
the changes before it was too late (i.e. nobody told us about the program
being changed yet again).
There are a few things we did:
1. The authors are informed about the release date of the software and any
changes to this date.
2. We have a deadline when changes to the program can only be bug fixes
but not
changes to the user interface or the functionality of the program.
3. We put a clause in our printed and on-line documentation saying that the
information was at the time of printing (release) up-to-date.
4. If there are any changes to the program interface or functionality
which cannot be
avoided, this goes into a release document which is supplied with the
software
(either in the help or as a separate document).
5. Proof-readers get printouts (chapter by chapter) of the documents
whilst it is being
written (we have at least three proof-readers and still typos... I am
sure the printer
puts them in...).