CLARANET LIMITED

Managed Detection & Response with Level Blue

Claranet Managed Detection & Response with LevelBlue USM Anywhere delivers 24/7 SOC monitoring, human‑led investigation, proactive threat hunting, automated and analyst‑driven response, and forensic/incident support. Using USM Anywhere and Claranet expertise, the service detects, investigates, and responds to threats across on‑premises and cloud environments, providing clear guidance and rapid containment.

Features

• 24/7 SOC monitoring and triage of security events
• Human‑led MDR investigations with analyst escalation
• Proactive threat hunting using correlated telemetry
• Agent‑based response: isolate host, kill process, quarantine
• Network response: block indicators via supported controls
• Forensic capture and investigation support
• Guided / hands‑on incident response assistance
• USM sensors for cloud and on‑prem sources
• Monthly reports and service ticketing via Claranet Online
• Customer read‑only access to USM console

Benefits

• Faster detection and investigation of sophisticated attacks
• Reduced dwell time through rapid containment actions
• Clear analyst guidance during security incidents
• Proactive hunts surface hidden threats earlier
• Automated actions limit lateral movement
• Consolidated visibility across hybrid environments
• Continuous tuning reduces false positives
• Improved audit and reporting outcomes
• Expert forensic support accelerates recovery
• Consistent 24/7 coverage and escalation

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

Framework

G-Cloud 15

Service ID

684543525903706

Contact

Claranet UK Bid Team
020 7685 8000
Uk-bidteam@claranet.com

About your service

• Service categories:

  Applications

  Production and operations

  • Other operations
• Multi cloud support: Yes

Service scope

• Software add-on or extension: Yes
• What software services is the service an extension to: LevelBlue USM Anywhere SIEM platform. Customers receive read‑only USM console access while Claranet manages configuration and operations and overlays an expert 24x7x365 UK-based SOC service.
• Cloud deployment model: Public cloud
• Service constraints: Service depends on successful deployment of USM sensors/connectors and correct log‑source configuration. ; Customers have read‑only console access; Claranet retains configuration rights. ; Onboarding requires completion of technical pre‑requisites (allowlisting, ports, credentials) and may be impacted by delays in customer readiness. Some agent capabilities have platform limitations (for example, Linux agent prerequisites/proxy restrictions). ; Planned maintenance by LevelBlue or Claranet tooling may temporarily affect dashboards or report access. ; Response actions depend on available integrations and customer change controls. ; Connectivity constraints (firewalls/proxies) can disrupt telemetry ingestion. ; Constraints and inclusions are captured in the Statement of Work and onboarding artefacts.
• System requirements:
  • Deploy USM sensor in AWS, Azure, GCP, VMware, Hyper‑V.
  • Configure outbound connectivity and allowlist required LevelBlue ranges/subdomains.
  • Open syslog and management ports per USM sensor prerequisites.
  • Provide admin credentials or API access for in‑scope log sources.
  • Prepare network devices, servers, cloud services for log forwarding.
  • Ensure time synchronisation (NTP) across monitored systems and sensors.
  • Linux agent: 64‑bit OS; proxy unsupported; disable auditd.
  • Grant Claranet SOC access to ticketing/communication channels.
  • Complete Asset Verification and technical pre‑requisites before onboarding.
  • Maintain change control for response integrations and actions.

User support

