From 7263fa4823a2c979801517438a192013a959bae5 Mon Sep 17 00:00:00 2001 From: Andy Jones Date: Fri, 15 Mar 2024 09:01:19 +0000 Subject: [PATCH 01/19] Fixes #180 --- app/views/tools/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/tools/index.html b/app/views/tools/index.html index 523dae97..eb7574b6 100644 --- a/app/views/tools/index.html +++ b/app/views/tools/index.html @@ -74,7 +74,7 @@

Design and development tools

Source code hosting. See additional guidance for using GitHub. + href="/design-system/github-heroku">additional guidance for using GitHub.
From 3d86e1a4d560961db8cefc1bf0b6974d5bfdb158 Mon Sep 17 00:00:00 2001 From: Andy Jones <42679439+andyjones81@users.noreply.github.com> Date: Fri, 15 Mar 2024 09:05:44 +0000 Subject: [PATCH 02/19] Update bug_report.md Signed-off-by: Andy Jones <42679439+andyjones81@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/bug_report.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index dd84ea78..055ab423 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -7,6 +7,10 @@ assignees: '' --- +**MUST DO** +Assign the 'DfE Design' project to this issue +Assign a label (Documentation, Bug, Enhancement etc) + **Describe the bug** A clear and concise description of what the bug is. From 1847814ff24e3e1e77ee6178ed9e95eb0088148a Mon Sep 17 00:00:00 2001 From: Andy Jones <42679439+andyjones81@users.noreply.github.com> Date: Fri, 15 Mar 2024 09:09:52 +0000 Subject: [PATCH 03/19] Update bug_report.md Signed-off-by: Andy Jones <42679439+andyjones81@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/bug_report.md | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 055ab423..f065a5bc 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -7,23 +7,32 @@ assignees: '' --- -**MUST DO** -Assign the 'DfE Design' project to this issue -Assign a label (Documentation, Bug, Enhancement etc) +# This is mandatory information for an issue to be accepted. -**Describe the bug** +If this information is not provided, it may be closed without action being taken. + +## Must associate a type and project + +1. Assign the 'DfE Design' project to this issue +2. Assign a label (Documentation, Bug, Enhancement etc) + +## Describle the issue A clear and concise description of what the bug is. -**To Reproduce** +## What do you do to reproduce it Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error -**Expected behavior** +## What should happen? A clear and concise description of what you expected to happen. +------ + +## The following is optional information + **Screenshots** If applicable, add screenshots to help explain your problem. From 6fb8776af674f52dd622affee9b00acbdaae1801 Mon Sep 17 00:00:00 2001 From: Andy Jones Date: Fri, 15 Mar 2024 09:13:18 +0000 Subject: [PATCH 04/19] fix heroku link --- app/views/tools/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/tools/index.html b/app/views/tools/index.html index eb7574b6..dddb0eb0 100644 --- a/app/views/tools/index.html +++ b/app/views/tools/index.html @@ -93,7 +93,7 @@

Design and development tools

Prototype hosting. See additional guidance for using Heroku. + href="/design-system/github-heroku">additional guidance for using Heroku. Don't create your own account.
From 7ed995a77b69cbfe25a48fb647aa60dcade1a136 Mon Sep 17 00:00:00 2001 From: Andy Jones Date: Tue, 26 Mar 2024 12:58:05 +0000 Subject: [PATCH 05/19] Fixes #181 - duplicate row in table on inclusivity calculator --- app/data/stats.json | 6 ------ 1 file changed, 6 deletions(-) diff --git a/app/data/stats.json b/app/data/stats.json index 312676b3..a6e5df42 100644 --- a/app/data/stats.json +++ b/app/data/stats.json @@ -249,12 +249,6 @@ "source": "https://www.ofcom.org.uk/__data/assets/pdf_file/0022/234364/digital-exclusion-review-2022.pdf", "type": "d" }, - { - "measure": "Households that only use mobile devices to access the internet", - "percent": 21, - "source": "https://www.ofcom.org.uk/__data/assets/pdf_file/0022/234364/digital-exclusion-review-2022.pdf", - "type": "d" - }, { "measure": "All age groups with zero digital skills", "percent": 8, From c3e75af08325c0216b3c37fb9343f314990d13e7 Mon Sep 17 00:00:00 2001 From: EladTrebor <150268161+EladTrebor@users.noreply.github.com> Date: Thu, 28 Mar 2024 08:05:39 +0000 Subject: [PATCH 06/19] Update to family-hubs - March 2024.html Have removed the information about the pilot opportunities as the application period is closed. Signed-off-by: EladTrebor <150268161+EladTrebor@users.noreply.github.com> --- app/views/our-work/projects/family-hubs.html | 25 +------------------- 1 file changed, 1 insertion(+), 24 deletions(-) diff --git a/app/views/our-work/projects/family-hubs.html b/app/views/our-work/projects/family-hubs.html index fc9ad43d..72dec2bf 100644 --- a/app/views/our-work/projects/family-hubs.html +++ b/app/views/our-work/projects/family-hubs.html @@ -167,29 +167,6 @@

