AVADA CONNECT LTD

Avada Connect

Avada Connect provides secure, scalable video and information management for organisations needing high‑performance surveillance. It enables recording, viewing, analysis, and management of video across diverse devices and multi‑site estates, supporting live monitoring, forensic search, incident handling, and operational control with strong cybersecurity and flexible deployment options

Features

• Enables scalable redundant video management through distributed architecture.
• Automatically discovers and integrates most IP and IoT devices.
• Delivers low‑latency streaming with efficient high‑performance video processing.
• Analyzes years of footage in seconds using metadata.
• Provides multi‑platform access via desktop, browser, mobile interfaces.
• Triggers automated rules, alerts, workflows, and PTZ actions.
• Uses AES‑256 encryption with optional keys and TLS.
• Provides full audit trails with tamper detection watermarking.
• Integrates LDAP and Active Directory for centralized management.
• Ensures uninterrupted video capture during server or hardware failures.

Benefits

• Find critical events rapidly using metadata‑driven forensic search.
• Reduce investigation time through rapid discovery and streamlined onboarding.
• Enhances situational awareness through unified monitoring and remote access.
• Strengthen evidence integrity with audit trails and tamper detection.
• Respond faster to incidents using automated alerts and actions.
• Maintain continuous recording using resilient redundant server architecture.
• Scale effortlessly across estates without redesigning existing infrastructure.
• Lower operational costs running efficiently on standard hardware.
• Improve security posture with encryption, RBAC controls, and 2FA.
• Enhance decision‑making using analytics delivering actionable real‑time insights.

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 enquiries@avadaconnect.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

638756474920497

Contact

Andy Stokes
07966658092
enquiries@avadaconnect.co.uk

About your service

• Service categories:

  Application Development and Deployment

  Application platforms

  • Model driven application platforms
• Multi cloud support: Yes

Service scope

• Software add-on or extension: No
• Cloud deployment model: Hybrid cloud
• Service constraints: Yes. The service includes several important constraints that buyers should understand. Performance depends on on‑premises hardware capacity, which limits how many cameras can be recorded or viewed simultaneously. Cloud features require stable internet bandwidth, low latency, and correct firewall rules allowing AWS access. Video transcoding can place heavy CPU and GPU demands on customer hardware. On‑premise maintenance is always scheduled, while cloud features receive advance notice before changes. Support is restricted for unsupported operating systems, non‑standard third‑party cameras, blocked firewall configurations, mismatched backups, or any modified Avada Connect files or databases
• System requirements:
  • Modern HTML5‑compliant browser required for cloud connectivity features.
  • - Stable internet connection scaled appropriately for each deployment site.
  • Remote access enabled to allow Avada support connections.
  • Customer‑provided hardware meeting specifications in the pricing list
  • IOS or Android mobile devices for mobile client access.
  • Firewall rules permitting required AWS URLs and ports.
  • Sufficient CPU and GPU resources for video transcoding workloads
  • Secure, environmentally controlled location for on‑premise servers and NVRs.
  • Standards‑compliant IP cameras supporting ONVIF or RTSP protocols.
  • Customer‑maintained network bandwidth suitable for video streaming performance.

User support

