Experienced user Archives | TheFormTool

Template Governance: Who Should Be Allowed to Change Automated Word Documents?

The Team at TheFormTool — Sat, 01 Aug 2026 20:09:41 +0000

Template Governance: Who Should Be Allowed to Change Automated Word Documents?

Automated templates carry professional decisions. They should not be changed casually.

A staff member finds outdated wording in an automated Word template. The correction looks obvious. A sentence needs to be updated. A role name should change. A clause should be removed. The person makes the edit and saves the file.

In an ordinary draft, that may be a small change. In an automated template, it can be much larger. The template may use that wording in several places, depend on the related answer in a condition, repeat the same value in another document, or use it to control a signature block, calculation, list, or document set. A change that looks local can affect every document produced from the template afterward.

That is why template governance matters. Once a Word document becomes an automated form, it is no longer only a file. It is part content, part process, and part professional judgment captured in reusable form.

Why automated templates need governance

A finished Word document states a result. An automated Word template produces results. It may ask questions, place answers, include or exclude language, calculate dates or amounts, repeat data through a document, create lists, build signature blocks, and in Doxsera-strength workflows generate related documents from the same answers.

That means the template carries more than approved wording. It carries the logic behind the approved wording. A clause may appear only when a particular answer is selected. A pronoun, defined role, or singular/plural choice may depend on a party answer. A date may be offset from another date. A document in a package may be included only for a specific category of matter, employee, client, transaction, or jurisdiction.

Without governance, the danger is not merely that someone changes text. The danger is that someone changes the firm’s document process without realizing it.

Separate the right to use a form from the right to change it

The most important distinction is between the people who use automated forms and the people who are allowed to change them. Form users need a reliable way to answer questions and generate documents. Template authors need the authority and training to change fields, conditions, lists, calculations, document sets, reusable passages, data connections, and other logic.

Those are different jobs. A paralegal, assistant, HR coordinator, or practice-group user may understand a particular matter very well. That does not necessarily mean the user should be able to alter the automated template that hundreds of future documents may depend on. The user should have a clear way to report a problem or request a change, but the change itself should move through a controlled path.

For smaller offices and simpler forms, that path may be informal but still deliberate. For larger libraries, it should be explicit: who owns the template, who may edit it, who approves content, who tests the automation, and who releases the production version.

Product capabilities matter, but policy comes first

TheFormTool family supports different levels of control, and the distinctions should be described accurately.

TheFormTool PRO can build intelligent single-document Word forms using questionnaires, fields, conditions, lists, grids, date and number formats, math, pronouns, and singular/plural logic. It is a strong tool for controlled Word forms, especially when the author and user are the same person or when an office manages access through ordinary file permissions and office practice. PRO does not include a separate Author/User access model.

Doxsera, Doxsera DB, and Aurora add a practical software control: Authoring commands can be password-restricted for users on particular computers. That allows an organization to let staff run approved forms while limiting who can use the authoring tools that change template logic.

DB User is more limited by design. It has no authoring capability and is priced at a significant discount from Doxsera DB. In organizations where a small number of specialists maintain the templates and a larger group only needs to generate approved documents, that distinction can be important both for governance and cost control.

Even with these software controls, governance remains a management responsibility. The software can help limit authoring access. It cannot decide who is professionally qualified to approve a clause, calculation, policy statement, jurisdictional variation, or release to production.

Assign ownership before the first serious update

Every important automated template should have a named owner. Ownership should not be vague, because vague ownership creates three common failures: outdated templates remain in use, duplicate templates appear in shared folders, and changes are made by whoever happens to notice the problem first.

The owner may be a senior lawyer, practice-group leader, HR manager, finance manager, compliance officer, document automation specialist, or small governance committee. The right answer depends on the document and the organization. What matters is that someone is responsible for keeping the template current and deciding when a revised version becomes the active version.

In many strong systems, content ownership and technical authorship are separate. The subject expert approves the meaning, professional standard, and wording. The template author implements those decisions inside Word. That separation is healthy. It keeps substantive approval with the people responsible for the work, and it keeps automation changes in the hands of people trained to make them safely.

Use a change process that respects both content and logic

A good change process does not need to be bureaucratic, but it does need to be visible. A user should not have to create a private copy to fix a problem, and a template author should not have to guess whether a requested wording change has been approved.

A practical process can be simple:

- A user or reviewer submits a written change request.
- The template owner decides whether the change is needed.
- The appropriate subject expert approves the wording or rule.
- A trained template author makes the change.
- The revised template is tested with common and unusual examples.
- The owner approves release to the production library.
- Outdated versions are removed or clearly retired.

Different changes require different levels of review. Correcting a typo in an internal instruction may be simple. Changing a legal clause, HR policy statement, tax calculation, notice period, data source, or document-package rule may require professional review before the template is touched.

Record what changed and why

Automated templates should have a change history. The record does not have to be elaborate, but it should be useful to the next person who has to understand the template. A note that says “updated language” is rarely enough.

A good record usually identifies the template name, version, date, requestor, author, reviewer, approver, reason for change, affected sections, related templates checked, testing completed, and release date. That record becomes more important as the library grows. Six months later, the organization should be able to tell which version is current, why a clause changed, and whether related forms were updated at the same time.

This is especially important when multiple templates share the same wording or logic. A change to a reusable clause, defined term, role, calculation, or question may need to be carried across a group of forms. In Doxsera, DB, and Aurora environments, authoring tools such as label reports and multi-form checking can help identify inconsistencies, but the organization still needs a habit of recording decisions.

Keep draft templates away from production templates

Governance fails when users cannot tell which version is safe to use. Master templates should live in a managed location. Draft templates should be separate from production templates. Old versions should be archived or withdrawn in a way that prevents them from becoming someone’s convenient starting point next month.

Clear file names, version numbers, folder permissions, and release notes all help. So does a simple reporting path. If users cannot report errors easily, they will solve problems locally. Local fixes become personal templates, personal templates become unofficial versions, and unofficial versions eventually become a firmwide consistency problem.

The goal is not to prevent improvement. The goal is to make improvement visible, reviewed, and controlled.

Test the automation, not just the wording

A wording review confirms that the language is acceptable. It does not confirm that the automated template still works. Testing has to include the logic.

A useful test should check the questions, repeated fields, conditions, calculations, lists, grids, pronouns, singular/plural choices, party roles, signature blocks, reusable passages, file names, saving instructions, and document-set behavior where applicable. The test should include common examples and the awkward cases most likely to expose hidden assumptions.

For a legal template, that may mean one party, several parties, an entity party, mixed individual and entity parties, optional clauses, missing information, and changed roles. For HR, it may mean full-time, part-time, remote, location-specific, and department-specific examples. For finance, it may mean different amounts, dates, rounding, rates, and schedules. The test should confirm that the form still carries the approved professional decisions into the document the user actually generates.

A large-library model: experts, specialists, and users

The most mature template-governance systems separate responsibility even further. Subject-area experts own the substance. A small group of automation specialists converts that expertise into intelligent templates. Everyday users generate documents from the approved library.

In a large firm, that model can support dozens of subject areas and hundreds of practitioners. The estate-planning group updates its forms when law, practice, or firm policy changes. The corporate group maintains its own best-practice language. The employment group does the same for its documents. A central document-automation team then implements the approved changes, tests them, and releases updated templates into a shared library.

The result is not only efficiency. It is institutional consistency. Everyone using the library starts from current, approved, best-practice documents rather than private copies, old samples, or local variations. The firm is no longer relying on every practitioner to know which file is current or which clause has been replaced.

Some organizations can take the model further. Once the firm has a disciplined template-maintenance process, that expertise can become a client service. A firm that helps major clients keep their own internal forms current on a retainer basis is no longer treating document automation only as an internal cost saver. It is using its document expertise to strengthen the client relationship and create revenue from a process it already knows how to manage.

