ACS TECHNOLOGY GROUP LTD

Microsoft Azure Services

ACS deliver end-to-end Microsoft Azure services covering assessment, secure cloud migrations, modernisation and ongoing optimisation. Our experts design, deploy and manage scalable, resilient environments, improving performance, cost control and security. Continuous monitoring, governance and optimisation ensure Azure platforms align with business goals and growth while supporting compliance, resilience and excellence.

Features

• Azure Readiness & Assessment
• Cloud Migration Services
• Azure Landing Zone Design
• Workload Modernisation
• Performance Optimisation
• Cost Management & FinOps
• Security & Identity Management
• Governance & Compliance Management
• Backup, DR & Resilience
• Ongoing Azure Management & Monitoring

Benefits

• Reduced risk through structured, proven Azure migrations
• Improved performance and scalability of workloads
• Lower cloud spend through ongoing cost optimisation
• Stronger security and identity protection
• Increased resilience with built-in backup and disaster recovery
• Faster time‑to‑value for new applications and services
• Improved compliance and governance control
• Improved compliance and governance control
• Access to certified Azure expertise without internal overhead
• Cloud platforms aligned to business growth and strategy

• Education pricing 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 ben.townend@acsgroup.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

559265856469831

Contact

Ben Townend
01274 556091
ben.townend@acsgroup.co.uk

About your service

• Service categories:

  Systems Infrastructure Software

  Physical and virtual computing

  • Virtual client computing

  Operating system environments

  • Core Operating Systems
  • Client Operating Systems
  • Embedded/Industrial Operating Systems

  Software defined compute

  • Virtual Machine Software
  • Container Infrastructure Software
  • Cloud System Software

  Other computing and storage software

  • Remote Desktop Control Software
  • Container Data and Infrastructure Management Software
• 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: Our Azure service extends existing Microsoft environments, including Microsoft 365, Windows Server, Active Directory, SQL Server, Dynamics 365 and the Power Platform. It integrates with on‑premises virtualisation, line‑of‑business applications, security, backup, disaster recovery and DevOps tooling, providing a seamless bridge between cloud and existing IT investments and operational management services.
• Cloud deployment model: Public cloud
• Service constraints: The service is limited to Microsoft Azure subscriptions within the agreed scope and relies on the customer providing timely access, information, approvals and licences. Third‑party platforms and Microsoft service availability remain outside provider control. Optimisation and security actions require customer approval, with services delivered in line with agreed service hours, SLAs and shared compliance responsibilities.
• System requirements:
  • Internet connectivity sufficient to access Azure services
  • Supported operating systems for migrated workloads
  • Documented application and data dependencies
  • User devices capable of accessing cloud‑hosted services

User support

• Email or online ticketing support: Yes
• Support response times: SLA's are dependent on service taken. ; ; 1 hour for Critical outages ; 4 Hour for Single user outages ; 8 Hours for small system changes ; ; The above are example of SLA offerings
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: EN 301 549
• Phone support: Yes
• Phone support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support: No
• Onsite support: Yes, at extra cost
• Support levels: Support services are provided on a time‑and‑materials basis at a standard professional services day rate of £1,200. This rate applies to Microsoft Azure, migration, optimisation, remediation and operational support activities delivered remotely or on customer premises, where agreed.; Services are delivered by suitably qualified engineers during standard business hours, excluding public holidays. All support activity is scoped, scheduled and agreed in advance with the customer. Work may include incident investigation, configuration changes, architectural design, security improvements and performance or cost optimisation.; Support is provided on a reasonable endeavours basis and is dependent on the customer supplying timely access, information, approvals and licences. Partial days may be charged on a pro‑rata basis. Any requirement for specialist resources, expedited delivery or out‑of‑hours support is subject to separate agreement and may incur additional charges.; Service delivery is governed by agreed service levels and does not include responsibility for third‑party services or Microsoft platform availability.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Onboarding begins with a formal initiation phase to confirm service scope, objectives and delivery approach. This includes agreement of supported Azure subscriptions, workloads, service levels and any required customisations. The customer provides necessary documentation, access permissions and licensing information to enable service delivery.; A discovery and assessment phase follows, during which the existing Azure environment is reviewed to establish a baseline covering architecture, security, performance, cost and governance. Findings are documented and used to validate assumptions, identify risks and confirm priorities.; Once discovery is complete, the service is configured in line with the agreed solution design. This may include setting up monitoring, security controls, access models, reporting and operational processes. Any required migrations or optimisation activities are planned and scheduled with minimal disruption.; The onboarding process concludes with a transition to steady‑state service delivery. This includes confirmation of support channels, escalation paths, service levels and reporting arrangements. Knowledge transfer is provided where appropriate, ensuring the customer understands service operation and ongoing engagement processes.
• Service documentation: Yes
• Documentation formats: PDF
• End-of-contract data extraction: The Data is kept within the customers tenant and is not held by ACS
• End-of-contract process: At the end of the contract, the service enters a structured offboarding phase to ensure a smooth and orderly transition. The supplier works with the customer to agree exit timelines, responsibilities and any handover requirements. Access to Azure environments, documentation and operational information is maintained until the agreed contract end date.; All customer data, configuration information, architecture documentation and service records created or maintained as part of the service are returned to the customer or a nominated third party, as requested. This includes reasonable assistance to support continuity of service and minimise disruption during transition. No additional charges are applied for the handover of customer information or standard service documentation.; The supplier will revoke its administrative access at the end of the contract in line with customer instructions and security best practice. Any customer data held by the supplier is handled in accordance with contractual and data protection obligations, with confirmation provided where data deletion is requested.; Following contract completion, no ongoing management or support is provided unless a new agreement is put in place.
• Documentation accessibility standard: EN 301 549

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
  • Opera
