[LabComm] PRESS RELEASE: July 16 re: CUPE challenges BC Rail bidders to spell out benefits to communities

Harprit Khaira hkhaira at cupe.ca
Mon Jul 21 12:57:32 PDT 2003


Hi All:

Please find attached the above noted press release.

Attention BC Division:  Lori...please post to the web.

Area Office Support Staff:  Please distribute.

BC Regional Staff:  Hard copy is in your in-tray.


In Solidarity,

Harprit Khaira, Opeiu 491
Secretary, BCRO Communications


CUPE challenges BC Rail bidders
to spell out benefits to communities

BURNABY – CUPE is calling on BC Rail bidders to tell communities how they
would benefit from a privatized railway.

“We think the four corporate bidders should spell out in public meetings
exactly how their bid would help the people of those communities,” acting
CUPE BC president Mark Hancock said.

“We know the citizens of communities served by BC Rail do not know what a
privatized railway would do for them or to them,” he added. “They want and
need more information than they will get from the secret government in
Victoria.”

“Clearly there would be job loss and that will have an impact on local
business and the community tax base,” Hancock said. “There are potential
dangers to road safety as well.

“So, letting citizens know at public meetings what is in store if the
railway falls into private hands is the responsible thing to do for the
successful corporate bidder,” he added.

While CUPE doesn’t have members in the rail industry, it does have 5,000
members who live in communities along the BC Rail line.

Part of the union’s ongoing Strong Communities campaign is to build
awareness of the impact of privatization on those communities.
-30-
Contact: Ron Verzuh, CUPE Communications, 604-828-7668.  Go to
www.cupe.bc.ca for more information on B.C. Rail privatization.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: July 21 03 BC Rail bidders-2.doc
Type: application/msword
Size: 366592 bytes
Desc: not available
URL: <http://bcfed.net/pipermail/labcomm/attachments/20030721/51b2e42c/attachment.doc>


More information about the LabComm mailing list