• led by the Digital Experience Team at Renfrewshire Council

Menu Close

Invitation to tender for Renfrewshire.gov.uk delivery phase

We’re looking for a delivery partner to develop a new Renfrewshire.gov.uk on Drupal CMS (version 10 or 11). The LocalGov Drupal distribution will serve as the foundation and be customised to suit the specific object-oriented needs of Renfrewshire.gov.uk.

Progress to date and delivery roadmap

In 2019, the council’s Digital Experience team led a Pre-discovery phase to assess the efficiency of the existing digital experience. Based on our findings, we shaped a digital experience vision to make our information and services easy to find and use online for our local communities and employees.

We then led a Discovery phase to validate the challenges we identified in Pre-discovery. We categorised them into four themes and recommended solutions for Renfrewshire.gov.uk and the wider digital experience. One of the solutions proposed was the development of a new Renfrewshire.gov.uk and Staff.renfrewshire.gov.uk using Drupal CMS.

In Alpha, the recommendations made in Discovery were tested. The focus was on testing the technical architecture, development processes, and object-oriented approach to ensure a coherent UX. Additionally, improvements in accessibility, security, performance, scalability, and sustainability were emphasised. You can read more about what we did and learned in Alpha.

These phases helped us design a delivery roadmap that requires contracts for the following components:

  • gov.uk delivery phase
  • renfrewshire.gov.uk delivery phase
  • Hosting
  • Support and maintenance
  • Automated comms technology.

This invitation to tender is specifically for the Renfrewshire.gov.uk delivery phase. The hosting, support and maintenance, and automated communications technology will be procured separately.

Scope of the Renfrewshire.gov.uk delivery phase

In this delivery phase, we’ll focus on developing a new Renfrewshire.gov.uk.

This website will be built on a robust technical architecture, utilising Drupal CMS (version 10 or 11, depending on when the development starts). The LocalGov Drupal distribution will serve as the foundation, customised to suit the specific object-oriented needs of Renfrewshire.gov.uk.

It’s essential that the development of Renfrewshire.gov.uk and its associated technical architecture aligns with our object-oriented model. This will foster a mindset centred around connected “objects” that make sense to users, rather than merely focusing on disconnected traditional page templates and CMS content types.

It’s essential that this architecture is designed to be highly scalable, capable of accommodating multiple websites in subsequent phases, including Staff.renfrewshire.gov.uk and the potential Renfrewshire Health and Social Partnership website, while reusing the HTML pattern library.

The new website must comply with our security requirements, GDPR and WCAG 2.2 AA.

This delivery phase will be executed through the collaborative efforts of an internal team and a digital agency. The contract with the digital agency is anticipated to start in July 2024 for a duration of up to 18 months, ideally 12 months.

Roles in the Renfrewshire.gov.uk delivery phase

The key Renfrewshire Council’s team members, integral to the Renfrewshire.gov.uk delivery phase, are as follows:

  • 1 Digital Experience Manager
  • 1 Lead Content Designer
  • 2 Content Designers
  • 1 Content Editor
  • 1 Senior Interaction Designer
  • 1 Front-end Developer.

Our internal team will assume responsibility for UX and content-related activities like ORCA (Object, Relationship, Calls-to-action, Attributes) and content modelling, content design and migration, interaction design, design system, Figma prototyping, and user research and testing. Our internal team will document and prototype objects on Figma including but not limited to, topic, service, guide, financial support (including grant, loan, fund, payment, benefit, discount, exemption), news (including news article, media release, and notification), event, consultation, place and space (including school, nursery, library, park, council building, etc.), group (including service team, board, association), person, contact, project (including initiative and volunteering opportunity), publication (including vision, strategy, plan, policy, report), training, and form.

The digital agency is expected to provide essential web development resources to coordinate, lead, and delegate activities related to technology and solution architecture, hosting configuration, and development activities and processes including Drupal development, front-end development, integration with third-party systems, quality assurance and testing. Overall, the digital agency is responsible for the end-to-end development and technical aspects of the website and its essential features and functionalities, from architecture design to deployment, while also ensuring efficiency, quality, and coordination throughout the process.

