GreenwichNews

Woolwich Ferry to face three months of disruption as workers strike

Commuters using the Woolwich Ferry are facing three months of travel disruption as workers strike after what they claim is ‘years of mismanagement’.

The 24-hour strikes will start on Monday, January 3 and be held every Monday, Wednesday and Friday until the end of March.

Unite the union, which represents 58 ferry workers claimed there has also been a failure to agree a new pay and reward scheme.

They also said there is an excessive use of agency staff and failure to provide adequate health and safety training to new employees.

The union said these are issues which have arisen since TfL took back control from the discredited Briggs Marine Contractors Ltd in January this year.

Unite also claim two of their representatives have been victimised.

Unite general secretary Sharon Graham, who has visited the ferry workers’ picket line, said: “The years of mismanagement, involving other operators, have been continued with TfL.

“However there is still an opportunity for TfL to retrieve the situation by entering into a constructive dialogue with Unite.

“Unite is pledged to defend our members’ jobs pay and conditions.

“That applies to our members at Woolwich Ferry who under TfL have had to fight victimisation of their union reps, deal with a total failure to produce a new pay award and end the use of agency staff.”

There have been more than 30 days of strike action this year.

Before the pandemic struck at the beginning of 2020 about 20,000 vehicles a week were using the free service across the Thames which opened in 1889.

Pre-Covid-19, an estimated 2.6 million passengers also used the ferry annually.

A TfL spokeswoman said: “We are in ongoing discussions with Unite and hope to find a resolution as soon as possible.”

Pictured top: Sharon Graham joins the picket line. (credit: Unite the union)

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.