RAINBIRD TECHNOLOGIES LTD

AI Decisioning Platform

Rainbird is a cloud-based SaaS decision intelligence engine for automating and scaling complex, high-stakes decisions. It captures expert knowledge into auditable decision models, integrates via secure APIs with customer systems, and returns deterministic recommendations with transparent explanations. Designed to augment human judgement, it improves consistency, compliance, traceability, and operational efficiency.

Features

• Low-code decision authoring to encode decision logic as graphs.
• Deterministic reasoning engine delivering consistent recommendations from runtime inputs.
• Evidence and audit trail explaining outcomes with traceable decision metadata.
• Test suite to validate accuracy and assure decision model performance.
• Secure APIs and SDKs integrating recommendations into customer applications.
• Natural language capability to capture knowledge and support user interactions.
• Governance controls for model versioning, approvals, and graph management.
• Operational visibility for automated decisions and audit trails.
• Run scenario and “what-if” testing before deploying decision models
• Apply role-based access controls to protect decision models and data

Benefits

• Rapidly capture and maintain expert decision logic without specialist coding.
• Deliver consistent and repeatable decisions at scale across complex processes.
• Provide transparent, explainable recommendations with full audit trails.
• Validate decision logic before deployment to assure ongoing accuracy.
• Embed automated decisions seamlessly into existing systems and workflows.
• Capture expert knowledge using natural language without technical barriers.
• Govern decision changes through controlled versioning and approvals.
• Monitor automated decisions to improve compliance and operational performance
• Improve decision consistency while augmenting, not replacing, human judgement.
• Reduce operational risk by standardising complex decisions across teams.

• Education pricing available
• Free trial available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at james.duez@rainbird.ai. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

632506703227973

Contact

James Duez
020 3650 3826
james.duez@rainbird.ai

About your service

• Service categories:

  Application Development and Deployment

  Application platforms

  • Model driven application platforms
• Multi cloud support: Yes

Service scope

• Software add-on or extension: Yes, but can also be used as a standalone service
• What software services is the service an extension to: Rainbird can be used standalone, but is commonly implemented as a decisioning platform called by other systems via secure APIs to provide recommendations. It can extend CRM, case management, finance, procurement, HR and other SaaS platforms, as well as Robotic Process Automation (RPA) and Agentic AI workflows.
• Cloud deployment model:
  • Public cloud
  • Private cloud
• Service constraints: 1. Rainbird is primarily a back-end decision intelligence engine rather than an end-user application. Buyers should plan to integrate it with existing systems, portals or workflows so operational users can consume recommendations and explanations in the tools they already use. ; 2. Licensing is usage based, so the volume of production decisions is limited by the agreed licence. Development and testing decision runs are excluded from this production usage limit.
• System requirements:
  • Chrome browser recommended for Rainbird Studio authoring environment access.
  • API connectivity required between Rainbird and consuming customer systems.
  • Supported cloud hosting on AWS, Azure, or Google Cloud Platform.
  • Hosting requirements vary by cloud provider and selected deployment model.

User support

• Email or online ticketing support: Yes
• Support response times: Rainbird provides rapid, clearly defined response times to ensure users receive timely support. For critical incidents affecting the Rainbird Runtime Environment, Rainbird responds within 30 minutes for service outages and within one hour for performance degradation, with 24x7 coverage including weekends. Continuous effort is made to restore service as quickly as possible. For service requests such as account access or technical issues, responses are provided within two to four hours during UK business hours, 08:00 to 18:00, Monday to Friday. Studio Support queries receive responses within four hours during the same weekday support window.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: None or don’t know
• Phone support: No
• Web chat support: No
• Onsite support: No
• Support levels: Depending on the client, we can provide specific maintenance and support for applications built on the platform, PoA. Support is typically structured in tiers, ranging from standard platform support through to enhanced application-level support for client-specific decision models and integrations. Standard support covers incident management, platform availability and service requests in line with the Rainbird Service Level Agreement. Enhanced support can include additional assistance for solution configuration, integration troubleshooting and ongoing optimisation of deployed decision models.; ; The cost of enhanced or bespoke support services is agreed on a case-by-case basis, depending on the scope, complexity and level of support required. Where appropriate, Rainbird can also provide access to a named technical account manager or cloud support engineer to act as a consistent point of contact, support service coordination and provide technical guidance throughout the service lifecycle.
• Support available to third parties: No

