diff --git a/app/methodology/page.tsx b/app/methodology/page.tsx index df1433e..d6842e6 100644 --- a/app/methodology/page.tsx +++ b/app/methodology/page.tsx @@ -5,6 +5,7 @@ import Link from "next/link"; import Image from "next/image"; import flowChart from "@/assets/methodology-flow-chart.png"; +import ToggleText from "@/components/ToggleText"; export default function MethodologyPage() { return ( @@ -18,7 +19,7 @@ export default function MethodologyPage() {
- +

Our Objectives

    @@ -39,7 +40,7 @@ export default function MethodologyPage() { - +

    Our Methodology

    @@ -166,10 +167,153 @@ export default function MethodologyPage() { - +

    Methodology FAQ

    -

    TODO

    + Why aren't you using the actual 2019 results? + } + content={ + <> +

    + + Westminster constituency boundaries were reviewed in + 2023 + + , and therefore many constituencies now have new + geographic boundaries. Some constituencies have been + abolished entirely and some new constituencies have been + created. +

    +

    + The 2019 general election was fought using the old + constituencies and boundaries, and these results cannot + be easily mapped onto the new constituency boundaries. + However,{" "} + + Sky & the BBC commissioned research + {" "} + which estimates the vote share each party would have + achieved in 2019 using the new constituency boundaries. + We use these implied 2019 results in our + methodology (see above). +

    + + } + /> + Why aren't you using byelection results?} + content={ + <> +

    + Byelections tend to have low turnout compared to general + elections, and parties may be able to dedicate + more resources to fighting a byelection campaign, + because they&re only fighting byelections in a small + number of constituencies at any one time. +

    +

    + Byelections will still also be using the old + constituency boundaries, which means byelection results + can be difficult to map directly onto the constituency + boundaries which the 2024 election will be fought on. +

    +

    + In constituencies where we manually override our + automated advice, we will consider any relevant + byelection results. +

    + + } + /> + Why aren't you using council election results? + } + content={ + <> +

    + Council elections tend to have low turnout compared to + general elections, and the issues they are fought on can + be significantly different from those which are the + focus in general elections. +

    +

    + In constituencies where we manually override our + automated advice, we will consider any relevant council + election results. +

    + + } + /> + + Why don't your tactical voting recommendations match + your methodology? + + } + content={ + <> +

    + We use the same methodology - described in detail above + - on all seats in England, Scotland & Wales. In some + cases, this methodology cannot give a tactical vote + recommendation, because it's not clear which + progressive party is best placed to stop the tories. +

    +

    + In these constituencies, we will manually make a + recommendation. This may happen close to the election + day, so that we can consider the most up-to-date + information, and we can make the most informed & + accurate recommendation possible. When making + recommendations manually, we consider the data used by + our automated methodology - implied 2019 results, recent + MRPs, target seat lists - as well as other data such as + westminster byelections, local council elections in the + area, etc. +

    +

    + There may be other situations where we need to manually + override our automated methodology, such as if the + candidate for the recommended party stands aside. +

    +

    + When manually making a recommendation, we always make + this clear on the website and in our{" "} + open data, and we cite the + data we have used to come to our recommendation. +

    + + } + /> + +
    + + + +

    + For questions not related to our methodology, please see our + main FAQ page. +