• Email or online ticketing support: Yes
• Support response times: Avada Connect responds to questions according to its defined support hours and incident‑based SLAs. During standard support hours of Monday to Friday, 9am–5pm, response times are: Critical within 2 hours, High within 4 hours, Medium within 1 business day, and Low within 2 business days. These times apply only within weekday support hours, as the service does not include weekend support unless the customer purchases an optional uplift for extended or 24/7 coverage. Support requests can be raised through the helpdesk ticketing system or automatically via email, ensuring timely acknowledgement and escalation when required.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.2 AAA
• 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: Avada Connect provides structured support levels designed to match different operational needs. Standard support is included as part of the service and covers access to the Avada UK Helpdesk from Monday to Friday, 9am–5pm. This level includes ticketing, email support, and phone assistance, with response times aligned to incident priority: Critical within 2 hours, High within 4 hours, Medium within one business day, and Low within two business days. Standard support is included in the core service price, with no additional charge.; For buyers requiring extended coverage, uplifted support packages are available at additional cost, as detailed in the pricing document. These uplifts can include out‑of‑hours or 24/7 support, faster response commitments, and additional onsite time. Costs vary depending on the level of extended coverage and the amount of onsite engineering required.; Avada does not provide a dedicated technical account manager or cloud support engineer as part of the standard service. Instead, support is delivered through the Avada Helpdesk and engineering teams, who manage ticket escalation, system updates, and onsite visits when required. Enhanced support arrangements, including more personalised engagement, can be purchased as part of uplifted service options.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Avada Connect supports users in getting started through a structured onboarding approach designed to suit different environments and levels of experience. New users receive clear, task‑focused user documentation, including setup guides, feature overviews, and step‑by‑step instructions for both the desktop client and mobile applications. This documentation helps organisations introduce the service without requiring specialist knowledge. Avada also provides online training resources, such as guided walkthroughs and remote support sessions, to help users understand core features, configure their environment, and become confident with day‑to‑day tasks. These sessions focus on practical use, including logging in, navigating the interface, managing alerts, and accessing video content.; While Avada does not offer formal onsite training as part of the standard service, organisations can supplement onboarding with their own internal training processes using the provided materials. The service interface is designed to be intuitive, reducing the learning curve for new users and enabling teams to become productive quickly. Administrators receive additional guidance on configuration, permissions, and system management to ensure smooth deployment. Overall, Avada Connect combines documentation, remote support, and accessible design to help users adopt the service effectively and begin using its capabilities with confidence.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: When a contract with Avada Connect ends, users can extract their data through a clear, controlled offboarding process designed to ensure continuity and compliance. Administrators retain access to the service for the duration of the agreed offboarding period, during which they can export video recordings, logs, configuration data, and other relevant information using the standard tools built into the platform. Data can be downloaded directly from the system in commonly used formats, allowing organisations to retain records, migrate to another service, or meet regulatory obligations. Where applicable, administrators can also retrieve cloud‑stored metadata and user‑generated content through the browser interface.; Avada does not provide bespoke data‑extraction tooling or custom export formats, and no API is available to automate extraction. All data retrieval must therefore be completed using the built‑in export functions and administrative controls provided within the service. Once the offboarding window closes, remaining data is securely deleted in line with Avada’s retention and disposal processes. Organisations are encouraged to plan their extraction activities early in the offboarding period to ensure all required information is captured. This approach ensures users can retrieve their data effectively while maintaining security, privacy, and operational integrity throughout the contract closure process.
• End-of-contract process: At the end of an Avada Connect contract, the organisation enters a defined offboarding period during which administrators retain access to the service to extract any required data using the platform’s standard export tools. Once this window closes, Avada securely deletes remaining data in line with its retention and disposal processes. Service access is removed, and no further use of the platform is permitted unless a new contract is agreed. Offboarding does not include bespoke migration support, custom data extraction, or extended access beyond the agreed timeframe.; The contract price includes access to the Avada Connect platform, standard configuration options, user documentation, remote onboarding support, and ongoing service operation for the duration of the agreement. Buyers also receive access to the desktop client, mobile applications, and browser‑based management interface as part of the core service. Additional costs apply only where buyers request services outside the standard offering, such as bespoke development, custom integrations, extended training, or specialist consultancy. No API access, customisation, or tailored export tooling is included in the base price.
• Documentation accessibility standard: EN 301 549

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
  • Opera
  • Other
• Application to install: Yes
• Compatible operating systems:
  • Android
  • IOS
  • Linux or Unix
  • MacOS
  • Windows
  • ChromeOS
  • Other
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: Mobile and desktop access offer different experiences within Avada Connect. The desktop client provides the full VMS feature set, including advanced configuration, multi‑camera monitoring, system administration, and integration management. It is designed for operational control rooms and power users who need complete functionality. The mobile apps for iOS and Android focus on lightweight, on‑the‑go access, enabling users to view live and recorded footage, receive alerts, and perform essential actions without the full administrative toolkit. Mobile access complements, rather than replaces, the desktop environment, offering convenience while the desktop client delivers the complete operational capability.
• Service interface: Yes
• User support accessibility: EN 301 549
• Description of service interface: The Avada Connect service interface is delivered through three integrated access methods, each supporting different aspects of the platform. The desktop client application provides the full VMS feature set, including configuration, monitoring, and administration. The mobile apps for iOS and Android offer streamlined access for viewing footage, receiving alerts, and performing essential tasks while away from a workstation. The browser‑based interface, accessible through any modern HTML5‑compliant browser, supports cloud identity, connectivity, and management functions. Together, these interfaces create a cohesive, multi‑channel environment that enables users to interact with the service effectively across devices.
• Accessibility standards: EN 301 549
• Accessibility testing: Avada Connect has not yet undergone formal accessibility or assistive‑technology user testing, and no structured audits have been completed against WCAG 2.2, it was built with EN 301 549 principles. However, elements of the interface have been exercised informally through internal evaluations that included users employing common assistive tools available within Microsoft Windows. These informal checks focused on verifying compatibility with screen magnifiers, high‑contrast modes, keyboard‑only navigation, and basic interaction with screen readers for non‑complex tasks. Testing also explored how UI scaling behaved across different resolutions and whether essential workflows—such as logging in, navigating menus, and accessing alerts—remained usable when assistive technologies were active.; While these activities helped identify and resolve minor usability issues, they do not constitute formal accessibility testing or certified conformance. No structured sessions have been conducted with external users who rely on assistive technologies, and no specialist accessibility consultancy has been engaged. As a result, Avada cannot claim validated accessibility performance or guaranteed support for specific assistive tools beyond standard operating‑system capabilities. Buyers with defined accessibility requirements are encouraged to discuss them with Avada so that available options, configuration approaches, or reasonable adjustments can be explored within the scope of the service.
• API: No
• Customisation available: No

