Compare to other Document Assembly Programs:

• HotDocs® , XpressDocs®, ProDocs® and Exari® are four popular document creation programs. Others (perhaps two dozen) exist, and new ones appear with regularity. Some limit you to using their clauses only. All require special working templates, libraries, work sheets, sometimes rather extensive coding, special databases and special overlays. 

  Pathagoras uses: your clauses, your directories, your databases, your language.

  Most of their features and interface screens are more 'dramatic' than those of Pathagoras, but the trade-off is not necessarily ease of use.
  
  Pathagoras, on the other hand, uses your clauses, your directories, your databases, your language. You start with, end with and never leave Microsoft® Word as you build and use your source and final text.

• Because of the special templates and hidden coding that other programs require, the document (base or final) frequently cannot be viewed or edited unless that program is running.
  
  Not so with Pathagoras. A Pathagoras document is a Word document, plain, simple and always. Whether you are viewing a source library or a final product, everything created by or for use by Pathagoras can be opened and edited on any computer running Word®, regardless of whether Pathagoras is running on that particular computer.

• Most other programs are "whole document" oriented. You start with, and edit from, a complete document as the base for future documents. These are typically called 'templates.' "If /Then" formulae are inserted at strategic points throughout the document (typically as hidden fields) so that clauses are added to (or deleted from) the final product depending upon certain conditions. Separate tables and control forms must be created outside the document which control how the document is personalized for the client or customer.

• Pathagoras is not 'whole document' oriented. But then, neither are we the polar opposite: 'clause oriented'.  We are "the way you want to work" oriented. It was built in an office environment, and follows the flow gleaned from contributions offered by dozens of real world working environments. Therefore, Pathagoras works just fine with either whole documents or simple clauses. You are not limited as to how your documents can be assembled.

--You can assemble documents from the Clause Selection Screen, building the document from a 'zero base' and adding the proper selection of clauses to make the perfect final draft.

--You can assemble a document one clause at a time using dropdown lists. (This 'one clause at a time' method is particularly useful when a lot of notes or dictation accompanies the inclusion of a particular clause, or when you want to add that 'one last clause.')

--You can pre-compose documents (i.e., 'templates') and using Optional text markers (also plain text) to pare away parts of the document that do not belong in the document being assembled for the particular client or customer.

--You can start with an essentially complete document and augment it with additional text that is easily accessed using either the Clause Selection Screen or the DropDown Lists.
 
--You can link to a database, or not. You can use Pathagoras' Instant Database feature, or not. You can even use both features. There is no preferable method. There is no wrong method.

Plain text 'automated' variables vs. any other kind

• Pathagoras uses plain keyboard entered text to create automated variables. Typically, these variables are set out in a document with simple square brackets. E.g.., [Customer Name] and [number of widgets]. (Any other kind of 'bracket' is acceptable, as well. The settings are practically infinite.)
  
  These variables are easy to create, easy to understand, in terms of purpose. They become fully 'automated' with no further effort on the part of the user.
  
  Here are the advantages of plain text variables:

1. A Pathagorized document with plain text variables is essentially neutral. HotDocs and other competitive programs change the essence of the form to meet that program's needs. The variables in their base forms are converted to fields. They become neither readily viewable or editable (and sometimes not even accessible) when the parent program is not active.

2. You need HotDocs, Exari, XpressDocs, etc., to read/use/edit a source form created by that program. You don't need Pathagoras to read/use/edit a Pathagorized form.
   
   If someone buys a manual of forms marked "Pathagorized" but doesn't own Pathagoras, it's not a problem whatsoever for the customer to use the forms in their present state. The customer can manually 'search and replace' any text (including bracketed variables) to personalize the document. (Of course, owning Pathagoras would make the process much faster, but it is 'neutrality' issue that we are discussing here, not speed.)

3. Plain text variables are clearly defined and clearly visible at all times. Editing is more accurate and precise. Plain text variables are obvious and they are intuitive to the casual users.

4. Plain text variables are simply easier to create. Other than typing an opening and closing bracket, there are no steps to create them. All steps are performed right on the editing screen.

• An author who wishes to market forms does not have to create a dual set of forms to sell to the target audience, one for the 'automated' market and the other for 'non-automated' users.
  
  A 'Pathagorized' document containing regular and multiple choice variables such as:

  "Please send to me [quantity] [dozen/gross] [red/blue/olive green/sunrise yellow] widgets"

  is as discernable and usable to a non-automated user as it is to the fully conversant Pathagoras user.
  
  Therefore, the market for an author who has created plain text forms is infinitely larger. (If someone buys a forms manual marked "HotDocs compatible," but doesn't own HotDocs, that user has nothing.)

Compare to Word 2007 'Building Blocks':

• Beginning with Word 2007, Microsoft added a clause management tool which it has named 'Building Blocks.' This tool allows you to highlight and add text blocks to a 'Building Blocks' library, and then recall individual terms from that library. As a practical matter, it is but an advanced version of Word's AutoText feature (a comparison to which is made below).
While Microsoft touts 'Building Blocks' as a document assembly tool, it is not. Read on.


• You cannot 'assemble' building blocks in the fashion contemplated by Pathagoras (i.e., display all available clauses and select potentially dozens of individual clauses in a desired order and build a document . With 'Building Blocks,' you must select one block at a time.
  
  
• You cannot create 'clause-sets' with Word 2007 Building Blocks.
   
  
  • With Pathagoras, you can generate 'sets' of individual clauses which, when selected, will create a specified document (or type of document) from the designated component clauses.
  
  
  
  • With 'Building Blocks,' you must select one block at a time.
  
  
  
  • Click this link to read more about Pathagoras' Clause-Sets
    
    
• You cannot directly edit 'Building Blocks.'  To change an existing block, you must edit from the original and re-add. (Indeed, you cannot even directly 'see' your Word 2007 'Building Blocks.' The 'blocks' are initially stored in a template called 'C:\Program Files\Microsoft Office\Office12\Document Parts\1033\Building Blocks.dotx'. But if you navigate to and display that template, you will see nothing but a blank page.)
  
• This limitation does not exist with Pathagoras. Pathagoras stores component text ('building blocks', as it were) as regular Word documents. They are easily located and easily edited using techniques you already know.
  
  
• You cannot instantly call in a desired 'Building Block' from your keyboard. With Pathagoras, you can assign a folder or glossary containing your building blocks to a 'Super' status. Then, by simply type the name of the clause you desire followed by <Alt-G>, Pathagoras will instantly locate and insert the clause into your document.
See this section of the Manual to learn more about the SuperFolder.


• Word 2007 'Building Blocks' work only if Word 2007 is loaded. While this is one of those 'duh' comparisons, it is important to know that Pathagoras has been doing the kind of document assembly that 'Building Block' is now beginning to mimic since Word 97 was introduced. Unlike 'Building Blocks, however, Pathagoras is not Word-version dependent. All clauses created in any version of Word can be easily and readily used by any Pathagoras user regardless of the version of Word being used.

Compare to other Document Management Programs:

• Pathagoras' disk navigation tools are built into the program. Locating documents or clauses for assembly or editing is easy. Saving a new document to a proper location is a snap. (See the PathSmart and SaveSmart pages on this site.)



• Pathagoras disk navigation tools are in fact Word/Windows functions. All Word folders and functions remain the same. Pathagoras tries its best to maintain the environment with which you are familiar. It doesn't block access to features which conflict with the program. Nothing conflicts with Pathagoras, and conflicts with nothing. (Exception: The PathSmart module of Pathagoras may not be compatible with some disk management programs such as Worldox®. These programs frequently store documents using their own (sometimes artificial) directory structures. In those cases, you can only use their programs to save and to locate the documents in their directories. (It's not that Pathagoras conflicts with them -- it is the artificial nature of their folder assignments, and the interruptions forced by these programs, which require you to use their programs to accomplish a document 'save' or 'retrieve'.)
  
  We fully recognize that the 'other guys' can provide indexing/search capabilities that Pathagoras/PathSmart cannot begin to approach. (That is simply not where we have gone with our 'document manager'.) But, with many of these programs, you have to give up 'normal' names and 'straight' saves. You simply have to decide how much you are willing to forego in order to obtain the indexing and desktop search capabilities that these other document managers can provide.
  
  Our recommendation -- if you have not already adopted a third party document manager (or are not happy with what you have), but need the kind of search power that a document manager can provide, try out PathSmart/SaveSmart to set up your file saving structure. Use it for daily file save and retrievals. When you are faced with a more complex search (e.g., "I know that I wrote a brief last year on the statute of limitations for contracts under seal, but where is it?"), use Google Desktop or one of the other desktop search tools such as Copernic®, Blinkx®, Locate32®,  and X1®. Some are free, some are quite expensive (but you can cross networks with the more powerful ones). All allow you to continue to use PathSmart and normal Word Find and Save windows. These alternatives quite literally gives you the best of both worlds.