- Published on
Using inteliLex - best practices
In this article you can find some advice how to use inteliLex to get most of it.
What kind of documents should I upload to inteliLex?
The type and quantity of documents to upload to inteliLex depends on the approach of your organization. There are a few main strategies however:
- Choosing role model provisions - this strategy is based on creation of a limited number of documents, that are not real documents but more sets of best provisions, templates and whole blocks of text, that are not duplicated and all are of the same importance.
- Choosing role model documents - using this strategy means upload real documents in the Customer Portal, but only those that are "best" or perceived as good examples. They consist both of unique provisions as well as those standard ones, present in many documents, what can influence the importance of provisions and the suggestion list.
- Upload a part of or whole document base - in this case the organisation puts all of its documents without any verification, what might cause a bit of informational noise (partially limited by the system). This is however the least demanding option when it comes to effort needed.
Those approaches do not exclude each other of course - you can upload part of your document base without verification together with one document with a long list of role model provisions.
So called “soft enter” (does not create a new paragraph; usually added by the combination of Shift + Enter keys) is handled by the system but we recommend not to use it unless needed - in some cases the algorithm might "join" paragraphs, that in the document look like separated ones.
Lists are treated as a whole (and suggested as a whole) only when they are created automatically i.e. when you use the list functionality in MS Word. When the author of the document creates a list manually (e.g. by putting numbers before each new sentence) - only part of the text will be returned as a suggestion in inteliLex.
List - continue numbering
Sometimes lists might seem as "joined" e.g. when numbering is restarted from 1 within a bigger list. From the system point of view, this is only one list and the whole list will be suggested, not only the part which was changed.
Lists with more than one level (nested)
Nested lists (i.e. lists, that have more than one level) are handled by inteliLex, but they have to meet the requirements stated above to work (automatically generated, created as one list).
Tables are also processed by the application, but we do not recommend using them unless needed, as visible provisions can differ from how they are "seen" by the system, what might result in suggestion looking different than in the source document.
Want to know more?