• Application to install: No
• Designed for use on mobile devices: No
• Service interface: No
• User support accessibility: EN 301 549
• API: No
• Customisation available: Yes
• Description of customisation: The service can be tailored to meet customer requirements through agreed variations to service scope, solution design and service levels. Customisation options include selecting specific Microsoft Azure workloads, environments or subscriptions to be supported, as well as adapting migration approaches, optimisation activities and security controls to align with organisational priorities, risk appetite and compliance requirements.; Service Levels can be customised by agreement, including adjustments to response times, support hours, escalation routes and reporting frequency. Any changes to SLAs are documented and agreed in advance and may affect service pricing or delivery schedules.; Solution customisation may include architecture design, resilience requirements, backup and retention policies, identity and access models, cost management controls and monitoring configurations. Where required, the service can integrate with existing customer systems, operational processes and third‑party tools.; All customisations are subject to technical feasibility, Microsoft platform constraints and shared responsibility considerations. Changes outside the standard service definition are managed through a formal change control process to ensure clarity, governance and transparency throughout service delivery.

Scaling

• Independence of resources: Microsoft Azure is designed to ensure that one customer’s usage does not adversely affect another’s service performance. Azure operates a multi‑tenant architecture with strict logical isolation at tenant, subscription and resource levels. Compute workloads are isolated using hypervisor‑based virtualisation, while storage and networking are segregated per subscription. Azure enforces resource quotas and capacity controls to prevent any single workload from monopolising shared infrastructure.

Analytics

• Service usage metrics: Yes
• Metrics types: The service provides clear, measurable metrics to support transparency and service governance. Metrics include performance against agreed service levels, such as response and resolution times, incident volumes and severity, and completion of scheduled support activities. Platform metrics may cover workload availability monitoring, backup and recovery success rates, security alert trends, and compliance status. Where optimisation services are delivered, metrics include usage visibility, cost trends and progress against agreed improvement actions. Migration and project activities are tracked against delivery milestones and scope completion, with reporting provided through agreed review cycles.
• Reporting types: Regular reports
• Resource tagging: Yes
• FOCUS resource tagging: No

Resellers

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

Staff security

• Staff security clearance: Staff screening not performed
• Government security clearance: Baseline Personnel Security Standard (BPSS)

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: Yes
• 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: Another external penetration testing organisation
• Protecting data at rest: Other
• Other data at rest protection approach: Microsoft Azure protects all customer data at rest by default using AES‑256 encryption across supported services, including storage, databases and virtual machine disks. Encryption is applied automatically as data is written to physical media and cannot be disabled for Azure Storage services. By default, encryption keys are securely managed by Microsoft. Where greater control is required, customers can use customer‑managed keys stored in Azure Key Vault to manage key access, rotation and lifecycle. For higher‑risk workloads, Azure also supports infrastructure‑level double encryption, providing defence‑in‑depth. Encryption at rest operates within Azure’s shared responsibility model, supporting recognised regulatory and security compliance requirements.
• Data sanitisation process: Yes
• Equipment disposal approach: A third-party destruction service
• Data sanitisation type:
  • Data Erasure
  • Degaussing
  • Physical Destruction / Hardware containing data is completely destroyed

