If the kinds of sub-groupings of documents you might need to custom-compile are categorizable in advance (or fall into a small group of fixed combinations known in advance), then you have additional useful options. At the risk of telling you things you already know, here is my best explanation of how you might use keywording, targetted compiling (and collections) for your purposes:
Suppose each document had associated with it one or more category terms (assigned to it as keywords).
You can search for docs that have a certain (or certain combo of) keyword(s). Then the Binder only shows those docs, making them easy to select. Then in Compile you can say to compile just the Current Selection.
Also, you can save your keyword search into a smart Collection and keep a little file of these searches, and Compile can be set to just compile the docs in a certain smart collection.
The usefulness of all of this depends on the collections of clauses you need not just being totally ad hoc, and their being a way of categorizing the parts with keywords so you could use them in combo to effectively get the sub-groups you need.
To use a simpleminded example, suppose the docs were clauses for a kind of contract that is used over and over, but in different combinations. There are certain Basic clauses that go in every contract, but there are some clauses that get added for a Moderately stricter contract and some others that only go in the Strictest contract. Then there is a section of the contract that comes in three flavors (Chocolate, Cherry, Martini) depending on the case (but independent of the strictness of the contract). There would be different ways to apply a keyword strategy to this situation, but here is one. You tag each different clause with one of the following keyword combinations:
Basic Moderate Strict --for a clause that goes in every contract
Moderate Strict – for a clause that goes only into moderate and strict contracts
Strict – for a clause that goes only into strict contracts
Then, when you want to draw up a Strict Cherry contract, you can do a search in Scriv that has this logic: .
You could compile on the fly from there by selecting the resulting binder items and Compiling the Current Selection. Or you could save that search as a Collection (“Strict Cherry”, we might call it), and then in the future all you need ever do is go to Compile and compile the collection Strict Cherry. (Of course, you can also call up the collection from the binder to review it, etc.). Smart collections and search results are, of course, dynamic, so changing what goes into your standard contracts is just a matter of changing keywords associated with the clauses (or adding some new keyworded docs).