Most front-end development tasks, such as developing the HTML pattern library and conducting accessibility testing, must be carried out by our internal Front-end Developer and Senior Interaction Designer, with support and guidance from the digital agency. Quality assurance and testing will be led by the digital agency, with the active involvement of our internal team. Additionally, there may be a need for strategic oversight, planning and project management resources from the digital agency to ensure clarity, collaboration and quality.

Throughout the contract duration, we anticipate that the digital agency will facilitate technology onboarding and provide training as required so the internal team becomes more independent. To ensure a transition in a sustainable manner, we foresee a range of handover methods such as gradual involvement, training repositories, and shadowing of development work.

In specific instances, the digital agency will need to collaborate with LocalGov Drupal and the chosen hosting provider to establish the technology and solution architecture.

Finally, the digital agency must integrate with the Renfrewshire Council team and use internal resources, share knowledge and insight, work in an open and transparent way, and bring valuable development expertise.

The digital agency must fully adopt the object-oriented approach and creatively integrate it into the Drupal CMS development to ensure the success of the Renfrewshire.gov.uk delivery phase.

What’s not in the Renfrewshire.gov.uk delivery phase contract

We don’t need the digital agency in the Renfrewshire.gov.uk delivery phase to provide hosting. A separate contract will be arranged through G-Cloud which will commence shortly before the Renfrewshire.gov.uk delivery phase begins.

Another invitation to tender will be released later in 2024 to contract with a digital agency to provide annual support and maintenance once the new Renfrewshire.gov.uk is launched. Due to the usage of Drupal and hosting we would expect fairly low maintenance overheads – largely focused on ensuring Drupal core and modules are kept updated to secure versions and implementing new features from our new prototypes and LocalGov Drupal.

The Staff.renfrewshire.gov.uk delivery phase and the digital communications platform will also be in different invitations to tender.


We expect to launch a partial version of Renfrewshire.gov.uk between November 2024 and March 2025.

Initially, this new website will contain selected sections, including waste, environment, council tax, benefit and money advice, and housing.

The new bin collection calendar must be launched on this partial website, ideally before the end of 2024. You can find more information about the calendar in the Solution architecture section.

The internal team will gradually review and incorporate content from other sections into the new website. This process will lead to the retirement of the old Renfrewshire.gov.uk.

Technology architecture

During Discovery and Alpha, we conducted a comprehensive assessment of the technology architecture requirements for our future digital experience estate, leading to the following key insights.

Drupal CMS

We’ve determined that a traditional Drupal CMS (version 10 or 11) best suits our needs as it prioritises effective content management through modularity and reusability, while ensuring coherent user experiences.

This architecture will delegate specialised functionality like some forms and maps to other applications that we use like MyAccount (Granicus) and ArcGIS.

Despite being traditional, the architecture should align with our object-oriented model and preserve the flexibility for a more decoupled architecture in the future.

The Drupal CMS architecture should also be designed for high scalability, ensuring it can accommodate multiple websites in subsequent phases, including Staff.renfrewshire.gov.uk and renfrewshire.hscp.scot. During the Renfrewshire.gov.uk delivery phase, the digital agency, in collaboration with the internal team, should explore options such as implementing a ‘multi-site’ enabling both the Renfrewshire.gov.uk and Staff.renfrewshire.gov.uk to share the same Drupal environment, HTML pattern library, database, and content.

LocalGov Drupal

We’ll leverage the LocalGov Drupal distribution as a solid foundation, from which we’ll further customise to our needs.

The LocalGov Drupal distribution comprises a collection of code, including modules, configurations, content types, and more, to provide a specialised foundation for council websites. Currently, the LocalGov Drupal distribution provides the following content types:

  • service pages
  • service landing pages
  • step by steps
  • guides
  • publications
  • directories
  • events
  • subsites
  • newsroom
  • news article
  • microsites
  • intranet (coming soon).

