From 978359619a31685f55b94abbf57b3a933250936f Mon Sep 17 00:00:00 2001 From: Kerry Lyons Date: Wed, 27 Mar 2024 17:12:36 +0000 Subject: [PATCH] all guidance interated to remove reference to alpha and beta peer reviews --- app/views/includes/_side-nav.html | 11 +- .../service-assessments/assessments.html | 37 ++++-- .../complete-peer-review-report.html | 33 ++--- .../discovery-peer-review.html | 60 +++++---- app/views/service-assessments/index.html | 25 ++-- .../peer-review-report.html | 11 +- .../service-assessments/run-peer-review.html | 124 +++++++----------- .../run-service-assessment.html | 33 +++-- app/views/service-assessments/survey.html | 4 +- 9 files changed, 170 insertions(+), 168 deletions(-) diff --git a/app/views/includes/_side-nav.html b/app/views/includes/_side-nav.html index c8c633e..1acbfa8 100644 --- a/app/views/includes/_side-nav.html +++ b/app/views/includes/_side-nav.html @@ -64,12 +64,6 @@ name: "Discovery peer reviews", url: "/service-assessments/discovery-peer-review" },{ -name: "Alpha and beta peer reviews", -url: "/service-assessments/alpha-beta-peer-review" -},{ -name: "Your peer review report", -url: "/service-assessments/peer-review-report" -},{ name: "Service assessments", url: "/service-assessments/assessments" },{ @@ -84,12 +78,9 @@ {% set assessors = [ { -name: "Run a peer review", +name: "Run a discovery peer review", url: "/service-assessments/run-peer-review" },{ -name: "Complete a peer review report", -url: "/service-assessments/complete-peer-review-report" -},{ name: "Run a service assessment", url: "/service-assessments/run-service-assessment" },{ diff --git a/app/views/service-assessments/assessments.html b/app/views/service-assessments/assessments.html index 6f86201..12aa02f 100644 --- a/app/views/service-assessments/assessments.html +++ b/app/views/service-assessments/assessments.html @@ -2,7 +2,7 @@ {% set selectedNav = "Service assessments" %} {% set pageName = "Service assessments" %} -{% set pageDescription = "Which services need to be assessed, types of assessment panels and the outcome for teams"%} +{% set pageDescription = "What a service assessment is, types of assessment panels and the outcome for teams"%} {% block content %} @@ -11,11 +11,14 @@ A service assessment measures a service against the [14 points of the GOV.UK Service Standard](/service-standard). It's a space for service teams to get expert advice from a panel of specialists. +They're usually 4 hours long and take place on Tuesdays, Wednesdays, or Thursdays. + + ## Why have one -All transactional services need to have an assessment. Getting assessed is a condition of your cabinet office spend approval. +All services need to have an assessment. Getting assessed is a condition of your cabinet office spend approval. Read the guidance for [what counts as a transactional service](https://www.gov.uk/service-manual/service-assessments/check-if-need-to-meet-service-standard#what-counts-as-a-transactional-service). @@ -40,10 +43,8 @@ ## DfE panel assessment -If your service has under 100,000 transactions per year, the panel will consist of DfE assessors. - -If your service is non-transactional, it could have a [peer review](/service-assessments/alpha-beta-peer-review). - +If your service has under 100,000 transactions per year, is non-transactional, or is an information service, the panel will consist of DfE assessors. + ## What to prepare for a service assessment Think about the best way to tell the story and show the work of the phase the team is in. This could be a mixture of Lucid boards, docs, and sketches. @@ -76,9 +77,29 @@ There may also be silent observers from DfE or cross-government for learning and development opportunities. -How you want the assessment to run is for you to agree with the panel. For example, you could agree to have a 45-minute show and tell, followed by sections to cover the problem area, users, hypotheses, and measures of success. +### Example assessment agenda + +You should agree in the pre-call with the assessors how the session will run. + +An example agenda might look like this: + +| Time | Action | +|------------------|----------------------------| +| 5 to 10 minutes | Introductions and housekeeping | +| 50 minutes | Team show and tell | +| 50 minutes | User research | +| 10 minutes | Break | +| 45 minutes | Design | +| 20 minutes | Team and governance | +| 25 minutes | Tech | +| 20 minutes | Performance | +| 10 minutes | Wrap up and next steps | + +### During an assessment + +Assessors will review the work of a service team in a [proportionate way](https://www.gov.uk/service-manual/service-assessments/check-if-need-to-meet-service-standard#adapting-the-service-standard) against the Service Standard. -It's up to the team to decide whether you have questions throughout or at the end of the assessment. You can discuss this with the panel on the pre-assessment call. +They will take into account the context the team are working in and ask questions to support the team in demonstrating why they’ve built what they've and how they’ve met the standard. ### After the assessment diff --git a/app/views/service-assessments/complete-peer-review-report.html b/app/views/service-assessments/complete-peer-review-report.html index 7eb2516..d2a0bc8 100644 --- a/app/views/service-assessments/complete-peer-review-report.html +++ b/app/views/service-assessments/complete-peer-review-report.html @@ -1,8 +1,8 @@ {% extends "layouts/content-with-sidenav.html" %} {% set selectedNav = "Service assessments" %} -{% set pageName = "Complete a peer review report" %} -{% set pageDescription = "How to complete a peer review report, what to consider and what happens after the report is submitted"%} +{% set pageName = "Complete a discovery peer review report" %} +{% set pageDescription = "How to complete a discovery peer review report, what to consider and what happens after the report is submitted"%} @@ -10,38 +10,29 @@ {% markdown %} -During the peer review, work together with the rest of the panel to gather your findings and recommendations. +The report should aim to conclude whether the team has understood the problem space and priorities for next steps following the end of discovery. -Do this in a way that suits you. For example, use a shared Word doc or the panel chat in Slack. +If the team has not yet reached a decision on next steps, the report will give feedback and recommendations based on the evidence shared at the peer review. ## Draft the report -### For discovery peer reviews - -During the peer review, consider the practical tips in [Apply the Service Standard in DfE](https://apply-the-service-standard.education.gov.uk/service-standard) against standards 1 to 7 in the discovery phase. This will help you understand if the team has done what they need to do to mark the end of discovery. +During the discovery peer review, consider the practical tips in [Apply the Service Standard in DfE](https://apply-the-service-standard.education.gov.uk/service-standard) against standards 1 to 7 in the discovery phase. This will help you understand if the team has done what they need to do to mark the end of discovery. Although a team in discovery won't yet have made tech choices, they should, if relevant, show an understanding of existing options. -Make sure you consider feedback on the positive aspects of the discovery too, not only on recommendations on what to improve. - -The report should aim to conclude whether the team has understood the problem space and priorities for next steps following the end of discovery. +Acknowledge any constraints or business requirements the team is working to. -If the team has not yet reached a decision on next steps, the report will give feedback and recommendations based on the evidence shared at the peer review. +### Include what the team has done well -You should aim to complete the discovery peer review report within 3 days. - -### For alpha and beta peer reviews - -The report should document what the team has done well and what the team could improve. You can use the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard) as a guide to provide recommendations. - -Think about how the report can support the team to either explore things further or move into the next phase. +Make sure you consider feedback on the positive aspects of the discovery too, not only on recommendations on what to improve. -Acknowledge any constraints or business requirements the team is working to. +Work together with the rest of the panel to gather your findings and recommendations. -Once the panel is happy with the notes, add them to the final report in the service. This is usually done by the lead assessor, but the panel can add their findings individually. +Do this in a way that suits you. For example, use a shared Word doc or the panel chat in Slack. -You should aim to complete the alpha or beta peer review report within 7 days. +Once the panel is happy with the notes, add them to the final report in the service. This is usually done by the lead assesor, but the panel can add their findings individually. +You should aim to complete the discovery peer review report within 3 days. ## Submit the report diff --git a/app/views/service-assessments/discovery-peer-review.html b/app/views/service-assessments/discovery-peer-review.html index 5ee7162..da69651 100644 --- a/app/views/service-assessments/discovery-peer-review.html +++ b/app/views/service-assessments/discovery-peer-review.html @@ -13,50 +13,34 @@ A discovery peer review is a 2-hour informal review of a team's work in the [discovery phase](https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works). - - It's a way to get feedback and recommendations at the end of this phase. All discoveries in DfE are required to have one. - - It's not an assessment. There are no assessments at discovery. - - [Book a discovery peer review.](/book) - - ## Why have one - - A discovery peer review will give reassurance to confirm whether you: - have understood what the problem is and priorities for the team - should move into the alpha phase - - After the review, the team will get a report with practical recommendations, and advice. It will not result in a pass or fail. It will not stop a team from progressing. But remember, if research shows that it's better to stop at the end of discovery, this is not a failure. The team will be saving time and money that could be better spent elsewhere. - - ### What a team gets out of having a review If the assessors have recommendations for the team, these will be detailed in the report. The team can then decide on how they want to act on the recommendations. This could mean having a follow-up call or a workshop. Use the report to the team's advantage. Communicate recommendations with stakeholders or use it to prepare for the next phase of delivery. - - ## When to book When you start your discovery, you should plan to [book your peer review](/book) so that it happens near the end of discovery. -However, you should request this at least 5 weeks in advance so the service assessment plus team has time to arrange a panel. +You should request this at least 5 weeks in advance so the service assessment plus team has time to arrange a panel. ## What to prepare for a discovery peer review @@ -79,7 +63,9 @@ ### After you request the peer review -You'll receive an email with next steps. This includes how to share links to artefacts for the panel to read. For example, Lucid boards, docs, or slide decks. You can add links to work in progress; it doesn't need to be finished, it just gives the panel an idea of the discovery. +You'll receive an email with next steps. + +This includes how to share links to artefacts for the panel to read. For example, Lucid boards, docs, or slide decks. You can add links to work in progress, it doesn't need to be finished, it just gives the panel an idea of the discovery. ### One to 2 days before @@ -93,21 +79,47 @@ See an [example agenda](/service-assessments/run-peer-review#example-discovery-peer-review-agenda). - - ### After the discovery peer review -The panel will meet after the peer review to discuss observations. +The panel will meet to discuss observations. They'll complete the report and share it with the team approximately 3 working days after the review takes place. -The report will include what the team has done well and recommendations that consider the first 7 points of the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard). +## Your discovery peer review report +You'll receive an email with a link to the report up to 7 days after the discovery peer review. + +The report will include what team has done well, plus recommendations that consider the first 7 points of the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard). + +The panel will support the team with any recommendations made. + +### Review recommendations as a team + +If your report has recommendations, you could: + +- consider stopping work or revisiting the problem space +- escalate issues or problems to the senior responsible officer or senior leadership team +- contact the lead assessor or relevant head of profession for support to plan next steps +- plan how to demonstrate actioning recommendations at an alpha or beta assessment. [Apply the Service Standard in DfE](/) can help with this + +### Accept or challenge the report + +Once you've read the report, the product or delivery manager has 10 working days to accept or challenge it. + +### To accept the report + +If the team agree with what's written, you can accept the report on [your dashboard](/book) in the Service assessment service. + +### To challenge the report + +Arrange next steps and email the service assessment plus team at [serviceassessment.plus@education.gov.uk](mailto:serviceassessment.plus@education.gov.uk). -The assessor panel will support the team with any recommendations made. +They'll set up a meeting for the team with the panel. You'll agree any changes to the report with the panel before you accept it. -Go to [your peer review report](/service-assessments/peer-review-report) for details about receiving a report and acting on recommendations. +## What happens next +Once the report has been accepted, it will automatically be published in the [reports section](/reports/) of the service. The team can then follow any recommendations and next steps. +Depending on the outcome, the team may be asked to provide evidence of any actions they've taken to implement recommendations. diff --git a/app/views/service-assessments/index.html b/app/views/service-assessments/index.html index 1da0133..0f6af47 100644 --- a/app/views/service-assessments/index.html +++ b/app/views/service-assessments/index.html @@ -12,13 +12,13 @@ {% markdown %} -All services need to have a service assessment. Getting assessed is a condition of your Cabinet Office +In DfE, all services need to have a service assessment. Getting assessed is a condition of your Cabinet Office spend approval. This includes: -- non-transactional -- transactional, and +- transactional +- non-transactional, and - information services Service assessments happen at the end of alpha, private beta and public beta phases. If you are in the discovery phase, @@ -44,7 +44,11 @@ ## DfE panel service assessment -You need a DfE panel assessment if your service or product is transactional and will have less than 100,000 transactions per year. +You need a DfE panel assessment if your service or product is: + +- transactional and will have less than 100,000 transactions per year +- non-transactional +- an information service The panel will be made up of people from across professions in DfE. @@ -52,16 +56,15 @@ ## Peer reviews -You need a peer review if your service or product is: +You need an end-of-phase peer review if your service or product is in the discovery phase -- in the discovery phase -- a non-transactional service, for example a guidance or information service - -The outcome of a peer review will be a report sharing what the team has done well and what they need to improve. +The outcome of a discovery peer review will be a report sharing what the team has done well and what they need to improve. -However, you can choose to have a DfE panel service assessment if you think your service will benefit from being assessed more formally against the [Service Standard](/service-standard). +Book a discovery peer review by emailing the service assessment plus team. + +If you would like a mid-phase peer review at the alpha or beta phase, you can arrange one as a team with DDaT colleagues. -Book a peer review by emailing the service assessment plus team. +They can be a useful way to get feedback and recommendations as you prepare for a service assessment. {% endmarkdown %} diff --git a/app/views/service-assessments/peer-review-report.html b/app/views/service-assessments/peer-review-report.html index f0c5329..96d77c8 100644 --- a/app/views/service-assessments/peer-review-report.html +++ b/app/views/service-assessments/peer-review-report.html @@ -1,8 +1,8 @@ {% extends "layouts/content-with-sidenav.html" %} {% set selectedNav = "Service assessments" %} -{% set pageName = "Your peer review report" %} -{% set pageDescription = "The outcome of a peer review and next steps for the team"%} +{% set pageName = "Your discovery peer review report" %} +{% set pageDescription = "The outcome of a discovery peer review and next steps for the team"%} @@ -10,16 +10,15 @@ {% markdown %} -You'll receive an email with a link to the report up to 7 days after the peer review. +You'll receive an email with a link to the report up to 7 days after the discovery peer review. The report will include what team has done well, plus recommendations to explore. The panel will support the team with any recommendations made. ## Review recommendations as a team -If your peer review report has recommendations, you could: +If your discovery peer review report has recommendations, you could: -- consider stopping work or revisiting the problem space, if in the discovery phase -- consider pausing work while the team address any recommendations, if in the alpha or beta phase +- consider stopping work or revisiting the problem space - escalate issues or problems to the senior responsible officer or senior leadership team - contact the lead assessor or relevant head of profession for support to plan next steps - plan how to demonstrate actioning recommendations at an alpha or beta assessment. [Apply the Service Standard in DfE](/) can help with this diff --git a/app/views/service-assessments/run-peer-review.html b/app/views/service-assessments/run-peer-review.html index afee8bd..a3bde3c 100644 --- a/app/views/service-assessments/run-peer-review.html +++ b/app/views/service-assessments/run-peer-review.html @@ -1,7 +1,7 @@ {% extends "layouts/content-with-sidenav.html" %} {% set selectedNav = "Service assessments" %} -{% set pageName = "Run a peer review" %} +{% set pageName = "Run a discovery peer review" %} {% set pageDescription = "Your role as an assessor and what you need to do"%} @@ -9,49 +9,44 @@ {% block content %} {% markdown %} -A peer review is an informal review of a team's work. -As an assessor, you'll help a team by giving feedback and recommendations at either the middle or towards the end of a phase. +As an assessor you'll help a team to understand if they've completed their discovery. -If a team is having an end-of-phase assessment, a mid-phase peer review can help them to identify areas they need to work on to meet the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard). +You'll consider whether they've made well-evidenced recommendations and are ready to move onto the next phase. -## For discovery peer reviews - -Discovery peer reviews are usually 2 hours long. - -As an assessor you'll help a team to understand if they've completed their discovery and whether they should move into alpha. - -## For alpha and beta peer reviews - -Alpha and beta peer reviews are 4 hours long. - -As an assessor you'll consider whether the team are doing the right thing in the right way and are considering the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard). You'll provide recommendations for the team to take forward. - -## The peer review panel +## The discovery peer review panel A panel will consist of user research, design, product or delivery and a technical role. -Together, you'll provide a level of assurance for a team to decide if they need to pause and focus on recommendations or carry on as they are. - -If the team is at discovery you can help them to decide whether to continue with the project or not. +Together, you'll provide a level of assurance for a team to decide if they need to stop the project, pause and focus on recommendations or carry on as they are. As part of the panel, there will be a lead assessor, who'll be responsible for chairing the peer review and coordinating the report. -### Before a peer review +## Before a discovery peer review Assessors should: -- read the supporting artefacts about the work. Start to think about questions +- read the supporting artefacts about the discovery. Start to think about questions - take part in a pre-call, organised by the service assessment plus team, to do introductions and agree an agenda - answer any questions or concerns the team may have -- read any reports from previous phases -Lead assessors should also: -- meet the team to finalise timings, what to cover, when to have breaks and how they want to take questions -- check if there's anything the team want assessors to focus on -- meet the assessor panel via Teams, or on Slack, check if they've read any previous phase reports and ask if there's anything they want to focus on -- check if anyone in the team or panel has any particular needs that should be taken into account +### Example discovery peer review agenda + +A discovery peer review is 2 hours long and can take place on Tuesdays, Wednesdays, or Thursdays. + +You should agree in the pre-call with the service team how the session will run. + +An example agenda might look like this: + +| Time | Action | +|------------------|----------------------------| +| 5 to 10 minutes | Introductions and housekeeping | +| 45 minutes | Team show and tell | +| 10 minutes | Break | +| 45 minutes | Questions and answers | +| 5 minutes | Wrap up and next steps | + -### During a discovery peer review +## During a discovery peer review Assessors should: - review the work of the discovery @@ -61,75 +56,48 @@ - determine if the team has things to work on in an alpha or should stop - provide authoritative advice, guidance, and recommendations -### During an alpha or beta peer review +## After a discovery peer review Assessors should: +- write up any recommendations or outcomes in the report +- submit the report, if you're the lead assessor +- provide any support needed after the peer review, along with any actions. This could mean answering questions or giving advice -- review whether the team are doing the right thing, are working in the right way, and are considering the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard) -- ask questions to support the team in demonstrating why they've built what they have -- use the practical examples in [Apply the Service Standard in DfE](https://apply-the-service-standard.education.gov.uk/service-standard) to review the work in a proportionate way. Take into account the context the team are working in +You'll be supported by the service assessment plus team throughout the process. -### Lead assessor responsibilities for all peer reviews -During all peer reviews, lead assessors should: -- explain the purpose of the peer review and how it will run -- manage time keeping, check people get breaks -- bring in the assessment panel for questions -- explain next steps and wrap up +## Complete a discovery peer review report +The report should aim to conclude whether the team has understood the problem space and priorities for next steps following the end of discovery. -### After a peer review on the day +If the team has not yet reached a decision on next steps, the report will give feedback and recommendations based on the evidence shared at the peer review. -Assessors should attend a wash-up call. +### Draft the report -The lead assessor should chair the call with the panel. Use this session to: -- check in with assessors -- run through the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard) to give advice in the report for the team and service owner to consider -- invite comments from observers +During the discovery peer review, consider the practical tips in [Apply the Service Standard in DfE](https://apply-the-service-standard.education.gov.uk/service-standard) against standards 1 to 7 in the discovery phase. This will help you understand if the team has done what they need to do to mark the end of discovery. -### In the week after a peer review +Although a team in discovery won't yet have made tech choices, they should, if relevant, show an understanding of existing options. -Assessors should: -- write up any recommendations or outcomes [in the report](/service-assessments/complete-peer-review-report) -- submit the report, if you're the lead assessor -- provide any support needed after the peer review, along with any actions. This could mean answering questions or giving advice +Acknowledge any constraints or business requirements the team is working to. -You'll be supported by the service assessment plus team throughout the process. +### Include what the team has done well -## Example discovery peer review agenda +Make sure you consider feedback on the positive aspects of the discovery too, not only on recommendations on what to improve. -A discovery peer review is 2 hours long and can take place on Tuesdays, Wednesdays, or Thursdays. +Work together with the rest of the panel to gather your findings and recommendations. -You should agree in the pre-call with the service team how the session will run. +Do this in a way that suits you. For example, use a shared Word doc or the panel chat in Slack. -An example agenda might look like this: +Once the panel is happy with the notes, add them to the final report in the service. This is usually done by the lead assessor, but the panel can add their findings individually. -| Time | Action | -|------------------|----------------------------| -| 5 to 10 minutes | Introductions and housekeeping | -| 45 minutes | Team show and tell | -| 10 minutes | Break | -| 45 minutes | Questions and answers | -| 5 minutes | Wrap up and next steps | +You should aim to complete the report within 3 days. -## Example alpha or beta peer review agenda +### Submit the report -An alpha or beta peer review is 4 hours long and can take place on Tuesdays, Wednesdays, or Thursdays. +It's the lead assessor's responsibility to submit the discovery peer review report to the service assessment plus team for final checks before it's shared with the service team. -You should agree in the pre-call with the service team how the session will run. - -An example agenda might look like this: +If the team accepts the report and there are recommendations the panel has offered to support, the team will be in touch. This could mean having a follow-up call or giving advice on a workshop, depending on the recommendations. -| Time | Action | -|------------------|----------------------------| -| 5 to 10 minutes | Introductions and housekeeping | -| 50 minutes | Team show and tell | -| 50 minutes | User research | -| 10 minutes | Break | -| 45 minutes | Design | -| 20 minutes | Team and governance | -| 25 minutes | Tech | -| 20 minutes | Performance | -| 10 minutes | Wrap up and next steps | +If the team challenges the report, they'll raise any issues with the service assessment plus team, who'll set up a meeting with the panel. diff --git a/app/views/service-assessments/run-service-assessment.html b/app/views/service-assessments/run-service-assessment.html index e4dd8f3..2a0ab70 100644 --- a/app/views/service-assessments/run-service-assessment.html +++ b/app/views/service-assessments/run-service-assessment.html @@ -39,31 +39,48 @@ - review previous reports, such as a discovery peer review or previous phase assessment. You’ll be sent a link to these by the DfE service assessment plus team - attend pre-assessment calls, organised by the DfE service assessment plus team. You'll meet the team being assessed, agree the agenda and answer any profession-specific questions or concerns - + Lead assessors should also: - + - meet the team via Teams, to finalise timings and check if there's anything they want to focus on + - meet the assessor panel via Teams, or Slack, to check if they've read any previous phase reports and if there's anything they want to focus on + - check if anyone in the team or panel has any particular needs that should be taken into account ### During an assessment - - Assessors will: - review the work of the team against the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard) in a proportionate way. Take into account the context the team are working in - ask questions to support the team in demonstrating why they’ve built what they have and how they’ve met the standard - +Lead assessors should also: +- explain the purpose of the assessment and how it will run +- manage time keeping +- bring in the assessment panel for questions +- explain next steps and wrap up + +### After an assessment on the day -### After an assessment +Assessors should attend a wash-up call. + +The lead assessor should chair the call with the panel. Use this session to: + +- check in with the assessors +- run through the [Service Standard](https://apply-the-service-standard.education.gov.uk/service-standard) to give advice for the team and service owner to consider +- invite comments from observers + +### In the week after an assessment Assessors will: - provide a [RAG (red, amber, green) rating](/service-assessments/complete-service-assessment-report#give-the-service-a-rating-for-each-service-standard) for each of the [14 Service Standard points](https://apply-the-service-standard.education.gov.uk/service-standard). Each point will be led by a different profession, with the lead assessor reviewing all 14. Read which points are most relevant to each profession on [Apply the Service Standard in DfE](https://apply-the-service-standard.education.gov.uk/service-standard) - detail any actions that the team must take, where a red or amber rating is given for that standard - work with the panel to determine an [overall RAG rating](/service-assessments/complete-service-assessment-report#give-the-service-a-rating-for-each-service-standard) for the assessment. You may want to have a final call together as a group, to review the completed report before submitting it - add any other observations to the report in the overview section, such as what the team has done well +- submit the report, if you're the lead assessor + +Read the guidance on [completing an assessment report](/service-assessments/complete-service-assessment-report) to help you through the process. + +The DfE service assessment plus team will support you in your role as an assessor. - -You’ll be supported by the DfE service assessment plus team throughout the process. diff --git a/app/views/service-assessments/survey.html b/app/views/service-assessments/survey.html index 945b509..472c3c3 100644 --- a/app/views/service-assessments/survey.html +++ b/app/views/service-assessments/survey.html @@ -30,8 +30,8 @@ We measure the user satisfaction of the: - booking process -- peer review or service assessment -- support and guidance around the peer review or service assessment +- discovery peer review or service assessment +- support and guidance around the discovery peer review or service assessment