Hands-on+Content+Development

MACUL CONFERENCE =// Hands-on Lab Sessions //= = = = May - September : = = 1. Identify the Hands-on Lab Chairperson (board member) and Committee Members. =
 * 1) Committee brainstorms and identifies areas, specific sessions, and levels of instruction that are considered of high interest for attendees.
 * 2) Chairperson communicates with Bill Wiersma regarding # of labs availablle- platforms and operating systems.
 * 3) Determine hands-on session schedule for conference. Get copy of spreadsheet from last year from Gail Aldridge.
 * 4) Ask Ieva for attendance at last years' hands on lab sessions to gauge interest for this year.
 * 5) Look at the evals from previous year to see if there is info that would improve sessions for this year.
 * 6) Generate a list of quality instructors for given areas for the chairpersonr to contact.
 * 7) Report progress to Board.
 * 8) Communicate with Conference planner regarding website proposal submissions. Who will evaluate the hands on proposals? The hands-on committee or the speaker selection committee??? ULTIMATELY it would be beneficial to have the Hands-On sessions separated from the general sessions and reviewed **__only__** by hands-on committee- as they know what sessions/strands are wanted and needed.

1. Review list of sessions- from online proposals submitted and individual contacts.Comipile the lab schedule in the Excel worksheet and send to Conference Planner, 2. Identify possible software concerns; communicate with the support person (Bill Wiersma). 3. Finalize sessions by late October. 4. Report progress to Board.
 * October **

1. Communicate with Hands-on committee-any possible issues-needs...etc. 2. Investigate whether this committee needs to help the Hands-on Lab Chair person- monitoring labs-making sure evaluation signs are posted, SB-Ceu volunteers are all set. 3. Communicate with conference planner-make sure all presenters have been notified and been given lab information (software needs.deadlines to Bill Wiersma)
 * December/January **:

Meet/communicate with Hands-on Committee re needs and session progress. Check on set-up and take-down of labs; help, if necessary. Help make sure evaluation links are posted and shared to attendees
 * March ** – (During the conference):

= Update timeline description as needed. =