Time to Delivery

Often, products are almost ready for shipment but still lack documentation. Although this is certainly not the ideal scenario, there is no reason to panic when you read the numbers given below. Should there be no chance to complete regular documentation on time we will certainly find a way to provide a preliminary solution which can be complemented later on.

Time needed for authoring

The time normally needed for a documentation project is directly proportional to the size of the planned documents. You can use the same rule of thumb as for estimating the costs. Roughly it will take:

about 1 hour per page for revisions
about 2 hours per page for new documents

So the maximum output is about 20 to 40 pages per week.

Time needed for review

When the texts are complete, usually there is a review which lets you verify the new documentation. The time needed for this review, plus the time needed for the implementation of potential changes, must be added to the time calculated above.

 

By the way: When necessary, work on your project will not stop on holidays and on the weekend.

Milestones of a Typical Documentation Project

 

Copyright | Terms of Use | Linking to indoition | Imprint

Newsfeed

 
Software user assistance and documentation
since 1989
Manuals and online help generated cost-effectively from one common text base
since 1995
Numerous publications and presentations, e.g. on:
information design,
user guidance and navigation,
embedded user assistance,
single source publishing,
authoring tools
technical documentation process improvement
Winner of the Golden Disc from the German computer magazine CHIP
Member of tekom, the German professional organization for Technical Communication and Information Development
Show intro: