Introduction

Everything up until now has been approaches and thought processes behind document assembly. Why you should or shouldn't invest in document assembly. To what degree document assembly should be taken to yield the best benefit for you firm. Whether you should in fact even invest in document assembly, or whether a related field would return better dividends.

From there, we've looked at naming schemas for variables, how to name dialogs consistently. How to create a tracking document to ensure that everything you do is recorded, leaving a blueprint of your works that can be analysed and error checked. But now, its time to look at how to actually commence work on your project.

So far, you should have a directory set aside for your project, as well as some sub folders to place documents and analysis files into. You should have a tracking document ready to record your every move. So, lets get on with it - you're no doubt thinking you've wasted far too much time reading this tripe already, so lets get down to it.

From this point forward, I'm going to presume the following

• Your firm has taken a serious look at document assembly, and decided that it IS document assembly they want to invest in
• Your firm understands that they are not going to see profits in days or maybe even weeks
• Your firm has chosen a single area of practice (regardless of how small, or 'niche' it may be) because it will yield some ROI
• We are working only on this single area of practice, or single set of documents