• Email or online ticketing support: Yes
• Support response times: Claranet operates 24/7 with defined MDR SLAs. Typical targets: triage within 30 minutes for new security incidents; response times of P1 15 minutes, P2 30 minutes, P3 2 hours, P4 4 hours. ; Analysts initiate investigation, hunting and agreed response actions, escalating with clear guidance. Communication uses agreed channels with ticketing via Claranet Online and scheduled reporting. These targets are confirmed per contract/SOW and may be tuned to customer risk and integration model.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: None or don’t know
• Phone support: Yes
• Phone support availability: 24 hours, 7 days a week
• Web chat support: No
• Onsite support: Yes, at extra cost
• Support levels: Standard MDR includes 24/7 monitoring, human‑led investigation, proactive threat hunting, alert tuning, automated/analyst‑driven containment, monthly reporting, and guided incident response. Customers receive read‑only USM console access while Claranet engineers manage configuration and tuning. Tickets and reports are delivered through Claranet Online.; Enhanced support adds extended reporting packs, stakeholder reviews, and service improvement plans. Premium tiers can include dedicated engineering time, bespoke integrations, tabletop exercises, and heightened response playbooks. Pricing is based on data volume/sensors, service tier, and optional add‑ons; USM Anywhere commercial constructs (for example retention tiers) underpin platform costs.; A technical account manager is available on enhanced/premium tiers; cloud/security engineers are available across tiers for onboarding, runbooks, and continuous tuning. Escalation paths and SLAs are documented in the SOW and service description.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Onboarding follows a defined process: scoping, Asset Verification, technical pre‑requisites, sensor deployment, log‑source onboarding, and tuning. Claranet provides pre‑requisite instructions (allowlisting, ports, credentials), runs a delivery kick‑off, and assists with onboarding one of each in‑scope log‑source type before wider rollout. Tuning begins immediately to establish a baseline and reduce false positives.; Customers receive documentation, runbooks, and workshops to familiarise teams with alarm visibility, ticketing via Claranet Online, and incident communication paths. Claranet validates ingestion and health, confirms SLAs, and agrees escalation contacts. The Statement of Work documents inclusions/exclusions and any bespoke integration. Where required, training covers operational processes, reporting, and response playbooks. After the initial period, ongoing optimisation continues as the environment evolves.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: Buyers can export alarms, events, and asset inventories via the console or API to formats consumable by their tooling (for example, CSV/JSON), and request copies of monthly reports and incident summaries issued through Claranet Online. Claranet coordinates a data‑extraction plan during notice, ensuring audit and compliance needs are met. USM data retention and availability for export are governed by the contracted retention tier; additional exports (for example, bulk historical data) may require API‑based retrieval ahead of tenant deactivation. After extraction, sensors and integrations are decommissioned, console access is revoked, and platform data is purged per vendor lifecycle policies. Any Claranet‑held analysis artifacts can be supplied on request. (Where buyers require specific export schemas, these can be addressed in the SOW.)
• End-of-contract process: Included within the contract price: USM tenancy, sensor use, 24/7 monitoring, human‑led investigations, threat hunting, tuning, monthly reporting, and agreed response playbooks. Additional costs may apply for bespoke integrations, extended data retention beyond the contracted tier, custom reporting packs, or extra professional services during offboarding. The SOW and service description define inclusions/exclusions and any time‑and‑materials activities requested by the buyer.; At contract end, Claranet disables SOC monitoring, coordinates data export, and decommissions sensors/integrations. Console access remains available for a limited period to complete extractions, after which access is revoked and data is purged under vendor policy. Any service credits or outstanding reports are finalised. Buyers may renew, transition to another Claranet service, or close the service.
• Documentation accessibility standard: None or don’t know
• How the documentation is accessible: Claranet provides all onboarding and offboarding documentation for the LevelBlue MDR service in accessible, user‑friendly formats and through clearly defined channels. During onboarding, customers receive structured documentation including the Asset Verification Form, Technical Pre‑Requisites, deployment instructions, and any scoping or solution‑design outputs. These documents are provided in standard PDF or DOCX formats to ensure compatibility with common business tools. Documentation is shared through the onboarding process via project communications or uploaded directly into the Claranet Online portal, which acts as the central hub for incident notifications, updates, service messages and MDR artefacts. This portal is explicitly identified in service materials as the customer’s primary point of contact for raising queries and accessing reports or service documentation.; Operational onboarding information—such as log‑source configuration steps, sensor deployment requirements, and technical pre‑requisite guides—is provided directly by the MDR engineering team and reflects details found in onboarding sections of the service description, including Technical Pre‑Requisites, onboarding responsibilities, and service decommission steps.; Offboarding follows the same pattern: Claranet supplies decommissioning instructions, data‑extraction guidance and service closure information through Claranet Online or direct project communication. All documentation remains available in accessible formats, and customers retain access to required offboarding artefacts until the service is fully decommissioned.

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
  • Opera
