Skip to content

Pay the legacy carer premium per qualifying claimant or partner; IS carer route through them only - #2001

Merged
MaxGhenis merged 16 commits into
mainfrom
legacy-carer-premium-claimant-only
Oct 4, 2026
Merged

MaxGhenis merged 16 commits into
mainfrom
legacy-carer-premium-claimant-only

Conversation

@MaxGhenis

@MaxGhenis MaxGhenis commented Oct 1, 2026 •

Copy link
Copy Markdown
Collaborator

#1896, which adds is_claimant_or_partner, merged on 2 October (3525263). This PR targets main, and main has been merged in five times. Three merges were clean: 3c48247 at 33339ab, 6fa14dc at 3f6c166 and 2cbf20c at 0cc1d94. Two had conflicts:

Both resolutions keep main's rule and this PR's rule (details below).

Summary

Two caring partners got one legacy carer premium, because gov.dwp.carer_premium.couple has always held the single rate. The law pays the premium once for each qualifying claimant or partner. This PR pays it per person and deletes couple. Since in law two people caring for the same severely disabled person cannot both be entitled, it also caps the premium at one in that case. It corrects the 2025-26 rate to £46.40.

Main has since taken in two parts of this PR's original change:

This PR keeps its tests for both.

Carer premium. IS Regs 1987 Sch 2 para 14ZA(1):

the condition is that the claimant or his partner is, or both of them are, entitled to a carer's allowance under section 70 of the Contributions and Benefits Act or carer support payment.

Para 15(7):

Carer Premium. £48.15 in respect of each person who satisfied the condition specified in paragraph 14ZA.

The same condition and the same "in respect of each person" amount appear in:

  • JSA Regs 1996 Sch 1 para 17 and Part IV (8);
  • ESA Regs 2008 Sch 4 paras 8 and 11(3);
  • HB Regs 2006 Sch 3 para 17 and Part 4 (8);
  • HB (SPC) Regs 2006 Sch 3 paras 9 and 12(4);
  • CTR England (SI 2012/2885) Sch 2 para 9 and Part 4 (4);
  • CTR Wales (WSI 2013/3029) Sch 2 para 9 and Sch 7 para 14;
  • CTR Scotland: SSI 2012/319 Sch 1 para 10. SSI 2021/249 Sch 1 para 5(3) pays "in respect of each partner if they both qualify for it, but only if they are not caring for the same severely disabled person".

One entitlement per cared-for person. SSCBA s.70(7ZA): where two people "would have a relevant entitlement for the same day in respect of the same severely disabled person, one of them only shall have that entitlement". SSI 2023/302 reg 5(3) does the same for Carer Support Payment.

All law text was fetched from legislation.gov.uk data.xml: current revised versions plus point-in-time copies of IS Sch 2 for 2015-2026 on 2026-10-01, and SSI 2021/249 Sch 1 para 5 as at 1 April 2025 on 2026-10-04.

