Southern California SPIN
Meeting Coordinator's Responsibilities and Timetable


As early as possible, ask the potential speaker if they would be willing to be a SPIN speaker. Explore possible SPIN dates against the speaker's calendar.

Speakers not familiar with us often want to know about us to help determine 1) whether they want to speak to our audience and 2) what they would say based on our background. To assist in this regard, you should point them to, or give/email them a copy of, the SPIN Speaker's Meeting Guidelines which is available at http://www.ics.uci.edu/IRUS/spin/spin_speaker_guidelines.html

Explain that, as the coordinator, you will be collecting various information and passing it to the IRUS Technical Relations Director, Debra Brodbeck. Make sure the speaker has your phone, email, and FAX for contacting you with any questions. The information we need from the speaker is:

Flyers are finalized such that they are made available at the SPIN meeting TWO months in advance, i.e. for two meetings prior.

About the first of the month 3 months prior to the SPIN

Remind the speaker that you need their name, title, affiliation, email address, and URL (if available) as they want it to appear on the flyer. You also need the presentation title, presentation abstract, and their bio at this time. Give them a sample from a previous email flyer. Remember to get their their complete contact information for yourself and IRUS.

Emphasize that we can include only one or two paragraphs. Expect to have to cut what they give you. Some speakers have a long biography. Snip the parts that our audience will want and keep the rest for your oral introduction of the speaker. That way you will have something to say that is not on the flyer.

Tell the speaker you need this by the 10th of the appropriate month to give you, the coordinator, enough time to edit them down and get them to the IRUS Technical Relations Director by the 15th.

When you [the coordinator] have this information edited and ready, please send plain ascii text via email to:

Plain ASCII text is best for most of us. If you also want to send it as HTML (no fancy bells and whistles), we may be able to get it onto Web pages more quickly.

We get into other organizations' newsletters if we get the information in on time or early AND they have space. The best thing is to provide 2 to 3 versions:

Version 1 is most accepted and you can get it in a month early, but send it again before the deadline for the next newsletter.

Giving the overworked newsletter editor a choice gives us more of a say over what does not get cut. If we make their job easier, we are more likely to get our information into their newsletter.

About 3 weeks before the talk

Remind the speaker that they should bring at least 60 copies of their viewgraphs as a handout (2-4 viewgraphs per page, make sure the diagrams and text aren't too small). IRUS prefers that the speaker bring the copies to save expenses. But, especially if the speaker is flying in, IRUS will make the copies if they receive a clean master no later than 1 week prior to the meeting. The address for this is:

snail mail:

FedEx or other special delivery:

Remind the speaker about the steering committee lunch and find out if they want to attend (for the lunch headcount, and be sure to notify the IRUS Technical Relations Director or Administrator). Warn the speaker that we discuss the current meeting and plan the future meetings. Indicate to them that they can stay for as long or as little as they like, i.e. when they get bored, they can leave :-)

IRUS will send a letter addressing AV requests along with a map, directions, parking pass, and flyer approximately 3 weeks prior to the meeting. An electronic version of this letter (i.e. sans hard copy materials) will also be emailed to them at that time.

At the SPIN Meeting

At the SPIN meeting, you will:


Written by Karen Owens, k.owens@ieee.org
Updated 6/20/97
Updated 7/20/98 by Debra Brodbeck, brodbeck@ics.uci.edu
Updated 8/04/98 by Debra Brodbeck

Permission to copy is granted to other SPINs as long as credit is given to the Southern California Software Process Improvement Network (SPIN) and the author, and logical changes changes are made (e.g., changing "IRUS representative" to an appropriate role, changing email and other addresses appropriately).

Return to SPIN home page.