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.
As a relatively new freelancer, I am conscious that I tend to be optimistic
when it comes to estimating tech writing projects; it's a difficult balance
between being fair to myself, and not scaring customers away! So far, the
customer is winning!
I've been asked to estimate a new project and I am determined to submit a
realistic figure this time, so I would appreciate input from those more
experienced than myself.
The customer has a user guide which is 180 pages. It looks to me as if the
guide has been auto generated (and translated) from some other source,
probably an online help system. I have been asked to estimate three
different levels of work:
(1) An overhaul of the look and feel. The general layout is a mess -
cluttered, unstructured pages with random use of different fonts, there are
no conventions for presenting field names, options, etc, headings are
difficult to identify... the list goes on. So, one of the first things it
needs is a new template and a complete face lift.
(2) An editorial review. Content is littered with basic errors and
translation issues.
(3) A full review. This is the 'big one'. I would go through the guide with
the software, making sure it is editorially and technically correct. At the
moment, there is a distinct lack of any explanatory information in the
existing guide - it is very much a set of functional instructions for each
option in the software, with no information about why users might want to
use a feature, what the implications of an action are, etc.
I realise that there are a whole host of factors to consider when estimating
a project (particularly with regard to the third option), but I was hoping
that some of you might be able to offer some ball park suggestions, at least
with options 1 and 2.
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-