A practical governance checklist

Before releasing or updating an automated template, ask:

- Who owns this template?
- Who is allowed to edit it?
- Who approves the substance?
- Who tests the automation?
- Where is the production version stored?
- How are draft and retired versions separated?
- What changed in this version, and why?
- Were related templates, clauses, labels, or document sets checked?
- Have common and unusual scenarios been tested?
- Can users report problems without editing the template themselves?
- Does access change when staff roles change?

A checklist is not a substitute for judgment, but it helps make the organization’s judgment repeatable. That is the same reason automated templates exist in the first place.

Conclusion

Automated Word templates carry approved language, questions, conditions, calculations, reusable content, party logic, and document-set choices. Changing one part of the template may affect many future documents, sometimes in places the editor did not intend.

Good template governance separates users from authors, authors from approvers, drafts from production files, and quick observations from approved changes. The right software controls help, especially where authoring can be restricted or user-only access is appropriate. The larger discipline is deciding who may change the rules that everyone else relies on.

The best systems do not keep templates frozen. They keep them current through a process that is deliberate, tested, and trusted.

The post Template Governance: Who Should Be Allowed to Change Automated Word Documents? appeared first on TheFormTool.

Every Firm Has One Person It Can’t Afford to Lose

The Team at TheFormTool — Tue, 14 Jul 2026 23:31:43 +0000

Scaling Expertise – Article 1

Every Firm Has One Person It Can’t Afford to Lose

Every professional organization has one.

The attorney everyone consults before filing an unusual motion. The partner who knows exactly how a complex transaction should be structured. The litigator who has refined an argument through years of experience. The assistant who remembers why a particular clause changed ten years ago.

Ask around the office who would be hardest to replace, and you’ll usually hear the same names. Most firms accept that reality.

One firm we worked with decided to change it.

Instead of allowing expertise to remain inside individual lawyers, they asked a different question:

How can the firm’s best lawyers work for everyone?

It was one of the most important management ideas we’ve encountered in nearly twenty years working with professional document systems.

A Different Way of Thinking

The firm was large enough that it didn’t have one “best” lawyer. It had dozens. Each was recognized as an authority in a particular practice area. Estate planning. Litigation. Real estate. Corporate. Employment. Tax.

Traditionally, that kind of expertise creates dependence. Other lawyers ask questions. Drafts circulate for review. The experts become increasingly busy because everyone relies on them.

This firm chose another path. Each expert became responsible for developing and maintaining the firm’s best work product in that area. Not merely writing documents. Capturing judgment. Explaining choices. Refining language. Improving procedures.

The firm’s technical specialists then transformed that expertise into intelligent document systems that every lawyer could use.

The result was remarkable.

A young lawyer could begin with the same carefully developed knowledge that previously required years of experience—or a call to one of the firm’s experts. The experts continued improving the system. Everyone else benefited from every improvement.

Expertise Became Infrastructure

Most organizations think of expertise as something people possess. This firm treated expertise as infrastructure. That single shift changed everything.

Instead of answering the same drafting questions repeatedly, experts improved the underlying system. Instead of correcting recurring mistakes, they eliminated the conditions that caused them. Instead of becoming bottlenecks, they became architects.

Every improvement they made strengthened the work of hundreds of other lawyers. Expertise no longer flowed one conversation at a time. It became part of the firm’s daily operation.

The Real Asset

Many firms believe their greatest assets are their people. That’s certainly true. But there is another asset hiding inside those people. Their accumulated judgment. Their experience. Their understanding of what works—and why.

If that knowledge leaves when someone retires, changes firms, or simply goes on vacation, the organization loses far more than another employee. It loses part of its institutional memory.

The most successful organizations we’ve observed understand that expertise should be captured while it is available, refined while it is current, and continually improved by the people most qualified to improve it. Not because experts are replaceable. Because they are irreplaceable.

The Experts Were Multiplied

