BYTES SOFTWARE SERVICES LIMITED

Microsoft Azure Cloud Services

Azure Backup provides cloud-based backup for Azure VMs, on-premises servers, and workloads. It offers application-consistent backups with flexible retention policies. The service supports various workloads including SQL Server, SAP HANA, and file shares.

Features

• Provides cloud backup for VMs databases and file systems
• Supports application-consistent backups for databases
• Enables instant restore for Azure VM recovery
• Provides flexible retention policies from days to years
• Supports incremental backup to reduce storage costs
• Enables cross-region restore for disaster recovery
• Provides soft delete protection against ransomware
• Supports backup for on-premises servers through MARS agent
• Enables backup policies with scheduling and retention
• Provides centralised monitoring through Backup Center

Benefits

• Provides cloud backup for VMs databases and file systems
• Supports application-consistent backups for databases
• Enables instant restore for Azure VM recovery
• Provides flexible retention policies from days to years
• Supports incremental backup to reduce storage costs
• Enables cross-region restore for disaster recovery
• Provides soft delete protection against ransomware
• Supports backup for on-premises servers through MARS agent
• Enables backup policies with scheduling and retention
• Provides centralised monitoring through Backup Center

• 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 tenders@bytes.co.uk. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

626548799464252

Contact

Richard Read
01372 418 500
tenders@bytes.co.uk

About your service

• Service categories:

  IaaS

  IaaS Storage

  • Object or Bucket
  • Block
  • File

Service scope

• Service constraints: Azure subscription limits and quotas - https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits
• System requirements:
  • Service selection dictates system requirements
  • Consult online pages for details
• Cloud deployment model:
  • Public cloud
  • Private cloud

User support

• Email or online ticketing support: Yes
• Support response times: The Initial Response Time varies with both the support plan and the Business Impact of the request (also known as Severity). For a breakdown of initial response times by several level and business impact, please visit https://azure.microsoft.com/en-us/support/plans/response/; Weekend support availability varies depending on your Azure support plan. For more information, please visit https://azure.microsoft.com/en-us/support/plans
• 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: WCAG 2.2 AA
• Web chat accessibility testing: We test all our services and support functions extensively with our customers and partner before release.
• Onsite support: Yes, at extra cost
• Support levels: Microsoft provides four Azure support plan options which include various levels of technical account management and cloud support engineering.; ; The support options and cost include the following:; - BASIC (included for all Azure customers); - DEVELOPER ; - STANDARD ; - PROFESSIONAL DIRECT; - UNIFIED SUPPORT; ; For more information, visit https://azure.microsoft.com/en-us/support/plans/ and https://www.microsoft.com/en-us/unifiedsupport/overview
• Support available to third parties: Yes
• AI chatbot: Yes

Onboarding and offboarding

• Getting started: Azure users can start by creating an account at azure.microsoft.com and signing into the Azure Portal. New users get $200 credit for 30 days, plus 12 months of free popular services and 55+ always‑free services like Azure Functions and Storage. Starting is free, and users are only charged if they choose to move to pay‑as‑you‑go or exceed free usage limits.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • Other
• Other documentation formats:
  • Markdown (source files in GitHub)
  • JSON (schemas, ARM templates, REST metadata)
  • YAML (Bicep specs, some configuration references)
  • Code‑comment formats generate API docs (XML, JSDoc, JavaDoc, Python docstrings)
• End-of-contract data extraction: Microsoft provides onboarding and offboarding training for Azure services through Microsoft Learn, Azure governance and management learning paths, and official Azure documentation. These resources cover provisioning, securing, managing, and retiring Azure workloads, along with role‑based training for administrators and engineers. Organisations can use these materials to guide users through the full service lifecycle using structured tutorials, best‑practice guidance, and hands‑on labs.
• End-of-contract process: When an Azure contract or subscription ends, Microsoft places the environment into a limited‑function state. Customers retain access to extract their data for approximately 90 days before deletion begins. Microsoft then disables the subscription and permanently deletes customer data no later than 180 days after expiration in accordance with the Online Services Terms and data‑handling policies.
• Documentation accessibility standard: EN 301 549