Data and sustainability

digital products.

-

Digital pilot opportunities for new local authority partners

- -

To support the family hubs digital project, we are looking to recruit and provide funding to up to 5 - new - local - authorities for 2 digital pilot opportunities. You can apply if you are interested in either:

- -

If you are from an interested local authority, you can find - out more about the pilots and how to apply. The closing date for applications is 23:59 on 19 - February - 2024.

-

Alternatively, if you want to contact us directly and obtain a copy of the application form and - guidance, - send an - email to digital.familyhubs@education.gov.uk. -

- -

Next steps

@@ -364,4 +341,4 @@

Date: Thu, 28 Mar 2024 15:39:43 +0000 Subject: [PATCH 07/19] Update family-hubs-ID date change.html Updated date Signed-off-by: EladTrebor <150268161+EladTrebor@users.noreply.github.com> --- app/views/our-work/projects/family-hubs.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/our-work/projects/family-hubs.html b/app/views/our-work/projects/family-hubs.html index 72dec2bf..beafca2d 100644 --- a/app/views/our-work/projects/family-hubs.html +++ b/app/views/our-work/projects/family-hubs.html @@ -31,7 +31,7 @@

{{pageName}}

Published

-

12 October 2023

+

28 March 2024

Author

From a3c7f53c3b20bd30d71ed80b0466682783f3abf7 Mon Sep 17 00:00:00 2001 From: Andy Jones <42679439+andyjones81@users.noreply.github.com> Date: Sun, 7 Apr 2024 09:32:00 +0100 Subject: [PATCH 08/19] Create ci.yml Signed-off-by: Andy Jones <42679439+andyjones81@users.noreply.github.com> --- .github/workflows/ci.yml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .github/workflows/ci.yml diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml new file mode 100644 index 00000000..467609b5 --- /dev/null +++ b/.github/workflows/ci.yml @@ -0,0 +1,20 @@ +name: CI +on: [push] +jobs: + lhci: + name: Lighthouse + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + - name: Use Node.js 16.x + uses: actions/setup-node@v3 + with: + node-version: 16.x + - name: npm install, build + run: | + npm install + npm run build + - name: run Lighthouse CI + run: | + npm install -g @lhci/cli@0.13.x + lhci autorun From ad48885a3475aaea5df7286eef7a042744c5c29e Mon Sep 17 00:00:00 2001 From: Andy Jones <42679439+andyjones81@users.noreply.github.com> Date: Sun, 7 Apr 2024 09:33:44 +0100 Subject: [PATCH 09/19] Create lighthouse.yaml Signed-off-by: Andy Jones <42679439+andyjones81@users.noreply.github.com> --- .github/workflows/lighthouse.yaml | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 .github/workflows/lighthouse.yaml diff --git a/.github/workflows/lighthouse.yaml b/.github/workflows/lighthouse.yaml new file mode 100644 index 00000000..60e3882b --- /dev/null +++ b/.github/workflows/lighthouse.yaml @@ -0,0 +1,24 @@ +name: Lighthouse +on: + push: + branches: [main] + pull_request: + branches: [main] +jobs: + lhci: + name: Lighthouse + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + - name: Use Node.js 16.x + uses: actions/setup-node@v1 + with: + node-version: 16.x + - name: npm install, build + run: | + npm install + npm run build + - name: run Lighthouse CI + run: | + npm install -g @lhci/cli@0.7.x + lhci autorun From 04e1f0da17d94858cd66e5453c64ab2fd5daef2b Mon Sep 17 00:00:00 2001 From: Andy Jones <42679439+andyjones81@users.noreply.github.com> Date: Sun, 7 Apr 2024 09:35:08 +0100 Subject: [PATCH 10/19] Update ci.yml Signed-off-by: Andy Jones <42679439+andyjones81@users.noreply.github.com> --- .github/workflows/ci.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 467609b5..8e6e6427 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -6,10 +6,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - - name: Use Node.js 16.x + - name: Use Node.js 20.x uses: actions/setup-node@v3 with: - node-version: 16.x + node-version: 20.x - name: npm install, build run: | npm install From f4826a122c4ef5c4128d320040c0adab0a10407e Mon Sep 17 00:00:00 2001 From: Andy Jones <42679439+andyjones81@users.noreply.github.com> Date: Sun, 7 Apr 2024 09:35:20 +0100 Subject: [PATCH 11/19] Update lighthouse.yaml Signed-off-by: Andy Jones <42679439+andyjones81@users.noreply.github.com> --- .github/workflows/lighthouse.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/lighthouse.yaml b/.github/workflows/lighthouse.yaml index 60e3882b..77420457 100644 --- a/.github/workflows/lighthouse.yaml +++ b/.github/workflows/lighthouse.yaml @@ -10,10 +10,10 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - - name: Use Node.js 16.x + - name: Use Node.js 20.x uses: actions/setup-node@v1 with: - node-version: 16.x + node-version: 20.x - name: npm install, build run: | npm install From c62fda7204218d4e9792e81c1b952c788b87283d Mon Sep 17 00:00:00 2001 From: Andy Jones <42679439+andyjones81@users.noreply.github.com> Date: Sun, 7 Apr 2024 09:41:09 +0100 Subject: [PATCH 12/19] Update lighthouse.yaml Signed-off-by: Andy Jones <42679439+andyjones81@users.noreply.github.com> --- .github/workflows/lighthouse.yaml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/lighthouse.yaml b/.github/workflows/lighthouse.yaml index 77420457..0c95e03f 100644 --- a/.github/workflows/lighthouse.yaml +++ b/.github/workflows/lighthouse.yaml @@ -1,19 +1,22 @@ name: Lighthouse + on: push: branches: [main] pull_request: branches: [main] + jobs: lhci: name: Lighthouse runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v3 - name: Use Node.js 20.x - uses: actions/setup-node@v1 + uses: actions/setup-node@v3 with: node-version: 20.x + cache: 'npm' # Enable caching of npm dependencies - name: npm install, build run: | npm install From 64e4e98421ea5f490de18704f488a86487fead76 Mon Sep 17 00:00:00 2001 From: Andy Jones Date: Sun, 7 Apr 2024 09:47:05 +0100 Subject: [PATCH 13/19] remove lighthouse --- .github/workflows/ci.yml | 20 -------------------- .github/workflows/lighthouse.yaml | 27 --------------------------- 2 files changed, 47 deletions(-) delete mode 100644 .github/workflows/ci.yml delete mode 100644 .github/workflows/lighthouse.yaml diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml deleted file mode 100644 index 8e6e6427..00000000 --- a/.github/workflows/ci.yml +++ /dev/null @@ -1,20 +0,0 @@ -name: CI -on: [push] -jobs: - lhci: - name: Lighthouse - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - name: Use Node.js 20.x - uses: actions/setup-node@v3 - with: - node-version: 20.x - - name: npm install, build - run: | - npm install - npm run build - - name: run Lighthouse CI - run: | - npm install -g @lhci/cli@0.13.x - lhci autorun diff --git a/.github/workflows/lighthouse.yaml b/.github/workflows/lighthouse.yaml deleted file mode 100644 index 0c95e03f..00000000 --- a/.github/workflows/lighthouse.yaml +++ /dev/null @@ -1,27 +0,0 @@ -name: Lighthouse - -on: - push: - branches: [main] - pull_request: - branches: [main] - -jobs: - lhci: - name: Lighthouse - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - name: Use Node.js 20.x - uses: actions/setup-node@v3 - with: - node-version: 20.x - cache: 'npm' # Enable caching of npm dependencies - - name: npm install, build - run: | - npm install - npm run build - - name: run Lighthouse CI - run: | - npm install -g @lhci/cli@0.7.x - lhci autorun From feb95eafad7db6a273fba5205c1f20f3aaac0283 Mon Sep 17 00:00:00 2001 From: Alice Date: Thu, 11 Apr 2024 12:04:49 +0100 Subject: [PATCH 14/19] update to Digital Education, Health and Care Plan (EHCP) Updated the EHCP page with the new content --- .../projects/education-health-care-plan.html | 210 ++++++++++-------- 1 file changed, 119 insertions(+), 91 deletions(-) diff --git a/app/views/our-work/projects/education-health-care-plan.html b/app/views/our-work/projects/education-health-care-plan.html index ec90fa81..7eff62f9 100644 --- a/app/views/our-work/projects/education-health-care-plan.html +++ b/app/views/our-work/projects/education-health-care-plan.html @@ -1,8 +1,7 @@ {% extends "layouts/content-full-width.html" %} {% set selectedNav = "Our work" %} {% set pageName = "Digital Education, Health and Care Plan (EHCP)" %} -{% set pageDescription = "The Education, Health and Care Plan (EHCP) digital project is a cross-government project. It -aims to support local authorities to improve outcomes for children and young people with EHC plans." %} +{% set pageDescription = "The education, health and care clan (EHCP) digital project is a cross-government project. It aims to support local authorities in improving outcomes for children and young people with EHC plans. " %} {% block hero %}
@@ -30,7 +29,7 @@

