Estimating is definitely an art, there’s no doubt about it. Each project is different because there are so many variables that come in to play. It’s difficult to try and distill them down to a set number of factors that you can then assign a timeline too. But as technical writers it’s something we’re asked to do each and every day. So figuring out how to do it efficiently and effectively is important.

To start off the process, ask these three questions:

1. Am I familiar with the subject?
2. What’s the scope/size of the project?
3. Do I have access to information/subject matter experts?

That’s it, that’s all. Oh sure, you could also add in “what’s the deadline?” if you already have a hard-and-fast delivery date for the overall project of which your documentation is a part, but that’s not always a main concern at this point. The timeline becomes a point of negotiation, as you determine how long it will take you to write, and then you see if it meshes with the overall project timeline.

The art comes in when you need to integrate your timeline with the overall project timeline, or development delivery dates, or the QA test cycle. That’s where you have to work your magic.