Using the service

• Web browser interface: Yes
• Using the web interface: The Azure Portal lets users create, configure, and manage cloud resources such as virtual machines, storage accounts, networks, databases, and identity settings. It supports monitoring, cost management, policy enforcement, automation, and role-based access control. Users can customize dashboards, deploy templates, and integrate services visually. However, the portal cannot perform advanced scripting or complex bulk automation—that requires tools like Azure CLI, PowerShell, or ARM/Bicep. Users also cannot directly modify underlying infrastructure, access physical hardware, bypass security controls, or perform tasks outside their assigned permissions. The portal focuses on secure, role‑based, GUI‑driven cloud management.
• Web interface accessibility standard: EN 301 549
• Web interface accessibility testing: We test all our services and support functions extensively with our customers and partner before release
• API: Yes
• What users can and can't do using the API: Azure Resource Manager (ARM) API and Azure PowerShell let users create, modify, delete, and query Azure resources programmatically, just like the Azure Portal. They support automation, RBAC management, policy deployment, templates, and tagging. However, they cannot manipulate the Azure Portal UI, access portal-only preview features, or perform actions outside ARM’s control plane (e.g., interacting with VM guest OS, reading portal dashboards, or executing workloads). Both tools manage Azure resources—not the portal experience itself.
• API automation tools:
  • Ansible
  • Chef
  • OpenStack
  • SaltStack
  • Terraform
  • Puppet
  • Other
• Other API automation tools:
  • Azure Automation
  • Azure PowerShell
  • Azure CLI
  • Azure Logic Apps
  • Azure DevOps
  • Azure Functions
  • ARM Templates / Bicep
  • Pulumi
  • Jenkins
  • Apache Airflow
• API documentation: Yes
• API documentation formats:
  • Open API (also known as Swagger)
  • HTML
  • Other
• Command line interface: Yes
• Command line interface compatibility:
  • Linux or Unix
  • Windows
  • MacOS
• Using the command line interface: Azure CLI lets users create, configure, and manage most Azure resources from any platform using command-line commands and automation scripts. It supports tasks like deploying VMs, managing storage, configuring networks, querying data, and running CI/CD workflows. However, it cannot provide graphical views, visual dashboards, or some advanced features found only in Azure Portal or Azure PowerShell. Some niche services may have limited CLI support.

Scaling

• Independence of resources: Azure limits noisy‑neighbor impact through strict resource isolation and governance. The hypervisor guarantees dedicated CPU and memory slices per VM; platform services enforce per‑tenant quotas and throttling; auto‑scaling and load‑balancing spread load across infrastructure; and continuous monitoring detects and mitigates contention. Combined, these controls ensure one customer’s demand doesn’t degrade another’s performance.
• Usage notifications: Yes
• Usage reporting:
  • Email
  • SMS
  • Other
• Other usage reporting: Voice Call (Phone call); Mobile Push Notification (Azure mobile app); Webhook (HTTP POST); Secure Webhook; Azure Function; Logic App; Azure Automation Runbook; ITSM Integration (ServiceNow, BMC, System Center, etc.); Event Hub; Email to Azure Resource Manager Role
• Optimising consumption: Yes
• Automatic scaling: No

Analytics

• Infrastructure or application metrics: Yes
• Metrics types:
  • CPU
  • Disk
  • HTTP request and response status
  • Memory
  • Network
  • Number of active instances
  • Other
• Other metrics: https://learn.microsoft.com/en-us/azure/azure-monitor/reference/metrics-index
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
• Resource tagging: Yes
• FOCUS resource tagging: Yes

Resellers

• Supplier type: Reseller providing extra support
• Organisation whose services are being resold: Microsoft

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:
  • United Kingdom
  • European Economic Area (EEA)
  • Other locations
• 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: In-house
• Protecting data at rest:
  • Physical access control, complying with CSA CCM v4.0
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
  • Other
• Other data at rest protection approach: Key management via Azure Key Vault; Encryption models such as envelope encryption and customer‑managed keys; Defense‑in‑depth physical and logical protections throughout the datacenter and service stack
• 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
  • Explicit overwriting of storage before reallocation / Secure Erase
  • Degaussing
  • Physical Destruction / Hardware containing data is completely destroyed