One detail from that firm’s experience has stayed with us. The experts never became less important. Quite the opposite. Their influence expanded dramatically. Instead of helping one lawyer at a time, they helped hundreds. Instead of reviewing the same issues repeatedly, they invested their time making the entire organization better.

Their expertise became available every day, on every matter, to every lawyer using the firm’s systems. The experts weren’t replaced.

They were multiplied.

An Unexpected Outcome

Years later, the lawyer who first championed this strategy has become one of the firm’s senior partners. Looking back, that isn’t surprising. He wasn’t proposing a better way to create documents. He was proposing a better way to manage knowledge. He recognized that the firm’s greatest competitive advantage wasn’t software. It wasn’t templates.

It wasn’t even its lawyers. It was the expertise those lawyers had accumulated over decades of practice. His insight was that expertise should become an institutional asset rather than remain an individual possession.

Every Firm Has One Person It Can’t Afford to Lose

Actually, every firm has many. The question isn’t whether those people exist. The question is whether their knowledge benefits only the people who know to ask—or whether it strengthens the entire organization.

The firms that will thrive over the next decade won’t simply hire outstanding professionals. They’ll find ways to capture, preserve, improve, and distribute the expertise those professionals develop. Because the greatest contribution an expert can make isn’t solving today’s problem.

It’s making tomorrow’s professionals better equipped to solve theirs.

The post Every Firm Has One Person It Can’t Afford to Lose appeared first on TheFormTool.

Multi-Party, Multi-Role Decisioning

The Team at TheFormTool — Sat, 23 Jul 2022 22:37:59 +0000

Multi-Party, Multi-Role Decisioning

Most of us are familiar with multi-party or multi-item uses of our software, where there are several signers, several choices from a sale catalog, or several symptoms described in a neurological exam. The “answer”, of course, is a List. Piece of cake.

It’s a little more complex to combine multiple parties and multiple roles. The best approach will typically include a GRID using checkboxes or dropdowns to capture the Roles. Even accommodating multiple roles for each person (executor and beneficiary, or all-terrain and mud and snow for a tire.

Where things start to get really complex is when a specific role order is required, where John is first choice for executor and successor beneficiary while Sally is first choice for beneficiary. Or, perhaps a breakfast choice might be bacon with sausage as backup, with oatmeal but if there is neither bacon or sausage, then the fruit selection. A recent example described three Tiers of treatment for the current COVID variant based on patient circumstances, but then went further to describe how Tier 1 oral medication might be modified for a medication conflict, thereby preventing a Tier 3 approach, one with only 30% efficacy.

A new article in the Knowledge Base describes how an intelligent form can easily manage multiple choices for multiple roles in multiple orders. The article includes a working form that may be downloaded and used for free.

Complexity: Multiple Roles in Varying Orders of Usage

The post Multi-Party, Multi-Role Decisioning appeared first on TheFormTool.

How to Master Complexity Building an Intelligent Form

The Team at TheFormTool — Wed, 13 May 2020 20:57:11 +0000

A number of our more expert users have asked what approach we use internally to build a particularly complex component in a form. This is an approach that we’ve found very helpful. It recognizes that really intelligent users tend to over-complicate their searches for solutions to a form that doesn’t work as intended. We call it the “Rule of Three.” This description may be too basic for you, but it helps make certain that we get it all in as far as “surrounding the issue”, so please excuse that.

1. Describe the goal, if possible in one sentence.

2. Describe the Rules that need to be followed by the eventual solution. Start broadly, setting no more than three Rules. They can be developed further in a bit, with each Rule further subdivided into up to three Rules.

3. Start building an example that will illustrate the issue; develop the possible solutions; and eventually illustrate the solution.

I know. It sounds basic, right? But it works better than all the alternatives we’ve tried over the last 10,000 or more service issues. The keys are to a) start from a fresh completely blank page; b) void any jargon at all; c) and proceed with one step at a time, proving each step as you go. We think of it as approaching the problem as a most basic new user would, one who doesn’t know anything and who is conditioned against taking shortcuts.

