BLUEFORT SECURITY LIMITED

OPSWAT Metadefender Cloud, Sandbox, ICAP Cloud, CloudStorage, Salesforce with BlueFort Evolve

Optionally delivered by BlueFort Evolve services for deployment and ongoing management, OPSWAT MetaDefender provides advanced malware prevention for ICAP, cloud storage and sandbox environments, using multi-scanning, deep file inspection and data sanitisation to detect and block known and unknown threats before they enter enterprise systems.

Features

• ICAP-based malware scanning for network gateways
• Multi-engine antivirus file inspection
• Deep file type detection and validation
• Cloud storage malware scanning (S3, Azure, GCS)
• Sensitive data detection and DLP checks
• File sanitization and content disarm reconstruction (CDR)
• Advanced sandbox detonation and behavior analysis
• Zero-day threat detection using dynamic analysis
• API-driven integration for cloud and on-prem workflows
• Centralized policy enforcement and reporting

Benefits

• Prevents malware before files reach critical systems
• Reduces zero-day risk with layered detection
• Secures data moving across cloud environments
• Simplifies compliance with automated file inspection
• Protects users without disrupting business workflows
• Improves threat visibility across file transfers
• Minimises attack surface from untrusted files
• Enables consistent security across hybrid environments
• Accelerates incident response with detailed file intelligence
• Lowers operational risk through centralized security controls

• 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 accounts@bluefort.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

437746415552733

Contact

Darren Smith
01252 917000
accounts@bluefort.com

About your service

• Service categories:

  Applications

  Production and operations

  • Other operations
• 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: It integrates with existing security infrastructure ( web apps, email gateways, ICAP-enabled devices, APIs) to add advanced file scanning and threat detection capabilities to those systems.; ; MetaDefender can be incorporated into other services’ workflows (APIs or connectors) effectively acting as an add-on enhancement to existing security products or cloud services.
• Cloud deployment model:
  • Public cloud
  • Private cloud
  • Hybrid cloud
• Service constraints: N/a
• System requirements:
  • Only 64-bit operating systems supported
  • Windows Server 2016, 2019, 2022, 2025 (64-bit)
  • CPU: 4–32+ cores (more cores for higher throughput)
  • RAM: 4–32+ GB depending on load
  • Disk: 10–120+ GB base,
  • SSD recommended for performance

User support

• Email or online ticketing support: Yes
• Support response times: Response times are based on severity level and support plan level. they range from 1 hour to 1 business day.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: EN 301 549
• Phone support: Yes
• Phone support availability: 24 hours, 7 days a week
• Web chat support: Yes
• Web chat support availability: 24 hours, 7 days a week
• Web chat support accessibility standard: EN 301 549
• Web chat accessibility testing: N/a
• Onsite support: No
• Support levels: Silver - 12 x 5 support with 4 hours to 1 day response level; Gold - 24 x 7 support with 2 to 8 business hours response level; Platinum - 24x x7 support with 1 to 4 business hours response level; ; depending on severity level.
• Support available to third parties: Yes
• AI chatbot: Yes

Onboarding and offboarding

