Allow for a Clause Library#74

Hi there. I was justing watching your “Templates within Tempates” video, which explains how you can pull in the content of a Word document (e.g., a clause sitting in a Word document) into a document generated from your separate master template when the workflow is run. At the moment, this seems to be an all or nothing approach, i.e., you either insert the entire content of the Word document, or you don’t. If you had, say, 10 clauses that you wished to pull in via this method, you’d need 10 separate Word docs. It would be awesome if we could pull in a part of the Word document, by reference to some tags or shortcode in the Word document that is specific to the part we want to pull in (i.e., the tags or shortcode would wrap around the part we want pulled in). If this were possible, we could compile a clause bank within a single Word document, which would be much more efficient. :)

Hi! You can actually add logic into the sub-document in the same way you would do a master document. Would that help with this use case?

Hi and thanks Dorna. I’m not sure how a single sub-document could be treated as a clause/boilerplate library, with individual clauses being called at different places in the master template/document. Perhaps I’m missing something, but I can’t see how this would work.

Hi Richard - I see what you’re saying, since the entire document would need to be pulled in (even after it had logic applied). This is a great feature suggestion for a clause library.
Currently, you could use a CSV to create a basic version of the clause library. For example:

1. CSV with rows for different non-disclosure clauses and non-compete clauses. The first column would be the name of the clause and the second column could be the full clause (though it wouldn’t respect line spacing if it’s multi-line)
2. Question in workflow that allows you to pick a specific row of the CSV
3. Document that allows you to insert the specific clause (second column) associated with the clause name (first column).

Either way, we can also work on a full clause library in the future, too!

Hi and thanks very much Dorna. The CSV approach is a useful workaround but would probably create formatting issues in the built document. A future feature for a clause library would be awesome :)

A clause library would be fabulous! Currently we do a “work around” by heavily coding a single document to display or hide based upon selections. It’s very labor intensive as we continue to make coding additions.

Just started to play around with Gavel and immediately I look for “Clause Library”… has this been implemented?