top of page

Citic Pacific Mining Sino Quid Quo Pro sex for Mining roles & Exposing Unsafe 14 Hour Shifts and Retaliation After Raising Fatigue Concerns

Writer: Admin
Admin
Oct 15
9 min read

A 12-hour shift in a remote mining roster is already demanding. Stretching that shift to 13 or 14 hours as a permanent expectation changes the risk. It affects fatigue, travel, judgment, reaction time, and the basic trust between workers and management.


This account describes a worker who began employment in October 2009 under a contract that stated a two-weeks-on, one-week-off roster with 12-hour shifts. According to the worker’s account, the actual expectation became much different: fixed shifts of up to 14 hours a day across the two-week swing.


The concern was not occasional overtime. The concern was extended hours becoming normal, then being treated as a condition of keeping the job. When the worker raised fatigue and safety concerns, the response was not a practical review of the roster. The worker says they were pressured to resign, went off work due to stress, received no pay while absent, and was later stood down after repeating that the added hours were a safety issue.


This article sets out the account in a clear timeline, explains why fixed 14-hour shifts can create serious safety concerns in mining, and shows why accurate records matter when fatigue management is under scrutiny.


Wide-angle view of a remote mine haul road at dusk.
Long rosters and dark travel hours can make fatigue harder to manage.

The contract said 12-hour shifts, but the roster told another story


The worker started at CITIC Pacific in October 2009. The contract, as described, stated a two-weeks-on, one-week-off roster with 12-hour shifts.


That kind of roster is common in remote operations, but it depends on clear limits. A 12-hour day already leaves little room for sleep, meals, washing, commuting between camp and site, and recovery. If the shift regularly grows to 13 or 14 hours, the recovery window shrinks.


According to the worker, the longer shifts were not a rare event caused by an emergency. They became an ongoing instruction. The worker says they were ordered to work up to 14 hours a day on a permanent basis during the two-week roster.


That difference matters.


Occasional overtime can be planned, recorded, paid, and reviewed. A permanent extension beyond the contracted day can become a hidden change to the job. If the extra time is not properly recorded, it can also make fatigue risks hard to see from the paperwork.


The worker says they had no issue with occasional overtime when needed. The objection was to fixed shifts above 12 hours, especially when the extra hours raised fatigue concerns and appeared to conflict with what the contract stated.


The timeline shows repeated warnings before the dispute escalated


The account points to several key dates where the worker says the issue was raised with supervisors and management. This timeline matters because it shows the worker did not raise the issue once and immediately refuse work. The concern appears to have been raised repeatedly.


Date

What the worker says happened

Why it matters

October 2009

The worker started employment under a contract describing a two-weeks-on, one-week-off roster with 12-hour shifts.

This sets the agreed baseline for working hours.

18 June 2010

The worker raised concerns on site with a supervisor after the shift had increased to 14 hours a day. The issue was said to be taken to an acting mine manager for later discussion.

This was an early formal warning that the roster increase was disputed.

30 June 2010

Back on site, the worker met with a leading hand about the ongoing 14-hour shifts. The worker says the issue was to be raised with the logistics manager.

The concern moved up the chain, but the worker says no effective change followed.

Late July 2010

A fatigue management meeting was recorded on video, with drivers discussing rosters and extended hours worked.

A video record could support that the issue was openly discussed.

27 July 2010

The worker says they were asked for their resignation after questioning the length of the extended hours.

If accurate, this marks a shift from discussion to pressure.

After 27 July 2010

The worker went to a doctor due to stress and says they received no pay while absent.

The dispute had health and income consequences.

Mine inspector investigation

The worker says the investigation found no one working more than 12 hours based on timesheets. The worker says this contradicted the reality of the hours worked.

This raises the central recordkeeping issue.

November 2010

The worker returned to work, attended a meeting with management, raised the safety concern again, and says they were stood down.

The worker says the retaliation continued after returning.


A timeline like this is not just background. It can show whether a safety concern was raised in good faith, whether management had notice, and whether later action against the worker followed that protected activity.


Close-up view of a handwritten shift roster beside a hard hat.
Written rosters can reveal whether overtime was occasional or built into the swing.

Fatigue management depends on the hours actually worked


Fatigue management is not a paper exercise. It only works if the roster, timesheets, travel time, start times, finish times, and rest periods reflect what is really happening.


In this account, the worker says there was a serious mismatch between recorded hours and actual hours. Mine inspectors reportedly found that nobody was working more than 12 hours according to the timesheets. The worker says that did not match the lived reality of 13 or 14-hour days.


That gap is critical.


If workers regularly perform extra hours that are not shown on official records, the system can look compliant while the workforce carries the risk. Management may point to the timesheets and say the roster is safe. Workers may be living with something very different.


For fatigue management to mean anything, records need to show:


  • The real start and finish time

  • The actual time spent performing work duties

  • Delays at shift change, transport, refuelling, loading, and handover

  • Any overtime required by supervisors

  • Missed breaks or shortened rest periods

  • Patterns across the full two-week swing


In mining, fatigue can affect more than one person. A tired driver or operator can place co-workers, contractors, and the wider site at risk. Heavy vehicles, night work, repetitive tasks, remote travel, and long swings all increase the need for honest reporting.


A fatigue system that ignores real hours worked is not managing fatigue. It is managing paperwork.

The video meeting may be an important record


The worker says there is video from a fatigue management meeting on 27 July 2010 showing drivers discussing rosters and extended hours worked.


A record like that can be important because it may show the issue was not private speculation or a later complaint. It may show that drivers were collectively raising extended-hours concerns in a fatigue management setting.