• Getting started: OPSWAT’s customer onboarding process is structured to ensure smooth deployment and effective use of its MetaDefender products. It begins with a discovery and needs assessment, where OPSWAT solutions teams gather information about the customer’s environment, file workflows, threat landscape, and compliance requirements. Next, licenses and access credentials are provisioned for the chosen products, whether on-premises (MetaDefender Core, Storage Security) or cloud-based (MetaDefender Cloud).; ; During installation OPSWAT or its partners assist in setting up servers, virtual machines, or cloud tenants. Configuration follows, with security policies, scan engines, file handling rules, user roles, alerts, and reporting tailored to the customer’s requirements. OPSWAT integrates its services into existing infrastructure via APIs, ICAP, and pre-built connectors, linking email systems, web gateways, cloud storage, and CI/CD pipelines.; ; Before full rollout, testing and validation ensure that scanning, sanitization, and policy enforcement function as expected. Administrators receive training and documentation to manage the system effectively. Support channels are activated, and the system goes live, with dashboards and alerts closely monitored. OPSWAT also offers ongoing optimisation, periodically reviewing policies, tuning performance, and recommending improvements to maintain security effectiveness and compliance.; ; This structured approach ensures customers can deploy, integrate, and manage OPSWAT security solutions efficiently while maximising against threats.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: When an OPSWAT service reaches the end of its lifecycle, whether a cloud subscription or an on-premises deployment, customers retain full control over their data. For MetaDefender Cloud, users can export all scan results, threat reports, and audit logs directly through the web portal or programmatically via the RESTful APIs. Data can be downloaded in standard formats such as JSON, CSV, or PDF, ensuring compatibility with internal systems and regulatory requirements.; ; For MetaDefender Core or Storage Security deployed on-premises or in private clouds, all files, scan results, policy configurations, and logs reside on local servers or storage. Administrators can extract this data directly from the system or databases, including quarantined or processed files, before decommissioning. This ensures continuity of records, audit compliance, and migration to alternative systems.; ; OPSWAT also supports automated data extraction for high-volume environments using APIs to pull metadata, scanning results, and threat intelligence, enabling integration with SIEM, compliance, or archival platforms.
• End-of-contract process: At the end of an OPSWAT service contract, whether for cloud or on-premises deployments, customers are supported to ensure a smooth transition and continuity of operations. For cloud services such as MetaDefender Cloud, all historical scan results, threat reports, and audit logs can be downloaded directly from the web portal or extracted via RESTful APIs. Data is provided in standard formats such as JSON, CSV, or PDF, enabling integration with internal systems, compliance reporting, or archival. For on-premises products like MetaDefender Core or Storage Security, administrators can extract files, policy configurations, logs, and quarantined items directly from servers or databases. OPSWAT provides guidance and support throughout the process to ensure secure, complete, and usable data retrieval. Once extraction is complete, active services are deactivated, and licenses are either renewed or terminated according to the agreement.; ; The contract price typically includes access to the licensed OPSWAT products or cloud services, standard support channels, regular updates, and security patches. Additional costs may apply for extra storage, high-volume API usage, custom integrations, extended training, or optional modules not covered by the base license. This ensures transparency and flexibility for organizations managing their security deployments.
• Documentation accessibility standard: EN 301 549

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
• Application to install: Yes
• Compatible operating systems:
  • Linux or Unix
  • Windows
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: Desktop/server versions are full-featured and installed locally — can scan, sanitize, and enforce policies directly.; ; Mobile support is mainly indirect — OPSWAT secures mobile workflows through cloud scanning and compliance checks rather than scanning the device itself.; ; Advanced features like multi-engine scanning, sandboxing, and file sanitization are not native on mobile.
• Service interface: Yes
• User support accessibility: EN 301 549
• Description of service interface: WAT provides multiple service interfaces to manage and integrate its security products. Users access a web-based GUI for configuration, monitoring, and reporting. RESTful APIs enable programmatic file scanning, policy management, and cloud or application integration. The ICAP interface allows transparent scanning for email gateways and web proxies. Additionally, plugins, connectors, and SDKs extend functionality to CI/CD pipelines, cloud storage, and enterprise apps. Command-line tools support automated workflows. Together, these interfaces let OPSWAT operate as a flexible, integrated security platform across desktops, servers, cloud environments, and mobile workflows.
• Accessibility standards: EN 301 549
• Accessibility testing: N/a
• API: Yes
• What users can and can't do using the API: The MetaDefender API lets users automate file security and integrate scanning into workflows. It supports malware scanning, hash and URL checks, file sanitization (CDR), sandbox analysis, and policy management. Users can connect MetaDefender to cloud storage, email, web apps, CI/CD pipelines, and custom applications without using the GUI.
• API documentation: Yes
• API documentation formats: Open API (also known as Swagger)
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Users can customize OPSWAT MetaDefender to match their organization’s security needs. They can define policies and rules for file types, threat actions, and content disarmament. Multi-engine selection allows choosing which antivirus or sandbox engines to use and adjusting scan depth. Workflows and integrations can be tailored via APIs, ICAP, or cloud connectors for automated scanning in email, cloud storage, or CI/CD pipelines. Reporting and alerts are configurable, and sandbox profiles can be customized for analysis depth and runtime behavior. Users can manage roles, permissions, storage allocation, and system resources, ensuring flexible, policy-driven security across environments.