Scaling

• Independence of resources: Avada Connect is not a shared, multi‑tenant cloud service. Each customer operates a self‑contained on‑premise system, with its own servers, storage, processing capacity, and configuration. Because every site is an isolated tenant, no resources are shared between organisations, and therefore no customer’s usage can affect another’s performance.; Performance is determined solely by the customer’s own infrastructure, as stated in the Service Definition. Optional cloud features handle only identity and connectivity, not video processing or storage, so cross‑tenant load cannot occur.

Analytics

• Service usage metrics: Yes
• Metrics types: Avada Connect provides a comprehensive set of service metrics designed to give organisations full visibility of system performance, operational activity, and evidence‑handling workflows. Metrics can be tailored to project requirements and typically include device and camera activity levels, recording timelines, event volumes, system uptime, SLA achievement percentages, and any SLA violations. Additional operational indicators such as Average Handling Time (AHT) for incident workflows, server and hive availability, and platform responsiveness are also captured. These metrics support governance, auditability, evidence integrity, and continuous improvement across the surveillance estate.
• Resource tagging: Yes
• 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: Supplier-defined controls
• Penetration testing frequency: Never
• Protecting data at rest: Scale, obfuscating techniques, or data storage sharding
• Data sanitisation process: No
• Equipment disposal approach: A third-party destruction service

Data importing and exporting

• Data export approach: Users export their data directly from Avada Connect using the system’s built‑in export tools. Because the platform is fully on‑premise, customers retain complete ownership of all video, metadata, incident files, evidence, and configuration information, and can export these at any time. Export formats vary by source and include options such as CSV and XLS. Offboarding does not require supplier involvement unless optional assistance is requested. Upon contract termination, Avada retains no customer data, and any cloud‑based identity or connectivity services are disabled once access is revoked.
• Data export formats:
  • CSV
  • ODF
• Data import formats:
  • ODF
  • Other

Data-in-transit protection

• Data protection between buyer and supplier networks: Legacy SSL and TLS (under version 1.2)
• Data protection within supplier network: Legacy SSL and TLS (under version 1.2)

Availability and resilience

• Guaranteed availability: Avada Connect’s availability commitments are defined by the architecture described in the Service Definition. Because the core platform is an on‑premise system, overall service availability is determined by the customer’s own infrastructure, including servers, storage, and network performance. For customers who enable optional cloud connectivity features, Avada guarantees 99.9% availability, excluding planned maintenance. Planned maintenance for cloud components is always communicated at least five working days in advance, and on‑premise maintenance is scheduled directly with the customer to avoid unplanned disruption.; Incident response times are also defined within the SLA framework: Priority 1 issues receive a response within two hours during support hours, Priority 2 within four hours, Priority 3 within one business day, and Priority 4 within two business days. These response targets support operational continuity but do not constitute a financial availability guarantee.; The Service Definition does not include any refund, service credit, or compensation mechanism if availability targets are not met. No commercial terms or financial remedies are specified for downtime or SLA breaches. Availability‑related financial commitments would therefore be governed solely by the call‑off contract rather than the service description itself.
• Approach to resilience: Avada Connect is designed with strong resilience principles, ensuring continuity even in demanding operational environments. The platform uses a distributed server‑hive architecture, allowing multiple servers to synchronise configuration, share load, and automatically act as failover for one another. This means that if a server becomes unavailable, recording and system functions continue without interruption. The system also supports local and cloud‑based storage options, enabling flexible retention strategies and additional redundancy where required. High‑performance media handling, encrypted data stores, and integrity checks further protect against data loss or corruption.; Because Avada Connect is primarily an on‑premise deployment, overall resilience is determined by the customer’s own infrastructure, including network, server hardware, and storage design. The service supports industry‑standard backup tools and allows configuration and evidence data to be exported for disaster‑recovery planning. Optional cloud connectivity features operate through AWS, which provides multi‑region redundancy and strong security controls; however, detailed datacentre architecture is not published in the Service Definition and can be provided on request.; Together, these capabilities ensure that Avada Connect maintains operational continuity, protects evidence integrity, and supports resilient multi‑site surveillance environments even during hardware failures or network disruption.
• Outage reporting: Avada Connect manages outage communication through a structured, ITIL‑aligned service management model rather than automated public reporting tools. The Service Definition does not include a public service‑status dashboard, an availability API, or automated email alerts for outage notifications. Instead, all incident and outage communication is delivered through the Avada Helpdesk, which acts as the central point of coordination for service issues. Customers can raise incidents via the helpdesk portal or email, and each ticket is assigned a unique reference number, tracked through to resolution, and updated throughout its lifecycle.; Second‑line engineers manage operational issues, while third‑line engineering teams address software‑level or integration‑related faults, ensuring that customers receive timely and technically informed updates. For optional cloud connectivity features, Avada provides a minimum of five working days’ notice before any planned maintenance that may affect availability. Unplanned outages are communicated through the same helpdesk‑driven process, ensuring consistent and accountable communication.; Because Avada Connect is primarily an on‑premise system, most operational continuity and outage visibility are determined by the customer’s own infrastructure. Additional detail on outage‑reporting mechanisms for cloud components or datacentre‑level resilience can be provided on request.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
  • Other
• Other user authentication: Avada Connect authenticates users through a secure, account‑based login model that enforces identity verification before any system access is permitted. Users authenticate using a username and password protected by strong password‑policy enforcement, salted and hashed credential storage, and brute‑force protection. The platform supports optional Multi‑Factor Authentication (2FA) to strengthen access security and integrates with LDAP/Active Directory for organisations that require federated identity management. All authentication traffic is encrypted using TLS/SSL, and access rights are controlled through granular role‑based access control (RBAC), ensuring only authorised users can view, manage, or export system data.
• Access restrictions in management interfaces and support channels: Avada Connect restricts access to management interfaces and support channels using the controls described in the Service Definition. Administrative access is limited to authorised engineering and support personnel through role‑based access control, strong authentication and encrypted connections. All actions within management interfaces are captured through audit logging, ensuring accountability and traceability. Support access is provided only through the Avada Helpdesk, where users authenticate before raising or viewing tickets. Each request is assigned a unique reference and handled through an ITIL‑aligned workflow, ensuring controlled escalation, monitored activity and secure communication throughout the support process.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • 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 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: Avada Connect follows a structured set of information security policies and processes designed to ensure secure development, controlled operation, and accountable governance. The platform is developed using secure‑by‑design principles and aligns with recognised industry frameworks including CAPPS, OWASP and NIST. Security is overseen by a named senior leader, the Technical Director, who holds board‑level responsibility for security governance, vulnerability management and compliance. This role provides clear accountability and ensures that security considerations are embedded across engineering, product development and operational support.; Policies cover secure coding, encryption, authentication, access control, audit logging, incident handling and change management. Avada operates a controlled CI/CD pipeline with automated testing and structured release processes to ensure that only validated, security‑checked updates are deployed. Vulnerabilities are triaged using a formal process, with high‑risk or critical issues addressed within a 14‑day Cyber Essentials‑aligned remediation window.; Compliance with policies is ensured through internal review, cross‑functional oversight and mandatory adherence to development and operational controls. Support teams follow ITIL‑aligned processes, ensuring consistent handling of incidents and change requests. Together, these policies and governance structures ensure that security is systematically maintained throughout the lifecycle of the service.
• 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: Avada Connect’s configuration and change management processes follow the controls described in the Service Definition. The service is developed using a secure‑by‑design model, supported by a CI/CD pipeline that provides automated integration, testing and controlled release of updates. This ensures that components are consistently validated throughout their lifecycle. Operational changes are managed through Avada’s ITIL‑aligned service management process, which governs incident handling, problem management and release activity. Security‑related changes follow the documented vulnerability‑management workflow, where issues are triaged and high‑risk or critical items are remediated within a 14‑day Cyber Essentials‑aligned window.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: Avada Connect follows a documented vulnerability‑management process in which all identified issues are triaged and assessed for potential security impact using recognised frameworks including CAPPS, OWASP and NIST. Threat information is gathered through secure‑development practices, internal testing, CI/CD validation and cross‑functional engineering review. High‑risk or critical vulnerabilities follow a defined remediation target aligned with Cyber Essentials expectations, requiring fixes to be deployed within 14 days. All patches are released through Avada’s controlled CI/CD pipeline, ensuring updates are validated, security‑checked and deployed in a consistent, governed manner.
• Protective monitoring type: Undisclosed
• Protective monitoring approach: Avada Connect uses supplier‑defined protective‑monitoring processes based on the platform’s built‑in audit, forensic and evidence‑integrity capabilities. Potential compromises are identified through comprehensive audit logging, forensic search, and chain‑of‑evidence reporting, which allow unusual activity or integrity issues to be detected. When a potential compromise is found, incidents are handled through Avada’s ITIL‑aligned service management process, ensuring structured investigation, escalation and resolution. Response times follow the documented SLA: Priority 1 incidents receive a response within two hours, with lower‑priority issues addressed within defined business‑hour targets, ensuring timely and accountable handling of security‑related events.
• Incident management type: Undisclosed
• Incident management approach: Avada Connect uses supplier‑defined, ITIL‑aligned incident‑management processes that cover common operational events, including service issues, faults and support requests. All incidents follow a predefined helpdesk workflow, where users report issues via the Avada Helpdesk portal or email, generating a unique ticket reference that is tracked throughout its lifecycle. Incidents are triaged and escalated to second‑ or third‑line engineering teams as required. Avada provides incident updates and outcomes directly through the helpdesk system, ensuring customers receive clear, accountable communication and a full record of actions taken, including resolution details and any follow‑up recommendations.
• Post-quantum cryptography secure: Yes

