Document assembly takes too much time to do it properly |
|
|
|
|
This one is not a myth: its very possible, depending upon what your vision of "too much time" is and what your firm wants/needs from document assembly... There are several areas of law where document assembly is relatively easy to implement and will yield noticeable results. Similarly with non-legal, there are numerous documents that can benefit from this stuff. As with any programming, its all about picking your targets and deciding on a level of investment versus projected returns. Here's the quickest benefits possible - you be the judge:
Its nothing but return on investment. Every time you have to stop and think about what to write in a document, you are spending time. If you have to stop and think about that paragraph more than a few times, you can program it and never have to think about it again. Do your documents contain the same decisions from client to client or project to project? Spend 30 minutes to get the optional content figured out - what questions to ask and what content has to appear. Spend 30 minutes integrating it into your system, then never have your staff have to re-draft or think about it again! They just dictate that the option applies, or it doesn't - voila - it appears in the document first time every time with a click or two. If you spend an hour on this process, but it saves 5 minutes every time that document is drafted, that means after that document is drafted 12 times, you have made 100% return on investment. Everything after that is profit. Is it taking too much time to do it properly? Well, that's your call. |