Awarded to Digital Craftsmen Limited

Start date: Monday 6 November 2017
Value: £21,900
Company size: SME
Grenfell Tower Inquiry (sponsored by Cabinet Office)

Website build and ongoing maintenance

15 Incomplete applications

14 SME, 1 large

34 Completed applications

33 SME, 1 large

Important dates

Friday 6 October 2017
Deadline for asking questions
Friday 13 October 2017 at 11:59pm GMT
Closing date for applications
Friday 20 October 2017 at 11:59pm GMT


Summary of the work
An new build of the current Grenfell Tower Inquiry website - - with a launch by mid-January, 2018, as well as training and ongoing maintenance until the close of the Inquiry.
Latest start date
Monday 6 November 2017
Expected contract length
Build - Feb 2018, Ongoing maintenace - June 2019
Organisation the work is for
Grenfell Tower Inquiry (sponsored by Cabinet Office)
Budget range

About the work

Why the work is being done
Public Inquiry into fire at Grenfell Tower on the 14 June 2017.

A new website needs to be launched mid-January 2018, with a beta version ready before Christmas 2017.
Problem to be solved
The Inquiry needs a new website that is more user-friendly and can hold more information than the current, temporary wordpress site.

Inquiry team members will need training on the day-to-day running of the site.
Who the users are and what they need to do
This has already been considered and structural design is well-underway although developers welcome to input thoughout the build.
Early market engagement
Having held one early engagement with the provider, we now have a clear set of technical requirements for the website:

- Full content management system to allow editing by the Grenfell Tower Inquiry team
- Good search engine optimisation
- Well-ordered markup (e.g. heading tags in a logical structure, up-to-date HTML5 tags used). We want the new site to achieve at least 85% for User Experience on the Google PageSpeed
- Insights checker.
- HTTPS required
- Functional across mobile, tablet and widescreen
- Must work in all major browsers, including desktop (Chrome/Firefox/IE/Edge on OSX and Windows) and mobile (iOS, Android, Windows Mobile, Blackberry)
- IE compatibility to v11
- Secure: restricted CMS login
- Video content would be hosted externally (e.g. Youtube) and not streamed directly.
- Fully accessible (WCAG 2.0)
- Regular backups - hourly backups with maximum of three hours downtime (RPO = 1 hour, RTO = 3 hour)
- 99.95% hosting uptime SLA
- UK-based data centre for hosting
- Google Analytics
Any work that’s already been done
The Inquiry already has a temporary website with content and a basic structure.

We have a plan for the new structure:

-Homepage (Dynamically updated when there is a hearing with a live stream; Follow us on Twitter; News feed)
-News (Inquiry updates; Press releases; RSS news feed; Tagged and filterable)
-Hearings (Transcripts; Videos; Filtered by date, tagged according to content)
-Key documents (With protocols, terms of reference etc; Tagged and filtered)
-Events (calendar for hearings)
-Evidence (Tagged and filtered)
-Contact (With web-form or email us button)
Existing team
You would be working with members of the Inquiry team who will manage the content when the build has been completed.
Current phase
Not started

Work setup

Address where the work will take place
The Inquiry is based in the Royal Courts of Justice. Suppliers will need to work in their own environments but regular face-to-face contact is required throughout the build.

Training for the team on the use and management of the website needs to be in-person in central London.
Working arrangements
Developers can work under their usual arrangements, as long as we can meet them face to face in London on a weekly basis.
As this quite a tight deadline, we would expect regular communication and updates, although this can be done remotely.
We do not expect to cover any travel or other expenses.
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
  • Have a portfolio of websites for consideration
  • Have resources to deliver by Jan 15, 2018
  • Have track record of delivering to tight deadlines
  • Be able to train face-to-face in central London
  • Be collaborative with Inquiry team throughout build
Nice-to-have skills and experience
Experience of working with government departments

How suppliers will be evaluated

How many suppliers to evaluate
Proposal criteria
  • Technical solution
  • Approach and methodology
  • How the approach or solution meets user needs
  • Estimated timeframes for the work
  • Value for money
  • Location
  • Experience of working with Gov Departments
Cultural fit criteria
  • Work as a team with our organisation and other suppliers
  • Be transparent and collaborative when making decisions
  • Take responsibility for their work
  • Can work with clients with low technical expertise