A video can help answer practical questions:


  • Were workers openly discussing shifts beyond 12 hours?

  • Did management hear those concerns?

  • Did anyone acknowledge the roster pattern?

  • Were workers told the hours would change?

  • Did the company treat the issue as a safety concern or as a performance problem?


The worker also says that after questioning the length of the extended hours, they were asked for their resignation. If that sequence is accurate, it raises a serious concern about retaliation.


A worker should be able to raise a fatigue risk without being treated as disloyal, difficult, or disposable. Safety reporting only works when workers can speak before someone gets hurt.


Being stood down after raising a safety concern changes the issue


The worker says they returned to work in November 2010 and attended a meeting with management. During that meeting, they again stated that the additional hours were a safety concern.


According to the account, a supervisor said that if the worker could not work 13-plus hours, the worker was “no good” to them. The worker says they were then stood down.


That statement, if accurately reported, matters because it frames the problem as a refusal to accept unsafe extended hours rather than a neutral staffing issue. It suggests the worker’s value was tied to accepting shifts beyond the 12-hour contract.


There are two separate issues here.


The first is the roster itself. Was the role supposed to be 12 hours, with occasional overtime, or had management effectively imposed a 13 to 14-hour standard day?


The second is the treatment of the worker after they raised concerns. Was the worker stood down for a legitimate reason, or because they challenged the length of the shifts on safety grounds?


Those are different questions, but they connect. If extended hours were required and the worker was punished for objecting, then the dispute is no longer just about pay or rosters. It becomes a matter of workplace safety, good-faith reporting, and fair treatment.


Eye-level view of a mine worker’s boots on red dirt near a parked haul truck.
Fatigue concerns are raised from the ground, where long hours are felt most.

The requested outcome is practical and limited


The worker’s stated request is not extreme. They are not saying they will never work overtime. They are asking for a return to the original position of a 12-hour day, with occasional overtime only when needed.


The requested outcome includes three clear points.


Return to the contracted roster


The worker wants to return to the original role based on a 12-hour day. That is the roster they say was set out in the employment contract.


Compensation for the unpaid absence


The worker says they have had no pay since going absent due to stress after the resignation request and dispute. They want compensation for that absence.


Payment for overtime actually worked


The worker also wants to be compensated for overtime when it was worked. If shifts extended beyond the contracted 12 hours, and those hours were required or approved, the worker says they should be recognised and paid.


This is a grounded position. It accepts that mining operations sometimes need flexibility. It rejects the idea that permanent unpaid or under-recorded extended hours should become the norm.


What a fair review should examine


A fair review of this situation would not rely only on timesheets if workers say the timesheets do not reflect reality. It would compare records against the full operating picture.


That review should examine:


  • Employment contract terms about roster length and ordinary hours

  • Daily timesheets and any changes made after submission

  • Gate records, bus records, camp travel records, and sign-in systems

  • Supervisor instructions about start and finish times

  • Payroll records for overtime

  • Fatigue management meeting notes or video

  • Statements from other drivers on the same roster

  • Any emails, text messages, notices, or roster sheets showing 13 or 14-hour expectations

  • Medical certificates or doctor records linked to stress absence

  • The reason given for asking for resignation or standing the worker down


The strongest evidence is often not one document. It is the pattern across many records. If timesheets say 12 hours, but transport logs, witness statements, and meeting footage point to longer days, that conflict needs to be treated seriously.


This is also why workers should keep their own accurate notes where possible. A simple diary can matter. Dates, start times, finish times, names of supervisors, and what was said can help reconstruct events when official records are disputed.


Why retaliation harms safety across the whole site


When one worker is punished after raising a safety concern, other workers notice. They may decide it is safer to stay quiet.


That silence can create a dangerous culture. Fatigue risks often build slowly. People adapt to being tired. They normalize near misses. They push through because everyone else does. If reporting leads to blame, the warning signs disappear from view.


A safe site needs the opposite culture. Workers need to know they can raise concerns about rosters, rest, and overtime without risking their income or position. Managers need to treat fatigue concerns as operational warnings, not personal attacks.


Exposing unsafe 14 hour shifts and retaliation after raising fatigue concerns is not about avoiding hard work. It is about recognising that hard work still needs limits. A roster that depends on people being exhausted is not a strong roster. It is a weak control dressed up as commitment.


High-angle view of a remote mining camp at sunrise.
A safe roster has to include enough time for real recovery between shifts.

The real issue is whether safety concerns were heard or punished


The central question is simple: did management respond to a fatigue concern by investigating the real hours worked, or by pressuring the worker to accept the longer shifts?


Based on this account, the worker repeatedly raised concerns after the roster increased from 12 hours to up to 14 hours a day. They say those concerns were discussed with supervisors and a leading hand, raised in a fatigue management meeting, and later repeated to management after returning to work.


The worker says the outcome was pressure to resign, stress-related absence without pay, reliance on timesheets that did not reflect actual hours, and being stood down after again stating the added hours were unsafe.


A fair outcome would start with restoring the 12-hour roster, reviewing the disputed records, paying any overtime that was actually worked, and addressing any loss caused by being removed from work after raising safety concerns.


The lesson reaches beyond one roster or one site. Fatigue management must be based on truth. If workers are expected to work 14 hours, the records should say so, the risk should be assessed, and the workers should be paid. If the contract says 12 hours, management should not turn 14 hours into a permanent hidden condition of employment.


This article is informational only and is not legal advice. Anyone facing a similar situation should keep clear records, seek advice from a qualified workplace representative or lawyer, and raise urgent safety risks through the proper safety channels.


 
 
 

Comments


                                                RECRUITMENT & LABOUR HIRE FOR ELECTRICAL AUTOMATION MECHATRONIC - MOB 0220100318
bottom of page