Scribe - Revision history

Ideath: /* Detailed Instructions */ add minutes checker.

2011-11-10T17:45:32Z

Detailed Instructions: add minutes checker.

Rfs: /* Quick Guide: */

2009-10-20T18:17:14Z

Quick Guide:

Rfs: /* Detailed Instructions */ people aren't keeping hard copies, removed

2008-12-19T19:42:38Z

Detailed Instructions: people aren't keeping hard copies, removed

Rfs: /* Detailed Instructions */

2007-05-17T21:09:18Z

Detailed Instructions

Rfs at 16:14, 22 September 2005

2005-09-22T16:14:57Z

Rfs at 19:56, 11 March 2005

2005-03-11T19:56:14Z

Rfs at 21:11, 21 January 2005

2005-01-21T21:11:29Z

Rfs at 20:58, 21 January 2005

2005-01-21T20:58:27Z

192.168.7.212 at 20:06, 21 January 2005

2005-01-21T20:06:20Z

192.168.254.89: link to Howto for scribing

2005-01-20T19:12:52Z

link to Howto for scribing

New page

For detailed instructions on how to scribe for a meeting, see the following:

[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]

@@ Line 36: / Line 36: @@
 * Before the facilitator asks for consensus, read the proposal back to the group. The facilitator should ask you, but if she doesn't, volunteer to do so. This should help everyone fix in their heads what they are agreeing on, and may bring up further issues.
 * Refine if necessary; just because you wrote it down once doesn't mean it's set in stone. After a proposal is changed, it should be read back to the group before consensus.
-* Note whether consensus was reached; preceding the proposal-become-decision with "DECISION:" so it's easy to find is good.
+* Note whether consensus was reached; preceding the proposal-become-decision with "DECISION:" so it's easy to spot is good.
-* Get names and tasks of those who commit to do stuff. This is important. If a committee is formed, get the names of everyone who is interested. Get as much info as you can, so people know what they said they'd do. It's easy to forget.
+* Get names and tasks of those who commit to do stuff. This is important. If a committee is formed, get the names of everyone who is interested. Get as much info as you can, so people know what they said they'd do. It's easy to forget. It is helpful to keep all of these commitments in their own section of the minutes, as a group "to do" list that can be easily copied to the next meeting's agenda for followup.
 * Rinse and repeat, until time or matter runs out.
 Keep a list of items that should be on next meeting's agenda; these may be followups on items in the meeting, reports from committees formed or research undertaken, items that didn't fit in the current meeting, or just things that come up offhandedly. These items should be in a list at the bottom of the minutes.
-Post the minutes promptly so people can see what was said, decided, and committed to. Minutes should be in plain text format (not html mail or in an attachment) and sent to the appropriate email list within a day or two of the meeting. The subject of the email should contain the name of the group that met, the date, and the word "minutes". A copy of the minutes should be posted to the minutes email list as well. (Remember to send any corrections to both places.)
+Post the minutes promptly so people can see what was said, decided, and committed to. Minutes should be in plain text format (not html mail or in an attachment) and sent to the appropriate email list within a day or two of the meeting. The subject of the email should contain the name of the group that met, the date, and the word "minutes". A copy of the minutes should be posted to the minutes email list as well. (Remember to send any corrections to both places.) Some groups (like the board) have a [[minutes checker]] role, who will double-check the text for comprehensibility, completeness, and sensitive material that shouldn't be published to the whole wide internet.
 == See also ==

@@ Line 20: / Line 20: @@
 * Keep a list of items that should be on next meeting's agenda
 * Post the minutes promptly (in plain text format) to the appropriate email list
-* Some groups will keep a hardcopy binder for minutes, and may also keep a list of decisions made at meetings.
+* Some groups may want to keep a hard copy binder for minutes, and may also keep a hard copy list of decisions made at meetings.
 == Detailed Instructions ==

@@ Line 42: / Line 42: @@
 Keep a list of items that should be on next meeting's agenda; these may be followups on items in the meeting, reports from committees formed or research undertaken, items that didn't fit in the current meeting, or just things that come up offhandedly. These items should be in a list at the bottom of the minutes.
-Post the minutes promptly so people can see what was said, decided, and committed to. Minutes should be in plain text format (not html mail or in an attachment) and sent to the appropriate email list within a day or two of the meeting. The subject of the email should contain the name of the group that met, the date, and the word "minutes". A copy of the minutes should be posted to the minutes email list as well.
+Post the minutes promptly so people can see what was said, decided, and committed to. Minutes should be in plain text format (not html mail or in an attachment) and sent to the appropriate email list within a day or two of the meeting. The subject of the email should contain the name of the group that met, the date, and the word "minutes". A copy of the minutes should be posted to the minutes email list as well. (Remember to send any corrections to both places.)
 == See also ==

@@ Line 42: / Line 42: @@
 Keep a list of items that should be on next meeting's agenda; these may be followups on items in the meeting, reports from committees formed or research undertaken, items that didn't fit in the current meeting, or just things that come up offhandedly. These items should be in a list at the bottom of the minutes.
-Post the minutes promptly so people can see what was said, decided, and committed to. Minutes should be in plain text format (not html mail or in an attachment) and sent to the appropriate email list within a day or two of the meeting.
+Post the minutes promptly so people can see what was said, decided, and committed to. Minutes should be in plain text format (not html mail or in an attachment) and sent to the appropriate email list within a day or two of the meeting. The subject of the email should contain the name of the group that met, the date, and the word "minutes". A copy of the minutes should be posted to the minutes email list as well.
 Some groups will keep a hardcopy binder for minutes, and may also keep a list of decisions made at meetings. This will mainly be for policy-making groups, like staff and council, but groups should decide whether they want to do this on a case-by-case basis. If a list of decisions is kept (a good idea), they should be dated so cross-referencing with the appropriate meeting's minutes is possible.

@@ Line 1: / Line 1: @@
-For detailed instructions on how to scribe for a meeting, see the following:
+We have lots of meetings; you've volunteered (or been volunteered) to take notes. The scribe can help make the meeting flow more smoothly and make sure people and committees follow through on their commitments. Here are some guidelines to help you in the task.
-[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]
+== Quick Guide: ==
-[[Meeting Tips]]
+Work together with the facilitator to make sure everyone knows what the conversation's about, what they're agreeing to, and to create a record so those discussions aren't wasted.

← Older revision		Revision as of 19:56, 11 March 2005
Line 3:		Line 3:
	[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]		[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]

−	[[~~Overview of a meeting~~]]	+	[[Meeting Tips]]

← Older revision		Revision as of 21:11, 21 January 2005
Line 3:		Line 3:
	[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]		[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]

−	[[~~Meeting Template~~]]	+	[[Overview of a meeting]]

← Older revision		Revision as of 20:58, 21 January 2005
Line 3:		Line 3:
	[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]		[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]

−	[[Meeting ~~Minutes~~ Template]]	+	[[Meeting Template]]

← Older revision		Revision as of 20:06, 21 January 2005
Line 2:		Line 2:

	[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]		[http://freegeek.org/howto/consensus/scribe.html Scribe Howto]
		+
		+	[[Meeting Minutes Template]]