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.
> Now the question: They have asked me to come up with a proposal for
> a flat rate (not billable hours). I have no idea how to calculate this
> estimate,
> or if I should high-ball in anticipation of a negotiation. Can anyone
> help me?
One set of the more commonly available rules of thumb are contained in
"Managing Your Documentation Project," by Dr. JoAnn Hackos. On p. 170
she suggests the following:
user guide 5 hrs/page
software app. ref. manual 4 hrs/page
hardware maint/troubleshooting 8 hrs/page
classroom training 40 hrs/deliverable hour of training
context-sensitive help 4 hrs/topic of help information
comprehensive help 4 hrs/topic, including hypertext links
videotaped instruction 30 hrs/finished minute of prod. time
CBT 60 hrs/finished hour of training
Every situation is a little different, but these are reasonable
benchmarks to use.
