Document Assembly & Case Management Blog

This October finds me on the road.

For better or worse, the future of document assembly is on the Web. The web offers cheaper maintenance, quicker updates, and a more consistent look and feel. The web is also the most cost-effective on total cost of ownership ("TCO").  The catch is that startup costs are much greater for web deployment of automated templates.  Particularly since most law firms wish to “dip before they dunk”, the presence of desktop or networked document assembly solutions is critical to the development of automated content.  In the past five years, millions of dollars have been invested in innovative web-delivery of automated document creation systems.  By contrast, the investment in client/server based document assembly software has been minimal.

Another year has come and gone ... LegalTech New York ... The largest annual technology show.  Despite the emphasis on Litigation support systems, there were some notable participants at the conference presenting document assembly solutions.  HotDocs was there as part of LexisNexis’ Total Practice Management initiative; DealBuilder with it online document assembly system powered by a unique “relevance engine”; Perfectus Solutions with its browser-based IPManager document creation and delivery system; iXIO with its innovate online document modelling solution (Q-Shift); and Microsystems with its Word-ML basis document creation system (D3).

Document assembly projects are subject to the 80/20 rule ... the final 20% takes 80% of the time.  And for that reason, many projects don’t get perfected.  When a system is for internal use, the benefits of automation are good enough; but when turned into an saleable application, or a client-focused application, much more is required.  This blog focuses on techniques for working with the template to reduce the time to get from 80 to 100%.

Is it the process or the document that comes first?  Does the user view the world as a series of data, with document as the outputs; or a series of documents, with data as the inputs.  These views govern how you will design a document assembly library.

Working with template systems (as opposed to individual templates) requires attention to detail and planning before execution.  The rewards of planning come from ease of maintenance, and flexibility to change.  The blog looks at formatting and design questions in Document Assembly system.

How does one explain to a web developer that document assembly is more than just throwing up some web-forms with fields tied an SQL database?  Sometimes, the hard way, by letting them try it themselves ...