Backup and recovery

• What’s backed up:
  • Azure Backup protects Azure VMs
  • SQL Server and SAP HANA in Azure VMs
  • Azure File Shares
  • On‑premises workloads via MARS, MABS, or DPM agents
  • VMware/Hyper‑V environments using MABS/DPM
  • Azure Managed Disks
  • Backups stored in Recovery Services Vaults, handling up-to 2,000 sources
• Backup controls: Users control Azure backups through backup policies, which define the backup schedule, frequency, retention, and backup type. Policies automate when backups run and how long recovery points are kept. Users can also run on‑demand backups for immediate protection. Additionally, Azure Policy can enforce backup requirements across resources to ensure compliance and consistency.
• Datacentre setup: Multiple datacentres with disaster recovery
• Scheduling backups: Users schedule backups through a web interface
• Backup recovery: Users can recover backups themselves, for example through a web interface
• Backup and recovery: Yes
• RPO/RTO: Yes

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection between networks: ExpressRoute private connectivity, keeping traffic off the public internet.; MACsec (IEEE 802.1AE) encryption on ExpressRoute provider edges and across Microsoft’s backbone network.; Double encryption in transit (TLS+MACsec) for defense in depth.; Private Link, giving access to Azure PaaS services via private IPs in your VNet (no public exposure).; Service Endpoints, ensuring traffic to Azure services stays on the Azure backbone rather than the internet.; Internal datacenter-to-datacenter encryption, protecting all Azure east‑west traffic inside the cloud.; Zero Trust network validation, requiring continuous authentication and authorization for all connections.; DDoS protection + Threat detection, preventing interception, tampering, or disruption of in‑transit data.
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection within supplier network: AES-265 encryption at-rest storage, disks, databases.; SSE enabled by default.; Azure Disk Encryption using BitLocker or dm‑crypt.; TDE for SQL and databases.; Key management, HSM protection.; Enforced HTTPS/TLS 1.2+ encryption in-transit.; Private Endpoints.; VPN Gateway encrypted tunnels.; ExpressRoute for private connectivity.; MACsec encryption link-layer protection.; Confidential Computing encrypting in-use data.; VNet segmentation isolate workloads.; NSGs restrict inbound/outbound traffic.; Stateful traffic filtering and application rules.; WAF protection against common exploits.; Zero Trust access, least privilege, continuous verification.; JIT MFA admin access with auditing.; Multitenant isolation logically separates environments.; Continuous monitoring via Microsoft Defender.; Sentinel and Azure Monitor threat detection & analytics.

Availability and resilience

• Guaranteed availability: Azure availability guarantees range from 95% to 99.99%, depending on:; ; Service type; Architecture (single instance vs. zone‑redundant); Storage redundancy configuration; Disk tier; ; The highest standard guarantee commonly offered is 99.99%, achieved when deploying VMs across multiple availability zones.
• Approach to resilience: Azure is designed to be resilient through distributed regions, Availability Zones, and redundant infrastructure, enabling workloads to withstand hardware, network, and datacenter failures. It incorporates fault isolation, multi‑region replication, and resilience-focused architectural patterns to maintain availability during disruptions. Azure’s Well‑Architected Framework emphasizes designing for resilience, recovery, and continuous operation so applications can detect, withstand, and recover from faults.
• Outage reporting: Azure reports outages through the public Azure Status page for broad, platform-wide incidents, providing a global view of service health. For personalized, subscription-specific issues, Azure Service Health delivers real-time notifications about service incidents, planned maintenance, and advisories via email, SMS, push notifications, or webhooks. Azure Service Health also shows impacted resources and updates until resolution.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Other
• Other user authentication: Azure authenticates users through Microsoft Entra ID. When a user accesses the service, they are redirected to Entra ID, which verifies identity using methods such as passwordless sign‑in, MFA, certificates, or federated identity providers. Conditional Access policies may enforce requirements like MFA. Once authenticated, Entra ID issues a signed token, which the service validates before granting access based on the user’s permissions.
• Access restrictions in management interfaces and support channels: We restrict access to management interfaces and support channels using role‑based access control, ensuring only authorized personnel can perform administrative actions. Multi‑factor authentication, passwordless sign‑in, and Conditional Access policies enforce strong identity verification. Administrative endpoints are protected with network restrictions, logging, and continuous monitoring. Support channels require verified identity, limited privileged access, and follow least‑privilege and just‑in‑time access principles to minimize exposure.
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Username or password
• Devices users manage the service through: Directly from any device which may also be used for normal business (for example web browsing or viewing external email)