During Alpha, we identified that it might sometimes be challenging to align the LocalGov Drupal distribution with our object-oriented model as it mainly focuses on templates rather than connected objects. It also has a standardised appearance with the conventional LocalGov theme, originated from the GOV.UK design system.

We plan to define our own custom theme with bespoke features to support our object-oriented model, all while harnessing the benefits of LocalGov Drupal’s foundational capabilities.

We also believe that usage of the LocalGov Drupal distribution fits with the Council’s ambitions to be open and collaborative. We’ll aim to share our work with the wider LocalGov Drupal community.

Pattern library via Chromatic and Storybook

We’re committed to developing more unified user journeys through consistent use of a design system / HTML pattern library across the digital experience including Renfrewshire.gov.uk, Staff.renfrewshire.gov.uk, and MyAccount.renfrewshire.gov.uk.

During Alpha, we prototyped a design system on Figma and an HTML pattern library using Storybook and Chromatic. We demonstrated how this could be integrated with both the Drupal instance and other applications like MyAccount. Chromatic and Storybook offer a practical solution for visualising, interactivity and accessibility testing, and documenting UI components. It’s also conveniently published as an NPM package, facilitating easy integration into platform-specific codebases.

In this delivery phase, we expect the digital agency, in collaboration with our internal Front-end developer and Senior Interaction Designer, to build upon the HTML pattern library.

Additionally, we plan to leverage GitHub as a centralised version control platform for both the website and the HTML pattern library, integrating a CI/CD pipeline via GitHub actions to streamline development workflows.

Currently, we’re configuring Chromatic and Storybook and building our HTML pattern library.

Hosting platform

In alignment with our IT principles, we’ve determined that Platform as a Service (PaaS) is the most adapted model for hosting Renfrewshire.gov.uk and future websites on Drupal.

In Pre-discovery, Discovery, and Alpha, we assessed the hosting market and different solutions specialised in Drupal hosting. We identified a few hosting providers that offer an environment that complies with the council’s IT standards. These include being cloud-based with no on-premises components, resilience, security, and a commitment to Environmental, Social, and Governance (ESG) principles.

In collaboration with the future hosting provider, we expect the digital agency to set up the hosting for Renfrewshire.gov.uk.

Solution architecture

During Discovery and Alpha, we also established essential solution architecture requirements to align technology with our vision and needs, with implementation driven by collaboration between our internal team and the digital agency.

Object-oriented development

We’re enhancing user experience by creating new objects or content types within the LocalGov Drupal distribution, guided by Object-Oriented User Experience (OOUX) principles. During Alpha, we focused on designing connected objects, integrating them into Drupal entities such as services, bins, waste items, or places. This approach will continue in the Renfrewshire.gov.uk delivery phase with defined responsibilities between our internal team and the digital agency.

The internal team will follow the ORCA process, which involves several steps:

  • defining objects and grouping them when necessary
  • defining instances for each object like the ‘Have your say on Barshaw park’s community garden’ consultation
  • establishing relationships between objects, including parent-child object relationships, like how a Financial support like a grant can consist of multiple application Rounds and list Recipients who have been awarded funding.
  • defining the calls-to-action offered to users, like encouraging them to provide feedback on a project, applying for financial support, or getting a reminder to apply
  • identifying the attributes (core content and metadata) of each object, which may be linked with Schema.org properties
  • prioritising and sequencing objects as well as their relationships, CTAs and attributes based on organisational objectives and users’ needs
  • creating an ORCA and content model for objects to document requirements for attributes, relationships, and calls-to-action
  • prototyping objects and testing them with users.

So far, the internal team has been working on:

  • News
  • Notifications
  • Financial support
  • Service
  • Guide
  • Waste, Bins, and Bin collection calendar.

Bins and recycling prototypes

View bins and recycling prototypes on Figma.

News prototypes

View news prototypes on Figma.

Financial support and service (appeal) prototypes

View financial support and service (appeal) prototypes on Figma.

Financial support, grants and funding ORCA model

View financial support ORCA modal on Figma.