Onboarding and offboarding

• Getting started: Our onboarding is designed for authorised Knowledge Engineers who are responsible for building, testing and governing decision models. New users are granted access following buyer approval and account setup using secure credentials. Initial onboarding support includes access to platform documentation and guided support to familiarise users with the Rainbird Studio environment, decision modelling concepts and governance controls. Support is available during onboarding through phone support channels to address setup questions and early usage queries. The duration of onboarding varies depending on the complexity of the decision models being developed and the buyer’s readiness.; ; Offboarding is supported at contract end or on request. User access is revoked, and buyer data is handled in line with agreed contractual terms and data protection requirements. We document all data export and deletion processes to support responsible exit and avoid vendor lock-in.
• Service documentation: Yes
• Documentation formats: HTML
• End-of-contract data extraction: At the end of contract, buyers can extract both decision models and runtime decision outputs using Rainbird Studio export and API export.; ; 1. Decision models can be extracted from Rainbird Studio by exporting knowledge maps as a portable .rbird file. This export includes the knowledge map code, the graph layout and any README information for the selected version. Automated tests, agents, statistics and reporting data are not included in the exported .rbird file and must be managed separately.; 2. Runtime outputs are extracted programmatically via the RESTful API, allowing buyers to retrieve interaction transcripts, outcomes and decision evidence in machine readable formats such as JSON for storage in buyer systems. Where evidence or interaction logs are secured, the appropriate API keys and access controls apply.; ; Platform support levels, including technical support, are defined within each contract and a named account manager coordinates exit activities and data extraction. Extraction can be performed during an exit window, as defined in the customer agreement, with support provided via agreed support channels and the buyer’s account manager. After extraction, access is revoked and customer data is retained, returned or deleted in line with contractual terms and data protection requirements, including confirmation on request.
• End-of-contract process: At the end of each contract, exit is managed through an agreed contractual notice and offboarding process. During the notice period, Rainbird agrees an exit plan with the buyer, led by the named account manager and supported by the contracted platform support levels, including technical support. This plan confirms scope, responsibilities acknowledged by both parties, and the timetable for data extraction and access removal.; ; Buyers can extract decision models and runtime decision outputs during an agreed exit window. Decision models are exported from Rainbird Studio as portable .rbird files. Runtime outputs, including interaction transcripts, outcomes and decision evidence, are extracted via the RESTful API in machine readable formats such as JSON, subject to API key and access controls.; ; At contract end, user access is revoked and credentials are disabled. Remaining customer data is retained, returned or deleted in line with the contract and data protection requirements, with confirmation on request. Any additional support for applications built on the platform can be provided on an agreed plan of action basis. Exit charges, if any, are as defined in the contract and order form. Public offboarding documentation is not currently published.
• Documentation accessibility standard: None or don’t know
• How the documentation is accessible: Onboarding documentation is provided as part of service initiation to support authorised users in getting started. Public offboarding documentation is not currently published. Offboarding activities, including user access removal and organisational exit, are managed by Rainbird in response to client requests, in line with contractual and data protection requirements, ensuring responsible handling of customer data.

Using the service

