Awarded to Unboxed Consulting Ltd

Start date: Tuesday 21 January 2020
Value: £240,000
Company size: SME
Public Health England


4 Incomplete applications

3 SME, 1 large

6 Completed applications

4 SME, 2 large

Important dates

Wednesday 21 August 2019
Deadline for asking questions
Wednesday 28 August 2019 at 11:59pm GMT
Closing date for applications
Wednesday 4 September 2019 at 11:59pm GMT


Summary of the work
To replace the website of the UK NSC by building and deploying a beta system based on the outcomes of the alpha.

The awarded Supplier will prepare PHE to take over project delivery from the end of private beta and support delivery on an ad-hoc basis during the Live phase.
Latest start date
Wednesday 9 October 2019
Expected contract length
24 months (2 years)
Organisation the work is for
Public Health England
Budget range
Up to £170k including VAT

About the work

Why the work is being done
The UK NSC legacy site needs to be upgraded:

This is due to technical, security and governance issues, and because the website cannot accommodate recent business changes which have resulted in fragmented workflows across to a second website.

Discovery and alpha findings have justified investment to complete the project with Beta and Live.

Both Beta and Live are being procured
Problem to be solved
UK NSC needs a digital service that is built around user-needs.

UK NSC needs a digital service which reflects the 4-country remit and independence of the UK NSC.

UK NSC needs a digital service for interested members of the public and stakeholders, by defragmenting UK NSC online content and workflows.

Boost the UK NSC online presence so that potential stakeholders can more easily find and engage with UK NSC.

UK NSC needs a solution which complies with Government Digital Service Standard.
Who the users are and what they need to do
The following users have been identified:

• Registered UK NSC Stakeholders (e.g. Charities, GPs, academic institutes, etc.) – take part in UK NSC consultations and provide expert opinion which informs policy
• Citizens affected by a condition - offering patient stories and opinion in consultations
• UK NSC Secretariat – responsible for managing website content, consultations, and policy review projects.
• UK NSC – responsible for making health screening policy recommendations and approving published documents.
• PHE Technical teams – to provide full infrastructure support, and general application support from public beta onwards.
Early market engagement
Any work that’s already been done
Pre-project, discovery and alpha have been delivered to date, and alpha has passed the digital service assessment.

A design and technology proposal has been approved and is to be built in beta, subject to ongoing user research. Clickable mock-ups of the proposal will be available to the awarded supplier.

PHE will provide full infrastructure support and general app support of the public beta product.
Existing team
PHE will provide the Product Owner who has managed this project since conception.

PHE Digital expertise will include a User Researcher, Content Designer and Interaction Designer.

Governance and ICT teams will support this project and provide expertise and directives where applicable.

You will be expected to work with multiple user research participants across England, Scotland, Wales and Northern Ireland; when possible, for face-to-face user research.
Current phase

Work setup

Address where the work will take place
The work can be performed from any location, but is likely to be co-ordinated by staff in PHE’s London Offices in Waterloo and Colindale.
Working arrangements
Work may be carried out from multiple locations, including the Supplier’s offices. Attendance at London PHE Offices will be required for meetings. Supplier staff will be expected to be on-site at PHE locations sufficient to manage the relationships with senior stakeholders; the project team and users; and, stakeholders and users in other organisations so that the outcomes of the project may be met. Members of the PHE team may also occasionally work in the supplier’s offices.

The supplier will be expected to work using Scrum and all ceremonies will be open to the PHE project team.
Security clearance

Additional information

Additional terms and conditions

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Essential skills and experience
  • For all questions where recent experience is asked, please ensure a date of previous projects cited is given.
  • E1) Recent (within 3 years) and demonstrable experience of skill and knowledge transfer into a customer organisation (technical and user research)
  • E2) Recent (within 3 years) experience of developing and delivering systems using Python, and Microsoft technology stacks such as .NET and SQL Server
  • E3) Recent (within 3 years) experience of building on existing user research and continuing user research as part of the development process
  • E4) Recent (within 3 years) experience of delivering web development projects using Agile methodology
  • E5) Recent (within 3 years) experience of content and document migration
  • E6) Recent (within 3 years) experience of delivering loosely coupled solutions to allow modules to be reused by other systems
  • E7) Recent (within 3 years) evidence of producing and risk-managing the development a secure service on infrastructure shared with other assets
Nice-to-have skills and experience
  • N1) Recent (within 3 years) experience of going through beta digital service assessments
  • N2) Experience of working on solutions for healthcare and/or a national scope
  • N3) Recent (within 3 years) experience of embedding Agile within an organisation with low Agile maturity
  • N4) Recent (within 3 years) of working in teams encompassing development staff from a customer organisation
  • N5) Recent experience of building on a Discovery and/or Alpha delivered by another organisation
  • N6) Experience of making software open source
  • N7) Recent (within 3 years) experience of delivering services taking a cloud-native approach using Iaas/PaaS platforms

How suppliers will be evaluated

How many suppliers to evaluate
Proposal criteria
  • P1) Proposed approach to the project including but not limited to taking over an existing alpha (20)
  • P2) Proposed approach to handover to an internal (PHE) managed service team (20)
  • P3) Approach to data analysis, transformation and migration, including user management (20)
Cultural fit criteria
  • The shortlisted suppliers will be invited to demonstrate cultural fit in demonstrating evidence of the following:
  • C1) Examples of previous experience of working with UK Government, local authorities or large organisations with a range of different stakeholders (3)
  • C2) Communicating effectively and being responsive to client needs (3)
  • C3) Understanding and respecting client's internal governance and procedures (3)
  • C4) Working within the constraints of public sector organisations, including budgets, timescales and change (3)
  • Cultural fit will solely be assessed through the presentations i.e. a written response will not be required.
Payment approach
Capped time and materials
Assessment methods
  • Written proposal
  • Case study
  • Work history
  • Reference
  • Presentation
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. 1 - You mentioned Python in the requirements, but it is not mentioned elsewhere. Could you expand on this please?
The beta environment will use Python and Django framework, using Postgres or MySQL on Openshift platform, Python experience will be essential. The legacy system is built using Microsoft technologies such as .NET and SQL Server, so knowledge of this is current stack build is desirable though not essential.
2. 2 - The opportunity states: 'PHE Digital expertise will include a User Researcher, Content Designer and Interaction Designer.'
How much time of each individual role will be available for this project?
Full time for all three roles will be provided so suppliers do not need to cover these roles.
3. 3 - Will this service be subject to the formal beta digital service assessment? If so, will the assessment be led by GDS or withing the department?
The assessments that are held within Department of Health are the same standard as the GDS ones and are assured by them, though because of the shifts around NHS X assurance it could be either. It makes very little difference as it is GDS level assessors either way.
4. 4 - Have the current stages been undertaken against GDS standards and is that expected to continue with the full Beta to live cycle?
Yes, the Alpha went through a GDS assessment and will continue to go through the Beta to live cycle with GDS assessments at all relevant phase changes
5. Have you made the outputs of previous stages Open Source and are we able to access any of this? Designs, solution architecture, prototypes etc
All outputs from previous stages such as the prototype coding is open source and will be made accessible to the awarded supplier. Please see Q1 for an overview of the solution architecture
6. 6 - Are you able to please share the current proposed technology stack that has been arrived at during Alpha?
Please see answer to Q1