The digital agency will be required to adopt our object-oriented approach and creatively integrate it into the Drupal CMS development to ensure the success of the Renfrewshire.gov.uk delivery phase. We expect the digital agency to use outputs from the ORCA and content model to:

  • determine how these objects and their properties translate into the content types and building blocks in Drupal, including entities and fields such as content types, taxonomies and custom entities
  • ensure a logical and semantic mapping between objects and the content management structures
  • map Drupal entities to Schema.org properties when possible and implement them as structured data in JSON-LD format
  • support back-referencing entity fields in Drupal, for example automatically linking bins to waste items and vice versa.

Content reusability

We aim to centralise essential information which frequently appears across multiple pages on Renfrewshire.gov.uk. This information could include things like opening times, prices, service titles and descriptions, and contact details.

In our current CMS, this information is spread out and manually updated on various pages, leading to inconsistencies and conflicting information. It’s not efficient when editing on the CMS.

We want to implement a COPE (Create Once Publish Everywhere) functionality for certain types of objects and their attributes. When changes are made in one place, they will automatically propagate to all relevant places across the website.

The internal team will identify objects and attributes that will need a COPE functionality to enable automatic synchronisation.

Page building and hygiene content

Many contemporary content management systems have transitioned from the traditional single WYSIWYG (What You See Is What You Get) editor to a component-based approach. This enables users to select from pre-configured ‘modules’ or ‘blocks’ to effectively organize their content, each of which could benefit from WYSIWYG functionality.

During Alpha, we adopted this approach, breaking down content types into manageable sections while offering a component-based authoring experience within these sections. However, we acknowledge the value of having ‘fixed’ content types to ensure reliable and consistent information structuring.

In this delivery phase, we aim to implement a hybrid approach to page building. Editors will have the flexibility to construct pages by selecting components from a library. However, certain objects or content types will be less flexible to maintain consistency and visual coherence.

The level of flexibility in page layout will vary based on the attributes being presented, with not all content types requiring the same degree of flexibility. Our internal team will document this flexibility level.

Additionally, our internal team will prototype core website functionalities such as the homepage, search index page, search results page, contact us, and landing pages.

Form building

Form building is not currently essentials since we can use MyAccount (Granicus). However, it’s prudent to prepare for future needs on Renfrewshire.gov.uk and Staff.renfrewshire.gov.uk.

We should enable the Drupal Webform module and use the LocalGovDrupal forms to provide additional configuration and components. Our HTML pattern library will inform the style of forms. Form components will be prototyped on Figma and front-end developed by the internal team.

The form building functionality on the LocalGov Drupal distribution, its address lookup, could be used for the bin collection calendar.

Content authoring

During the Alpha phase, we evaluated the content authoring platform GatherContent and its integration with Drupal. We discovered limitations that would prevent us from achieving the desired content authoring experience within Drupal.

In this delivery phase, we intend to use the Workflow feature provided by LocalGov Drupal.

Additionally, we require to incorporate some reporting features to enhance the content authoring experience, streamline content management, and gain insights into user activities, access control, content lifecycle, workflow progress, and version history within the CMS. These features will help us to:

  • capture and report on user activities, including login/logout times and content edits
  • monitor user roles, permissions, and access levels to ensure proper access management
  • keep track of content and media status, including the date published/reviewed, owners, and states like ‘draft’, ‘under review’, ‘published’, and ‘archived’
  • monitor the progress of content through the publishing workflow, including approvals, rejections, and delays – automatic notifications would be useful
  • track on and compare the revision history of content and media within the CMS, including who made changes, when changes were made, and what specific changes were made.

The ability to restore previous versions of content is also desired for content control and version management.


Building upon the work carried out during Alpha, the Renfrewshire.gov.uk delivery phase will focus on advancing the integration between the HTML pattern library and the Drupal theming layer.

We want to:

  • use Twig to seamlessly integrate the components from our pattern library into our Drupal templates
  • override the default Twig templates provided by Drupal core with our own Twig templates, built within our custom theme
  • include the templates and markup defined in our external HTML pattern library (added as a dependency of the website via NPM)
  • compile and compress styles and scripts from the components in our HTML pattern library within our Drupal theme via Webpack.