• Application to install: Yes
• Compatible operating systems: Linux or Unix
• Designed for use on mobile devices: No
• Service interface: Yes
• User support accessibility: None or don’t know
• Description of service interface: The USM Anywhere console presents correlated alarms, asset views, investigations, dashboards, and search across ingested telemetry. Customers can review alarms and evidence while Claranet analysts manage tuning, rules, and response orchestration. Access is read‑only for customers to ensure integrity and consistency of MDR operations. ; The Claranet Online portal provides incident tickets, monthly reports, communications, and escalation. Together, these interfaces give buyers visibility of threats, actions taken, and service performance without exposing sensitive back‑end configuration. Role‑based access, authentication controls, and audit logging are applied.
• Accessibility standards: None or don’t know
• Description of accessibility: The MDR LevelBlue service is accessed through two interfaces. Users receive browser‑based, read‑only access to the USM Anywhere console, where they can view alarms, search collected logs, review reports, and see vulnerability and asset information. They cannot change configurations, alter detection rules, adjust sensors, or execute response actions, as these are fully managed by Claranet. Users also access the Claranet Online portal to receive incident notifications, view and comment on SOC tickets, access monthly reports, and raise support queries. Both interfaces provide visibility and communication, while configuration, tuning, and response remain under Claranet SOC control.
• Accessibility testing: Claranet’s MDR delivery relies on LevelBlue’s web console plus Claranet Online for service communications. Where users employ assistive technologies, Claranet supports reasonable adjustments, including alternative report formats and accessible communications on request. For buyers with formal accessibility requirements, Claranet will coordinate with LevelBlue to review current console accessibility (for example, keyboard navigation, contrast, labels) and provide guidance or workarounds.; During onboarding, Claranet can capture accessibility needs and validate that critical workflows—viewing alarms, accessing reports, receiving notifications—are operable for the buyer’s team. If specific gaps are identified, Claranet will assist with practical mitigations (for example, scheduled emailed reports, alternative dashboards, or API‑driven exports to buyer tooling that already meets their accessibility standards). Evidence of any vendor accessibility testing can be shared on request or appended to the SOW if required.
• API: Yes
• What users can and can't do using the API: The API supports programmatic retrieval of alarms, events, assets, and vulnerability data; management of investigations; and integration with ticketing/SOAR to automate workflows (for example, creating tickets or triggering response actions via supported integrations). Buyers can use the API to export data at scale, build custom dashboards, or integrate with existing monitoring/reporting pipelines.; Service setup steps—such as onboarding assets, validating sensor connectivity, and establishing log‑source ingestion—are typically executed by Claranet. Where appropriate, buyers can use API functions to query ingestion health, list assets, or pull alarm data into internal systems. Changes to MDR‑controlled configuration are performed by Claranet; buyer API actions are limited by read‑only role permissions to preserve service integrity. Rate limits and permission scopes apply per vendor design. These boundaries ensure consistent MDR operation and prevent conflicting configuration. (Formal API specifications can be supplied or referenced in the SOW upon request.)
• API documentation: Yes
• API documentation formats: HTML
• API sandbox or test environment: No
• Customisation available: Yes
• Description of customisation: Customisation focuses on what is monitored and how incidents are handled, while preserving MDR control of underlying configurations. Buyers can request log‑source scope changes, alarm tuning, suppression or enrichment rules, alert routing, playbook preferences (for example, when to isolate or block), and reporting cadence/content. Requests are raised via Claranet Online or change tickets and implemented by Claranet engineers, ensuring consistency and auditability.; Role‑based permissions provide buyers with read‑only visibility, avoiding inadvertent changes that could degrade detections. Where buyers need automation with internal tools, Claranet will assist with API‑driven exports or ticketing integrations documented in the SOW. Tuning is continuous throughout the service to reduce false positives and adapt to environment changes and emerging threats. Constraints and responsibilities are captured in the service description and SOW templates.

