Home Office

Home Office Modern Slavery Statement Reporting Service

Incomplete applications

14
Incomplete applications
11 SME, 3 large

Completed applications

15
Completed applications
9 SME, 6 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Monday 9 September 2019
Deadline for asking questions Monday 16 September 2019 at 11:59pm GMT
Closing date for applications Monday 23 September 2019 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work Using user research and interaction design to produce an MVP digital service for businesses to publish an annual modern slavery statement. The service needs to make these statements available to the public. The service will re-use elements of the codebase for the gender pay gap reporting service.
Latest start date Sunday 1 December 2019
Expected contract length At least until March 2020 with potential to extend for a further year.
Location London
Organisation the work is for Home Office
Budget range The budget in 2019/20 is up to £500k and will include all development activity including user research, design and development as well as hosting, IT Health Checks, accessibility audit and civil servant costs.

Any expenditure beyond 2019/20 will be dependent on departmental budgets.

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done The Transparency in Supply Chains (TISC) legislation in the Modern Slavery Act 2015 mandates certain companies to publish an annual statement declaring their activities to tackle modern slavery in their operations and supply chains.

Our goal is to
-support business to comply with legislation and improve the quality of annual statements.
-Provide a trusted service that provides data to wider public in an open, easily accessible form for further scrutiny and research into modern slavery.
-Provide a platform for HO to learn further about the impact of our policies.

MVP will need to be ready by end of March 2020
Problem to be solved Reusing the existing Gender Pay Gap (GPG) codebase to solve the following problems:

1. How might the HO monitor business compliance with the Modern Slavery Act?

2. How might the HO make it easier for users to access, understand and compare companies' statements?

3. How might the HO raise the standards of companies' statements?

4. How might the HO encourage companies to adopt good practice approaches and metrics for reporting?

5. How might the HO encourage companies to comply or deter non-compliance?

6. How might the HO enable third parties to make creative, positive use of data in companies' statements?
Who the users are and what they need to do As a business I can submit the relevant information to the HO so that I can meet my statutory obligations and be satisfied that I am complying with the relevant legislation.

As a member of wider society, I can easily access all/any of the statements so that I can make informed decisions and undertake research.

As the HO I can monitor compliance with the legislation and increase understanding of TISC so that I can develop policies that have a tangible impact on reducing modern slavery.
Early market engagement The HO has analysed the solution developed for the Gender Pay Gap (GPG) service and concluded that the core code is highly re-useable with a large number of features being close in similarity to our anticipated solution.
The Independent review of the modern slavery act explored the issue and recommended a central registry. Please see the Government’s response here.

https://www.gov.uk/government/publications/government-response-to-the-independent-review-of-the-modern-slavery-act
Any work that’s already been done Service design workshops to develop problem definitions and hypotheses to be tested.
Some limited user research has been conducted as part of a wider consultation on the TISC legislation.
Review of GPG codebase by head technical architect confirmed its suitability for reuse. This review will be made available to the successful tenderer.
Existing team The existing team includes a Project Manager, Product Manager and Service Owner and other team members.

The successful supplier will be working alongside established HO enterprise teams in order to successfully integrate the service into existing architecture.
Current phase Discovery

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place 2 Marsham Street SW1P 4DF or Fleetbank House, London EC4Y 8AE.
Working arrangements General office working hours, core 10-4, Monday – Friday. Expenses will conform to HO internal policies and will not be payable within the M25. Occasional travel to other HO locations may be required.

The team must use agile methodologies, with regular stand ups and show and tells.
Security clearance The Supplier’s personnel will be required to obtain CTC security clearance. This may be extended to SC clearance in the lifetime of these requirements.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions The development must meet the cross-Government service standard, and the supplier must participate in assessments at end of alpha, private beta and public beta.

The service must meet level AA of the WCAG (Web Content Accessibility Guidelines) 2.1 as a minimum, and work with the most common assistive technologies.

Team must work with their relevant professional communities in the HO – using their ways of working and sharing knowledge as set out by each community.

Dependent on the outcome, the supplier may be awarded subsequent phases.

Skills and experience

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

Skills and experience
Opportunity attribute name Opportunity attribute value
Essential skills and experience
  • Provide demonstrable experience of planning and delivering user-centred digital services to the cross-Government service standard, corresponding service assessment process, and Technology Code of Practice.
  • Have experience in using Agile/Scrum methodology to iteratively architect/develop high quality government digital services to GDS open source standards.
  • Have prior experience which includes using GDS Design Principles and Digital Service Standard and keeping up to date with Gov APIs, services, libraries and toolkits, service assessments.
  • Have experience of hands on management and ability to conduct high quality handover and training sessions to ensure effective long-term support and further development of the service.
  • Provide demonstrable experience of working with .Net framework in the last 12 months.
  • Demonstrable experience of working as a joint team with commissioning organisation and operating within its governance.
  • Have the ability to quickly mobilise a skilled and experienced team, responding flexibly to peaks and troughs in demand.
  • Demonstrable evidence of working with common IaaS, PaaS and SaaS offerings within the last twelve months.
  • Demonstrate experience building services that comply with Web Content Accessibility Guidelines (WCAG) 2.0/1 AA standard.