• Web browser interface: Yes
• Supported browsers: Chrome
• Application to install: No
• Designed for use on mobile devices: No
• Service interface: No
• User support accessibility: None or don’t know
• API: Yes
• What users can and can't do using the API: Yes, Rainbird provides an active RESTful API intended for system integrators and development teams building buyer-facing applications and workflows. Using the API, users can support the end-to-end runtime lifecycle, including:; ● Submitting runtime data and request a decision or recommendation from a specified model.; ● Initiating and managing decision interactions so a consuming system can guide a user through questions and capture responses.; ● Retrieving the decision outcome along with supporting evidence, audit metadata, and interaction transcripts, enabling transparent explanations and traceability.; ● Integrating Rainbird outputs into existing services such as case management, CRM, HR, finance, procurement, RPA and other bespoke digital services.; ; Using the API, users cannot:; ● Create, edit, upload or manage knowledge maps, policies or decision models.; ● Perform decision authoring, model testing, approvals, versioning or governance activities through API endpoints.; ● Bypass the separation between runtime decision execution and model development controls.; ● API access is controlled using API keys so only authorised systems can invoke decision services.; ; This separation prevents runtime systems from changing decision logic and ensures clear controls between model development and operational execution, supporting governance and security.
• API documentation: Yes
• API documentation formats:
  • Open API (also known as Swagger)
  • HTML
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Rainbird is a back-end decision intelligence platform and does not provide customer-facing user interfaces, therefore branding and visual customisation are not applicable.; ; However, knowledge engineers will build custom models for each customer.

Scaling

• Independence of resources: Rainbird is delivered in both single tenant or multi tenant environments, ensuring appropriate isolation between customers. The platform is built on a microservices architecture deployed to cloud provider managed Kubernetes services, allowing workloads to be isolated and independently scaled. The service is designed to scale automatically during peak usage through horizontal workload scaling, cluster level autoscaling, and load balancing. ; ; Capacity is continuously monitored using centralised monitoring and alerting to proactively detect and respond to changing demand. If demand increases suddenly, additional compute capacity is provisioned automatically and traffic is redistributed across available resources, preventing one buyer’s activity from impacting another.

Analytics

• Service usage metrics: Yes
• Metrics types: To support operational oversight and transparency, metrics are presented through real time dashboards at the individual knowledge graph level, allowing authorised users to monitor how decision models are being used. This includes activity and usage information associated with each knowledge graph. Metrics are updated in real time and can be downloaded in common formats such as CSV, enabling buyers to analyse usage, support reporting requirements, and integrate metrics into their own monitoring or management processes.; ; Access is restricted to users with permission to the relevant workspace, for enhanced role based visibility and control.
• Reporting types: Real-time dashboards
• Resource tagging: No
• FOCUS resource tagging: No

Resellers

• Supplier type: Not a reseller

Staff security

• Staff security clearance: Conforms to BS7858:2019
• Government security clearance: None

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations:
  • United Kingdom
  • European Economic Area (EEA)
• User control over data storage and processing locations: Yes
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 4.0)
• Penetration testing frequency: At least every 6 months
• Penetration testing approach: ‘IT Health Check’ performed by a CHECK service provider
• Protecting data at rest:
  • Encryption of all physical media
  • Other
• Other data at rest protection approach: Hosting within AWS data centres with no customer physical access; Logical separation of customer data; Access control policies limiting access to data
• Data sanitisation process: No
• Equipment disposal approach: In-house destruction process

Data importing and exporting

• Data export approach: Users export data in two main ways. Knowledge Engineers can export decision models directly from Rainbird Studio as portable .rbird or .xml files, allowing knowledge maps to be retained, shared, or moved between environments. Runtime outputs can be exported via the REST API, enabling authorised systems to retrieve interaction logs, transcripts, and decision evidence in application/JSON for storage or analysis in buyer systems. Data can be exported at any time during service use, subject to access permissions. Support is available through agreed customer help channels to assist with export questions, troubleshooting, and offboarding requests.
• Data export formats: Other
• Other data export formats: JSON
• Data import formats: Other
• Other data import formats: JSON

Data-in-transit protection

• Data protection between buyer and supplier networks: TLS (version 1.2 or above)
• Data protection within supplier network: TLS (version 1.2 or above)

Availability and resilience

