Hi Steve,
we normally manage the sheet index for all disciplines.
Even if some subs do not use Revit, we are the ones authoring the indexes and printing the G sheets containing them. We create placeholders for all disciplines sheets, so that we can do the indexes.
Using the issue/revision parameters gives me the closest thing to a real Sheet Set manager built-in Revit.
When a team member set the issuance for the sheet, of when a cloud is drawn in it, then automatically:
- My index (sheet schedule) shows the sheet.
- The sheet title block information updates.
- The project browser lists the sheet under the current issuance group.
The Sheet Set updates with the sheet and its ready to export the PDFS.
Well, for number 4 we still need to use pyRevit "Create Revised Sheet Set" or use Dynamo scripts to print / export a sheet schedule, but you get the idea.
In order to see some meaningful information in the browser (instead of just 1, 2, 3...), I also have to tweak the numbering of the issue/revision to show the text we need, such as a short description of the set:

The two issues now are:
- If all parameters were exposed in the browser organization, I could use Description, and not need to mess with the Numbering parameter, as shown above.
- This system does not work if we use Numbering by sheet, because the numbering of the issues/revisions is not consistent across the table of revisions, but it varies by sheet, which means the groups in the browser simply show the latest issuance the sheet was assigned to, which is not a consistent sheet set per se:

I hope this makes sense.
Thank you
regards
Gio