We’ll continue the delivery of transactional services through MyAccount (Granicus) while ensuring a seamless experience with Renfrewshire.gov.uk.

This seamless experience entails users starting on Renfrewshire.gov.uk, being directed to a MyAccount form for a specific transactional service via a hyperlink, and then being redirected back to Renfrewshire.gov.uk after completing the transaction.

Granicus’s existing redirect functionality supports conditional redirects based on transaction outcomes (successful or cancelled) and allows passing query strings in the URL. Further exploration is needed in this delivery phase to determine the extent to which dynamic content can be utilised.

To achieve coherence between Renfrewshire.gov.uk and MyAccount, we’ll use the shared design system and HTML pattern library. However, there are limitations regarding the customisation within MyAccount (Granicus), necessitating some compromises in usage. We anticipate the digital agency to provide some support and guidance to our Front-end developer and MyAccount team to facilitate the integration of Renfrewshire.gov.uk and MyAccount.

Bin collection calendar

As part of the Renfrewshire.gov.uk delivery phase, we need to develop a bin collection calendar which will be in some ways similar to the existing process where user-supplied addresses determine displayed information. To improve this online service, we want to explore a more advanced real-time information integration into Renfrewshire.gov.uk and use our future digital communications platform for transactional communications.

In Alpha, we developed new Renfrewshire.gov.uk waste and recycling prototypes. With these prototypes, which we’re still optimising, our users will be able to:

  • easily find the information they’re looking for on their preferred search engine and smart speaker
  • check their bin collection dates on Renfrewshire.gov.uk and receive reminders via emails, SMS and potentially WhatsApp
  • if subscribed, get notified if their bin collection has been missed, understand why, and see if and when it’ll be collected so they don’t have to report it
  • check what they can put in each bin to effectively recycle and avoid contamination
  • check information about recycling centres so they know when they open and what they can bring
  • see alternative recycling options to encourage people to recycle or upcycle in different ways
  • ask for things online like additional bins or replacements if broken so they can continue to recycle and receive effective waste and recycling services from the council.

To make these prototypes available on the future Renfrewshire.gov.uk, we think we’ll need to connect the route optimisation software with:

  • our future Renfrewshire.gov.uk
  • our future digital communication platform (currently being defined).

The Ordnance Survey Places API from the LocalGov address lookup could be used for bin collection postcode lookup, but the location of bin collection data and extraction methods remain uncertain pending procurement of a new routing system. This system should be known at the start of the Renfrewshire.gov.uk delivery phase.

In collaboration with the internal team, we expect the digital agency to provide some support to:

  • assess what APIs from the route optimisation software based around the UPRN we can surface digitally for the end-users
  • assess how our digital communication platform could integrate best with the future route optimisation software
  • assess how waste and recycling information can be provided via smart speakers (our Front-end developer will be the lead for this work)
  • develop, test, and deploy the back-end and front-end of the waste and recycling prototypes including the bin collection calendar, list of waste items, and list of recycling centres on the future Renfrewshire.gov.uk
  • develop, test, and deploy the back-end and front-end of the waste and recycling notifications via email, SMS and potentially WhatsApp sent to users including bin collection reminders and missed bin collection.

Newsletter sign-up

We’re evaluating solutions for a new digital communications platform and planning to build a newsletter banner component within our design system and HTML library. This component will be used for different email subscriptions and transactional emails like:

  • bin collection reminders and missed bins notifications
  • funding and service reminders
  • consultation notifications.

We’ll need to build it as a component in Drupal and integrate it with the new communications platform and its lists so it can be used across the website.

Depending on the selected platform, integration might involve existing Drupal modules or third-party options like Zapier, with implementation likely handled by the digital agency. We might seek some advice from the digital agency when selecting the new platform.

We’ll have selected a platform by September 2024.

Internal search

Our Drupal environment must incorporate with a search functionality like Apache Solr and provide advanced features like faceted search, support for synonyms, spellcheck, and hit highlighting.