• Guaranteed availability: Rainbird commits to making the Rainbird Runtime Environment available 99.4% of the time, measured over a weekly service period, subject to the customer licence volume limits and the Subscription Agreement. In line with our Service Level Agreement, if the 99.4% uptime goal is not met in a given week, customers are eligible to have their subscription extended by one hour for every minute of outage experienced. ; ; Support for incidents affecting the Runtime Environment is provided 24x7, with defined response and resolution targets based on impact. Exclusions include issues caused by using the service in a way not recommended without prior written agreement, and where agreed invoices are not paid on time. ; ; Availability is monitored and the platform is actively maintained, including upgrades and bug fixes. Planned maintenance arrangements are managed through the contractual service and communications process, including advance notice where applicable.
• Approach to resilience: Rainbird is designed and operated for resilience using cloud-native deployment patterns and managed infrastructure. It is hosted on a managed Kubernetes platform, with containerised microservices distributed across multiple availability zones to remove reliance on any single server, node, or zone and maintain continuity if a component fails. Core data services use cloud-managed databases with built-in high availability and automated failover, reducing operational risk and supporting rapid recovery capabilities. ; ; Single points of failure are mitigated through redundancy and automated recovery. Key application components run with multiple replicas, with load balancing to route traffic to healthy instances. Kubernetes’ self-healing detects failed containers or nodes and automatically replaces or reschedules workloads. ; ; Data protection is embedded within the platform design. Data is encrypted in transit and at rest using cloud-provider security controls, and access is restricted using identity-based, least-privilege permissions. Automated backups with defined retention protect against data loss and support recovery scenarios.; ; Operational resilience is maintained through continuous monitoring of health, performance and logs, with proactive alerting to surface abnormal conditions early. Resilience controls are periodically reviewed, and improvements are made based on testing results and lessons learned from incidents.
• Outage reporting: Rainbird detects outages through continuous internal monitoring and alerting, supplemented by customer reports raised through support channels. When an outage is identified, customers are notified by email using the agreed notification contacts confirmed during onboarding, ensuring messages reach operational and technical stakeholders without delay.; ; Outage communications include the affected service component, the customer impact, and the actions being taken to restore service. Where an incident is ongoing, Rainbird provides regular email updates at appropriate intervals, so buyers have transparent visibility of progress, expected next steps, and clear service restoration status. For planned maintenance, notification email recipients are also agreed during onboarding to ensure timely communications and avoid surprises.; ; Once service is restored, Rainbird confirms recovery by email. An incident report is produced internally to capture the timeline, investigation and corrective actions. Root cause information may be shared with the customer by exception, where it is appropriate and relevant, for example where the buyer needs assurance on recurrence prevention or operational controls. This approach provides prompt notification, clear status information throughout the incident, and professional closure communication.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Username or password
• Access restrictions in management interfaces and support channels: Rainbird maintains an Access Control Policy and limits access to management interfaces and support channels by enforcing strong authentication, role-based permissions, monitored administrative access, and rapid deprovisioning. Rainbird ensures that only explicitly authorised personnel can manage or support systems.
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Username or password

Audit information for users

