Also, I got in the habit of putting a table of actions right at the front of the minutes (after the preamble of time/date/attendees etc). It was the first thing people would see on opening the doc.
PDF: http://dl.dropbox.com/u/486678/ExampleMinutes_2012-02-14.pdf
DOC: http://dl.dropbox.com/u/486678/ExampleMinutes_2012-02-14.doc
Edit: I once toyed with the idea of trying to write an iPad app that can automagically structure a set of minutes for you. It would have been a way for me to learn iOS and do something useful for myself at the time.
I toyed with a similar idea for an application, but this was about a decade ago when my (most excellent) secretary grumbled about my nitpicking.
It is such a valuable experience because eventually you have to work with people who mess with meetings for a living (politicians, bureaucrats, middle managers in large firms, and the list goes on). Knowing their tricks puts you one step ahead.
1. Metadata -- who was there, start time, end time.
2. What was discussed. Regular reports are typical.
3. What decisions were made.
4. Who will carry out which decisions.
It's common to see 3&4 in one of two formats:
1. Interpolated. "Motion: Jack to install new monitoring package. Moved Jill, Seconded Wei Li. Passed."
2. Appended. A list at the bottom of "action items". The UCC minutes I linked above take this approach, which has the readability advantage.
I offer gentle caution about bureaucracy - some people are great at setting agenda and forming committees and voting on chairs and so on, but lousy at actually getting any work done.
Yes, absolutely. I saw meetings abused during my student politics days. Some really dramatic stuff.