For a specific example, really do start from complete scratch to eliminate mental distractions caused by details that make no difference. Leave out all the jargon and instead use A, B, C or X, Y, and Z and 1,2,3 and Andy, Betty, and Charlie or Apple, Banana, Carrot. The key is to use words that have no meaning or merit so that our brains don’t leap ahead of themselves to make connections that don’t exist, or spending effort trying to decode the jargon in case it is important (it never is), Then reduce the number of examples to test to just three, a nice manageable number that has the added benefit of fitting on one page. Finally, reduce the number of drivers, whether they are Lists, Conditions, Tags, or rows in a spreadsheet to just three, again a manageable number. What’s cool is that it turns out that anything that works with three variables will work just as well with 53 but won’t burn up brain power trying to keep everything under control.

The added benefit of the approach is that if there is a problem with the program it becomes very easy to communicate the problem and show it by example.

Give this approach a try. It will allow you to either solve the issue by looking at it completely differently or make it really easy for us or other professionals to see it and “get it” if additional help is necessary.

Searching for a pro bono Partner

The Team at TheFormTool — Wed, 14 Aug 2019 20:04:01 +0000

Searching for a pro bono Partner

We’re looking for a partner to co-sponsor pro bono legal access services to disadvantaged consumers using Aurora webData, Doxserá DB and DB User for data collection and document assembly. Our software and services will be provided at no cost.

The ideal candidate will be a law school, significant bar association, or large pro bono legal services provider in the United States that already responds to, or is capable and interested in responding to, at least 100,000 matters per year.

Likely focus areas might include consumer, tenant, family, or elder law.

Contact probono@theformtool.wp.urdemo.website.

The post Searching for a pro bono Partner appeared first on TheFormTool.

Eight ways to stay up to date with new items at TheFormTool, LLC

The Team at TheFormTool — Fri, 12 Aug 2016 22:29:18 +0000

News happens in real time. Here’s how to stay informed without being overwhelmed

Thanks to our enthusiastic customers, now representing more than 40 countries and more than 200 truly fascinating industries, there seems to be something new to share almost weekly. Recently, merely keeping up with it all has been a royal chore, with hundreds of features and functions spread across a handful of products, all matched by “how-to” ideas contributed by thousands of customers.

We pride ourselves on producing the easiest to use and most powerful document assembly and automation software in the world. In recent months we’ve turned a bit of that ingenuity and energy toward providing our users with more of the information they need, faster and easier.

We’re creating specific channels of information to inform users of specific changes, such when we release an update, or create a new subject-specific video, or even a “heads up” on upcoming discussion items for the live weekly The Learning Curve podcast.

The main website (www.theformtool.com) will continue to anchor our efforts, ably supplemented with the online Knowledge Base, the amazing online training course (the video version of The Learning Curve), the Word Warrior monthly newsletter (subscribe here), Twitter (@theformtool) and this blog. We’re going to make each of those channels more specific to your interests.

Here are two very specific action items.

You can now receive real time notifications of posts such as this one, or the recent discussions of how to connect Dox DB to MySQL, the very first announcement of Dox DB 2.0, notice of a fix for a troubling bug, and the story of four early adopters of our software. This blog is now publishing RSS feeds in real time that you can access through your news feed or RSS reader just by selecting www.theformtool.com as a feed. If you don’t already have an RSS reader, we suggest you look at feedly.com. Feedly is free and easy. and a great tool. Open an account and then select www.theformtool.com as one of your interests. Check in with feedly as often as you wish to catch summaries of and links to any new items.

If you’d like to be notified as updates become available for your program, subscribe to the article Current Version Numbers of TheFormTool Products, either with an RSS feed or by registering with the Service Center and requesting email updates (by subscribing) to just this one area.

Either way, you’ll be up to date with the latest news of most importance to you, in real time.

And, you’ll learn what more we have in store as its announced in coming weeks.