Search engine optimisation

The website must incorporate Search Engine Optimisations (SEO) best-practice, including the implementation of structured data in JSON-LD markup for enhanced search engine results. Here’s how we’ve used markups in Alpha:

  • We included commonly used meta tags, such as titles and meta descriptions, to optimise search engine visibility.
  • For improved integration with social media platforms, we incorporated standard Open Graph meta tags, along with the necessary meta tags for X (Twitter) cards.
  • To enhance the visibility of Place-related content, we implemented the RecyclingCenter Schema.org type, which is a subset of the LocalBusiness and Place types.
  • For Service-related content, we implemented the GovernmentService Schema.org type, ensuring accurate and structured representation.
  • An XML sitemap, following the format defined by the sitemaps protocol, was added. It’s set to update at regular intervals through cron jobs, refreshing every thirty minutes. This feature helps search engines in efficiently crawling and indexing website content.

As part of the content modelling, the internal team will identify Schema.org types and properties to use. We expect the digital agency to support this activity when possible.

Cyber security plan

As part of our cyber security plan, we should incorporate these best practices:

  • Security responsibilities: The development resources in this phase (both internal and external) will be responsible for the security in the environment. The hosting provider will be responsible for the security of the environment.
  • Application security: The website should follow Twelve-Factor App principles and install Drupal security hardening modules to minimise the storage of personal data.
  • Secure environment: The hosting provider will be responsible for the secure hosting environment, including vulnerability management, firewall setup, and file permissions. The development resources should use the hosting provider’s performance and security features, like Global CDN and SSL configuration.
  • Monitoring: The hosting provider will handle secure event monitoring, while the development team should configure an uptime monitoring service like UptimeRobot if required.
  • Security updates: The website modules and other dependencies should be kept continuously updated as new versions are released. The development team should subscribe to the Drupal RSS security feeds to ensure they are notified of security issues relevant to the Drupal instance.
  • Incident response and disaster recovery: The hosting provider will provide daily backups, and the development resources can troubleshoot using event streams. The hosting provider’s support team should be informed of potential security incidents for assistance so that they can assist in their resolution.
  • Access controls: Identity management should be centralised (e.g. SSO enforced for content editors). The ‘principle of least privilege’ should be applied and Drupal’s role-based permission system used to ensure that data is only exposed to users who require it. Security hardening controls (e.g. 2FA and enforced password policies) should be applied to any services with user accounts relevant to the website.
  • Assessment: The development team should regularly assess website security, request a go-live audit from the hosting provider before launching, and conduct an annual penetration test by a trusted supplier.

Security hardening via Drupal

Drupal community modules for security hardening should be enabled and appropriately configured.

Drupal comes with a variety of security features such as: password-based authentication, role-based access control (RBAC), data validation, and Anti-DDoS protection.

We’d like the following community modules or similar to be installed on the website: Honeypot, Password Policy (if allowing non-SSO login), Automated Login, reCAPTCHA, Security Kit.

The Security Review module provides a quick and easy way to ensure that a subset of common security exploits have been avoided.

Patches for security vulnerabilities in website dependencies should be applied, tested, and deployed as soon as possible after they have been released.

Analytics, performance, and compliance

GA4 and Google Search Console tracking should be configured via Google Tag Manager. Any other tracking snippets like Smartlook or Ahrefs should be loaded onto the site via Google Tag Manager.

As part of the broader performance monitoring, we’ll configure and use the correct tooling to measure relevant KPIs.

We expect to configure and use the following tools:

  • Accessibility – WAVE and SortSite
  • Emissions – EcoPing
  • Page speed – Calibre
  • Security – Webcheck and NCSC vulnerability checks.

CookieBot or CivicUK cookie consent mechanism should be used with Google Consent Mode API to ensure that any tags loaded via GTM are only served to users who have opted-in to the relevant cookie category. The CookieBot, CivicUK or browser scanning tools should be used to ensure that all cookies on the site are identified and categorised correctly.