Data importing and exporting

• Data export approach: No
• Data export formats: Other
• Other data export formats: None
• Data import formats:
  • CSV
  • ODF
  • Other
• Other data import formats:
  • VHD
  • VHDX

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
  • Legacy SSL and TLS (under version 1.2)
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway

Availability and resilience

• Guaranteed availability: The service is hosted on Microsoft Azure and benefits from Azure’s enterprise‑grade infrastructure and availability commitments. Microsoft Azure provides formal Service Level Agreements (SLAs) that define guaranteed levels of service availability, measured on a per‑month basis.; For most Azure services, Microsoft guarantees a minimum availability of 99.9% per calendar month, equating to a maximum of approximately 43 minutes of unplanned downtime per month. Higher availability levels are achievable where services are architected in line with Microsoft best practices, for example by deploying resources across Availability Sets or Availability Zones. In such configurations, availability guarantees can increase to 99.95% or 99.99%, depending on the service and deployment model.; Availability is monitored continuously by Microsoft and is supported by resilient datacentre design, redundant power and networking, proactive maintenance, and automated failover mechanisms. Planned maintenance is managed to minimise disruption and, where possible, performed without customer impact.; If Microsoft fails to meet the applicable SLA for an Azure service, customers may be entitled to service credits in accordance with Microsoft’s published SLA terms. The service operates under a shared responsibility model, meaning availability guarantees apply where the service is configured and operated in line with documented Azure guidance.
• Approach to resilience: The service is designed to be resilient and is hosted on Microsoft Azure, which provides built‑in platform capabilities to support fault tolerance, high availability, and business continuity. Resilience is achieved through redundant infrastructure, geographic distribution, and automated recovery mechanisms.; Azure regions are composed of multiple physically separate datacentres. Where supported, services are deployed across Availability Zones, which are independent locations within a region with separate power, cooling, and networking. This design ensures that a failure in a single datacentre or zone does not result in a service outage. Azure also supports fault domains and update domains, reducing the risk of correlated failures during hardware faults or planned maintenance.; Many Azure services provide zone‑redundant or region‑redundant configurations, enabling automatic replication of data and services and supporting failover in the event of infrastructure disruption. Platform monitoring, health checks, and automated recovery processes are used to detect and respond to failures without manual intervention.; Resilience is implemented in line with Microsoft’s Well‑Architected Framework and reliability guidance. The service operates under a shared responsibility model, meaning resilience is supported by both the Azure platform and service configuration. This approach enables the service to continue operating during component failures and recover quickly from unexpected incidents.
• Outage reporting: The service reports outages using Microsoft Azure’s built‑in service health and incident reporting capabilities. Azure continuously monitors the health of its infrastructure and services and provides real‑time visibility of service issues through Azure Service Health and the public Azure Status Page.; For widespread or significant incidents affecting multiple customers, regions, or services, Microsoft publishes updates on the Azure Status Page, which provides a global view of current and historical service issues. This page is updated in real time and includes incident status, affected regions, and post‑incident reviews where applicable.; For customer‑specific or targeted issues, outage notifications are delivered through Azure Service Health within the Azure portal. This provides a personalised view of incidents, planned maintenance, and service advisories that may affect the service based on the deployed resources and regions. Notifications can be configured to alert service administrators via email, SMS, or integrated IT service management tools.; During an incident, Microsoft provides ongoing updates until service is restored, followed by a post‑incident report where appropriate. This approach ensures timely, transparent communication of outages and supports effective incident response and stakeholder communication.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Dedicated link (for example VPN)
  • Username or password
• Access restrictions in management interfaces and support channels: Access to management interfaces and support channels is restricted using Microsoft Azure identity and access management controls. Microsoft Entra ID is used to centrally manage user identities and enforce strong authentication. Role‑Based Access Control (RBAC) ensures users are granted only the minimum permissions required for their role, following the principle of least privilege. Conditional Access policies require multi‑factor authentication and restrict access based on device compliance, location, and risk. Administrative access is limited to authorised personnel, and all access activity is logged and monitored using Azure logging and audit capabilities to support oversight and security monitoring.
• Access restriction testing frequency: Less than once a year
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Username or password

