Monday, July 20, 2009

Re: Parent use of email lists

I teach my users to Bcc for parent addresses also, but it doesn't always
happen. Additionally, we don't have a whole lot of parent
non-solicitation going on, but when we do, we'd like something in
writing to refer back to. Most people know and understand not to use
email lists for their own purposes, but there's always those few.

Bernadette Roche

Director of Technology
Oakhill Day School
www.oakhilldayschool.org
bernadette.roche@oakhilldayschool.org
816.436.6228

-----Original Message-----
From: A forum for independent school educators
[mailto:ISED-L@LISTSERV.SYR.EDU] On Behalf Of Fred Austin
Sent: Monday, July 20, 2009 8:21 PM
To: ISED-L@LISTSERV.SYR.EDU
Subject: Re: Parent use of email lists

We channel all communications through our Publicity Administrator =20
position. Our database of parent email addresses is private and is =20
stated so in our policies. eMail is a very important part of our =20
school communications and expect our parent community to use email as =20
one of the main vehicles of information. Therefore we simply do not =20
allow any non-school communications to go through our system. All of =20
our emails use BCC for the parent addresses.

We agree with Jason that it is a fine line to not overuse the email =20
system vs good consistent information.

Fred Austin
Technology Director
The Oakwood School
Greenville, NC


On Jul 20, 2009, at 6:08 PM, Jason Johnson wrote:

> While a policy is good cover there a few steps that I believe are =20
> more important, since so few read policies until they have violated =20
> them:
>
> 1. If you do not have one, create an =20
> abuse@[yourschoolsitehere.something]. You should have one for =20
> external entities to report suspected spam (as part of being a good =20
> domain name owner) but publish it at the beginning of the policy and =20
> else where to ensure everyone knows who to tell. This will limit, =20
> but not eliminate, the recriminating email swirl that usually =20
> follows solicitations; which will still happen no matter the policy.
>
> 2. This excuse can be cover because the parents think you do/will =20
> send too much email as a school. Cultures and attitudes vary on how =20
> much is too much but often parents become fatigued on the days they =20
> get one email from the Head, another from the room parent, a third =20
> from the PTO and a fourth from the finance office. If a lot of =20
> parents are using this excuse you may want to look at how you, as a =20
> school, send email.
>
> 3. When it happens, and it will, just send out a friendly reminder =20
> of the policy to all. Do not send the whole policy, just a reminder =20
> that it exists and the abuse@ email address. Certainly talk to the =20
> individual parent, but remind the group as a whole. This is simply =20
> a way to let all parent's know that you have addressed it and that =20
> you have a process that worked.
>
> _J
>
> ____________________________
> Jason at jasonpj@yahoo.com
>
>
>
>
> ________________________________
> From: Bernadette Roche <Bernadette.Roche@oakhilldayschool.org>
> To: ISED-L@LISTSERV.SYR.EDU
> Sent: Monday, July 20, 2009 4:45:09 PM
> Subject: Parent use of email lists
>
> We would like to add a policy to our parent handbook regarding parent
> use of email addresses for solicitation. Some parents won't give us
> email addresses for communication because they are worried they will
> also receive emails from other parents regarding garage sales, beauty
> product sales, etc. Does anyone have a policy that would cover this
> situation and can share?
>
> Thanks,
>
>
>
> Bernadette Roche
>
>
>
> Director of Technology
>
> Oakhill Day School
>
> www.oakhilldayschool.org
>
> bernadette.roche@oakhilldayschool.org
>
> 816.436.6228
>
>
>
>
> [ For info on ISED-L see http://www.gds.org/ISED-L ]
> Submissions to ISED-L are released under a creative commons, =20
> attribution, non-commercial, share-alike license.
> RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=3DISED-L
>
>
>
>
> [ For info on ISED-L see http://www.gds.org/ISED-L ]
> Submissions to ISED-L are released under a creative commons, =20
> attribution, non-commercial, share-alike license.
> RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=3DISED-L
>
>

[ For info on ISED-L see http://www.gds.org/ISED-L ]
Submissions to ISED-L are released under a creative commons,
attribution, non-commercial, share-alike license.
RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=3DISED-L

[ For info on ISED-L see http://www.gds.org/ISED-L ]
Submissions to ISED-L are released under a creative commons, attribution, non-commercial, share-alike license.
RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=3DISED-L