Finally, Renfrewshire.gov.uk must be fully accessible and compliant with WCAG 2.2 AA.

The internal team will lead activities related to Analytics, performance, and compliance. Some advice and support from the digital agency might be sometimes needed.

Carbon footprint reduction

We should use Calibre and EcoPing in the development pipeline, enabling the monitoring of page weight and data transfer.

At the application level, we should follow the Web Sustainability Guidelines (WSG) 1.0 to reduce emissions including: minimizing/compressing assets, considering the application cache strategy, blocking traffic from bots, using images and videos selectively and delivering them in the most appropriate format, lazy loading content, disabling autoplay on videos, minimising the ‘round trips’ required to fetch content, avoiding heavy/bloated 3rd party scripts.

At the environment level, some hosting features should be enabled to improve performance and reduce emissions including: HTTP/2, caching via Varnish HTTP reverse proxy and Memcache key-value store, global CDN for ensuring that content is served ‘closer’ to the end user.

Expertise from the digital agency

For the successful delivery of this phase, we expect the digital agency to provide the following areas of expertise:

  • High-level system management: expertise in defining and managing the high-level aspects of the CMS, including system architecture, CMS setup, configuration including security, hosting setup, and integration with external tools and systems. This also includes defining non-functional requirements, specifying the development approach, selecting appropriate tools and frameworks, and collaborating with the quality assurance expertise to establish testing standards and approaches.
  • Drupal development: Full stack development expertise will be essential to focus on various aspects of Drupal website development. This expertise encompasses site building, theming, and custom module development within Drupal. A natural division of responsibilities could involve one developer focusing on backend configuration and another on supporting the theming and integration with the pattern library in collaboration with our internal Front-end developer.
  • Front-end development: The digital agency must use our internal Front-end Developer and Senior Interaction Designer to establish a robust pattern library. They excel in front-end tooling, possess an in-depth understanding of the latest CSS and accessibility standards. However, they need more experience with Drupal. To bridge this gap, the digital agency may consider involving one of their front-end developers. This expertise could provide training and participate in the integration of the pattern library with the website, ensuring a seamless transition and knowledge transfer.
  • Quality Assurance: We expect the digital agency to lead assurance and the internal team to actively participate in quality assurance activities. This will be essential to maintain the right level of detail within functional requirements, develop test strategies and plans, and ensure comprehensive testing. The quality assurance expertise from the digital agency should provide oversight to enforce best practices related to tooling and quality assurance processes. They should also ensure that the delivered work aligns with functional specifications.
  • Strategic oversight, planning and project management: The agency should have experienced project managers who can oversee the entire development process, from initial planning to deployment. This includes creating a timeline, allocating resources, managing risks, and ensuring timely delivery within budget. A UX and/or technical senior role could also be involved to provide strategic oversight throughout the delivery process.

What the procurement timeline is

These are the key procurement dates:

  • Published on Digital Marketplace: Tuesday 2 April 2024
  • Deadline for asking questions: Thursday 11 April 2024
  • Closing date for applications: Tuesday 23 April 2024
  • Stage 1 shortlisting: Wednesday 24 April – Friday 14 May 2024
  • Feedback to suppliers not shortlisted: Wednesday 15 – Monday 20 May 2024
  • Stage 2 invitation to submit proposal for shortlisted suppliers: Wednesday 15 – Monday 20 May 2024
  • Stage 2 deadline for asking questions: Tuesday 28 May 2024
  • Stage 2 closing date for submitting proposal: Tuesday 4 June 2024
  • Stage 2 evaluation: Wednesday 5 June – Friday 14 June 2024
  • Stage 2 update to suppliers: from Monday 17 June 2024
  • Contract award: June 2024
  • Expected contract start date: July / August 2024.

Order forms and schedules

You can download forms and schedules including the Order Form, Joint Schedules and Call Off Schedules. These have been included for reference only in order to note the additional Terms and Conditions and the documents will be required to be completed by the successful supplier, later in the process.

Philippe Fara
Philippe is Digital Experience Manager at Renfrewshire Council.