• Access to user activity audit information: Users receive audit information on a regular basis
• How long user audit data is stored for: At least 12 months
• Access to supplier activity audit information: Users contact the support team to get audit information
• How long supplier audit data is stored for: At least 12 months
• How long system logs are stored for: At least 12 months

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards: ISO/IEC 27001
• Information security policies and processes: Core information security controls are defined through the Access Control Policy, Password Policy, Cryptographic Controls Policy, Virus Protection Policy, Network Systems Monitoring Policy, Backup Policy, and Penetration Testing Policy. Secure handling of information is governed through the Clear Desk and Clear Screen Policy, Secure Printing Policy, Laptop Policy, Mobile Computing Policy, Equipment and Storage Media Disposal Policy, and Information Sensitivity Policy. Acceptable use is managed through the E-mail and Internet Acceptable Usage Policy, Telephone Acceptable Usage Policy, Social Networking Policy, and Anti-Piracy Policy.; ; Data protection and incident handling are addressed through the Data Protection Policy, Information Exchange Policy, Security Incident Management Policy and Data Breach Management Policy. Secure delivery, change and third-party risk are governed through defined development, change and supplier management policies. People and governance controls are supported by the Hiring Policy, Disciplinary Policy, Termination or Change of Employment Policy, Complaints and Grievance Policy, and policies including Anti-Bribery, Money Laundering, and Health, Safety and Environmental policies.; ; All policies are governed through Rainbird’s Information Security Management System (ISMS). The ISMS manual defines policy approval, monitoring, and escalation processes. Accountability sits with the ISMS Manager, with operational oversight by the Infrastructure Engineer. Policies are reviewed annually or following incidents and audits.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Supplier-defined controls
• Configuration and change management approach: Rainbird manages configuration and change through a JIRA-based workflow. All changes are raised as formal requests, reviewed, approved and scheduled by a Change Coordinator to ensure accountability and traceability. Approved changes are planned, including defining requirements, assessing risk and agreeing actions to minimise impact, before being assigned to appropriate delivery resources for implementation with disruption.; ; After deployment, a post-implementation review confirms outcomes and required follow-up actions. Buyers or end users are involved where validation is needed, users are informed of operational changes through agreed channels, and all records are retained in JIRA to maintain an audit trail.
• Vulnerability management type: Supplier-defined controls
• Vulnerability management approach: An Infrastructure Engineer is responsible for day-to-day monitoring of the service environment, including system availability and successful completion of scheduled backups. Security-relevant logs, including server events, remote sessions, antivirus and firewall activity are regularly reviewed to identify abnormal behaviour or potential vulnerabilities.; ; System, firewall, backup and application logs, together with performance metrics, are centrally monitored using AWS CloudWatch Logs and retained for 180 days. Remote session logs are stored and reviewed in Amazon S3. Rainbird’s infrastructure runs on AWS managed services, with patching and security updates applied by AWS.; ; Serious vulnerabilities are escalated to the ISMS Manager for assessment.
• Protective monitoring type: Supplier-defined controls
• Protective monitoring approach: We apply protective monitoring to detect security events early, led by the Infrastructure Engineer. This involves capturing and reviewing day-to-day security relevant activity, including firewall events, server and application service logs, remote session activity, antivirus logs, backup status and performance indicators. These logs are centralised to enable correlation and oversight, through AWS CloudWatch Logs and Amazon S3. We configure automatic alerts to highlight failures and flag abnormal conditions.; ; Incidents are investigated, prioritised by impact and handled through escalation routes to the ISMS Manager for serious events. Actions are tracked for audits and lessons learned. Our monitoring effectiveness is reviewed periodically.
• Incident management type: Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
• Incident management approach: We identify incidents through proactive service monitoring and customer reports raised via support channels. Incidents are logged, tracked and managed through defined support and incident workflows, with prioritisation based on service impact and severity. Responsibility for incident management sits with the operational support team, with escalation to senior technical or security roles where required. ; ; Customers are informed of incidents that affect them through agreed communication channels, typically email. Once resolved, service restoration is confirmed and incidents are reviewed internally to identify root causes, corrective actions and improvement opportunities, which are fed back into our resilience and monitoring processes.
• Post-quantum cryptography secure: Yes

Secure development

• Approach to secure software development best practice: Conforms to a recognised standard, but self-assessed

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: Yes
• Description of free trial: Yes, through Rainbird Community

Discount percentage by annual call-off contract value (excluding VAT)

