We also urge shared layout books from PlotMaker. Although with some of the shortcomings of know precisely which views need updating, easily finding views that may be placed twice, and coordination of updates to solo models in use (
http://www.graphisoft.com/support/archicad/archiguide/LBKupdate.html), adding the complexity of teamwork functionality to the mix may be premature. It does need to get there though - the sooner the better.
Our current experience on projects with teams greater than four is to have a person wholly devoted to the "talking" and "coordination" required for the layout book.
To answer part of Terrence's post more directly:
We use 2-3 layout books per project
(If you've successfully implemented auto-detailing stay with 1)
(We current use Architectural, Structural and Details)
We designate a single Plot Manager for the project
(They are the traffic cop for importing, updating and plotting)
We carefully use ArchiCAD view sets
(A CAD Manager is assigned if it is too much for the Project Manager)
(Some specific to ease importing to PlotMaker)
(Some specific to common team navigation within the model)
(Some specific to individual navigation within the shared model)
We update in "batches" as best we can
(Just as sign-ins to a shared model should be as infrequent as possible)
(Updates to large layout books are time consuming)
("Plot" from ArchiCAD for revision review as much as possible)
I hope this helps. As you can see there is the potential for two large administrative roles once you are past 30 sheets or so). We view this required overhead and many of these steps as "workarounds" as John sees his (undesired) steps. Both office's efforts indicate that there are improvements necessary in PlotMaker. I am beginning to believe there must be some non-compete clause that must expire before Graphisoft can fully modify PlotMaker for team based projects.
Our one analog architect in the office kindly reminds us of how important getting the drawings onto paper is. That is all we sell besides with time.