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.
Thankyou, Geoff and Dawson. Excellent suggestions from all who was good enough to respond to me. It's true, I am a Lone tech writer, and with little experience, and it's going to be a struggle for me to assert myself.
Now, good planning next time will be the key. I'll take the organization and review procedure suggestions into account.
Part of the problem in this project was that everything was done haphazardly with the engineers, while we all should have been meeting to make sure we were on the same page and that they understood it was my manual, and that I had a deadline.
But I have new dertmination that the situation will not be repeated, and that appropriate steps to seeing a manual out the door will be taken, and the manual will go out the door, on my deadline. (Before all of you start laughing at that vow, let me add that the manual is still being delivered on its appointed day, because that's the way I work, despite the engineer spending the whole day nitpicking.)