Scaling

• Independence of resources: USM Anywhere is a multi‑tenant SaaS platform with logical isolation between tenants and elastically scalable ingestion/processing. Claranet MDR operations are similarly segregated, ensuring one buyer’s event load does not impede another’s service. Workflows, tickets, and runbooks are partitioned per customer, with resource monitoring to maintain performance. Where exceptional demand arises, Claranet adjusts analyst capacity and tuning priorities to preserve SLA adherence. (Platform multi‑tenancy and operational segregation are described in service materials and SOWs.)

Analytics

• Service usage metrics: Yes
• Metrics types: Metrics include alarm volumes, incident counts/severity, mean time to triage/response, false‑positive reductions, top use cases, tuned rules, log‑source coverage, and sensor health. Reporting summarises analyst actions, containment steps, and threat‑hunting outcomes. Over time, trend analysis evidences risk reduction and environment changes. Reports are delivered via Claranet Online and can be augmented with customer‑specific views by agreement.
• Reporting types: Regular reports
• 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: Security Clearance (SC)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations: United Kingdom
• 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: At least once a year
• Penetration testing approach: In-house
• Protecting data at rest:
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • 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
  • Explicit overwriting of storage before reallocation / Secure Erase

Data importing and exporting

• Data export approach: Data can be exported via the console (on‑demand reports, searches) or API for scale/automation. Common outputs include CSV/JSON for alarms, events, assets, and vulnerabilities; monthly reports are available through Claranet Online. Where SIEM/ticketing integrations exist, buyers may already receive continuous data synchronisation into their systems. Claranet can assist to script API extractions before termination to meet compliance timelines aligned to the retention tier contracted with USM Anywhere.
• Data export formats:
  • CSV
  • Other
• Other data export formats: JSON
• Data import formats:
  • CSV
  • Other
• Other data import formats: JSON

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
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • Other
• Other protection within supplier network: Segregation of customer data in multi‑tenant SaaS

Availability and resilience

• Guaranteed availability: USM Anywhere is designed for high availability as a SaaS platform, with distributed processing and resilient ingestion. Claranet’s SOC operates 24/7 to maintain MDR continuity. Availability aligns to vendor SLA; if the platform’s uptime falls below guaranteed thresholds, service credits are handled per contract. Major incidents trigger customer notifications, regular updates, and post‑incident summaries. Claranet maintains alternative monitoring pathways (for example, direct ticketing/communications and runbooks) to preserve operational response during console disruptions and synchronises data once service stabilises.; The MDR SOW/service description define service scope, responsibilities, and exclusions (for example, force majeure, third‑party failures outside Claranet control). Buyers receive clear guidance on impact and remediation steps during outages, with escalation paths documented.
• Approach to resilience: USM Anywhere’s SaaS architecture uses distributed components and elastic scaling to handle ingestion spikes and regional issues. Telemetry is processed across resilient pipelines to minimise single points of failure. Claranet SOC operations are resilient via redundant tooling, mirrored alerting channels, and geographically distributed analyst coverage. Playbooks and escalations function independently of a single console session, with alternative communications if needed.; Further architectural details and vendor redundancy patterns can be shared under NDA or referenced from vendor attestation documents. Claranet provides resilience information in onboarding packs and can conduct tabletop exercises to validate failover procedures for the buyer’s context.
• Outage reporting: Platform incidents are communicated through vendor status channels and in‑platform notifications; customers can subscribe for updates. Claranet monitors vendor announcements and promptly informs buyers via Claranet Online tickets/emails, providing context, impact, and workarounds. For Claranet tooling incidents, buyers are notified through agreed channels with periodic updates until resolution. Post‑incident reports summarise cause, impact, and improvements.; Where required, Claranet can expose API‑based status feeds or integrate with buyer monitoring systems for consolidated views. Incident communications and escalation contacts are confirmed during onboarding and documented in the SOW.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Dedicated link (for example VPN)
  • Username or password