Secure development

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

Public sector networks

• Connection to public sector networks: No

Pricing

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

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

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

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: No
• ISO 28000:2022 certification: No
• ISO 9001 certification: No
• Quality management systems (QMS): No
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Please provide your Cyber Essentials Certificate Number: 4b01d517-3ef5-4bb4-bf39-7426b1d0d405
• Cyber essentials plus: No
• Cyber Essentials Alternative: None of the criteria
• 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
    • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
    • Plans to engage the contract workforce in deciding the most important workplace issues to address
    • Ensuring new workers are informed of their right to join a trade union
    • Monitoring of employee engagement rates (by protected characteristic) and, where necessary, the development of actions to ensure all voices are heard across the diversity of the workforce
    • Employment contracts that reflect actual hours worked; steps taken to ensure employees understand their contracts and have the ability to review and adjust them if actual hours regularly exceed contracted hours
    • Activities that support an environment where staff are educated about, and feel empowered to, address their physical wellbeing
    • Activities that support an environment where staff are educated about and feel empowered to report and address bullying and harassment
    • Activities to cascade good practice on fair working conditions throughout the supply chain
    • 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 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
    • Understanding of the modern slavery risks and issues affecting the market, industry, sector or country (of origin or of source) relevant to the contract, and the workforce in the supplier’s own organisation and those of its key subcontractors
    • Measures to identify, mitigate and manage modern slavery risks relating to the contract and how these will be implemented
    • Outline policies and practices to be applied to or put in place for the contract to mitigate and manage modern slavery risks, including: Pre-employment checks, recruitment practices. Workplace conditions, safeguarding plans and processes in place and regular monitoring with relevant groups considered, which may include sampling
    • How these flow down the supply chain and are monitored Illustrative examples include reporting, site visits, audits, etc.
    • How to ensure business decisions re: price/cost, short lead times, payment timescales do not create modern slavery risks in the supply chain
    • Means of influencing staff, suppliers, customers, communities and/or any other appropriate stakeholders with respect to modern slavery risks relating to the contract

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

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

    • Understanding of employment and relevant skills issues, and of the education and training issues relating to the contract. Illustrative examples: demographics, skills shortages, new opportunities in high growth sectors, geographic/local community and skills/employment challenges
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Delivery of apprenticeships, supported internships and T Level industry placement opportunities (Level 2, 3 and 4+) in relation to the contract

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

    Policy Outcome 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
    • Understanding of local demographics, needs and opportunities for the co-design of the goods, services and works to be delivered under the contract
    • Measures to involve local stakeholders and/or users in design (e.g. in the design of services, systems, products or buildings)

  • 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

  • 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 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 recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
    • Offering a range of quality opportunities with routes of progression if appropriate, e.g. T Level industry placements, students supported into higher level apprenticeships.
    • Working conditions which promote an inclusive working environment and promote retention and progression
    • Other measures to provide equality of opportunity for disabled people and those with health conditions into employment, including becoming a Disability Confident employer and inclusion of supported businesses in the contract supply chain

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

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