Scaling

• Independence of resources: Multi-tenant isolation: Each customer’s resources are allocated separately to prevent interference.; ; Load balancing: Requests are distributed across multiple processing nodes for consistent performance.; ; Dynamic scaling: Infrastructure scales automatically to handle spikes in demand.; ; Rate limiting & quotas: API calls and service usage are capped per customer to avoid overconsumption.; ; Dedicated deployments: On-premises or private cloud installations give exclusive resources to an organization.; ; Continuous monitoring: System load and performance are tracked to proactively address potential bottlenecks.; ; This ensures consistent service for all users regardless of others’ activity.

Analytics

• Service usage metrics: Yes
• Metrics types: OPSWAT provides detailed service usage information to help organizations monitor activity, manage licenses, and ensure compliance. Web portal dashboards display scanning activity, policy enforcement, API calls, and file processing statistics, often visualized with graphs and tables. Users can generate exportable reports in PDF or CSV formats for auditing or operational review. RESTful APIs allow programmatic access to usage metrics, enabling integration with SIEMs or internal reporting systems. Administrators can also track license consumption, storage usage, and API quotas, ensuring operations remain within contractual limits. These tools give organizations full visibility into MetaDefender usage and performance.
• Reporting types:
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: Yes
• FOCUS resource tagging: No

Resellers

• Supplier type: Reseller providing extra features and support
• Organisation whose services are being resold: Opswat

Staff security

• Staff security clearance: Other security clearance
• Government security clearance: Developed Vetting (DV)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations: European Economic Area (EEA)
• User control over data storage and processing locations: No
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 4.0)
• Penetration testing frequency: Less than once a year
• Penetration testing approach: Another external penetration testing organisation
• Protecting data at rest: Encryption of all physical media
• Data sanitisation process: Yes
• Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001
• Data sanitisation type:
  • Deleted data can’t be directly accessed / Cryptographic Erasure
  • Data Erasure
  • Physical Destruction / Hardware containing data is completely destroyed

Data importing and exporting

