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.
Company Overview in an SOP (was there is vs. there's)
Subject:Company Overview in an SOP (was there is vs. there's) From:"kelly keck" <kelly -dot- keck -at- imagine-one -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 18 Apr 2008 08:54:20 -0500
Zen wrote:
>As mentioned earlier the SOP document I am reviewing is for a specific
>department within the company on how to manage tasks. We are a business
>unit
>(acquired company) of a larger organization.
>The SOP doc I am reviewing has an overview of the parent company, other
>partners the company works with, our company etc..Does an SOP for a
>specific
>department need to have all that information?
>My thought is that the employee is provided with other manuals to read
>about
>the company and why does one have to repeat it in a SOP that is for a
>specific department. I would only write about the Department and the
tasks.
Any overview information that's *necessary* for understanding the
Department and the tasks that go with it should be included. I can't
imagine that much of that overview would be needed in the case you
describe.
I may have missed it, but are these manuals in print or on-line? If
they're electronic, it should be simple to link to the higher-level
manuals (or relevant chunks of those manuals) as appropriate, so that
those who want to refer back to the higher-level company information can
and those who don't need it will not be distracted.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