Audit information for users

• Access to user activity audit information: You control when users can access audit information
• How long user audit data is stored for: User-defined
• Access to supplier activity audit information: Users have access to real-time audit information
• How long supplier audit data is stored for: User-defined
• 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:
  • CSA CSM version 4.0
  • ISO/IEC 27001
  • Other
• Other security governance standards: ISO 27001 (Information Security Management); ISO 27701 (Privacy Information Management); ISO 27018 (Protection of Personally Identifiable Information in the cloud); FedRAMP (U.S. government cloud security); DoD IL5 (U.S. Department of Defense cloud requirements); HIPAA / HITRUST (Healthcare data protection); PCI DSS (Payment card data security); GDPR compliance mechanisms
• Information security policies and processes: ISO/IEC 27001 Information Security Management System (ISMS); ISO/IEC 27002 Security Controls; ISO/IEC 27018 (protection of personal data in the cloud); ISO/IEC 27701 (privacy information management); SOC 1, SOC 2, SOC 3 audited controls; NIST SP 800‑53 security and privacy controls; NIST Cybersecurity Framework (CSF) alignment; FedRAMP security assessment and continuous monitoring; PCI DSS processes for cardholder data protection; GDPR-compliant privacy and data protection processes; Azure Security Development Lifecycle (SDL); Azure Policy governance and compliance enforcement; Continuous monitoring, logging, and threat intelligence processes

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: Azure uses automated, auditable change management built on Azure Resource Manager. Changes are tracked through services like Microsoft. Change Analysis, which records what changed, when, and by whom to detect configuration drift and support rapid incident resolution. Azure DevOps adds structured processes for identifying, reviewing, approving, and tracking changes using Agile best practices to minimise risk and ensure clear documentation and governance.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: We maintain a continuous vulnerability‑management program that includes automated scanning, threat intelligence monitoring, and rigorous patch management. Identified vulnerabilities are assessed, prioritised by severity and business impact, and remediated within defined SLAs. Our process includes regular penetration testing, configuration baseline reviews, and monitoring for zero‑day threats. Remediation activities are tracked to completion, with verification to ensure fixes are effective. We follow secure‑engineering practices, maintain incident‑response integration, and undergo independent audits aligned with recognised standards to validate the effectiveness of our controls.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: Azure protective monitoring involves continuously collecting, analysing, and correlating security signals across the cloud environment. It uses services like Azure Monitor, Defender for Cloud, Sentinel, and Activity Logs to detect anomalies, policy violations, and potential threats. Automated analytics identify suspicious behaviour, trigger alerts, and support incident response. Data is retained for auditing, investigation, and compliance, ensuring proactive detection and rapid mitigation of security risks.
• 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: Azure’s incident management process follows a structured lifecycle. Azure continuously monitors services to detect outages or security issues, then prioritises and analyses incidents to determine impact. Microsoft’s incident response teams isolate affected components, mitigate the issue, and restore normal operations. Throughout the event, Azure provides customer communications through the Service Health Dashboard. After resolution, Microsoft conducts post‑incident reviews to improve processes, strengthen detection, and prevent recurrence.
• 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)

Separation between users

