JOB AID: Notes Template for ECC Meetings: Difference between revisions

From WikiNET
Jump to navigation Jump to search
mNo edit summary
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
{| class="wikitable" style="width: 25%; "
{| class="wikitable" style="width: 25%; "
|+
|+
| style="background: powederblue; color: white" |'''Authored by Kristin Thiel, Kerns NET'''
| style="background: PaleTurquoise; color: black" |''Authored by Kristin Thiel, Kerns NET, March 2024''
|}
|}


'''Note-taking Guidance, with Starter Template'''
== Before Meeting ==


# Before meeting:
* Confirm with supervisor or meeting convener what roles/titles are useful to include with names in attendance. This is particularly important during an activation when attendees will have task force roles and regular roles outside the task force (e.g. Ronnie Mompellier's title outside of the activation is "Duty Officer", but in the context of the response she is "BES Liaison"). '''''So''''', which title/role, or both, should be included in the notes?
* Confirm with supervisor the planned organization of the Executive Summary for the notes (see template below).
* Create a new notes document for the meeting: either from a preexisting template if the agency has one, or the starter template below).
* If an agenda is available ahead of the meeting, use that to structure the '''Detail''' section.
* Request a list of invitees from a supervisor. That list will help clarify name spellings later and make it easier to provide a complete list of attendees.
* Use a font that is easy to read for screen. Preferred is Arial 12 pt. Use single spacing and bulleted lists.


## Confirm with leadership what roles are useful to include with names in the attendance. (This is particularly important during a task force when attendees will have task force roles and regular roles outside the task force—which, or both, is most useful to include in the notes?)
== During Meeting ==
## Confirm with leadership the planned organization of the notes’ Executive Summary (see template below).
## Make a new notes doc (from any preexisting templates the agency has or on your own; starter template below in this doc).
## If there’s an agenda you can access ahead of time, use that to structure the Detail section.
## Use an easy-to-read font such as Times New Roman or Arial and 12 pt. Single space. Bulleted lists.


## Log in to the meeting and start adding attendee names as they appear.
* Log into the meeting and add attendee names as they appear.
* Capture concepts: decisions and decision points, to-do's, questions/parking lot topics, and kudos. '''You do not have to write every word or record who said what''' (unless that is important to the context of what is said).
* It is appropriate to say: "For the notes, could you please clarify if there was a decision or follow-up in this conversation?"


# During meeting:
== As Meeting Ends ==


## Capture concepts–including decisions, to-dos, questions/parking lot matters, and kudos. You do not have to write every word or record who said what (unless that is important to understanding the content).
* Copy and paste the chat log into the notes. The raw chat log will not stay in the notes, but it is useful during notes cleanup.
* Check spelling of names and complete roles. Reference the agency/task force and meeting invitation lists to do so.
* Decide if points made throughout the meeting can be reasonably combined by their concepts.
* Include key info from the chat transcript in the meeting minutes in the appropriate locations. Delete the rest of the copied chat transcript.
* Place key points from the meeting, color coded, in the Executive Summary.
* Keep the minutes clear and as brief as possible.
* When the meeting notes are complete, name the file using the following naming convention: ''yyyymmdd_group/task force name_meeting name''.  


## OK to say, “For the notes, could you please clarify if there was a decision or follow-up in this conversation?”
== Basic Meeting Notes Template ==
NOTES HEADER - put in the following lines at the top of the notes, in this order:


# As meeting ends:
* '''Draft status:''' status of the notes (e.g. in process, pending review, final, etc)


## Copy and paste into the notes the chat transcript. (You won’t leave the whole thing in there, but it’ll be useful during your cleanup.)
* '''Group/Task Force Name'''
* '''Name of Meeting - Meeting Notes'''
* '''Date-Time''' (use [[Military Time Conversion Chart|24 hour convention]])


# During cleanup:
''Instructions:'' Leave this color key in the notes for the reader.


## Check spelling of names and complete roles, etc. Reference agency/task force and meeting invitation lists to do so.
* Follow-up: <span style="background:yellow">highlighted in yellow</span>
* Decisions and key reminders: <span style="background:Violet">highlighted in purple</span>
* Questions and parking lot topics: <span style="background:LightSkyBlue">highlighted in blue</span>
* Kudos: <span style="background:Gainsboro">highlighted in gray</span>


## See if points made throughout the meeting can reasonably be combined by concept and do so. (It may be useful to leave record of each point where it happens in the agenda, but it’s often even more useful to place things like asides in with the concept’s main report-out.)
'''Attendees''': ''Instructions:'' First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); etc.


## Include key info from the chat transcript in the meeting minutes in the appropriate locations. Delete the rest of the copied chat transcript.
'''Executive Summary''' ''Instructions:'' Place key points from the meeting here; color-code in the Exec Summary only.
## Put key points from the meeting, color-coded, in the Executive Summary.


## Keep the minutes as brief as possible and clear.
'''Detail:''' ''Instructions:'' organizing by the agenda is a good idea.
 
'''Basic Meeting Notes Template'''
 
[instructions: file naming convention]
 
YYMMDD_GROUP/TASK FORCE NAME_MEETING NAME meeting notes
 
'''PUT STATUS OF NOTES HERE [e.g., in process, pending review, final]'''
 
'''GROUP/TASK FORCE NAME'''
 
'''NAME OF MEETING – Meeting Notes'''
 
'''DATE – TIME''' [instructions: use 24-hour convention]
 
[instructions: Leave this color key in the notes for the reader. The outward-facing colors chosen for this template are the fourth down in their color continuum; the first color is too bright for easy reading.]
 
Follow-Up: highlighted in yellow
 
Decisions and Key Reminders: highlighted in purple  
 
Questions and Parking Lot: highlighted in blue
 
Kudos: highlighted in gray
 
'''Attendees''': [instructions: First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); etc.]
 
'''Executive Summary''' [instructions: put key points from the meeting here; color-code in the Exec Summary only]
 
 
 
'''Detail''' [instructions: organizing by the agenda is a good idea]
 
 
 
[end of template]

Latest revision as of 20:32, 25 March 2024

Authored by Kristin Thiel, Kerns NET, March 2024

Before Meeting

  • Confirm with supervisor or meeting convener what roles/titles are useful to include with names in attendance. This is particularly important during an activation when attendees will have task force roles and regular roles outside the task force (e.g. Ronnie Mompellier's title outside of the activation is "Duty Officer", but in the context of the response she is "BES Liaison"). So, which title/role, or both, should be included in the notes?
  • Confirm with supervisor the planned organization of the Executive Summary for the notes (see template below).
  • Create a new notes document for the meeting: either from a preexisting template if the agency has one, or the starter template below).
  • If an agenda is available ahead of the meeting, use that to structure the Detail section.
  • Request a list of invitees from a supervisor. That list will help clarify name spellings later and make it easier to provide a complete list of attendees.
  • Use a font that is easy to read for screen. Preferred is Arial 12 pt. Use single spacing and bulleted lists.

During Meeting

  • Log into the meeting and add attendee names as they appear.
  • Capture concepts: decisions and decision points, to-do's, questions/parking lot topics, and kudos. You do not have to write every word or record who said what (unless that is important to the context of what is said).
  • It is appropriate to say: "For the notes, could you please clarify if there was a decision or follow-up in this conversation?"

As Meeting Ends

  • Copy and paste the chat log into the notes. The raw chat log will not stay in the notes, but it is useful during notes cleanup.
  • Check spelling of names and complete roles. Reference the agency/task force and meeting invitation lists to do so.
  • Decide if points made throughout the meeting can be reasonably combined by their concepts.
  • Include key info from the chat transcript in the meeting minutes in the appropriate locations. Delete the rest of the copied chat transcript.
  • Place key points from the meeting, color coded, in the Executive Summary.
  • Keep the minutes clear and as brief as possible.
  • When the meeting notes are complete, name the file using the following naming convention: yyyymmdd_group/task force name_meeting name.

Basic Meeting Notes Template

NOTES HEADER - put in the following lines at the top of the notes, in this order:

  • Draft status: status of the notes (e.g. in process, pending review, final, etc)

Instructions: Leave this color key in the notes for the reader.

  • Follow-up: highlighted in yellow
  • Decisions and key reminders: highlighted in purple
  • Questions and parking lot topics: highlighted in blue
  • Kudos: highlighted in gray

Attendees: Instructions: First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); First Last (role, agency); etc.

Executive Summary Instructions: Place key points from the meeting here; color-code in the Exec Summary only.

Detail: Instructions: organizing by the agenda is a good idea.

Retrieved from "https://volunteerpdx.net/index.php?title=JOB_AID:_Notes_Template_for_ECC_Meetings&oldid=5695"