DFR: steward playbook

From the first member call to a defensible file: the statutes, the clocks and plain-language member updates

On this page

Duty of fair representation (DFR) is the union’s legal duty to handle each member’s representation without arbitrariness, discrimination, or bad faith. Most board complaints grow from missed clocks and silence, not malice. This playbook walks stewards through intake, investigation, deadlines, and member conversations across Ontario's private sector (Labour Relations Act), Ontario colleges (Colleges Collective Bargaining Act), and federally regulated workplaces (Canada Labour Code). Orientation only — not legal advice.

Not legal advice

This page helps stewards run a fair process. It does not coach members to file against the union. Confirm procedure with your local officers and counsel.

Officer Learning module

Before the next meeting, open Module 15 and use its worked example to prepare the question, record, or decision in front of your local.

Duty of Fair Representation

Before you open a file — who owes what

DFR binds the union, not individual stewards personally — but stewards create the paper trail officers and boards will read. Run this gate on every new member contact.

Steward role. You intake facts, start the clock, and document what you did. You do not promise outcomes. Hand complex or conflict files to an officer the same day.
Member rights. Members can ask how their file is being handled. If the union declines to grieve, give them the reasons in writing. No statute requires a letter, but it is the practice that protects everyone. Members cannot demand that every complaint become a grievance.
Officer decision. Local officers (or your CA’s named decision-maker) decide whether to file, advance, or settle. That decision must follow a real investigation — not a hallway vote with no notes.
Conflict of interest. If you cannot represent the member fairly — same department feud, family tie, or you are a witness — recuse in writing and name who took the file.

Silence is the breach

A thoughtful “no” with a written explanation rarely loses a DFR complaint. Ghosting the member after intake, or missing a CA deadline while deciding, is what boards punish.

Which statute and board apply

DFR language is similar across regimes, but the act and board differ. Confirm coverage before you cite a section in a member letter.

Most Ontario private-sector unions. Labour Relations Act, 1995, s. 74. Complaints go to the Ontario Labour Relations Board (OLRB). The duty covers every employee in the bargaining unit, member or not. Read Information Bulletin 12 for the member-facing test.
Ontario college support staff. Colleges Collective Bargaining Act, 2008, s. 56, not the Labour Relations Act. It covers academic and support staff, and complaints also go to the OLRB. Confirm your unit’s act with your staff representative before you quote a section number.
Federally regulated workplaces. Canada Labour Code, s. 37. Complaints go to the Canada Industrial Relations Board (CIRB), usually within 90 days of when the member knew or ought to have known of the problem (s. 97(2)). The test uses the same arbitrary, discriminatory, or bad faith language, with a different board and different forms.

The arbitrary / discriminatory / bad faith test

Boards and courts look for honesty of purpose, non-discrimination, and a non-arbitrary process. Perfect outcomes are not required — a serious process is.

Arbitrary. Rubber-stamping a refusal, never reading the file, treating similar cases differently for no documented reason, or missing known CA deadlines with no reason on record. One honest mistake is not usually a breach, but a pattern of neglect can be.
Discriminatory. Treating members differently because of protected grounds, local politics, or personal dislike. Apply the same intake and investigation steps to every member.
Bad faith. Lying to the member, burying evidence, advancing a personal agenda, or punishing a member for criticizing the local.
Honest disagreement. After a real investigation, officers may reasonably decline a grievance. Document what you reviewed and why — a member can disagree without that being a DFR breach.

Day zero — open the file

The member’s first call sets every clock. Capture facts before opinions, and log the contact before you hang up.

Same-day log entry. Record date, member name, contact info, supervisor or manager, what happened, and which CA articles might apply. One paragraph is enough — but it must exist.
Calendar every deadline. Count forward from the triggering event: Step 1 filing, referral to arbitration, policy grievance windows. Put each date in your calendar and Officer Hub if you use it.
Set expectations. Tell the member you will investigate before deciding. Do not say “we will win” or “this is definitely a grievance.” Give a realistic return date for your next update.
Hand off conflicts. If you cannot act fairly, email the president or chief steward the same day: member name, issue summary, and who is taking the file. Do not leave the member waiting while you “think about it.”

Takeaway

If you only do one thing: write the intake note before end of shift. Memory is not a file.

Days 1–3 — build the record

Boards ask what the union did, not what it believed. Neutral notes beat clever arguments.

Interview the member. Ask what happened, who was present, and what documents exist. Summarize in neutral language — “Member states…” — not “Member is right.”
Request employer documents. Discipline letters, emails, schedules, attendance records — whatever the CA lets you request. Log the date sent and the date received.
Identify witnesses. List names and what each might know. You do not need every statement before officers decide, but you must show you asked.
Keep internal notes internal. Strategy belongs in the officer file — not group texts, not public social posts, not employer cc lines. Redact before sharing anything with the member.

CA deadlines — count forward

Missed grievance clocks are the fastest path to a DFR complaint. Your CA defines the trigger; this section is about discipline-style files where the event starts the clock.

Find the triggering event. Usually the date of discipline, the date the member knew about the decision, or the date of the alleged violation — your CA names which. Write that date at the top of the file.
Count business or calendar days. Read the CA literally: business days vs calendar days, whether weekends count, and whether the clock runs to the employer or the union. When unsure, ask your staff representative before the window closes.
Extensions in writing. If the employer agrees to extend a Step 1 meeting or filing window, get it in email or letter before the original date passes. “They said it was fine on the phone” is not a file.
If you are already late. Stop and escalate to an officer immediately. Document when you discovered the miss and what remedy the CA allows. Under the Labour Relations Act, s. 48(16), an arbitrator may extend a grievance-procedure time limit when there are reasonable grounds and the employer is not substantially prejudiced, unless the CA says that power does not apply. Never count on it, and involve legal counsel.

Calendar beats memory

Officer Hub grievance tools track steps and due dates — use them. A sticky note on your monitor does not survive vacation coverage.

When the union says no — say it in writing

Declining is lawful when the process was real. Silence or vague verbal brush-offs are what members take to the board.

Written explanation. Plain language: what you reviewed (dates, documents, interviews), why the facts do not meet the grievance test under the CA, and the effective decision date.
Offer a review path. Name who can reconsider — president, executive board, staff representative — and how to reach them. Follow your local constitution if it adds steps.
Escalate internally first. If the member asks for review, treat it seriously. A second pair of eyes on the same facts is cheap insurance against a DFR filing.
Never ghost. Even a short email — “We reviewed your file on [date] and will not file a grievance because…” — closes the loop. No response reads as bad faith.

Takeaway

Members remember tone, but boards read timestamps. Send the letter within a few days of the officer decision.

Worked walk-through: written warning intake

Member Alex receives a written warning on Tuesday, 3 March 2026, for “failure to follow scheduling procedure.” Alex believes the warning is without just cause. Your CA gives ten calendar days from receipt to file Step 1. Step 1 deadline: Friday, 13 March 2026.

1. Day 0 — Tuesday 3 March
Alex calls at 4 p.m. You log intake: warning letter date, supervisor name, CA discipline article, and Step 1 due 13 March. You calendar 11 March as your internal “officer decision” date to leave two days’ slack.
2. Day 2 — Thursday 5 March
You interview Alex and request the warning letter plus scheduling emails from HR. A colleague witness may confirm the shift was changed after Alex clocked in. Notes go in the file — facts only.
3. Day 3 — Friday 6 March
Documents arrive. Officers review: warning cites a procedure Alex was never trained on. Decision: file Step 1. If instead the facts were weak, you would draft the decline letter now — not after the 13th.
4. Day 8 — Wednesday 11 March
Step 1 meeting scheduled with employer for 12 March. Alex gets a plain-language update: what was filed, meeting date, and steward attendance. If you had declined, Alex would have the written explanation by today.

Takeaway

Copy this timeline structure for any discipline file — swap dates, keep the spacing between intake, investigation, decision, and member update.

What loses DFR complaints in practice

Most cases are process failures, not evil intent. Leave a paper trail that shows serious consideration.

Missed Step or referral deadline. The CA clock expired while the file sat in someone’s inbox. No extension on record. Fix: calendar at intake; escalate the day you see risk.
No investigation on record. No interview notes, document requests, or officer decision memo. Fix: four neutral paragraphs in the file beat a perfect oral argument with nothing written down.
Verbal no with no follow-up. Member told “we’re not grieving this” in a parking lot, never gets mail or email. Fix: send the decline template the same week officers decide.
Promising victory. “We will get this thrown out.” Then the file is denied. Tell the member what evidence is still missing, who will review it, and when you will report back.
Personal conflict driving the decision. Steward dislikes the member or favours the supervisor. Fix: recuse early; let another steward or officer own the file with clean notes.

What to say — and not say — to the member

Good member communication prevents DFR complaints as often as good files do. Plain language, realistic timelines, confidentiality.

Do not promise outcomes. Say: “I will investigate and the executive will decide whether to file.” Not: “This is an open-and-shut grievance” or “HR will back down once they see our letter.”
Status on a schedule. If you promise an update by Friday, send one — even if the answer is “still waiting on documents.” A short update keeps the member from having to chase the file.
Keep their story confidential. Do not discuss the member’s case in the lunch room or on local social channels. Share facts only with officers who need them for the file.
Disagreement is allowed. A member may be angry when you decline. Stay professional, point to the written explanation, and name the review path. Do not argue in text threads.

Track files in Officer Hub

Officer Hub grievance tools log steps, due dates, and handoffs so coverage stewards see the same clocks you do. They support a fair process — they do not replace legal judgment or your staff representative.

Open grievances in Officer Hub

Sources & references

External resources cited in this guide. National and government URLs often move; if a link 404s, search from that organization’s home page. OPSEU / SEFPO pages on opseu.org may block automated checks — open those links in a browser before you share them in a workshop.

Labour Relations Act, 1995 (Ontario)
Ontario LRA s.74 sets the duty of fair representation (arbitrary, discriminatory, bad faith). College CAAT units may use the CCBA instead — confirm which act applies.
Colleges Collective Bargaining Act, 2008 (Ontario)
Governs Ontario college-sector bargaining. DFR for CAAT support staff is in this Act, not the LRA.
OLRB Information Bulletin 12 — What does DFR mean?
Plain-language OLRB explainer for members. Stewards use this to understand the test — not to coach filing against the union.
OLRB Information Bulletin 11 — DFR applications
How members file a DFR application at the OLRB — know the process so you can run a clean representation file.
Canada Labour Code — s.37 (duty of fair representation)
Federal-sector units — CIRB handles complaints; same arbitrary / discriminatory / bad faith language.

Before you open a file — who owes what

Which statute and board apply

The arbitrary / discriminatory / bad faith test

Day zero — open the file

Days 1–3 — build the record

CA deadlines — count forward

When the union says no — say it in writing

Worked walk-through: written warning intake

1. Day 0 — Tuesday 3 March

2. Day 2 — Thursday 5 March

3. Day 3 — Friday 6 March

4. Day 8 — Wednesday 11 March

What loses DFR complaints in practice

What to say — and not say — to the member

Sources & references

Before you open a file — who owes what

Which statute and board apply

The arbitrary / discriminatory / bad faith test

Day zero — open the file

Days 1–3 — build the record

CA deadlines — count forward

When the union says no — say it in writing

Worked walk-through: written warning intake

1. Day 0 — Tuesday 3 March

2. Day 2 — Thursday 5 March

3. Day 3 — Friday 6 March

4. Day 8 — Wednesday 11 March

What loses DFR complaints in practice

What to say — and not say — to the member

Sources & references