Changes

  • carer_premium: the number of members who are both is_claimant_or_partner and is_entitled_to_carer_benefit, times gov.dwp.carer_premium.single, times 52.
    • That gives 0, one amount or two. It is capped at one amount when partners_care_for_same_severely_disabled_person is true.
    • The entitlement test is main's (Reduce Carer's Allowance and Carer Support Payment by overlapping benefits #1994). It keeps an allowance that an overlapping benefit reduces to nil, and it excludes caring hours without a claim.
    • On main, the premium was couple, which held the single rate, for two or more such members, and single for one.
  • gov.dwp.carer_premium.couple is removed.
    • It has never been twice the single rate. Both files were created in 2021 at £37.50, and from 2023 each uprating copied the single value into couple. Two qualifying partners therefore got £48.15 a week instead of £96.30.
    • single is relabelled as the per-person amount.
    • Reforms should change single. A reform that sets couple now fails with "Could not find the parameter" instead of silently doing nothing.
  • gov.dwp.carer_premium.single, 2025-26: £46.38 → £46.40. That is IS Sch 2 para 15(7) as in force from 7 April 2025, and SSI 2021/249 Sch 1 para 5(1) as in force from 1 April 2025. Every other year from 2015 to 2026 matches the point-in-time legislation.
  • New benefit-unit variable partners_care_for_same_severely_disabled_person. When it is true, the premium is capped at one amount for the benefit unit. It can be supplied.
    • Default: true, unless at least two claimants or partners are entitled and have an award. An award is either:
      • a reported Carer's Allowance or Carer Support Payment award (carers_allowance_reported); or
      • an entitlement that caring hours do not explain, which must have been supplied directly: an amount in payment, a pre-overlap amount or the entitlement itself. "Not explained" means fewer than the qualifying hours, or no claim.
    • Qualifying hours: Carer Support Payment's in Scotland from 2025, and Carer's Allowance's otherwise, as in carers_allowance_pre_overlap.
    • Why: in law, two entitlements mean two different people cared for. In the model, though, Carer's Allowance and Carer Support Payment also follow caring hours, and hours cannot show who is cared for. So a couple who both qualify on hours alone get one premium unless the variable is set to false.
    • The two allowances themselves still pay both partners (Carer's Allowance and Carer Support Payment pay two people caring for the same person (SSCBA s.70(7ZA), SSI 2023/302 reg 5(3)) #2028).
    • Scottish working-age CTR also counts a Universal Credit award with the carer element (SSI 2021/249 Sch 1 para 6(1)(c)). The model does not apply that limb (Scottish working-age CTR carer premium ignores the UC carer element limb (SSI 2021/249 Sch 1 para 6(1)(c)) #2124).
  • income_support_eligible: the formula is main's (Use the State Pension Credit qualifying age, and start-of-year status for Class 4 NI #1907). Its carer limb needs a claimant or partner who is a carer and under the qualifying age for State Pension Credit, so a dependant's caring never opens it. This PR adds only two references, IS Regs reg 4ZA and Claims and Payments Regs 1987 reg 4, and keeps its route tests.
  • Where the premium reaches benefits: in this model, the Income Support, Housing Benefit and council tax reduction applicable amounts, through main's working-age and pension-age premium schedules. Income-based JSA and income-related ESA come from reported awards.

Impact (Enhanced FRS 2024-25, real microsimulation runs)

Both runs use a private copy of the Enhanced FRS 2024-25 file (sha256 e433e532…):

Main now contains steps 1 and 3 of the earlier tables (#1994 and #1907), so the whole change is the old step 2: one amount per qualifying person, £46.40 in 2025-26, and the same-person cap. There are no step rows.

£m 2025 2026 2027 2028 2029 2030
Carer premium as computed for every benefit unit +23.06 +22.73 +23.34 +23.90 +24.49 +25.09
Income Support +0.09 +0.00 +0.00 +0.00 +0.00 +0.00
Housing Benefit +0.00 +0.00 +0.00 +0.00 +0.00 +0.00
Council tax reduction +0.05 +0.05 +0.06 +0.06 +0.07 +0.07
Household net income +0.15 +0.05 +0.06 +0.06 +0.07 +0.07
2025 2026 2027 2028 2029 2030
Benefit units with two caring partners (k) 9.0 9.1 9.1 9.1 9.2 9.2
  of which on IS, HB or CTR (k) 0.12 0.12 0.12 0.12 0.12 0.12
Carers who are not the claimant or partner (k) 0.0 0.0 0.0 0.0 0.0 0.0
IS eligibility changes (k) 0.0 0.0 0.0 0.0 0.0 0.0
Households better off (k) 91.7 0.1 0.1 0.1 0.1 0.1
Households worse off (k) 0.0 0.0 0.0 0.0 0.0 0.0
Base Income Support (£bn) 0.514 0.000 0.000 0.000 0.000 0.000
Base Housing Benefit (£bn) 13.13 13.87 14.24 14.29 14.65 15.03
Base council tax reduction (£bn) 2.26 2.32 2.39 2.46 2.53 2.61
  • The premium: it rises by £22.7m to £25.1m a year.

    • Almost all of that is in the 9.1k benefit units (6 survey records) where both partners report Carer's Allowance. Only 0.12k of them receive IS, HB or CTR.
    • In 2025 the 2p a week rate correction adds £1.2m across 1.18m benefit units.
  • 2025 rate correction: 91.7k households are better off in 2025, mostly through Income Support (+£0.09m; 89.7k benefit units gain).

  • No Housing Benefit change: both benefit units on Housing Benefit with two entitled carers (0.12k units, 2 survey records) are passported on main, which took in Disregard the whole income and capital of Housing Benefit claimants on IS, income-based JSA or income-related ESA #2000 after the earlier tables were run. in_receipt_of_income_support_jsa_ib_or_esa_ir holds for both, so housing_benefit_applicable_income is 0, at or below the applicable amount. Their HB applicable amount rises by about £0.3m a year (2025 and 2026), but their Housing Benefit does not change. In the earlier tables the same units gained about £0.2m a year of Housing Benefit. (An aggregate-only diagnostic on main at b1dd418 checked both records.)

  • Council tax reduction: CTR rises by £0.05m to £0.07m a year, almost all of it in the two-carer units (£0.052m of £0.053m in 2025, and all of it from 2026). CTR showed no change in the earlier tables.

  • Earlier runs: before main took in Reduce Carer's Allowance and Carer Support Payment by overlapping benefits #1994, Use the State Pension Credit qualifying age, and start-of-year status for Class 4 NI #1907, Disregard the whole income and capital of Housing Benefit claimants on IS, income-based JSA or income-related ESA #2000 and its other HB and CTR changes, the household net income change was:

    • +£0.28m in 2025: £0.19m Housing Benefit and £0.09m Income Support;
    • +£0.20m to +£0.21m a year in 2026-30, all of it Housing Benefit.

    The old table is kept locally as tables_before_merge4.md.

  • Unchanged facts:

    • No household is worse off in any year.
    • Income Support eligibility changes for nobody.
    • The model pays no Income Support from 2026.
  • Same numbers at earlier heads: runs at 86acb01 and 8c12d27 give the same numbers as this head in every year. The review fixes only change results for supplied entitlements or for reforms to the minimum hours, and the Enhanced FRS supplies only reported awards and no caring hours.

Scripts and full comparisons are kept locally: dataset_impact.py, compare_impact.py, make_tables.py, and the run JSONs. They hold aggregates only, with no record-level values.

Tests

  • tests/policy/baseline/finance/benefit/carer_premium.yaml (27 cases, hand-computed from the law). PE-UK reads gov parameters at 30 April of the simulation year, so 2025 uses the April 2025 rate. The cases:

    • Single and couple amounts:
      • a single carer; the partner only;
      • both partners with awards, at the 2026 rate (2 × £48.15 × 52) and the 2025 rate (2 × £46.40 × 52).
    • Dependants:
    • Applicable amounts:
      • a working-age couple who both care: benefits_premiums and the CTR applicable amount, (HB Sch 3 para 1(3)(b) £150.15 + 2 × £48.15) × 52;
      • a pension-age couple who both receive CA: the HB applicable amount, (HB (SPC) Sch 3 para 1(2)(b) £383.35 + 2 × £48.15) × 52.
    • The same-person rule, supplied:
      • partners supplied as caring for the same person get one premium;
      • partners supplied as caring for different people get two;
      • three members supplied as claimant or partner (a polygamous marriage) get three premiums, or one if they care for the same person.
    • The default:
      • both partners caring by hours alone get one premium;
      • caring hours without a claim, a reported award its holder would not claim, and an allowance an overlapping benefit reduces to nil (still two);
      • supplied entitlement next to an entitled adult who is not a partner;
      • supplied Carer's Allowance (England) and Carer Support Payment (Scotland) for both partners: two;
      • supplied amounts with 35 hours and no claim: two;
      • supplied pre-overlap Carer's Allowance for a pension-age couple whose State Pension overlaps it to nil: two, with HB applicable amount (383.35 + 2 × 48.15) × 52;
      • supplied entitlement without hours or payment: two;
      • a supplied allowance next to 35 hours: not an award.
    • Roles:
      • an 18-year-old 15 years younger than the other adult is a partner, and 16 years younger is presumed a child (the property generator's boundary);
      • a 17-year-old partner supplied through is_claimant_or_partner counts.
  • tests/policy/baseline/finance/benefit/family/income_support/income_support_carer_route.yaml (5 cases):

    • eligible: a single carer; a carer who does not claim Carer's Allowance (Sch 1B para 4(a)); a partner carer;
    • not eligible: a lone parent whose only carer is a QYP; a couple whose only carer is a 12-year-old.
  • care.yaml: three of main's cases are removed:

    The first two are now in carer_premium.yaml, built per person.

  • council_tax_reduction_carer_support_payment.yaml (main's Count Carer Support Payment as Council Tax Reduction income #1992): the 2025 case is re-derived at £46.40, as above.

Invariants (tests/test_legacy_carer_premium_properties.py)

The generator. The properties are drawn over families of a claimant aged 18-85, an optional partner, and up to three children or QYPs. Each family has:

  • a random reported Carer's Allowance award;
  • random caring hours;
  • a random would-claim flag;
  • for adults, an optional overlapping incapacity benefit.

The generator never draws an adult under 20 who is 16 or more years younger than the other adult, because the model would presume them to be the other's child. That boundary (18 with 33) is pinned with @example.

The properties (Hypothesis).

  1. A dependant's caring never changes carer_premium or income_support_eligible.
  2. carer_premium = (claimants and partners entitled to a carer benefit, capped at one when treated as caring for the same person) × the per-person amount × 52.
    • So it is bounded by 0 and twice the amount.
    • The reference derives entitlement and awards from the inputs, and checks the model's is_entitled_to_carer_benefit against them.
    • The same test checks the default same-person rule.
  3. Caring by the claimant or partner never removes Income Support eligibility and never lowers the premium. Below pension age it always opens the IS route.
  4. Supplying "same person" never raises the premium, and caps it at one amount.

A plain test pins the Scottish hours rule. With the Carer's Allowance minimum raised to 40, a Scottish couple in 2026 who each care 36 hours get one premium. In England, and in Scotland in 2024, the same couple gets none.

Test runs

Local runs at this head's code (8c12d27 for the full suites; f201e7a changes only tests, comments and one documentation string):

  • the benefit and gov YAML suites: 2,072 passed at 8c12d27; at f201e7a, carer_premium.yaml and the CTR Carer Support Payment file pass (39);
  • the property tests: 3 passed at 8c12d27; at f201e7a the new Scottish hours test passes, and it fails under the previous formula;
  • ruff format --check: clean.

CI on f201e7a: run 37218386187 passed: Lint, the four smoke imports (Python 3.11-3.14) and Test (the YAML suite, then pytest including the property tests). CI on 8c12d27 (run 37214155858) also passed.

Earlier records:

Review

Every round ran on a Subfleet lane unless noted. The records are kept locally.

  1. Round 1 (REQUEST CHANGES): the Scottish same-person overpayment, other IS gates, boundary cases and wording. All were fixed. The other IS gates are in Apply the Income Support conditions to the claimant and partner only #2013, which is stacked on this PR.
  2. Round 2 (REQUEST CHANGES): the generator age bound, and the default's stated reason. Both were fixed in 9c7cde8.
  3. Round 3 (APPROVE WITH NITS): its nits were fixed in aa360aa.
  4. After the Reduce Carer's Allowance and Carer Support Payment by overlapping benefits #1994 merge (APPROVE WITH NITS, at fa9a8b6):
  5. After the Use the State Pension Credit qualifying age, and start-of-year status for Class 4 NI #1907 merge (REQUEST CHANGES, at 86acb01):
    • It confirmed the IS conflict resolution and the composition with main's new premium schedules. It checked the hand-computed HB and CTR amounts and every new YAML case.
    • Fixed in 8c12d27:
    • Its other nits:
      • this description was stale; it is rewritten here;
      • the removed couple parameter gives a bare error rather than migration directions, which is left as a follow-up;
      • the property generator supplies no allowance amounts, so the YAML pins those cases.
  6. Confirmation of 8c12d27 (APPROVE WITH NITS):
    • It checked 14,976 couples comparing the old and new default. The two give the same result whenever nothing is supplied and the two minimum-hours parameters are equal, and no input over-pays.
    • Its nits were fixed in f201e7a:
      • the Scottish CTR citation (SSI 2021/249 Sch 1 para 5(1));
      • a docstring note to supply an entitlement for every member;
      • the Scottish hours test;
      • the property-test docstring.

The model's 2026 IS personal allowances (£104.43 single 25+, £164.06 couple) differ from IS Sch 2 para 1 (£95.55, £150.15). That is why no case asserts the IS applicable amount. #1925 rewrites those parameters.

Downstream

axiom: TheAxiomFoundation/rulespec-uk#403 queued (no module encodes the carer premium condition or IS Sch 1B para 4; HB Sch 3, HB (SPC) Sch 3 and ESA Sch 4 are in the pinned corpus, IS Sch 2/1B and JSA Sch 1 need ingesting)

🤖 Generated with Claude Code

MaxGhenis and others added 2 commits October 1, 2026 11:19
IS Regs 1987 Sch 2 para 14ZA(1) and the JSA, ESA, HB and CTR equivalents
give the premium where "the claimant or his partner is, or both of them
are" entitled to Carer's Allowance or Carer Support Payment, and para 15(7)
pays it "in respect of each person who satisfied the condition". The model
counted every benefit-unit member, so a caring child or young person gave
the family the premium, and paid two qualifying partners one amount because
the couple parameter held the single rate. Count only the claimant and
partner, pay the per-person amount for each, remove the couple parameter,
and correct the 2025-26 rate to £46.40.

The Income Support carer route (Sch 1B para 4 with reg 4ZA and SSCBA
s.124(1)(e)) likewise opens only through the claimant or partner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ibility

Hypothesis properties over families of a claimant, an optional partner and up
to three children or qualifying young persons: a dependant's caring never
changes carer_premium or income_support_eligible; the premium is the
per-person amount times the caring claimants and partners; and caring by the
claimant or partner never removes Income Support eligibility. Both fail on
the base branch. Add changelog fragments and note that the premium reaches
the IS, HB and CTR applicable amounts only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SSCBA 1992 s.70(7ZA): where two people would be entitled to Carer's
Allowance for the same severely disabled person, only one of them is, so only
one satisfies the premium condition; SSI 2021/249 Sch 1 para 5(3)-(4) says the
same for Scottish working-age council tax reduction. Add the benefit-unit
input partners_care_for_same_severely_disabled_person (default false, since
two partners who both receive Carer's Allowance must be caring for different
people) and cap the premium at one amount when it is set.

From the independent review of this PR: describe is_carer_for_benefits as the
model's proxy for entitlement, qualify the Scottish working-age rule, add
cases for a pension-age couple, a supplied 17-year-old partner and the same
cared-for person, assert the HB and CTR applicable amounts directly, widen the
property generators to ages 18-85, add a same-person property, and write the
changelog fragments as bullets. The second property (caring by the claimant
or partner never removes IS eligibility) is a positive invariant that also
held before this PR; only the first fails on the base branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis added a commit that referenced this pull request Oct 1, 2026
…sa_income

Review r1 of this PR found three ways a member outside the claimant and
partner, or the wrong partner, still decided eligibility:

- An excluded member's reported ESA switched off the fallback for an
  esa_income entered directly. The gate now asks the simulation whether
  esa_income is an input (simulation.input_variables, as
  marginal_tax_rate_on_capital_gains does). If it is, it reads it as the
  claimant's or partner's award. Otherwise it applies the esa_income
  calculation, now the shared income_related_esa_award helper, to the
  claimant's and partner's reported amounts.
- The award and the conditions could sit on different partners. No new
  claim can be made (UC (TP) Regs 2014 reg 6A(1)), and a partner who
  takes over an award makes a claim (Claims and Payments Regs 1987
  reg 4(4)). So the claimant is the partner who reports the existing
  award, and that person must satisfy (aa), (e) and the first limb of
  (h).
- youngest_child_age_for_legacy_benefits counted a child placed by a
  local authority, who is not a member of the claimant's household
  (IS Regs 1987 reg 16(4)). It now uses
  is_child_or_young_person_for_legacy_benefits.

#2001's "partner is the carer" case now puts the award on the caring
partner. YAML: 21 cases, 5 of which fail on this PR's previous head and
10 on #2001's. The Hypothesis generators add placed children, esa_income
entered directly and household savings, and the differential test
follows the award holder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Round-2 review of this PR: the model pays Carer's Allowance and Carer Support
Payment on caring hours as well as on a reported award, so "both receive a
carer benefit" does not show that two partners care for different people, and
the earlier default (false) still paid two premiums to a couple who entered
hours for the same person. In law two awards do mean two different people
(SSCBA s.70(7ZA); SSI 2023/302 reg 5(3) for Carer Support Payment), so
partners_care_for_same_severely_disabled_person now defaults to true unless at
least two of the claimant and partner report a Carer's Allowance award, and it
can still be supplied. It moves beside carer_premium, since it has a formula.

Also: bound the property generator's partner age in both directions so no
adult under 20 is presumed the other's child (pinned with @example; 20,000
draws find no violation), check the default rule and the cap inside the
per-person invariant, cite SSI 2023/302 reg 5(3) for Carer Support Payment,
add Welsh working-age CTR to the formula comment, say that the same-person cap
applies to the whole benefit unit, test partners supplied beyond two, and give
the two-premium YAML cases reported awards. The model's own Carer's Allowance
and Carer Support Payment still pay both partners (issue #2028).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Round-3 review (APPROVE WITH NITS): count reported awards only among carers,
so a reported award its holder would not claim does not make two; say
"Carer's Allowance or Carer Support Payment award", since
carers_allowance_reported is the model's reported-receipt input for both; and
pin both sides of the property generator's age boundary in YAML (an
18-year-old 15 years younger than the other adult is a partner, 16 years
younger is presumed a child).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MaxGhenis

Copy link
Copy Markdown
Collaborator Author

Composition note from #2078 (stacked on #2009), which makes the CTR means test assess the applicant and partner rather than the benefit unit's claimant and partner.

#2078 adds council_tax_reduction_premiums, which the CTR applicable amount now reads in place of benefits_premiums. For ordinary families it is benefits_premiums, so this PR's premium changes flow through unchanged. Where the household head applies alone (council_tax_reduction_head_applies_alone: the head is liable but is not the benefit unit's claimant or partner), it computes the head's own premiums at the single rates, mirroring the single-claimant rules on #2009's base.

A property test in #2078 (test_head_applying_alone_matches_her_own_benefit_unit) checks that a head who applies alone gets the same applicable amount as the same head entered as her own benefit unit. Whichever of the two PRs lands second should therefore carry this PR's rules into the head-alone path of council_tax_reduction_premiums. For example: pension-age schedules with no adult disability premium; severe disability premium conditions; the carer premium per qualifying claimant. That test fails until it does.

MaxGhenis and others added 3 commits October 3, 2026 10:15
Conflicts with #1994 (carers-overlapping-benefits), resolved as the
composition of both changes:

- carer_premium.py: #1994 changed the qualifying test to
  is_entitled_to_carer_benefit for claimants and partners; this branch
  pays gov.dwp.carer_premium.single once per qualifying claimant or
  partner, capped at one when they care for the same severely disabled
  person, and deletes the couple parameter. The premium now counts
  claimants and partners who are entitled to Carer's Allowance or Carer
  Support Payment (including an entitlement reduced to nil by an
  overlapping benefit), times the single rate, times 52, with the
  same-person cap. The couple parameter stays deleted.
- care.yaml: kept this branch's removal of the three num_carers cases;
  main had rewritten them around the couple rate. Their per-person
  equivalents are in carer_premium.yaml.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After the merge with #1994 the premium counts claimants and partners
with is_entitled_to_carer_benefit. The same-person default now counts
the same people: it is false only when at least two claimants or
partners are entitled with a reported award. Before, a reported award
held by someone who would not claim but cared 35 hours counted towards
the two awards (review round 3, finding 2).

- carer_premium.yaml: the header states the entitlement test; new cases
  for caring hours without a claim (no second premium even when the
  partners care for different people), an allowance reduced to nil by
  an overlapping benefit (still two premiums), supplied entitlement with
  a non-partner adult (main's rewritten care.yaml case, per person), and
  a would-not-claim award that no longer lifts the cap.
- Property tests: the generator draws would_claim_carers_allowance and
  an overlapping incapacity benefit for the adults; the reference derives
  entitlement and the award count from the inputs and checks the model's
  is_entitled_to_carer_benefit against it.
- Changelog: #1994 already restricted the premium to claimants and
  partners, so the fixed entry describes only the per-person amount.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis and others added 7 commits October 3, 2026 16:39
… 4(a)

Review of fa9a8b6: APPROVE WITH NITS
(~/reviews/legacy-carer-premium-2026-10-01/subfleet/review-after-merge.md).

1. The same-person default read only carers_allowance_reported as an
   award, so two partners with Carer's Allowance or Carer Support Payment
   supplied directly got one premium. An award is now a reported award or
   a carer benefit in payment that the qualifying hours do not explain,
   which must have been supplied; a benefit paid to someone who cares the
   qualifying hours is still not read as one. The Enhanced FRS supplies
   only carers_allowance_reported and no hours, so this does not change
   its results. YAML cases: both partners with a supplied allowance in
   England, with supplied CSP in Scotland, and a supplied allowance
   alongside 35 hours.
2. The carer_premium comment now names SSI 2021/249 Sch 1 para 6(1)(c)
   (a UC award with the carer element) and says the model does not apply
   it; filed as #2124.
3. IS carer route: the YAML header quotes Sch 1B para 4(a) and 4(b), and
   a new case pins that a carer who does not claim Carer's Allowance
   still opens the route (para 4(a)).
4. fa9a8b6's message said it addressed review round 3, finding 2. It
   fixed the would-not-claim half; the half about more than two supplied
   claimants or partners, one caring on hours alone, remains as the
   variable documents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No conflicts. Main's #2040 changes is_claimant_or_partner (a flagged
parent with no child under 20 to explain the flag is the parent of a much
younger member at any age); the premium, the same-person default and the
IS carer route read it unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…laim

Second check of 3179fd3 and 0cc1d94 (in-session Opus reviewer):
APPROVE WITH NITS.

1. carer_premium's documentation still described the same-person default
   as counting only reported awards; it now names both kinds of award.
2. The default treated any carer benefit in payment alongside 35 hours as
   explained by the hours. Hours only produce an allowance for someone who
   would claim, so a benefit in payment to someone who would not claim was
   supplied and is now an award. New YAML case: both partners supplied
   Carer's Allowance with 35 hours and no claim get two premiums.

The Enhanced FRS supplies no care_hours, so neither change affects it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One conflict, in income_support_eligible.py. Main's #1907 rewrote the
Income Support conditions: the carer limb now needs a claimant or partner
who is under the qualifying age for State Pension Credit and a carer
(SSCBA 1992 s.124(1)(aa) and (e), IS Regs 1987 Sch 1B para 4). That
already contains this branch's rule (a claimant or partner carer, not any
member), so the formula and its comments are main's. The reference tuple
is the union of both sides: Sch 1B, reg 4ZA, s.124 and Claims and
Payments Regs 1987 reg 4.

Main also brought in a fix for the read-only cache test fixture with
policyengine-core 3.32.16 (#2125), which failed this branch's last CI run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After merging main, income_support_eligible's formula is main's (#1907),
which already opens the carer route only through a claimant or partner,
who must also be under the qualifying age for State Pension Credit. Main's
changelog records that, so this branch no longer claims it. The branch
keeps its Income Support route tests and two extra references.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… £46.40

Review of 86acb01 (subfleet/review-after-merge-2.md): REQUEST CHANGES.

1. Main's #1992 council tax reduction test, which arrived with the merge of
   b1dd418, expected the model's old 2025-26 carer premium of £46.38.
   This branch sets the statutory £46.40 (IS Regs 1987 Sch 2 para 15(7)
   from 7 April 2025), as that test's header already noted (#2110). Its
   applicable amount is now (92.04 + 46.40) x 52 = 7,198.88, and the
   reduction 2,000 - 0.2 x (11,331.60 - 7,198.88) = 1,173.46. The 92.04
   personal allowance half of #2110 is unchanged.
2. The same-person default read only a carer benefit in payment as a
   supplied award. A pension-age couple with supplied Carer's Allowance
   entitlement that the State Pension overlaps to nil, or with
   is_entitled_to_carer_benefit supplied, got one premium where
   s.70(7ZA) gives two. An award is now a reported award or any
   entitlement the caring hours do not explain, which must have been
   supplied. Two YAML cases, both failing under the old formula: the
   pension-age couple (HB applicable amount (383.35 + 2 x 48.15) x 52)
   and supplied entitlement without hours or payment.
3. The hours that explain an entitlement are Carer Support Payment's in
   Scotland from 2025 and Carer's Allowance's otherwise, as in
   carers_allowance_pre_overlap. Both are 35 today, so only reforms
   change: with the Carer's Allowance minimum raised to 40, a Scottish
   couple each caring 36 hours now gets one premium, not two.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review of 8c12d27 (subfleet/review-after-merge-3.md): APPROVE WITH NITS.

1. The Scottish council tax reduction test now cites SSI 2021/249 Sch 1
   para 5(1) for its 2025 carer premium. The point-in-time copy from
   1 April 2025 reads "£46.40".
2. The same-person docstring says to supply an entitlement for every
   member, since members left out take the default.
3. New test: with the Carer's Allowance minimum raised to 40, a Scottish
   couple in 2026 who each care 36 hours are entitled to Carer Support
   Payment on hours alone and get one premium. In England, and in Scotland
   in 2024, the same couple gets none. The test fails under the previous
   formula, which read the Carer's Allowance hours everywhere.
4. The property-test docstring names pre-overlap amounts and entitlements
   among the inputs these families never supply.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MaxGhenis
MaxGhenis merged commit 3518331 into main Oct 4, 2026
6 checks passed
@MaxGhenis
MaxGhenis deleted the legacy-carer-premium-claimant-only branch October 4, 2026 17:32
MaxGhenis added a commit that referenced this pull request Oct 5, 2026
Brings in #1896, #2001 and #1907 among others. Two conflicts:

- income_support_eligible.py: keeps this branch's rule (the award holder
  is the claimant or partner who reports Income Support, and must be in a
  covered prescribed category, under the qualifying age and without
  contributory ESA; income-related ESA read for the claimant and partner
  only; capital test unchanged). Takes main's age test
  (has_attained_state_pension_credit_qualifying_age instead of is_SP_age)
  and main's s.124(1)(g) bar (meets_pension_credit_age_conditions and
  would_claim_pc), with its comment, and says so in the documentation.
- income_support_carer_route.yaml: keeps main's para 4(a)/(b) header and
  its new para 4(a) case, and this branch's award-holder wording and the
  partner case with the award on the caring partner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant