'Document assembly' is the process by which an operator creates an entire document from a variety of component parts and then personalizes that document to meet the needs of the intended recipient.

   Included within the scope of the term 'document assembly' are the means by which the source clauses are:



assembled and


   Pathagoras provides two distinct ways to 'assemble' documents.

  I.  The "classic" method is dubbed 'paragraph assembly'. It is frequently dubbed 'building block assembly. Same idea. The setup for this is simple:

   Create a folder to house a collection of files related to a specific subject. For example, you might place a collection of clauses used for building Wills in a folder called "Wills". Put a collection of clauses used to create real estate contracts in a folder called "Real Estate Contracts". (The name of the folder is not critical. The content is what matters. If you already have a collection of clauses reasonably broken down by subject, you do not need to create new content to implement Pathagoras. What you have, and where you have it, is likely just fine.)

   We call the folder in which you have your clauses a 'Book'.  

   Each file in the Book would (typically) contain a paragraph (or two, or several) of a complete document. These text blocks, when combined with other documents during the paragraph assembly process, would create a 'perfect' initial draft for a specific project. (So hopefully you are visualizing the 'building blocks' idea.)

   We want to again emphasize that the content of the book need not be new content. It need not be 'Pathagorized' content. Plain ol' text as it now exists works just fine. Pathagoras works well with anything you have.

   On command, Pathagoras will display these snippets onto a 'clause selection screen.' Select one, several, or all of them. Once you have selected the appropriate clauses, press the Next button. The selected clauses are quickly cobbled together into a complete document.

   Paragraph assembly is discussed in much greater detail in the following pages under Technique 1.

II. A second technique is 'assembly from templates' (or, imperfectly, 'template assembly').

   A 'template' is simply a generic form document that contains every likely clause and variation needed to produce a final document.  

   'Template assembly' doesn't offer quite as many permutations of possible documents as does paragraph assembly, at least not without greater effort. Plus, when an address, statutory reference, firm or attorney name, or other piece of text found in all templates changes, you are forced to make the changes in each of the templates.

   However, for newcomers to the document assembly process, template assembly is quite a bit easier to implement. (The document 'dis-assembly' aspects of system preparation -- when individual clauses and paragraphs needed for paragraph assembly are created -- can be easily postponed until a time when the office is 'ready' for that level of assembly power.)

   Assembly from templates is discussed under 'Technique 2' below.

   For a more detailed comparison between 'Paragraph Assembly' using clause snippets and 'Assembly using Templates', click here.


redarrowAn Overriding 'Pathagorean' Rule:

  Never use an original document as your 'base' for a document assembly session. So long as you abide by this rule, you will not accidentally overwrite the original by forgetting to save the edited document under a new name.

Of course, there is one exception to this rule. When you are intentionally editing the original, with the goal of improving the source text itself, correcting spelling errors, etc., you must open and work on the original document. Just NEVER NEVER NEVER call up the original document with the idea of editing it into a final document for a specific client or customer.

   When you follow the guidelines in this Manual, Pathagoras automatically implements this rule for you. When you call up a documentto the screen using Pathagoras tools, you will be working on an exact copy of the original How do you know it is a copy? Look for the 'name' of the document in the top-center of the screen. It will be named "Document1", "Document5", etc.

   If you find yourself working on the original for other than source editing purposes, you should rethink your process, and implement the tools provided by the program. If you do nothing else in your early days with the program, you should at least "Create your First Library" and "Shelve your First Book" or create a DropDown List. Call up copies of documents from your Books or DropDown List. If you find yourself working primarily on complete documents or templates, consider our exceptionally popular DropDown Lists.

Click the button_next_h button in the menu bar to read more about Document Assembly.