Skip to content

ThomasMoreAI/legal-skills-open / ca/administrative/skills/administrative-law-canada-dmang69

administrative-law-canada-dmang69

Verified

Canadian administrative law doctrine — the Vavilov framework for judicial review, standards of review (correctness and reasonableness at common law; patent unreasonableness preserved by BC's ATA s.58), duty of procedural fairness (the Baker factors), legitimate expectations, bias and the reasonable apprehension of bias test (Committee for Justice and Liberty; Wewaykum), jurisdictional error (as reconstituted post-Vavilov), delegated legislation, sub-delegation, fettering of discretion, improper purposes, taking irrelevant considerations into account, and the doctrine of legitimate deference to administrative decision-makers. Focused on Canadian and BC practice where the RTB, Human Rights Tribunal, and other statutory decision- makers operate. ALWAYS trigger when: user asks about judicial review, procedural fairness, standards of review, tribunal decisions, Vavilov, Baker, patent unreasonableness, or the doctrine underlying their BC judicial review petition. Sits underneath bc-judicial-review-guide as the substantive doctrine layer.

templates/procedural-fairness-analysis.md

View on GitHub
# Procedural Fairness Analysis — Blank Template

Full Baker analysis for a procedural fairness ground on judicial
review.

```
DECISION-MAKER: [tribunal / authority]
DECISION UNDER REVIEW: [what decision, date]
AFFECTED PARTY: [who is challenging]

──────────────────────────────────────────────────────────────

STEP 1 — CONTENT OF FAIRNESS (Baker Analysis)

FACTOR 1 — NATURE OF THE DECISION
  Type:    [adjudicative / administrative / legislative]
  Analysis: [how this factor weighs]
  Weight:   [strong / moderate / weak — for higher fairness]

FACTOR 2 — STATUTORY SCHEME
  Applicable statutes: [list]
  Statutory procedural rights: [what the statute provides]
  Appeal / review rights: [what's available]
  Analysis: [how this factor weighs]
  Weight:   [strong / moderate / weak — for higher fairness]

FACTOR 3 — IMPORTANCE TO THE INDIVIDUAL
  Consequences of adverse decision: [what's at stake]
  Severity: [severe / moderate / limited]
  Analysis: [how this factor weighs]
  Weight:   [strong / moderate / weak — for higher fairness]

FACTOR 4 — LEGITIMATE EXPECTATIONS
  Established practices of decision-maker: [what has been done]
  Express promises or representations: [if any]
  Published policies: [if applicable]
  Analysis: [how this factor weighs]
  Weight:   [strong / moderate / weak — for higher fairness]

FACTOR 5 — AGENCY'S CHOICES
  Procedures adopted by agency: [what agency chose]
  Rationale for those choices: [if known]
  Analysis: [deference vs override]
  Weight:   [supports agency / does not override other factors]

──────────────────────────────────────────────────────────────

REQUIRED CONTENT OF FAIRNESS (based on Baker analysis)

The duty of fairness in this specific context required:

  [ ] Adequate notice of the case to be met
  [ ] Adequate time to prepare
  [ ] Opportunity to make submissions (oral / written)
  [ ] Opportunity to call evidence
  [ ] Opportunity to challenge adverse evidence
  [ ] Cross-examination rights
  [ ] Right to counsel
  [ ] Disclosure of adverse material
  [ ] Reasoned decision
  [ ] Unbiased decision-maker
  [ ] Right of appeal or review
  [ ] Other: _______________________

──────────────────────────────────────────────────────────────

STEP 2 — WHAT ACTUALLY HAPPENED

For each required element:

Element: [required element]
  What was required: [content]
  What happened: [what the tribunal actually did]
  Gap: [difference, if any]

Element: [required element]
  ...

──────────────────────────────────────────────────────────────

STEP 3 — IDENTIFYING THE BREACH

Specific procedural defect:
  [precise description]

Where in the record: [reference to transcript, correspondence, etc.]

──────────────────────────────────────────────────────────────

STEP 4 — MATERIALITY

Did the procedural defect affect the outcome?

  For SIGNIFICANT procedural defects, materiality is often presumed
  (e.g. denial of hearing, bias, failure to give notice)

  For LESS SIGNIFICANT defects, materiality must be shown:
    - What could the party have done differently?
    - What evidence or argument was foreclosed?
    - Could the outcome have differed?

Materiality analysis: [reasoning]

──────────────────────────────────────────────────────────────

STEP 5 — DEFENCES

Anticipated defences:

  Defence 1: [waiver — party did not raise the concern at the time]
  Response: [why waiver does not apply]

  Defence 2: [any procedural fairness was afforded]
  Response: [why what was afforded was inadequate]

  Defence 3: [immateriality — the outcome would be the same]
  Response: [why the outcome could have differed]

──────────────────────────────────────────────────────────────

STEP 6 — REMEDY

Sought:
  [ ] Set aside the decision
  [ ] Remit for reconsideration by different panel
  [ ] Remit with directions
  [ ] Declaration

──────────────────────────────────────────────────────────────

STEP 7 — INTEGRATION WITH OTHER GROUNDS

If this is one ground among several, note:
  - Whether it's stronger or weaker than merit grounds
  - Whether success on this ground would avoid the need to argue merit
  - Order in which to present grounds

Note: Procedural fairness is often the strongest ground for a self-
represented petitioner because it doesn't require demonstrating the
tribunal was wrong on the merits — only that the process was unfair.
```
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall