Document Assembly & Case Management Blog

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.

Part of a continuing series on applications of Document Assembly at a Wall Street law firm.  This blogs deals with the application of document assembly to a practice specializing in Asset Securitization.

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.

The key to a successful implementation of document assembly is an intelligent markup. The key to an intelligent markup is a solid understanding of the subject matter which is being marked up; as well as an awareness of what “can be done” with document assembly.