{{pageName}}

Published

-

14 November 2023

+

11 April 2024

Author

@@ -58,105 +57,142 @@

Author

Project overview

-

The DfE have made a commitment in the The Department for Education (DfE) have made a commitment in the SEND and alternative provision improvement plan to support further - digitisation of the EHCP process.

-

Following a discovery in summer 2023 to understand the benefits, barriers and limitations of the - digitisation of the EHCP process, we are moving into alpha.

+ class="govuk-link">SEND and alternative provision improvement plan to support further digitisation of the EHCP processes.

+

We carried out a discovery phase in summer 2023 to understand the benefits, barriers and limitations of the EHCP digitisation process. Following a subsequent alpha phase, we are now moving into our beta phase.

- -

The EHCP

- - -

An EHCP is a legal document for an individual child or young person (aged 0-24 years) with special - educational needs and disabilities (SEND).

-

The EHCP includes:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
PhaseStartEnd
DiscoveryMay 2023June 2023
AlphaOctober 2023February 2024
BetaFebruary 2024March 2025
+ +

1) Guidance recommendation

+ +

The guidance will be co-produced with local authorities (LAs), Integrated Care Board professionals, software suppliers and wider stakeholders in the sector. This is to ensure that children and young people gain the most benefit from digitisation. 

+ +