Payment approach
Capped time and materials
Assessment methods
Written proposal
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. Will the supplier need to host the website?
Yes, the supplier will need to host the website. It needs to be a UK server.
2. Have designs been completed?
We will be working on the design and plan to have a fairly concrete structure to handover to the developers. We will open to suggestions, however, if something can be improved.
3. What is the budget range for this project?
We have an indicative budget in mind, but will adapt this subject to the response in the marketplace. Value for money is one of the criteria we will be using to assess potential suppliers.
4. Has a budget been considered for the development of this project?
As above, we have an indicative budget in mind, but will adapt this subject to the response in the marketplace. Value for money is one of the criteria we will be using to assess potential suppliers.
5. Is there a full brief available that lists the scope of work and the budget available for the project?
What we have published on the Marketplace is as much detail as we have on the project to date. If you have any specific questions, please be in touch and we will attempt to answer them for you.

We don't plan to publish details of the budget. Although we have a budget in mind, we will evaluate this against the submissions before this is confirmed.
6. What is the anticipated website traffic? Are there specific periods of peaks that must be considered in terms of hosting?
There will be certain key hearings that will be live-streamed from the website. These will attract a higher number of views. We will be able to predict these and will give the provider advanced notice.

A useful comparator is the Leveson Inquiry website that received around 1.8m hits from 652k unique visitors vetween Nov '11 and Oct '12.
7. Is there budget range we should aim to quote for ?
As above, we have an indicative budget in mind, but will adapt this subject to the response in the marketplace. Value for money is one of the criteria we will be using to assess potential suppliers.
8. It is our understanding from the brief that you're requiring hourly backups. Do you anticipate that the information presented on the website, will be that volatile, or would you consider nightly backups as standard?
We would be updating the website on a daily basis, with more activity in busy periods (eg. during a hearing). We are open to influence here. If you believe that hourly backups is more than is required, please state why and what would you would offer as an alternative.
9. What is the expected scope of the CMS training, and for how many people/how many locations?
The CMS training would be in a single location in central London to a maximum of 5 people.

Teams would need to be trained to be proficient in the management of the website.
10. You mention that the existing temporary site is built in WordPress, are you looking to change CMS, or is WordPress one of the CMS options you would consider as a solution?
We are happy to use any user-friendly CMS.
11. Should the 'dynamically updated' homepage detect the presence of a live media stream, or would a human editor manage this process?
It should be detected automatically.
12. Is there a requirement for the content submitted by webform to be transmitted to a third party application/case management system?
No, the webform would just be for contact purposes. No upload functionality is required.
13. Can we clarify - are there interface designs (ie pixel-perfect) being produced, or is the design limited to structural/IA?
We will not be producing any interface designs. We will prepare structure and content only.
14. The opportunity notes you are working on the "structural design" and you have a "fairly concrete structure to handover". I understand this to mean you have worked on the website structure / Information Architecture and you require a supplier to create a new website design (i.e. look and feel) as well as build the website. Can you confirm if this is correct?
Yes, that is correct.
15. Do you have an idea of how many distinct page templates the site will need?
Not at this stage. Please make suggestions in your application. For more information, please have a look at what we have outlined in the 'Any work that’s already been done' section, the existing website and at other inquiry websites which can be found online.
16. Is an internal or external team undertaking the "structural design" work? If an external team, are they tendering for this opportunity?
It is an internal team.
17. Do you have a project specification detailing the functionality and pages required to be built?
We are in the process of creating this and will hand over a completed version to the developer. In the meantime, other Government inquiry websites provide good examples of the structure and functionality required.
18. How much content will need to be added to the new site, how much of this is new / how much can be repurposed from the current site?
We expect that all of the content will be transferred from the old website to the new version. Any extra content will be generated by the Inquiry team and handed over to the developers at the commencement of the build.
19. Do you require any integration with third party systems, e.g. a CRM?
The website needs a 'follow' button for the Inquiry twitter account.

