Ties in with the creation of the 2005 version of the Fitting & Misfitting workshop format.
As I allude to in the BiCon 2005 report, there's a big learning curve on which I'm only a little way up, about how to hand on complex information so that someone else can use it and groove with it! and this is all part of that exploration.
When preparing the notes for other people to work from, I felt I was skating an impossible line between (a) giving people too much text to read (both to read out in the session, and as background information), and (b) leaving stuff out which needs to be said.
(For me it's not a problem to read things out word for word and still sound fairly natural, and when I'm preparing notes for myself, I often prepare them with that intention in mind. But most people would rather speak from notes. That's one small aspect of it.)
As regards layout, perhaps one helpful move would be for leaders to get a file some weeks before, as "rich text", HTML or maybe even XML, which they could experiment with to edit & style it into a form they feel happy with. This would have been fairly impractical during BiCon 2005, mainly because as it turned out, I was tweaking the content each time it ran, but could become more practical with a format which had settled down into some kind of final-ish shape.
On the other hand, even if the leaders all wanted to do that (which they might not), that probably still wouldn't be enough to support people in feeling thoroughly at home with the material and understanding why it is as it is. One of the pitfalls is that something unforeseen can come up in the session, and not be written down anywhere in the documented design. Because if I were leading, that situation would be new to me too! so I wouldn't have planned it either - I'd be winging it, but based on all the background thinking which had the design turn out the way it is.
On the other other hand, perhaps the way forward is simply to accept that complex stuff built on complex backgrounds of other thinking takes too much handover effort for the circumstances and available time, and invent simpler things if I want them to be replicated more closely.
So lots to think about there for the future. But, for what it's worth, here is what we had for the sessions at BiCon 2005.