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.
Subject:RE: how long does "fixing" a document take From:<Karen -dot- Murri -at- wellsfargo -dot- com> To:<eddy -dot- skau -at- gmail -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 13 Jun 2007 07:19:09 -0500
I had a project a couple of years ago that involved editing and
formatting a number of existing standards documents. I kept a
spreadsheet that tracked how much time I spend on each document and how
many pages were in the original (typical single-spaced dense text). At
the end, I averaged about 1/2 hour per page. Some documents took much
less, some took much more. The winner was a doc that I spent about 2.5
hours per page. A few took only 10 minutes per page (these were usually
mostly re-formatting and not much editing).
It does sound more like you're writing a manual from scratch using SME
notes, though, so I'm not so sure my estimates apply.
-Karen
(My opinion, not my employer's.)
-----Original Message-----
On 6/11/07, Carrie Baker <carriebak -at- gmail -dot- com> wrote:
>
> I am sure that this is a question where the answer is "it depends",
> but I would like to get a sort of estimate to see if I am in the
> correct direction.
> A programmer for whom English is not their mother tongue, wrote an
> internal document explaining to sales staff how to demonstrate a
> complex application. (it is not a user guide, but more in the
> application note direction).
> The document is around 31 pages long and covers over 20 screens some
> of which are divided into additional panes etc.
> I was asked to edit this.
> Apart from editing, I am running the data he used, with the
> application to make sure no steps are missed out.
>
> All in all, I am fixing the English, adding formatting, (headings,
> numbers whatever is required), and making sure the whole thing makes
> sense and works.
>
> This seems to be taking me a long time. How long do you think
> something like this should take??
> --
> Carrie Baker
> carriebak -at- gmail -dot- com
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-