Get approval to spend Beta amber evidence review
Service Standard report Get Approval to Spend 17/05/2024
Service Standard report
Get Approval to Spend
| Assessment date: | 17/05/2024 |
| Stage: | Beta amber evidence review |
| Result: | Green |
| Service provider: | Central Digital and Data Office (CDDO) |
Previous assessment reports
-
Alpha assessment report (met)
-
Beta reassessment report (amber)
Service description
A single service system that enables government organisations to raise and submit a request to the Cabinet Office for spend control approval while also enabling Cabinet Office assessors’ greater visibility of spend control cases in the pipeline, reporting and case management functions, along with the ability to easily apply and track case conditions.
Service users
This service is for…
-
Government Organisation Spend Assurance Case Submitters (for example Project Leads)
-
Government Organisation Spend Assurance Leads
-
Cabinet Office Spend Control Assessors
4. Make the service simple to use
Decision
The service was rated green for point 4 of the Standard.
6. Have a multidisciplinary team
Decision
The service was rated green or point 6 of the Standard.
10. Define what success looks like and publish performance data
Decision
The service was rated green for point 10 of the Standard.
12. Make new source code open
Decision
The service was rated green for point 12 of the Standard.
13. Use and contribute to open standards, common components and patterns
Decision
The service was rated green for point 13 of the Standard.
14. Operate a reliable service
Decision
The service was rated green for point 14 of the Standard.
Next Steps
This service can now move into a public beta phase, subject to implementing the recommendations outlined in the report and getting approval from the CDDO spend control team.
This service now has permission to launch on a GOV.UK service domain with a beta banner. These instructions explain how to set up your *.service.gov.uk domain.
The service must pass a live assessment before:
-
turning off a legacy service
-
reducing the team’s resources to a ‘business as usual’ level, or
-
removing the ‘beta’ banner from the service