• Less than £250,000: 7.5%
• Between £250,000 and £500,000: 12.5%
• Between £500,001 and £1,000,000: 17.5%
• Between £1,000,001 and £2,500,000: 22.5%
• Between £2,500,001 and £5,000,000: 27.5%
• Over £5,000,001: 30%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: Citation ISO Certification Limited.
• ISO/IEC 27001 accreditation date: Monday 2 November 2015
• What the ISO/IEC 27001 doesn’t cover: The ISO/IEC 27001 certification applies to the information security management system governing the development, operation, and support of the Rainbird platform within Rainbird-controlled environments.; ; The certification does not extend to customer-managed environments, customer end-user devices, or third-party services not operated or controlled by Rainbird. It also does not cover client-specific configurations, integrations, or data once exported or processed outside the Rainbird platform.
• ISO 28000:2022 certification: Yes
• Who accredited the ISO 28000:2022: Citation ISO Certification Limited.
• ISO 28000:2022 accreditation date: Monday 2 November 2015
• What the ISO 28000:2022 doesn’t cover: The ISO/IEC 27001 certification applies to the information security management system governing the development, operation, and support of the Rainbird platform within Rainbird-controlled environments.; ; The certification does not extend to customer-managed environments, customer end-user devices, or third-party services not operated or controlled by Rainbird. It also does not cover client-specific configurations, integrations, or data once exported or processed outside the Rainbird platform.
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: Citation ISO Certification Limited.
• ISO 9001 accreditation date: Monday 2 November 2015
• What the ISO 9001 doesn’t cover: The ISO/IEC 27001 certification applies to the information security management system governing the development, operation, and support of the Rainbird platform within Rainbird-controlled environments.; ; The certification does not extend to customer-managed environments, customer end-user devices, or third-party services not operated or controlled by Rainbird. It also does not cover client-specific configurations, integrations, or data once exported or processed outside the Rainbird platform.
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: No
• Cyber Essentials Alternative: In relation to the services you do not have a current and valid Cyber Essentials certificate which has been awarded by one of the government approved Cyber Essentials accreditation bodies but you are working towards gaining it, and will be in a position to confirm that you have been awarded a current and valid Cyber Essentials certificate by one of the government approved accreditation bodies within 12 months of the date of award.
• Cyber essentials plus: No
• Cyber Essentials Alternative: In relation to the services you do not have a current and valid Cyber Essentials Plus certificate which has been awarded by one of the government approved Cyber Essentials accreditation bodies but you are working towards gaining it, and will be in a position to confirm that you have been awarded a current and valid Cyber Essentials Plus certificate by one of the government approved accreditation bodies within 12 months of the date of award.
• Other security certifications: No

Social value