Nice-to-have skills and experience
  • Demonstrate experience of providing on the job coaching and mentoring on agile delivery and specialist digital skills to the client’s ‘in house team’.
  • Demonstrable experience of working with a policy area within a central government department to deliver digital transformation to meet a policy objective.
  • Demonstrable experience of working with a wide range of user groups including business stakeholders, civil society organisations, Government and the general public.

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 5
Proposal criteria
  • Technical solution – including openness / approach to base your solution on an existing .NET Core / SQL Server service.
  • Approach and methodology.
  • How the approach or solution meets user need.
  • How the approach or solution meets the organisation's policy or goal.
  • Estimated timeframes for the work.
  • How they've identified risks and dependencies and offered approaches to manage them.
  • Team structure.
  • Value for money.
Cultural fit criteria
  • Demonstrable experience of working as a joint team with commissioning organisation and operating within its governance.
  • Work in the open: be transparent and collaborative when making decisions.
  • Have a no-blame culture and encourage people to experiment, iterate and learn from their mistakes.
  • Take responsibility for their work.
  • Share knowledge and experience with other team members.
  • Challenge the status quo and be comfortable standing up for their discipline.
  • Can work with clients with low technical expertise and convey technical concepts in a way which is meaningful to senior policy officials.
  • Care deeply about citizens and victims of modern slavery.
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Work history
  • Reference
  • Presentation
Evaluation weighting

Technical competence

65%

Cultural fit

10%

Price

25%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Is there a current or preferred supplier for this project? No.
2. Has a third party supplier been involved in the Discovery activities? A third party supplier was involved in the review of GPG codebase by head technical architect.
3. Which third party suppliers were involved in the delivery of the gender pay gap reporting service? This information will be made available in the Invitation to Tender.
4. Where is the gender pay gap service hosted? This information will be made available in the Invitation to Tender.
5. What is the budget without the civil servant costs? The final budget and team breakdown is yet to be finalised and will be dependent on the supplier’s proposed solution.
6. Does the team require CTC clearance before starting, or are they able to start work onsite with BPSS clearance, and pending CTC clearance? We require CTC clearance before any work onsite can start.
7. What is the timeline after the closing date? When do you plan to shortlist applicants and when will you require written proposals? The anticipated timeline is as follows:-

With a closing date of September 23rd we intend to complete the initial sift that week.

We then intend to issue the ITT ready during the following week.

Tender responses would be expected mid to late October.

We would then carry out the Evaluation, Presentations then Due Diligence activity.

Please note that these timescales are all indicative only. Should there be significant changes then they will be communicated to all relevant parties.
8. The document says the budget (up to £500,000) will include all development activity including user research, design and development as well as hosting, IT Health Checks, accessibility audit and civil servant costs. What do you mean by Civil Servant costs? Civil Servant costs are resource costs for Civil Servants working on the project. Further information will be contained within the Invitation to Tender.
9. Can you confirm what role third party suppliers have played in Discovery and GPG code? No third party supplier has been involved in the Discovery phase for TISC.

The Home Office did engage a third party supplier in reviewing the GPG code base for potential reuse but that isn’t part of the Discovery Phase for TISC.
10. How was the GPG supplier engaged? As part of the review of the GPG code base, Home Office staff engaged the supplier currently delivering the GPG service.
11. Can work start offsite while CTC clearance is obtained? CTC is required, but if the Home Office feels that it would not impact on delivery, it may consider off-site working while clearance is obtained.
12. Is the GPG code base open source and can we get a link to it? This information will be made available in the Invitation to Tender.
13. it would be beneficial to understand the GPG source code before making our application; is there any way this can be shared, since it is open source, prior to the ITT? The GPG repository is open source; it can be found via this link:- https://github.com/DFEAGILEDEVOPS/gender-pay-gap.
14. Can you please suggest of the MVP should include a public beta or a private beta? The expectation is for the supplier to deliver an MVP to private beta as a minimum.
15. Q16. Is the supplier expected to be on site at all times (Mon-Fri) or is there scope to work from the suppliers office where appropriate? A16. Co-location is highly preferred, however, the Home Office may consider off site-working if there is no impact on delivery.
16. 17 .NET capability is listed as an essential requirement – is this a mistake and you'd be willing to use alternatives (e.g. Ruby on Rails, Django) or is this a hard and definite requirement? 17 .NET Core capability is an essential requirement given our intention to re-use the GPG codebase.
17. 3. Given the project has not moved into alpha yet would the team be open to the suggestion of other technologies which may be more suitable than http://the.net codebase? No, .NET Core capability is an essential requirement given our intention to re-use the GPG codebase.
18. Was the same supplier that built the GPG service used to review the suitability of the GPG codebase for reuse? As outlined in #9 above, the Home Office did engage a third party supplier in reviewing the GPG code base for potential reuse
19. Given the GPG codebase appears to be implementation specific how was the service identified and considered appropriate for reuse? HO performed a gap analysis between the required capabilities for Modern Slavery and Gender Pay Gap. A supplier then assisted in reviewing the GPG code base for potential reuse and change.