• Data export approach: MetaDefender Cloud processes files for security inspection and does not store customer content beyond processing. As a result, there is no customer data to extract when the contract ends.
• Data export formats: CSV
• Data import formats: CSV

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: Availability and Service Levels; ; OPSWAT’s cloud services are designed for high availability, using resilient, redundant infrastructure, load balancing, and continuous monitoring to minimise service disruption. Availability is measured on a monthly basis, excluding planned maintenance and events outside OPSWAT’s reasonable control.; ; OPSWAT provides Service Level Agreements (SLAs) for availability as part of its G-Cloud service offering. The SLA defines a minimum monthly uptime commitment, which is detailed in the service agreement. Planned maintenance is scheduled to minimise impact and, where possible, communicated to customers in advance.; ; If OPSWAT fails to meet the agreed availability level in a given month, customers may be entitled to service credits, calculated as a proportion of the monthly service charge. Service credits are applied to future invoices and represent the customer’s sole remedy for failure to meet the availability SLA, in line with standard G-Cloud terms.; ; For customers requiring greater control over availability, OPSWAT also supports on-premises or private cloud deployments, allowing organisations to manage resilience and uptime within their own environments.; ; Full SLA details, exclusions, and credit calculations are defined in the customer contract.
• Approach to resilience: OPSWAT’s services are designed with resilience as a core principle to ensure reliable operation, continuity of service, and protection against failure. Cloud-based services are built on redundant, highly available infrastructure, with no single point of failure. Traffic is distributed using load balancing, allowing the platform to continue operating even if individual components become unavailable.; ; The service supports horizontal scaling, enabling additional processing capacity to be added automatically to handle increases in demand or unexpected spikes in activity without service degradation. Critical components are continuously monitored, and automated health checks allow issues to be detected and addressed quickly.; ; Data is protected through regular backups, secure storage, and controlled access, reducing the risk of data loss. Planned maintenance activities are carefully managed and scheduled to minimise disruption, with advance notice provided where possible.; ; For customers with enhanced resilience requirements, OPSWAT offers on-premises and private cloud deployment options, enabling organisations to design high-availability architectures tailored to their own environments. OPSWAT also supports integration with existing disaster recovery and business continuity plans.; ; Together, these measures ensure OPSWAT’s services remain available, performant, and secure, even in the face of infrastructure failures, high demand, or maintenance activities.
• Outage reporting: OPSWAT reports service outages and service status using multiple communication channels to ensure customers are informed promptly and transparently.; ; OPSWAT provides a public service status dashboard that displays the current operational status of cloud services and highlights any active incidents or scheduled maintenance. This allows users to independently check service availability at any time.; ; In the event of an outage or service degradation, OPSWAT issues email notifications to registered customer contacts. These alerts include information on the nature of the incident, affected services, and progress updates until resolution.; ; For operational monitoring and integration purposes, service and usage information can be accessed via APIs, allowing customers to monitor activity and integrate service data into internal monitoring or reporting systems. While real-time outage notifications are primarily communicated via the status dashboard and email alerts, APIs can be used to support automated health checks and operational oversight.; ; Together, the public dashboard, email communications, and programmatic monitoring options ensure customers have timely visibility into outages, maintenance events, and service status.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
• Access restrictions in management interfaces and support channels: OPSWAT authenticates users through secure account based access and API keys for MetaDefender Cloud. Access is controlled using role based permissions and protected management interfaces, as described on opswat.com.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Identity federation with existing provider (for example Google Apps)
  • Username or password

Audit information for users

• Access to user activity audit information: No audit information available
• Access to supplier activity audit information: No audit information available
• How long system logs are stored for: User-defined

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: OPSWAT operates a comprehensive set of information security policies and processes governed by a formal Information Security Management System (ISMS) aligned with ISO/IEC 27001. These policies define how information is protected across people, processes, and technology.; ; Core policies cover access control, data protection, encryption, asset management, risk management, incident response, vulnerability management, business continuity, and secure system development. Access to systems and data is restricted using role-based access controls, least-privilege principles, and multi-factor authentication where appropriate.; ; OPSWAT conducts regular risk assessments, internal audits, and independent third-party security assessments to validate the effectiveness of controls. Security incidents are managed through documented incident response procedures, including investigation, remediation, and customer communication where required.; ; Security awareness is supported through employee screening, mandatory training, and ongoing policy enforcement. Changes to systems and services follow controlled change management and secure development lifecycle (SDLC) processes to ensure security risks are assessed prior to deployment.; ; These policies and processes are reviewed and updated regularly to reflect evolving threats, regulatory requirements, and industry best practice.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Configuration and change management approach: OPSWAT follows formal configuration and change management processes aligned with ISO/IEC 27001. These include controlled change approval, version management, testing prior to release, audit logging, and documented rollback procedures, as described on opswat.com.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: OPSWAT manages vulnerabilities through continuous monitoring, regular internal and external testing, timely patching, risk based prioritisation, and independent audits, aligned with ISO/IEC 27001 and documented on opswat.com.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: OPSWAT uses continuous protective monitoring to identify potential compromises through logging, alerting, threat intelligence, and security monitoring controls. When a potential compromise is detected, incidents are investigated and contained using defined incident response procedures. Response times are prioritised based on risk and severity, with timely remediation actions taken in line with OPSWAT’s security governance and incident management processes documented on opswat.com.
• 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: OPSWAT follows predefined incident management processes aligned with its security governance framework. Common incident scenarios are documented and handled through established response procedures. Users report incidents via OPSWAT support channels, and incident reports are provided to affected customers as appropriate, including impact, actions taken, and remediation outcomes, in line with OPSWAT’s policies documented on opswat.com.
• Post-quantum cryptography secure: No