• Section B - Commitment for Future: Delivery:

  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 1: Fair work: That offers fair wages and good working conditions. Help people get a job, stay in work, and progress in their careers, with good employment opportunities across the country. Notes: Where there is a large proportion of labour costs in the contract, commercial teams should consider MAC in Outcome 1 as a priority

    • New or retained jobs on the contract workforce in the relevant area that meet the criteria set out in MAC 1b, 1c and 1d
    • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
    • Plans to engage the contract workforce in deciding the most important workplace issues to address
    • Ensuring new workers are informed of their right to join a trade union
    • Monitoring of employee engagement rates (by protected characteristic) and, where necessary, the development of actions to ensure all voices are heard across the diversity of the workforce
    • Employment contracts that reflect actual hours worked; steps taken to ensure employees understand their contracts and have the ability to review and adjust them if actual hours regularly exceed contracted hours
    • Activities that support an environment where staff are educated about, and feel empowered to, address their physical wellbeing
    • Activities that support an environment where staff are educated about and feel empowered to report and address bullying and harassment
    • Activities to cascade good practice on fair working conditions throughout the supply chain
    • Offer a pay and leave entitlement to all eligible staff who become kinship carers, ideally equivalent to statutory adoption pay and leave
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • Monitoring and reporting of gender and ethnicity pay gaps and plans to address them where necessary
    • Entitlement to sick pay for the contract workforce, with provision in place for any staff who do not meet the earnings threshold for statutory sick pay, payment of sick pay from day one of absence and payment of staff on the contract workforce who are off sick a replacement income of 100% of their usual earnings for as long as possible
    • Plans for an appropriate income replacement policy for staff who are required to spend time away from work to care for a sick dependent or close relative
    • Understanding of in-work progression issues affecting the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
    • Measures to support in-work progression to help people in the contract workforce, to move into higher paid work by developing new skills relevant to the contract
    • Support for the contract workforce by providing career advice, and providing opportunities for staff working on the contract with in-work progression career development into known skills shortages or high growth areas
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Volunteering opportunities for staff
    • Understanding of the modern slavery risks and issues affecting the market, industry, sector or country (of origin or of source) relevant to the contract, and the workforce in the supplier’s own organisation and those of its key subcontractors
    • Measures to identify, mitigate and manage modern slavery risks relating to the contract and how these will be implemented
    • Outline policies and practices to be applied to or put in place for the contract to mitigate and manage modern slavery risks, including: Pre-employment checks, recruitment practices. Workplace conditions, safeguarding plans and processes in place and regular monitoring with relevant groups considered, which may include sampling
    • How these flow down the supply chain and are monitored Illustrative examples include reporting, site visits, audits, etc.
    • How to ensure business decisions re: price/cost, short lead times, payment timescales do not create modern slavery risks in the supply chain
    • How the supplier will work with NGOs, trade unions or other businesses to address modern slavery risk
    • Means of influencing staff, suppliers, customers, communities and/or any other appropriate stakeholders with respect to modern slavery risks relating to the contract

  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 2: Skills for growth: Supporting growth sectors and addressing skills gaps.

    • Understanding of employment and relevant skills issues, and of the education and training issues relating to the contract. Illustrative examples: demographics, skills shortages, new opportunities in high growth sectors, geographic/local community and skills/employment challenges
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Activities to support relevant sector related skills growth and sustainability in the contract workforce. Illustrative examples: careers talks, curriculum support, literacy support, safety talks and volunteering

  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 3: Resilient, innovative and flexible supply chains: Support economic growth through enabling resilient businesses, opportunities for small businesses and voluntary, community and social enterprises

    • Understanding of the types of businesses in the market and the level of participation by new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Ensuring accessibility to contracting and subcontracting opportunities for disabled business owners and employees
    • Structuring of the supply chain selection process to ensure fairness (e.g. anti-corruption) and encourages participation by a diverse range of businesses, including with regard to new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutual
    • Understanding of local demographics, needs and opportunities for the co-design of the goods, services and works to be delivered under the contract
    • Plans for positive actions with community groups.
    • Plans to respond flexibly and adapt approaches to community engagement and initiatives

  • Mission: Make Britain a clean energy superpower: To cut bills, create jobs and deliver security with cheaper, zero-carbon electricity by 2030, accelerating to net zero

    Policy Outcome 4: Sustainable procurement practices: Reducing carbon footprints, minimising waste, and promoting the use of clean energy and green technologies.

    • Understanding of opportunities for additional environmental benefits delivery in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Delivery of additional environmental benefits through the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Understanding of how to influence staff, suppliers, customers, communities and/or any other appropriate stakeholders through the delivery of the contract to support climate and nature protection and improvement

  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 6: Employment and training: For those who face barriers to employment

    • Understanding of employment and skills issues, and of the skills and employment shortages of high growth sectors relating to the contract
    • Understanding of the issues affecting the representation of disabled people in the workforce in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
    • Collection of the views and expertise of disabled people and their representative organisations on successfully supporting disabled employees or applicants
    • Inclusive and accessible recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
    • Understanding of the issues affecting inequality in employment, skills and pay in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors. Measures to tackle inequality in employment, skills and pay in the contract workforce
    • Inclusive and accessible development practices, including guidance for line managers on recruiting, managing and developing people with a disability or health condition

  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 7: Creating a pipeline of opportunities: For the contract workforce, reducing barriers to entry for under-represented groups.

    • Understanding of the issues affecting the development of new skills by target cohort
    • Understanding of the underlying factors affecting improvements to reduce barriers to entry and training schemes for the target cohort(s) related to the contract workforce
    • Understanding of issues relating to entering the contract workforce
    • Creation of outreach activities to create a pipeline of employees for the future contract delivery

  • Mission: Build an NHS fit for the future: That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.

    Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.

    • Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
    • Understanding barriers to access to health and social care services or employment opportunities e.g. digital inclusion
    • Inclusive and accessible recruitment practices, development practices and retention policies that support-focused activities including those provided in the Guide for line managers on recruiting, managing and developing which support people with a disability or health condition
    • Actions to invest in the physical and mental health and wellbeing of the contract workforce

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at james.duez@rainbird.ai. Tell them what format you need. It will help if you say what assistive technology you use.