Audit information for users

• Access to user activity audit information: Users contact the support team to get audit information
• How long user audit data is stored for: User-defined
• Access to supplier activity audit information: Users contact the support team to get 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: ISO/IEC 27001
• Information security policies and processes: The organisation follows a documented set of information security policies and processes aligned with ISO/IEC 27001:2022. Policies are designed to protect the confidentiality, integrity, and availability of information and apply to all employees, contractors, and third parties. Core policies cover information security governance, access control, information classification and handling, incident management, application security, physical security, and the secure use of cloud services.; Information security risks are identified and assessed on an ongoing basis. Appropriate controls are implemented to manage identified risks and their effectiveness is reviewed through regular internal audits and formal management reviews. Policies and procedures are reviewed at least annually, or sooner where required due to changes in risk, technology, or regulatory requirements. Staff receive information security awareness training and are required to comply with all relevant policies as part of their role.; A reporting structure is in place. All users are required to report actual or suspected information security incidents promptly using defined reporting channels. Reported incidents are escalated to the designated incident owner and information security leads for investigation and response. Significant incidents, risk trends, and compliance matters are reported to senior management to ensure oversight, accountability, and continual improvement of the information security management system.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Supplier-defined controls
• Configuration and change management approach: The service uses structured configuration and change management processes aligned with Microsoft Azure best practices. Service configuration is controlled using standardised, documented settings and is reviewed regularly to prevent configuration drift. Changes are planned, risk‑assessed, and approved prior to implementation, with testing performed where appropriate to minimise service impact. Changes are implemented in a controlled manner and monitored to ensure successful deployment. Azure platform controls, logging, and monitoring are used to track configuration changes and operational activity. This approach supports service stability, auditability, and consistent operation across environments, in line with the Azure Well‑Architected Framework’s operational excellence guidance.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: The service follows a structured vulnerability management process aligned with Microsoft Azure security best practices. Vulnerabilities are identified through continuous assessment using Microsoft Defender for Cloud if client takes the service, which provides both agentless and agent‑based scanning of supported resources. Identified vulnerabilities are reviewed within the Azure security portal, prioritised based on severity and risk, and tracked until resolution. Remediation actions, such as applying patches or configuration changes, are implemented in a controlled manner and monitored for effectiveness. The process supports ongoing risk reduction, auditability, and compliance through continuous monitoring and reporting.
• Protective monitoring type: Undisclosed
• Protective monitoring approach: The service uses layered protective monitoring across endpoints and cloud infrastructure using Datto and Microsoft Azure services. Datto RMM provides monitoring of managed devices, generating automated alerts when systems operate outside defined security or performance thresholds, including service failures, patching issues, and security events. Alerts are reviewed and investigated to enable timely response.; Within Azure, protective monitoring is delivered through Microsoft Defender for Cloud and Azure Monitor, which collect and analyse security and operational telemetry. Microsoft Sentinel correlates security events and threat indicators, providing monitoring, alerting, and incident visibility to support early detection, investigation, and remediation of security threats.
• Incident management type: Undisclosed
• Incident management approach: The service operates a structured incident management process aligned with ITIL best practices using Autotask. Incidents are identified through monitoring, automated alerts, or user reports and are promptly logged, categorised, and prioritised based on impact and urgency. Appropriate technical teams investigate incidents to restore normal service as quickly as possible, with escalation applied where required. Progress is tracked throughout the incident lifecycle and relevant stakeholders are kept informed. For cloud‑related incidents, Microsoft Azure Service Health is used to receive incident notifications, updates, and post‑incident reports. After resolution, incidents are reviewed to identify lessons learned and support continuous service improvement.
• Post-quantum cryptography secure: Yes

Secure development

• Approach to secure software development best practice: Supplier-defined process

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: No

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

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

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: BSI
• ISO/IEC 27001 accreditation date: Monday 15 July 2024
• What the ISO/IEC 27001 doesn’t cover: N/a
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: BSI
• ISO 9001 accreditation date: Tuesday 2 September 2025
• What the ISO 9001 doesn’t cover: N/a
• 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: Ade3587b-337c-4113-9179-8b25d272282f
• 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 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
    • 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
    • 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
    • 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

  • 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
    • 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
    • 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
    • Measures to involve local stakeholders and/or users in design (e.g. in the design of services, systems, products or buildings)
    • 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

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

  • 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
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach 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

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