Welcome,
How Can We Help You?

Best-Practice: Editing History and Team Mode

To ensure an overview of changes, extensions or adaptations when creating intelligent templates, we recommend so-called pair programming as a best practice.

The goal of document automation is to ensure a consistently high quality of all templates as well as to minimize errors in the generation of important documents.

  • With this method of working, there is one responsible person (the "pilot"). This person is responsible for the creation of the template in Lawlift and "holds the reins". This person receives change requests and decides on their implementation. In this way, the overview can be maintained and the quality assured.
  • In addition, there is a second person (the "navigator"). Their task is to help identify and document all changes according to the four-eyes principle. However, this person does not work directly in Lawlift.

Together, content decisions are made that are implemented by the pilot and documented by the navigator outside of Lawlift. Similar to pair programming, there is a lively exchange of knowledge and errors can be identified more quickly.

Delete

Tip

This ensures that the changing status of the template is kept in view and that quality is ensured. Confusion and different procedures are prevented. This gives everyone an overview of the project, knowledge is shared and errors are detected more quickly.

Such an approach also eliminates the need for a change history in Lawlift, since the editor always knows where the template currently stands and which changes have been made or are still pending.

The Team Mode

The team mode offers you the possibility to work on a template with several editors at the same time or at different times. But you should be careful here. It can happen quickly that you lose the overview.

Use cases for the team mode are for example a change of editors by other users or the case that a small group of editors shares the responsibility.

If employees have change requests, it can make sense to collect them outside of Lawlift, evaluate them and then have them implemented from a single source.

In any case, it should be avoided that the overview of the editors is lost. Otherwise, there is a risk that the current processing status will be lost from sight and the quality of the template will suffer.

Was this article helpful?

Can't find what you're looking for?

Our award-winning customer care team is here for you.

Contact Support