We will also need to embed videos, all of which will initially be live-streamed. We will have a third party provider generating this content and the developer can work with them to establish the most cost-effective way to achieve this.
20. Do you require web hosting as part of this project?
As above, yes, the supplier will need to host the website. It needs to be a UK server.
21. The evidence requested for essential and nice-to-have skills is quite generic and doesn't cover the other requirements listed under “early market engagement” or those requirements mixed in with other things such as the required SLA. Should we try to provide evidence of our understanding of requirements and our ability to delivery those requirements within the generic questions asked?
We've differentiated between skills/experience and technical requirements for the website. It would be helpful if the bid could cover both.
22. Is user research and usability testing in scope of this project?
We do not believe that user research is necessary for this build as the Inquiry team is familiar with the user requirements for Inquiry websites. Reasonable usability testing would be considered. Please explain why you think it would be necessary, how you would conduct it and how much it would cost in your submission.
23. Please could you provide further detail on the team including roles, responsibilities and capability?
The project team is made up of members of the Inquiry team (who aren’t digital specialists) and the Cabinet Office IT team.
24. Could you provide further information and reasoning behind the timelines for launching mid-January?
This is the requested date for delivery of the project.
25. You state “Inquiry team who will manage the content when the build has been completed.”. How many different permission levels do you need, and will there need to be workflow approval setup?
We require one permission level. Workflow approval is not required.
26. “Be collaborative with Inquiry team throughout build” - do you have preferred collaboration or project management tools?
The Inquiry team has no preferred collaborative tool. We do ask that the developer communicates regularly and effectively with the Inquiry, giving advice and responding to feedback.
27. Are you open to using Agile project management methodology including development sprints, sprint planning and sprint reviews? Does your team currently have experience of doing this on other projects?
Yes, we are open to using Agile methodology. There is limited experience of Agile in the Inquiry team.
28. What are the factors you’re using to decide between different solutions and suppliers?
These are set out in the requirements.
29. Your current problem is that a new content management system is needed to ‘replace the current, temporary wordpress site’. Can you explain the difficulties you are having with wordpress and how this can not be adapted to hold more information and be more user friendly?
We would be happy to continue using Wordpress. We do not have the capability or capacity to develop the website to the required level of usability and functionality. If you believe that you can develop the existing Wordpress site rather than build a new one, please expand upon that in your submission.
30. Does the team have a preferred CRM that they are familiar with?
We do not have a preference.
31. Please can you define the users and purpose of the website? Is it purely to disseminate information to the public or will it also be used for the coordination and storage of evidence and sensitive information behind the login?
The site is for the dissemination of public information. No additional information will be held behind the login.
32. Do you have any specific requirements for accreditation of the solution or staff engaged in the project?
33. You state “Good search engine optimisation” as a technical requirement. What criteria or tool will you use to evaluate this?
There is no one set of criteria to use. The site must be properly formatted, have the right metadata, including social media cards, and be correctly indexable by major search engines.
34. You state “Fully accessible (WCAG 2.0)” as a technical requirement. Are you looking for A, AA or AAA rating? Do you have a focus group that will assess the accessibility, if so when is this scheduled? Will this be performed by an internal or external team?
AA - we will use a combination of automated accessibility checkers and manual checking. No focus groups. The site should work without javascript and even if CSS is dropped.
35. ‘Security clearance’ was left empty. Does that mean it is not necessary?
Security clearance is not necessary for the delivery of this project.
36. Platform compatibility, the stated requirements are different to those listed in the Service Design Manual ( Please can you confirm the browser and software version requirements? We note that Blackberry devices are not listed in the Manual, definition will be helpful.
Please use the GOV.UK Service Manual list on the link.
37. “Must work in all major browsers” as a technical requirement. In addition to the current version, how many previous versions do you wish to be supported?
It needs to work in all browsers listed here:
38. Analytics - Can you provide any analytics (specifically, we are after total average visits/sessions per month)?
This will be variable depending on the activity of the Inquiry. The live-stream of the opening of the Inquiry on 14 November had 500 live viewers on YouTube.
39. Please can you advise who is responsible for the migration of the content from the old to the new website?
The content (text, files, links) of individual pages will be provided to the developers alongside a structure for the website upon the commencement of the build.
40. Please can you advise whether there are any specific security requirements or classifications for the information stored behind the login?
The site is for the dissemination of public information. No additional information will be held behind the login.
41. In ‘About The Work’, you state “Functional across mobile, tablet and widescreen” as a technical requirement. How many breakpoints are you expecting designs for? For example does tablet cover portrait and landscape as two different breakpoints?
The completed website needs to work across all breakpoints.
42. We have some clients who are major players in the construction sector. We are interested to know if there are limitations or restrictions on bidders and their clientele, to prevent the perception of a conflict of interest?
Developers will not have access to any privileged information. If developers perceive any potential conflict of interest, however, it should be flagged in their response. Responses should also detail how any conflict of interest would be managed.