Employer reputation and the right of workers to a private life in dismissal cases: Finding the balance in Canada
Bibliographic record
Abstract
Dismissal of workers for their online and social media activity in circumstances that employers may consider ‘inappropriate,’ even if ‘off-duty,’ has gained much attention recently. The test to determine whether dismissal for off-duty conduct of unionized workers is justified was formulated almost sixty years ago in Millhaven, in which a worker was dismissed for coming to colleagues’ houses at 3:00 a.m. to damage their property. Despite claiming to strike a balance between employer interests and worker rights, Millhaven, and its subsequent application, places great emphasis on employer reputation – emphasis that has recently increased in prominence. In this article, we examine how technological and societal changes contributed to this increased significance and to the erosion of workers’ right to a private life. Employer reputation has become more expansive with the growth of corporate social responsibility and more volatile, yet easier to impact, with the widespread use of technology. Concurrently, technology has erased traditional boundaries between work and personal life, leading to conflicts between workers and employers over worker ‘off-duty’ conduct and what control employers should exercise over it. Protecting the right of workers to a private life in such circumstances has become more important and critical than ever before, and, therefore, Millhaven should be reformulated to restore the balance between employers and workers. We propose a new test that recognizes the importance of the right to a private life and the values it supports, such as individuality and freedom of expression. Our new twofold test strikes a proportionate balance between the right of workers to a private life and the employer’s reputational concerns and obligations to maintain an effective and inclusive workforce. Employers are required to prove that the harm to their reputation has been long-lasting, substantial, and quantifiable and that they are unable to manage the workplace without significant hardship. This principled approach should apply to all workers.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.032 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.004 |
| Science and technology studies | 0.028 | 0.009 |
| Scholarly communication | 0.009 | 0.003 |
| Open science | 0.004 | 0.006 |
| Research integrity | 0.003 | 0.005 |
| Insufficient payload (model declined to judge) | 0.006 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".