2) Specification for minimum functionality of systems

+ +

These are the functions that a digital EHCP system must do as a minimum and will allow LAs to:

    -
  • a description of the child or young person’s educational, health and social care needs
    • -
  • what provisions must be put in place to help the child or young person achieve key life outcomes
    • -
  • details about the child or young person’s aspirations
    • -
  • details for those in Year 9 or above about preparation for adulthood
    • -
+
  • benchmark their level of digitisation
    • +
  • identify areas they need to improve
    • +
  • identify digital systems that meet the minimum functionality
    • + . + +

    It will also help software suppliers understand what they need to provide and allow new suppliers to come to market.

    +

    We will look to mandate these.

    -

    Discovery activity

    -

    The discovery looked to understand what part digitisation should play in the EHCP process and the potential - longer-term benefits of digital, through research with: +

    3) EHC record data standard

    +

    A data standard will support the digital EHC process, including:

      -
    • local authorities
      • -
    • national bodies
      • -
    • families
      • -
    • digital system suppliers
      • +
    • a data schema (the classification and categorisation of data fields and related hierarchies)
      • +
    • guidance on how it should be used by suppliers and LAs
    -

    The team conducted two deep dives with local authorities (LAs) who have established digital EHCP systems - in place. They spoke to a wide range of LAs, education and healthcare professionals based in that region, - and to local families who had used the software.​ This led to an understanding of LA and - other professionals' experiences of procuring, implementing and using a digital EHCP hub. +

    This will ease data sharing across different systems, integration of systems and allow for consistent data reporting and analysis. 

    -

    The team also reviewed a selection of local authority digital EHCP systems. They considered how information - is captured and whether better communication could improve efficiency. +

    We will look to mandate the data standard. 

    -

    Working with digital Case Management System (CMS) and digital EHCP system suppliers, the team looked to - better understand the products and services on offer.

    -

    Digital EHCP implementation

    -

    Our research found benefits to adopting digital EHCP systems for users including families, young people and - children, and LA case workers. There were still some issues EHCP users faced when using digital systems, - which impacted upon the: +

    4) Secure EHC record transfer mechanism

    +

    We aim to understand options for a technical mechanism for safely and securely transferring an EHC record and plan from one LA to another.

    +

    The mechanism will reduce the administrative burden for LAs and create smoother experiences for children, young people and families.

    +

    Once the options are considered, we will add the mechanism options to the minimum specifications and data standard. This will ensure that LAs use a consistent method which is supported by software suppliers.

    + +

    5) LA support community

    +

    This is long-term engagement with all LAs, enabling them to network with and support one another during their digitisation process. The community will allow us to consistently engage with LAs to develop and test the:

      -
    • experiences of families
      • -
    • quality of plans
      • -
    • ability to keep to deadlines
      • +
    • expected digital EHCP system functionality required
      • +
    • EHC record data standard
      • +
    • way a secure EHC record transfer mechanism would work in practice
      • +
    • LA guidance
    -

    As professionals and families are asked to use the systems multiple times, these pain points occur multiple - times, therefore exacerbating the need to address them.

    -

    The experiences vary depending on where the professional is based, for example within health, education or - special educational needs and disability case management.

    - -

    During alpha phase

    -

    We conducted research to understand the experiences of special educational needs and disabilities (SEND) - leaders in local authorities, education, health and care settings.

    -

    The alpha phase is where we test and shape the ideas and hypotheses from our discovery.

    -

    At the end of this phase, we want a clear set of recommendations that we will look to fund and test during a - private beta phase (like a pilot).

    -

    We are currently testing whether local authorities would be best supported to digitise their EHCP processes - through all or a combination of the following:

    +

    This will include using digitised LAs to form an advisory group.

    -
      -
    • a data standard
      • -
    • a set of requirements for digital systems
      • -
    • standardised EHCP record
      • -
    • facilitation of advice and support
      • +

      6) DfE SEND digital supplier channel

      +

      We will engage with suppliers and LAs on the minimum functionality and data standard of digital EHCP systems through regular meetings. +

      +

      When we reach business as usual, we will have one communication channel to engage with suppliers, share our plans and receive any feedback. +

      +

      This will be a dedicated public sign-up function for all current suppliers and new ones. +

      + +

      Playback webinars

      + +

      We held four playback webinars for local authorities, Integrated Care Boards, software suppliers and wider stakeholders to share both our:

      +
        +
      • alpha findings
        • +
      • recommendations for our beta phase.
      -

      To understand the challenges, benefits and further ideas, we have engaged with:

      -
        -
      • local authority special educational needs and disabilities (SEND) leads
        • -
      • SEND coordinators within education settings
        • -
      • local authority digital and IT leads
        • -
      • suppliers of digital systems
        • -
      • integrated care board designated clinical or medical officers
        • + +

        We explained the case for all SEND services to digitise their EHCP processes to:

        +
          +
        • deliver better experiences for both families and professionals
          • +
        • enable them to continuously improve their services
          • +
        • focus staff time on family engagement rather than managing bureaucracy.
        -

        We have spoken to people using user research interviews, and we held three online workshops. We are also - testing our ideas with a prototype that helps aid discussions during the later stages of the alpha phase. -

        -

        You can find out more about our research and design on our design history.

        -

        Get involved

        -

        To find out more or get involved email: EHCP.reform@education.gov.uk -

        +

        We are looking at the best way to do this, based on both:

        +
          +
        • on-going user-centred research
          • +
        • insights from the Change Programme.
          • +
        + +

        We would like all local authorities to gain the benefits outlined in the SEND and Alternative Provision (AP) Improvement Plan by digitising.

        +

        The DfE is also working hard to identify and spread best practice of delivering EHCPs to improve both the:

        +
          +
        • quality of plans
          • +
        • experience of getting or providing them
          • +
        -

        Background information

        +

        Core principles of our digital EHCP system design and related guidance will include both:

        +
          +
        • embedding transparency
          • +
        • ensuring it captures the child or young person’s voice and needs.
          • +
        -

        The education, health and care plan digital project is work that forms part of the Department for Education's SEND and alternative provision improvement plan.

        +

        A local authority's digital EHCP system should cover the entire EHCP process, including, assessment, drafting, implementing and maintaining a plan.

        +

        Based on the SEND and AP Improvement Plan timelines, we will continue to communicate project timelines on this page and through our community group.

        + +

        Dates for the next LA community group sessions:

        +

        9th May: 1.30 - 2.30pm

        +

        11th June: 11 - 12noon

        +

        18th July: 2.30 - 3.30pm

        + +

        Contact the team

        + +

        To find out more or get involved email: EHCP.reform@education.gov.uk

        +
    -

    Design histories

    @@ -202,19 +238,11 @@

    - - - - -

    - - - @@ -303,4 +331,4 @@

    Date: Thu, 11 Apr 2024 15:34:21 +0100 Subject: [PATCH 15/19] Update index.html Added detail for job titles to keep generic. Signed-off-by: Kerry Lyons <48559114+kerryalyons@users.noreply.github.com> --- .../design-system/style-guide/index.html | 21 +++++++++++-------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/app/views/design-system/style-guide/index.html b/app/views/design-system/style-guide/index.html index ded07a9e..9646edd1 100644 --- a/app/views/design-system/style-guide/index.html +++ b/app/views/design-system/style-guide/index.html @@ -211,20 +211,23 @@ ### job titles -We try to avoid generic job titles because they can change regularly. We don't use the job title as an identifier alongside a name, for example: +We try to avoid generic job titles because they can mean different things to different people. -Delivery officer: Joe Bloggs -Caseworker: Francis Blunderbuss +For example, a school business manager might have different responsibilities from one school to another. - +Instead, use language that describes the thing a job role does. Something like, "The person who manages your recruitment should upload the job advert" rather than "Your HR Lead should upload the job advert". + +For internal products and services, try not to use the job title as an identifier alongside a name, for example: + +Delivery officer: Joseph Bloggs +Caseworker: Josephine Bloggs +Project lead: Joey Bloggs -We describe the thing that the job role does. This should make more sense to more people and help guard against future changes, for example: +We would write that a project is assigned to a particular person, for example: -Prepared for advisory board by: Joe Bloggs -Completed by: Francis Blunderbuss -
    Case owner -Project owner +Assigned to: Josephine Bloggs +Job titles can and do change as departments and divisions reorganise and restructure. Avoiding job titles can help to reduce confusion when those titles are no longer used. ## K From b39a2fe62018c1494846b12abe222c779a02ff0f Mon Sep 17 00:00:00 2001 From: Kerry Lyons <48559114+kerryalyons@users.noreply.github.com> Date: Thu, 11 Apr 2024 15:39:48 +0100 Subject: [PATCH 16/19] Update index.html Change to job title section. Deleted 2 examples. Signed-off-by: Kerry Lyons <48559114+kerryalyons@users.noreply.github.com> --- app/views/design-system/style-guide/index.html | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/app/views/design-system/style-guide/index.html b/app/views/design-system/style-guide/index.html index 9646edd1..5ab6acfb 100644 --- a/app/views/design-system/style-guide/index.html +++ b/app/views/design-system/style-guide/index.html @@ -219,9 +219,7 @@ For internal products and services, try not to use the job title as an identifier alongside a name, for example: -Delivery officer: Joseph Bloggs -Caseworker: Josephine Bloggs -Project lead: Joey Bloggs +Delivery officer: Josephine Bloggs We would write that a project is assigned to a particular person, for example: From 6a321b7e89598d321bc18da02de575f1e4d9799f Mon Sep 17 00:00:00 2001 From: Alice Date: Fri, 12 Apr 2024 07:24:36 +0100 Subject: [PATCH 17/19] Fixing a typo EHCP --- app/views/our-work/projects/education-health-care-plan.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/our-work/projects/education-health-care-plan.html b/app/views/our-work/projects/education-health-care-plan.html index 7eff62f9..5df2dfa7 100644 --- a/app/views/our-work/projects/education-health-care-plan.html +++ b/app/views/our-work/projects/education-health-care-plan.html @@ -1,7 +1,7 @@ {% extends "layouts/content-full-width.html" %} {% set selectedNav = "Our work" %} {% set pageName = "Digital Education, Health and Care Plan (EHCP)" %} -{% set pageDescription = "The education, health and care clan (EHCP) digital project is a cross-government project. It aims to support local authorities in improving outcomes for children and young people with EHC plans. " %} +{% set pageDescription = "The education, health and care plan (EHCP) digital project is a cross-government project. It aims to support local authorities in improving outcomes for children and young people with EHC plans. " %} {% block hero %}
    From acf6ffded61cf37e09ecf3b89fd4cbf35c7cb572 Mon Sep 17 00:00:00 2001 From: EladTrebor <150268161+EladTrebor@users.noreply.github.com> Date: Fri, 12 Apr 2024 15:27:35 +0100 Subject: [PATCH 18/19] Update family-hubs-test.html Test - just changed the date Signed-off-by: EladTrebor <150268161+EladTrebor@users.noreply.github.com> --- app/views/our-work/projects/family-hubs.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/views/our-work/projects/family-hubs.html b/app/views/our-work/projects/family-hubs.html index beafca2d..29b09ff6 100644 --- a/app/views/our-work/projects/family-hubs.html +++ b/app/views/our-work/projects/family-hubs.html @@ -31,7 +31,7 @@

    {{pageName}}

    Published

    -

    28 March 2024

    +

    12 April 2024

    Author

    From 742716b83d193b6be4d5ea628ff0a065da1b8ebe Mon Sep 17 00:00:00 2001 From: EladTrebor <150268161+EladTrebor@users.noreply.github.com> Date: Fri, 12 Apr 2024 16:29:09 +0100 Subject: [PATCH 19/19] Update family-hubs - update to LA details.html Updated the list of LA partners Signed-off-by: EladTrebor <150268161+EladTrebor@users.noreply.github.com> --- app/views/our-work/projects/family-hubs.html | 27 +++++++++++--------- 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/app/views/our-work/projects/family-hubs.html b/app/views/our-work/projects/family-hubs.html index beafca2d..535a90f5 100644 --- a/app/views/our-work/projects/family-hubs.html +++ b/app/views/our-work/projects/family-hubs.html @@ -31,7 +31,7 @@

    {{pageName}}

    Published

    -

    28 March 2024

    +

    12 April 2024

    Author

    @@ -70,24 +70,27 @@

    Project overview

    Partnership working

    We are delivering the project through an iterative, agile process. We are working collaboratively - with a - small number of local authority partners who are helping to develop, test and iterate our digital + with a number of local authority partners who are helping to develop, test and iterate our digital products.

    -

    We are working with:

    + +

    During the discovery phase we identified user needs and developed digital solutions. These digital + solutions were then tested in the alpha phase. We are now in the private beta stage. This stage involves + piloting the digital products within our partner local authority areas. +

    + +

    We are currently working with:

      -
    • Lancashire
      • +
    • Lewisham
      • +
    • North East Lincolnshire
    • Redbridge
    • Salford
      • +
    • Sheffield
      • +
    • Somerset
      • +
    • Wolverhampton
    - -

    During the discovery phase we identified user needs and developed digital solutions. These digital - solutions - were then tested in the alpha phase. We are now in the private beta stage. This stage involves - piloting the - digital products within our partner local authority areas.

    - +

    Gaining wider input

    Our partnership working is supplemented by our local authority co-design group.

    We set up the co-design group in September 2022. The group is made up of representatives from local