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.

references/standards-of-review-decision-tree.md

View on GitHub
# Standard of Review — Decision Tree

Systematic process for identifying which standard applies to a given
question on judicial review.

---

## Step 1 — Is There a Statutory Standard?

```
Does a statute prescribe the standard?

  YES → Apply the statutory standard.
        In BC, this is often ATA s.58 for administrative tribunals.
        Proceed to Step 5 to apply the standard.

  NO  → Continue to Step 2 (Vavilov categories).
```

### BC Statutory Standards (ATA s.58)

Where s.58 applies to a tribunal (including the RTB):

- **Findings of fact** → patent unreasonableness (s.58(2)(a))
- **Discretionary decisions** → patent unreasonableness (s.58(2)(a))
- **Home statute interpretation** → varies by tribunal; check statute
- **Application of common law** → varies
- **Procedural fairness** → Baker analysis, not merit standard

---

## Step 2 — Vavilov Correctness Categories

Under the common-law Vavilov framework (where no statutory standard),
does one of the five correctness categories apply?

```
Is this a CONSTITUTIONAL question?
  YES → Correctness

Is this a GENERAL QUESTION OF LAW OF CENTRAL IMPORTANCE?
  Something like solicitor-client privilege, res judicata, Charter
  interpretation, or other issues that extend well beyond the specific
  administrative context
  YES → Correctness

Is this a JURISDICTIONAL BOUNDARY question between two tribunals?
  Which of Body A or Body B has authority?
  YES → Correctness

Is there a STATUTORY RIGHT OF APPEAL for questions of law?
  YES → Correctness for those questions of law

Has the LEGISLATURE clearly prescribed correctness?
  YES → Correctness
```

If any of the above → Correctness applies.

If none → Continue.

---

## Step 3 — Default to Reasonableness

Where no statutory standard and no correctness category → Reasonableness
is the presumptive standard for the merits.

---

## Step 4 — Procedural Fairness Is Separate

Procedural fairness is not on the standards-of-review spectrum. It's a
separate analysis under Baker.

For any procedural fairness ground:

- Apply the Baker factors to determine required content
- Compare to what the tribunal did
- Argue breach if there's a gap

---

## Step 5 — Applying the Standard

### Correctness Application

- Court substitutes its own judgment
- No deference to tribunal reasoning
- Court decides the question anew
- Tribunal's reasons are irrelevant to the analysis

### Reasonableness Application (Vavilov)

- Focus on the reasoning process, not just outcome
- Consider legal and factual constraints
- Consider whether reasons engage with central submissions
- Consider whether reasons are intelligible
- Consider whether outcome falls within acceptable range

The court asks: is the decision transparent, intelligible, and
justified?

### Patent Unreasonableness Application (ATA s.58)

Highest deference. Court asks whether the decision:

- Was made without any evidence
- Rests on a finding no reasonable tribunal could make
- Reflects legal reasoning so defective no reasonable tribunal could
  adopt it
- Falls so far outside the acceptable range that no reasonable
  interpreter could reach it

For fact findings under s.58(2)(a): "clearly irrational" is another
formulation used in the case law.

---

## Step 6 — For Compound Questions

Sometimes a single decision involves multiple types of questions.
Different standards may apply to different aspects.

Example: An RTB decision might involve:
- Fact finding (patent unreasonableness under s.58)
- Application of RTA (patent unreasonableness or reasonableness,
  depending on how the ATA treats interpretation for that tribunal)
- Procedural fairness (Baker analysis)

Apply each standard to the aspect it governs. Don't argue every aspect
under one standard.

---

## Step 7 — Building the JR Argument

For each ground of review:

```
GROUND: [description]

APPLICABLE STANDARD:
  Source: [ATA s.58(x) / Vavilov / Baker]
  Standard: [correctness / reasonableness / patent unreasonableness /
             procedural fairness]

APPLICATION OF STANDARD:
  [How the tribunal's decision fails the standard]

REMEDY SOUGHT:
  [Set aside / remit / declare]
```

Calibrating the argument to the correct standard is crucial. Arguing
correctness on a patent unreasonableness ground weakens the argument.
Arguing patent unreasonableness on a correctness ground is
unnecessarily deferential.

---

## Common Standard-Selection Errors

### Error 1 — Ignoring Statutory Standards

Post-Vavilov, statutory standards persist. In BC administrative law,
ATA s.58 controls for many tribunals. Skipping to Vavilov reasonableness
where the ATA prescribes patent unreasonableness is an error.

### Error 2 — Assuming Correctness for "Legal Questions"

Not every legal question attracts correctness. Under Vavilov, most
legal questions in the tribunal's home statute attract reasonableness.
Only the five categories trigger correctness.

### Error 3 — Assuming Reasonableness for Everything

Reasonableness is presumptive but not universal. The five correctness
categories exist. Statutory standards exist. Procedural fairness is
separate.

### Error 4 — Conflating Standards With Procedural Fairness

Procedural fairness is not correctness or reasonableness. It's a
separate analysis under Baker. Don't jam it into a standards-of-review
framework.

### Error 5 — Framing Everything as Jurisdictional

Post-Vavilov, the "true jurisdictional questions" category is gone.
Framing an argument as jurisdictional to attract correctness rarely
works — the question is now whether the tribunal's interpretation of
its enabling statute was reasonable.

---

## Practical Discipline

For each ground of review, before drafting:

1. Read the ATA / applicable statute — is there a prescribed standard?
2. If no statutory standard, run Vavilov — correctness category?
3. If no correctness category, apply reasonableness
4. If the ground is procedural, run Baker
5. State the standard and its source clearly in the argument
6. Apply the standard rigorously — don't smuggle in a different level
   of scrutiny

A JR that argues the wrong standard is on the wrong footing from the
start. Get the standard right first.
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