The decision by the authors of Pathagoras to program an engine that allows the end-user to mark up their documents with plain text characters was an existential one. (BTW, other programs claim that space today, and older programs that started with a different approach have since somewhat, but not fully, adopted the concept. We are glad for them, but we have always been there.)

 

An aggregator site now lists over two dozen document assembly programs. They all have one thing in common. They're all HotDocs knock offs.  In one way or another, they depend heavily upon Word fields to connect data to their proprietary databases, collateral documents and overlay screenage.

.

Many function wholly outside of Word, requiring users to leave the familiar Word environment to learn yet another program. Only as the final step are their results into Word. Once assembled, the document cannot directly be augmented by the program that built it.

 

The exception is Pathagoras. Pathagoras is a plain text based document assembly program. It that contains no fields, no complex setups and no databases prerequisites. Is quite simply the simplest and easiest to use and teach document assembly program on the market. Everything is performed while you are in Word and you are never taken outside of Word to complete your task.

 

The design of your base templates or individual clauses is done inside of Word. The processing of the document . . . inside Word. The replacement of variables . . . we augment Word's find and replace routine, but it's still just Word. Editing, adding new clauses, formatting, printing.  Still Word. 'All Word, All the Time.'

 

Also unique to Pathagoras is that we've been around for over 25 years.  Only HotDocs can also make that claim  But unlike HotDocs, the same documents that were written for Pathagoras 20 years ago are still usable today. Ask that of any other document assembly program.

 

Now it is true that Pathagoras doesn't have the fancy interfaces that some of the more modern programs have. Pathagoras is still programmed in Word's macro language VBA. From a 'visually pretty' and 'dynamic screen imaging' point of view, VBA hasn't been improved by Word very much. Dang some of those those programs look good. But we'll stick with VBA.

 

With our approach, everyone in your office can use Pathagoras because everyone in your office can create a variable that looks like this: [Client name].

 

Not everyone in your office can navigate the complexity of supposedly easy ancillary screens. Just like it did when it came out 20 years ago, Pathagoras works wholly within Word.

 

With Pathagoras, you will never feel bound by a single or a proprietary way of doing things. It is easily adapted to the way that you wish to assemble documents. From the simplest variables to the most complex cascading conditional text blocks, Pathagoras can do it in a way that you will understand and be able to easily implement, not just one particular topic, but for all your office documents.

 

It is directly editable at the point in the  document where you want  the change to occur. With all other programs, you must activate their program and probably call up a collateral document just to make a simple change. Not so Pathagoras. (Whether the change is substantive or just one that affects appearance, style, etc., you make your changes on the face of your original document, not some other location that is often impossible to recall.

 

Because we only point, all of your documents are always Word documents, unencumbered by any code. (Yes there are markups for the conditional text, but remember it's just text. If you decide to move to another program, the documents don't need to be recreated. Just remove the text.)

 

The forms in a 'Pathagorized' system are your forms. The language is your language. There are only a few easy to implement rules that you must observe to create a very powerful system.

Pathagoras does not require you to abandon your current files or file structure. Pathagoras adapts to the methods that you currently use to store and retrieve documents. Your current folder(s) of forms can remain intact. Each can be used as a Pathagoras 'book' without any special configuration, programming or changes.

There is no pre-packaged text that limits you in your document production. (However, if you already have forms on your computer in which variables are noted between square brackets, those forms are already 'automated documents' as far as Pathagoras is concerned. No further editing is needed.)

Pathagoras self-generates the data input forms it needs to feed its database. You do not have to spend any time composing data intake sheets. You do not have to preconfigure a database and use only those names for your variables.

Pathagoras self-generates its interviews for the selection of 'optional' and 'multiple-choice' text blocks. There are no complex forms that you have to create, and no complex formulas that you must write to link conditions to results.

Pathagoras' 'plain text' structure means that content travels to other documents unencumbered by fields and links, tables or anchor documents. We have no need for auxiliary and component files. There is not a separate 'author' program (which takes you out of Word, and that you must revisit to edit the component files). Indeed, there is one version of Pathagoras, called Pathagoras. Everything we offer is in the program, and we don't require you to choose among different levels and different product names. And yes this is possible simply because we operate in a plain text environment.

There are no existential built-in references to external resources, collateral files or indexes. Nothing has to be connected or disconnected for it to work.

All content is freely transportable from one document to another and from one program to another. (What we mean by this is that text from Pathagoras can be copied and pasted into anything and it will appear just as it did when you copied it.

It is as universal as it gets. It means you can have shared data with your community by storing it on a central server or restrict it by saving it on a single users computer.  Or share with some and not others. It is never an all or nothing decision.

It's not so much a consequence of our plain text approach, but it reflects our over-arching principle that the user should always have full control:

With other programs, the main objective is to turn over full control of the document creation process to the computer. Answer questions and this document is selected, and that's all there is to it.

While in theory it may mean fewer mistakes, the assumption is that the original programming is accurate. When it isn't, there is another big problem. A whole bunch of bad documents may have been produced.

This approach also leads to fewer thoughtful decisions. Uniformity definitely is enhanced. But this benefit should only apply to your core, simple, basic bespoke documents. Simple Wills, NDAs, Retainer Agreements for routine cases. (If you do produce bespoke documents, Pathagoras is a wonderful tool for that, with clause sets and simple interviews.)

These 'time savings'  may not apply to the complex type of documents that most attorneys are hired to write.  Pathagoras' primary intent (and design) has always been to let the user choose the clauses, to select the conditions and the responses. The questions can be automated, and the retrieval of the clauses made simple and quick, but the control of the drafting is always and firmly in the hands of the author. And since you are always within Word, you format the document with Word tools, add clauses while within Word, edit further within Word, etc.  If upon review and editing of the draft document  (and that is still a critical part of document creation) a mistake is found, ou are still in Word, and Pathagoras keeps all your clauses fingertip/mouseclick close.