Secure development

• Approach to secure software development best practice: Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: Yes
• Description of free trial: OPSWAT provides several free tools: MetaDefender Cloud Community offers online malware scanning for files, URLs, and hashes. MetaDefender Endpoint Free scans USB devices and vulnerabilities for small networks. MetaDefender Access Community assesses endpoint compliance. Additionally, free plugins and extensions support integration with CI/CD tools and browsers, all at no cos
• Link to free trial: https://www.opswat.com/free-tools?deviceId=62ae13ad-dc73-4769-bfd4-236527ee9771&deviceId=62ae13ad-dc73-4769-bfd4-236527ee9771

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

• Less than £250,000: 20%
• Between £250,000 and £500,000: 20%
• Between £500,001 and £1,000,000: 20%
• Between £1,000,001 and £2,500,000: 20%
• Between £2,500,001 and £5,000,000: 20%
• Over £5,000,001: 20%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: URS
• ISO/IEC 27001 accreditation date: Tuesday 23 September 2025
• What the ISO/IEC 27001 doesn’t cover: NA
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: URS
• ISO 9001 accreditation date: Tuesday 26 December 2023
• What the ISO 9001 doesn’t cover: NA
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: No
• Cyber Essentials Alternative: None of the criteria
• Cyber essentials plus: Yes
• Please provide your Cyber Essentials Plus Certificate Number: 93dcd8e1-1939-481b-b4e9-d630ec2d7db1
• 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
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • 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
    • Activities to identify opportunities to open up sub-contracts under the prime contract to a diverse range of businesses, including new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Plans for engaging a diverse range of businesses in engagement activities prior to appointing subcontractors (including activities prior to award of the main contract and during the contract term)
    • Activities that demonstrate a collaborative way to work with a diverse range of businesses as part of the supply chain
    • Advertising of supply chain opportunities openly and to ensure they are accessible to a diverse range of businesses, including advertising all subcontracting opportunities on Contracts Finder
    • 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
    • Methods for engaging with different parts of the community (including the education system and charities representing the community) and how communities come together to inform decisions, strategy and projects to leave a positive legacy for future generations
    • Measures to involve local stakeholders and/or users in design (e.g. in the design of services, systems, products or buildings)
    • Plans for positive actions with community groups.
    • Measures for making facilities used in the delivery of the contract available for community groups, education or training
    • Measures to engage users and communities and build relationships to increase community integration build trust and influence how the contract is delivered
    • Plans to respond flexibly and adapt approaches to community engagement and initiatives
    • Support for community-led initiatives relevant to the contract. Illustrative examples: improving transport links; reducing loneliness; helping with English language proficiency; and facilitating social mixing among people with different backgrounds

  • 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
    • Collaborative ways of working with the supply chain to deliver additional environmental benefits 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
    • Activities to reconnect people with the environment and increase awareness of ways to protect and enhance it

  • 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
    • Creation of employment opportunities particularly for those who face barriers to employment, such as prison leavers, care leavers and/or who are located in deprived areas, and for people in industries with known skills shortages or in high growth sectors
    • Delivery of training schemes and programmes to address any identified skills gaps and under-representation in the workforce for the contract (e.g. prison leavers, care leavers, kinship carers, disabled people)
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach the target cohort
    • 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
    • Introducing transparency to pay and reward processes
    • Offering a range of quality opportunities with routes of progression if appropriate, e.g. T Level industry placements, students supported into higher level apprenticeships.
    • Working conditions which promote an inclusive working environment and promote retention and progression
    • Other measures to provide equality of opportunity for disabled people and those with health conditions into employment, including becoming a Disability Confident employer and inclusion of supported businesses in the contract supply chain
    • 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
    • Other measures to offer development opportunities for the target cohort(s) in 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
    • Content of the outreach activity is designed to suit the target cohort

  • 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 accounts@bluefort.com. Tell them what format you need. It will help if you say what assistive technology you use.