• Virtualisation technology used to keep applications and users sharing the same infrastructure apart: Yes
• Who implements virtualisation: Supplier
• Virtualisation technologies used: Other
• Other virtualisation technology used: Microsoft Hyper‑V; Hyper‑V–isolated Containers (micro‑VMs); Kata Containers (sandboxed containers); AMD SEV‑SNP (Confidential VM memory encryption & integrity); Intel TDX (Hardware‑based Confidential VM isolation); Intel SGX (Enclave‑based secure execution); Azure Software‑Defined Networking (SDN); Virtual Networks (VNet) & virtual switches; Virtual NICs; Virtualized disks (Azure VHD / managed disks); Virtual TPMs (vTPMs); Linux kernel namespaces & cgroups (container process isolation)
• How shared infrastructure is kept separate: Azure keeps organisations separate through multilayered isolation: hardware‑level protections prevent one VM accessing another’s memory; the Hyper‑V hypervisor enforces strict compute separation; software‑defined networking isolates traffic using VNets and firewalls; storage accounts and disks are logically and cryptographically segregated; and Azure Entra ID provides identity‑level boundaries. The Azure control plane validates every action against each tenant’s permissions, and Microsoft uses just‑in‑time, audited access to prevent cross‑tenant exposure.

Energy efficiency

• Energy-efficient datacentres: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: Yes
• Description of free trial: Azure users can create an account at azure.microsoft.com and sign into the Azure Portal. New users get $200 credit for 30 days, 12 months of free popular services, and 55+ always‑free services. Starting is free, and users are only charged if they move to pay‑as‑you‑go or exceed free usage limits
• Link to free trial: https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account

Discount

• Provide your minimum discount applicable to your baseline prices: 0%

Formula for calculating price of your services

• Formula for calculating price of your services:

  Which of the core deployment models you intend to offer

  Public Cloud

  Public Cloud - Formula for calculating price of your services

  ---

  Total Cost

  The Total Cost for a buyer's call off requirement in a Public Cloud Deployment

  =

  Baseline Pricing

  Azure Calculator

  Baseline Pricing - Web link

  https://azure.microsoft.com/en-gb/pricing/calculator/

  -

  Minimum Discounting

  0%

  +

  Onboarding Activity

  Onboarding costs may vary based on your specific requirements, please confirm with suppliers during the clarification process

  +

  Additional sources of cost

  N/A

  -

  Additional sources of cost reduction

  N/A

  ---

• Total Cost: The Total Cost for a buyer's call off requirement in a Public Cloud Deployment
• Baseline Pricing: Azure Calculator
• Baseline Pricing - Web link: https://azure.microsoft.com/en-gb/pricing/calculator/
• Minimum Discounting: 0%
• Onboarding Activity: Onboarding costs may vary based on your specific requirements, please confirm with suppliers during the clarification process
• Additional sources of cost: N/A
• Additional sources of cost reduction: N/A

Mandatory certifications

• Mandatory certifications:

  Are you are bidding to offer IaaS and/or PaaS as a reseller or are you in sole control of the infrastructure

  Reseller

  Cloud service suppliers you intend to resell with evidence

  Organisation 1

  Organisation name

  Microsoft

  Website address/upload for organisation

  Upload

  Upload

  Provided

  Organisation 2

  Organisation name

  Amazon AWS

  Website address/upload for organisation

  Website address

  Website address

  https://partners.amazonaws.com/partners/001E0000011c6LiIAI/Bytes

  ISO 9001 certification

  Provided

  ISO 27001 certification

  Provided

  ISO 20000-1 certification

  Provided

  Are you reliant on the Cloud Service Provider for some accreditations

  Yes

Cyber Essentials

• Do you have a Cyber Essentials Plus certificate?: Yes
• Cyber Essentials Plus certificate Number: 21e94cf4-cda7-4d3a-8343-71e6363aef69

Non-mandatory Standards and certifications

• ISO 28000:2022 certification: No
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: Yes
• Who accredited the PCI DSS certification: SecurityMetrics
• PCI DSS accreditation date: Wednesday 5 March 2025
• What the PCI DSS doesn’t cover: N/A
• Other security certifications: Yes
• Any other security certifications: IASME Cyber Assurance L2

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
    • New apprenticeships on the contract workforce in the relevant area that meet the criteria set out in MAC 1b
    • 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
    • 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
    • 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
    • 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 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

  • 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

  • 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

  • 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
    • 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 issues relating to entering the contract workforce

  • 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 tenders@bytes.co.uk. Tell them what format you need. It will help if you say what assistive technology you use.