• Access restrictions in management interfaces and support channels: Access uses RBAC and MFA with least‑privilege assignment. Administrative roles are tightly controlled and monitored; sensitive actions require elevated permissions. Support interactions require authentication and verified contacts before sharing incident details. Network access to administrative paths can be constrained (for example, IP allowlisting/VPN). All activity is logged for audit, and periodic access reviews are conducted.
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Dedicated link (for example VPN)
  • Username or password

Audit information for users

• Access to user activity audit information: Users have access to real-time 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
• Information security policies and processes: Claranet operates an information security management system aligned to recognised standards (for example, ISO/IEC 27001), covering access control, data protection, logging, incident handling, vulnerability and change management, and supplier governance. Governance assigns clear roles and reporting lines; policies are reviewed periodically and on material change. Compliance is enforced via audits, technical controls, and mandatory security training. Deviations or issues follow the incident/problem processes with leadership oversight. (Organisation‑wide policies and certifications can be provided to buyers on request.); For MDR delivery, segregation of duties, RBAC, MFA, and audit logging are enforced across operational systems. Customer‑specific controls are captured in the SOW and onboarding artefacts.
• 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: All MDR components are inventoried and tracked through their lifecycle. Changes are assessed for security impact, tested, scheduled, and approved before deployment. High‑risk changes align to maintenance windows and include rollback plans. Configuration baselines and version control preserve consistency; monitoring detects unauthorised modification. All changes are recorded and periodically reviewed against policy and the SOW.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: Claranet tracks vendor advisories, intelligence feeds, and industry sources to identify relevant vulnerabilities. Potential threats to MDR tooling are triaged and remediated based on severity; critical patches are prioritised for rapid deployment. Automated scanning and manual review verify remediation. Indicators of exploitation are monitored in SOC operations, with escalation as needed. Where buyer assets exhibit vulnerabilities visible in MDR telemetry, Claranet provides recommendations and supports remediation planning.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: Claranet applies SIEM analytics, correlation, and behavioural detections to identify potential compromise, with automated/analyst triage. Suspect activity is escalated for investigation and response per playbooks. High‑severity incidents target response within minutes, with continuous coverage from the SOC. Activity is recorded in tickets with audit trails.
• 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: Pre‑defined procedures cover common events (malware, credential misuse, lateral movement). Users report issues via support/tickets; all suspected incidents generate tracked records. Analysts investigate, recommend/execute containment and remediation, and maintain communications until closure. Post‑incident reports summarise impact, root cause, and improvements; major incidents include periodic updates and management‑level reviews.
• 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: Time‑limited PoC deploys sensors, onboards representative log sources, enables alarm visibility, and demonstrates MDR triage/investigation. It excludes full incident response, bespoke integrations, extended reporting, and production‑scale tuning. The PoC validates ingestion, detection efficacy, workflows, and reporting before committing to the full MDR service.

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

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

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: Intertek
• ISO/IEC 27001 accreditation date: Wednesday 22 May 2024
• What the ISO/IEC 27001 doesn’t cover: This certification covers everything we do applicable to ISO/IEC 27001, no exclusions.
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: Intertek
• ISO 9001 accreditation date: Wednesday 7 June 2023
• What the ISO 9001 doesn’t cover: This certification covers everything we do applicable to ISO 9001, no exclusions.
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: Yes
• Who accredited the PCI DSS certification: Pen Test Partners
• PCI DSS accreditation date: Friday 13 December 2024
• What the PCI DSS doesn’t cover: N/a
• Cyber essentials: Yes
• Please provide your Cyber Essentials Certificate Number: 4377ebef-31ac-49ef-9943-13c7f3e3f9a5
• Cyber essentials plus: Yes
• Please provide your Cyber Essentials Plus Certificate Number: 66b24695-ed3f-4797-bb2c-65b58932576d
• 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
    • New apprenticeships on the contract workforce in the relevant area that meet the criteria set out in MAC 1b
    • 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

  • 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
    • Delivery of apprenticeships, supported internships and T Level industry placement opportunities (Level 2, 3 and 4+) in relation to the contract

  • 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 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

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