[Top] [All Lists]

Re: [CQ-Contest] CQ Contest Certificates.

To: cq-contest@contesting.com
Subject: Re: [CQ-Contest] CQ Contest Certificates.
From: Pete Smith N4ZR <n4zr@contesting.com>
Date: Fri, 16 Nov 2012 09:47:35 -0500
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
I'm not sure I agree with Randy on this. If I could download a certificate with my name, callsign and details of my place in the contest already inserted, I think that would give me as big a rush as receiving a paper certificate in the mail.

73, Pete N4ZR
Check out the Reverse Beacon Network at
blog at reversebeacon.blogspot.com.
For spots, please go to your favorite
ARC V6 or VE7CC DX cluster node.

On 11/16/2012 3:35 AM, Maarten van Rossum wrote:
I certainly can remember my first certificate! In my case it wasn't that
long ago, it must have been the year 2008. I emidiately bought a frame to
put it in so that I could put it on the wall in the shack. Unfortunaltely
it didn't fit the frame (in the US everything is bigger, even the
certificates ;-)).

I think easiest way to let the contest sponsor know that there's no need to
send a certificate is to not mention your address in the Cabrillo file.
If someone left out his of her address by accident, then there should
always be the abbility to download the certificate from the sponsors

By the way, I for one would like to be able to download my certificates in
the European A4 paper size. Fits our frame without having to modify it.

Keep up the good work Randy!

73, Maarten PD2R
PI4DX Contest group

Op vrijdag 16 november 2012 schreef Randy Thompson K5ZD (k5zd@charter.net)
het volgende:


You are right that it is expensive to print and mail certificates to
thousands of people per contest.  However, it is worth it when we get
excited emails from new contesters happy to have won their first award.  I
think we can all remember getting our first few certificates and hanging
them proudly on the wall.  Hard for a pdf file to match that!

We have discussed providing a way for contest participants to opt out of
receiving a certificate.  Perhaps they have a box of them or just don't
to cause us the expense.

The logical place to do this is by a new field in the Cabrillo file.  So
far, the people who maintain the Cabrillo file "standard" have not been
interested in adding a new tag.  Perhaps some more support would encourage
them to change their mind.

Should there be one new tag that says "don't send certificates or plaques
anything"?  Or should be there be two?  One for no certificates and another
for no plaques/awards?  Or could it be as simple as a convention that says
if there is no address provided then don't send anything?


Randy, K5ZD

PS - Hoping for good conditions and lots of certificate/plaque winners in
the CQWW in just 8 days!

-----Original Message-----
From: CQ-Contest [mailto:cq-contest-bounces@contesting.com<javascript:;>]
On Behalf Of
brian coyne
Sent: Wednesday, October 31, 2012 9:19 PM
Subject: [CQ-Contest] CQ Contest Certificates.

On the morning of the ssb contest the mailman delivered two certificates
from CQ, always nice to get them. One was for CQWW CW 2011 the other for
CQWW SSB 2011.

Looking at that mail got me to thinking about the expense incurred by CQ
Mag in sending us these for free. Two A4 envelopes two lots of postal
charges, the logistics of stuffing the envelopes, taking them to the
mailing centre not to mention the task of hand signing them when there
must be many hundreds if not into the thousand of these certificates for
both contests. All businesses benefit from cost reducing measures and CQ
organisation is no exception to that.

I would venture that the majority of entrants have facilities to print e-
certificates, perhaps something could be included in the cabrillo header
or the soabox to the effect that an e-certificate will be acceptable.

Just my thoughts anyway.

73  Brian 5B4AIZ / C4Z.
CQ-Contest mailing list
CQ-Contest@contesting.com <javascript:;>
CQ-Contest mailing list
CQ-Contest@contesting.com <javascript:;>

CQ-Contest mailing list

<Prev in Thread] Current Thread [Next in Thread>