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.
Method 1. If the project's purpose is solely academic, then you should
feel free to invent any missing information.
Method 2. If the client has actually been persuaded to part with money
for your work, you should focus on the ROI of each answer the client
might give you, and I mean the ROI as seen from his perspective. In
other words, what use can he make of each tiny part of your manual? How
much money will it make him? If the whole thing will merely sit on a
workbench holding up the things piled on top of it, see Method 1, and do
not charge the poor guy a single penny.
Method 3. If the client agreed to help you in a moment of
soft-heartedness, like perhaps he's your uncle, but truly lacks the time
and interest to devote to the project, see Method 1. The business has
persisted for 40 years without the manual.
On 10/12/2010 02:49 PM, schmittl -at- students -dot- westerntc -dot- edu wrote:
> As a tech comm student, I am compiling a "policies and procedures" manual for a small business--operating for 40 years. I have solid background info on this client; but, without direct access to any documents, how do I determine optimum outline headings and (or) content choices re: inventory? Note: The client has not implemented a business plan or any product/services/customer inventory, and he is seldom available for interviews.
> If anyone has advice for content/collecting data, I would welcome it.
> To give some context, I have included the following proposal item.
> Project PurposeThe prospective business manual will (1) serve as a first step in organizing Spotless Cleaning and (2) echo philosophies and protocol that have shaped a successful business. The segments of your business likely to be documented include products and services, customers and inventory, and equipment and labor.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-