The post Eight ways to stay up to date with new items at TheFormTool, LLC appeared first on TheFormTool.

Connectivity Class in The Service Center

The Team at TheFormTool — Thu, 04 Aug 2016 22:11:08 +0000

A new Doxserá DB^® customer, Jeff Kinstler, stumbled a bit as he connected his software to his office database. While he was comfortable with our explanation that the thousands of variations in the DB world preclude us from covering all connection possibilities, he wished for more information than what we provide. (We suggest customers turn the task of writing the connector to their IT support; it’s not particularly difficult, but it does require specific technical knowledge of the specific database and system and how they’ve been configured.)

After a couple of missteps, Jeff figured out his installation himself and then went a step further, drafting step by step instructions for adding access to a MySQL database to Doxserá DB^®. We were impressed with both the idea and Jeff’s writing and built a new classroom named Connectivities from Users: DSN and Connection Strings into the DB product section of our online Service Center. From time to time, we’ll add other customer suggestions on how to wire things up in a specific DB environment. We’d like to thank Jeff for a great idea and the fortitude to see it through, and welcome Jeff Kinstler as its inaugural author. If you’re running MySQL and don’t want to bother IT, this is a great resource to check out. Who knows, perhaps you’ll be our next author!

The post Connectivity Class in The Service Center appeared first on TheFormTool.

Staying informed about The Learning Curve, effortlessly

The Team at TheFormTool — Sat, 27 Feb 2016 01:49:35 +0000

The Learning Curve, housed within our online Service Center, has grown substantially, both in numbers of viewers and in numbers of videos and the breadth of subject areas they cover. The Service Center itself now boasts hundreds of instructional and demonstration videos and articles exploring ways to maximize the return on time invested.

This four minute video demonstrates two different approaches to effortlessly staying informed of new additions to The Learning Curve or any other of our subject areas, automatically and at a glance.

You can visit the online Service Center at https://service.theformtool.com/home.

The post Staying informed about The Learning Curve, effortlessly appeared first on TheFormTool.

Announcing Our New Online Training Course

The Team at TheFormTool — Mon, 25 Jan 2016 20:14:18 +0000

Taking you “from the basics to rocket science” and beyond

We’re excited to announce the launch of The Learning Curve video course, an online training tutorial covering all aspects of its software. The course is organized into scores of subject-specific videos assembled into levels of sophistication and subject matter into easily assimilated lessons.

The videos average less than ten minutes each and the course is completely free to all owners.

Inquisitive owners can browse through the seven increasingly advanced “grade levels” of material looking for subjects that appeal. They can use search tools to find keywords describing lessons or subjects of special interest. Or, they can “take the course” by starting at the beginning and proceeding through the lessons and levels to the end, or to wherever their need to learn is satisfied.

TheFormTool PRO and Doxserá are unique in that they don’t require complete mastery in order to benefit from their use. Enormous value can be achieved at every level of experience, even as little as ten minutes.

So dig in now. Be the first among your colleagues to know all that there is to know…

or at least as much of it as you’d like to learn and use!

Drop into The Learning Curve in the Knowledge Base today.

The post Announcing Our New Online Training Course appeared first on TheFormTool.

How best to “lock down” your valuable forms

The Team at TheFormTool — Sun, 17 Jan 2016 20:56:13 +0000

Our customers, some of whom have thousands of dollars worth of time and expertise invested, are very interested in protecting their forms from two sources of potential risk.

First is systemic risk to the library of forms. Whether the risk is an accidental overwrite or a malicious deletion, the result can be catastrophic.

The lesser risks are at the user level: What are the best ways to prevent user errors, overwrites, and accidental modifications?

This new video describes a half dozen ways to “lock down” your valuable forms at the various stages of their development and use, from the first gleam in the author’s eye to final delivery to the customer, client, or opponent.

This one has it all and you’ll find it in our online Knowledge Base.

The post How best to “lock down” your valuable forms appeared first on TheFormTool.