AARAV SOLUTIONS EUROPE LTD

Odoo Consultancy - AI platforms

Aarav Solutions delivers Odoo ERP as a fully managed SaaS, hosting, securing, and operating your platform while providing consulting, implementation, migration, customization, and integrations. Backed by 12+ years’ experience and 120+ certified ERP specialists, Aarav tailors Odoo across finance, sales, inventory, HR, and projects to automate end‑to‑end operations for enterprises.

Features

• Aarav’s Odoo SaaS supports consulting and requirements analysis aligned.
• ​Aarav’s Odoo SaaS enables configurable workflow implementation with budget-conscious delivery.
• ​Aarav’s Odoo SaaS supports legacy-data migration and other ERP integration.
• Aarav’s Odoo SaaS supports customization and modular integration
• ​Aarav’s Odoo SaaS enables functional training and user adoption
• ​Aarav’s Odoo SaaS supports custom modules and advanced automation
• ​Aarav’s Odoo SaaS enables eCommerce with integrated CRM and accounting.
• ​Aarav’s Odoo SaaS supports finance, sales, HR, inventory & manufacturing
• ​Aarav’s Odoo SaaS enables centralized workflows with rules-based approval routing.
• Service supports continuous optimization with knowledge transfer and capability building.

Benefits

• Aarav’s Odoo SaaS enables 6-week eCommerce launch for online stores.
• ​Aarav’s Odoo SaaS reduces inventory errors 25% through consolidation platform.
• Aarav’s Odoo SaaS lowers operating costs 20% via automation integration.
• Aarav’s Odoo SaaS enables faster approvals, reducing PO turnaround time.
• Aarav’s Odoo SaaS eliminates silos, enabling single source of truth.
• Aarav’s Odoo SaaS improves customer experience with seamless payments, personalization.
• Aarav’s Odoo SaaS enables flexible pricing and reliable on-time delivery.
• Service reduces manual work via automation, minimizing errors.
• ​Aarav’s Odoo SaaS enables transparent compliance controls supporting financial discipline.
• ​Aarav’s Odoo SaaS supports scalable growth from SMBs to enterprises.

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

Framework

G-Cloud 15

Service ID

629038116587125

Contact

Bhavin Patel
+447904047484
bhavin.patel@aaravsolutions.com

About your service

• Service categories:

  Application Development and Deployment

  AI platforms

  AI life cycle

  • AI Build Software
  • Trustworthy AI Software

  AI software services

  • Conversational AI Software Services
  • Computer Vision AI Software Services
  • Generative AI Software Services
  • Document AI Software Services
  • Anomaly Detection AI Software Services
• Multi cloud support: Yes

Service scope

• Software add-on or extension: Yes
• What software services is the service an extension to: Implementation and support of Commercial Off-the-Shelf Software Solutions for CRM, ERP and Revenue Management across Industries
• Cloud deployment model:
  • Public cloud
  • Private cloud
  • Hybrid cloud
• Service constraints: Aarav’s Odoo SaaS is delivered as a standardised, managed service. Planned maintenance windows may be required for platform upgrades, security patching, and performance tuning. Some deep server-level changes (kernel, database engine internals, custom OS agents) are not exposed to end users because hosting is managed. Customisations are supported through configuration, approved extensions, and controlled release processes to protect upgradeability. Integrations may require customer-owned API access, credentials, and third‑party vendor cooperation. Data migrations depend on source system quality and availability. Service scope and response targets are defined in the contracted support tier.
• System requirements:
  • Modern web browser supporting TLS 1.2+ and JavaScript enabled.
  • Reliable internet connectivity for web access and API integrations.
  • Customer-managed endpoint protection on user devices accessing the service.
  • Unique named user accounts; shared logins not permitted.
  • Customer email domain access for invitations, alerts, and password resets.
  • Ability to allowlist SaaS URLs/IPs if customer uses firewalls.
  • API-capable middleware/ETL tool for complex legacy integrations.
  • Supported file import tools for CSV/XLSX data loading.
  • Customer-owned SSO/IdP if SSO is required.
  • Supported mobile device OS for Odoo mobile app usage.

User support

• Email or online ticketing support: Yes
• Support response times: P1: 30 mins / 8 Hrs; P2: 60 mins / 24 Hrs; P3: 2 Hrs / 36 Hrs; P4: 4 Hrs / 48 Hrs; ; Service is not available on the weekends.
• 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: Yes
• Web chat support availability: 9 to 5 (UK time), Monday to Friday
• Web chat support accessibility standard: EN 301 549
• Web chat accessibility testing: Not applicable
• Onsite support: Yes, at extra cost
• Support levels: - We provide two levels of support: Hypercare and on-going support. ; - Support Duration: 1 Months; 8x5 on Weekdays [Mon-Fri]; On-call Support on Weekends [Sat-Sun]; - Ticket Logging: Helpdesk App/Email; - Other Operations: Bug fixing & Resolution; Issue Resolution; Maintain and publish a support roster to the Customer Operations team; Publish an escalation matrix.; Run a Status call with your Project Team; Track the Open Issue for resolution; Regular updates, security patches, and enhancements to both core and customised features.; Clear release notes and updated training materials with each significant update.; Responsive support for troubleshooting, bug fixes, and workflow optimisation.; Optional development packages for new features or integrations outside the initial project scope, cost and scheduled as separate work packages.
• Support available to third parties: No
• AI chatbot: No

Onboarding and offboarding

• Getting started: Aarav will conduct the following training or knowledge transfer during the System Integration Phase and before the User Acceptance Testing. The tables below state the training details: ; ; - Training will cover the following: ; -- Functional understanding of the Architecture; -- Functional understanding of the application. ; -- Day operations and maintenance work that is required to be performed on these applications. ; -- User Administration-related activities; -- Job Schedule and List. ; -- Troubleshooting of issues & possible resolutions. ; - No of Participants: 10; - Type of training: Instructor-led training; - Mode: Online/Offline; - No of Days: Depends on the requirements, but generally for 2 weeks; - No of Sessions: 1 session per day of 2-4 hours ; - Training Language (Sessions): English; - Training material: English
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: Before the contract end, Aarav schedules an agreed exit window to provide a final data extract and (if contracted) an assisted migration pack. Exports include transactional records, master data, and attachments where technically feasible, plus configuration documentation and agreed custom developments. Users validate the extract in a staging location. After confirmation, access is removed according to the offboarding plan, and residual data is retained or securely deleted per contractual retention terms. If users require additional transformation or loading into a new ERP, that assistance is provided as a separately scoped professional service.
• End-of-contract process: Included in contract price: hosting/operations for the subscribed period, standard support per tier, routine maintenance (patching/updates), monitoring, and agreed backups/restore processes. At contract end, included activities are account closure, access revocation, and one standard export package (as defined in the order form). Additional cost items: bespoke export formats, large-scale historical exports, assisted data transformation/mapping, third-party integration rework, custom report redevelopment, extended retention, and any accelerated timelines outside standard offboarding windows. If the customer requests on-site workshops, complex re-architecture, or parallel-run support, these are charged separately.
• Documentation accessibility standard: WCAG 2.2 A

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
• Application to install: Yes
• Compatible operating systems:
  • Android
  • IOS
  • Linux or Unix
  • MacOS
  • Windows
  • ChromeOS
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: Platform Access: Native mobile apps for Android and iOS are exclusive to Odoo Enterprise. Desktop users typically access Odoo via a standard web browser on Windows/macOS.; Hardware Integration: The mobile service leverages device features like barcode scanning via the camera and biometric login (fingerprints), whereas the desktop relies on peripherals like external scanners and keyboards.; User Interface: Mobile uses a touch-optimized portrait layout with vertical navigation; desktop offers a more expansive landscape interface with multi-level menus and hover actions.; Offline Functionality: Mobile apps provide superior offline capabilities for field work, while desktop service is designed for stable, high-speed internet environments.
• Service interface: Yes
• User support accessibility: WCAG 2.2 A
• Description of service interface: Users can access Aarav’s Odoo SaaS through a web-based Odoo interface, organised by apps (for example Accounting, Sales, Inventory, HR, Projects) with role-based menus, dashboards, and list/form views. Administration is provided through a managed console for configuration, users, permissions, and integrations, with change control for customisations and releases. Support is delivered via service desk channels (ticketing/email) and agreed escalation paths, plus optional governance calls for continuous improvement. Integrations use standard APIs and scheduled imports/exports. User enablement includes guided training and documentation aligned to configured workflows.
• Accessibility standards: EN 301 549
• Accessibility testing: Screen Reader Compatibility: The interface is designed to work with screen readers such as NVDA, JAWS, and VoiceOver.; Keyboard-Only Navigation: Odoo supports navigation via keyboard-only, including focus indicators for interactive elements.; WCAG 2.2 Compliance: Odoo is moving toward meeting Web Content Accessibility Guidelines (WCAG) 2.2 Level A & AA, as well as Section 508 and EN 301 549 standards.; Visual Adjustments: The platform supports high-contrast modes and screen magnification to assist users with visual impairments.
• API: Yes
• What users can and can't do using the API: Users can use Odoo’s external APIs to integrate Aarav’s Odoo SaaS with other systems for automated data exchange, but they cannot bypass Odoo’s security model or perform restricted platform administration via API.; ​What users can do via API: ; Authenticate and connect using Odoo’s remote procedure call interfaces (XML-RPC/JSON-RPC patterns used by Odoo integrations).; Read and write business records (for example customers, orders, invoices) when their user role permits it, using standard model operations (create/read/update/delete).; Configure “service setup” elements that are inside Odoo application scope (for example master data, products, price lists, users, and access within granted admin roles).; ​What users can’t do via API (limitations): ; Cannot override access rights or record rules; all API calls are constrained by Odoo ACLs and record rules applied per operation.; Cannot access data outside their permitted company/records if record rules restrict it.; Cannot perform Aarav-managed platform operations (hosting, backups, patching, infrastructure scaling) via customer API, as these are controlled by the SaaS operator.; ​Change management through API; Users can automate changes to Odoo configuration and transactional data via API only within their authorised permissions; higher-risk changes (role elevation, bulk deletes, sensitive exports) are governed by Aarav’s support/change control processes.
• API documentation: Yes
• API documentation formats:
  • Open API (also known as Swagger)
  • HTML
  • PDF
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Users can customise Aarav’s Odoo SaaS mainly through Odoo configuration, low-code tools (where licensed), and controlled extensions, while all changes remain governed by role-based access rights and record rules.; ; ​What can be customised: ; - Business workflows: stages, approval flows, automated actions, routing rules.; - Data model elements: custom fields, labels, and screen layouts/views.; - Reporting outputs: templates and report layouts (where supported).; - Security and access: user groups, permissions, and record-level visibility rules.; - Integrations: API-based connections, scheduled imports/exports, webhooks/middleware.; ; ​How users can customise: ; - No/low-code: Odoo’s Studio capabilities to add fields and modify views/reports (Enterprise feature, where licensed and enabled).; - Configuration: adjust settings within each Odoo app (Sales, Accounting, Inventory, etc.) using standard menus.; - Controlled development: custom modules and deeper changes are delivered via an agreed change process to protect stability and upgradeability.; ​; Who can customise; - Customer admins can configure apps and manage users within granted rights.; - Power users can tailor personal views/filters if permitted by access rules.; - Aarav engineers perform advanced custom development and platform changes under governance, because Odoo security rules apply and must not be bypassed.

Scaling

• Independence of resources: Aarav’s Odoo SaaS uses tenant isolation and capacity controls so one customer’s workload cannot starve another. Each tenant is provisioned with defined resource reservations and scaling rules, and noisy-neighbour risks are mitigated through workload separation, quotas, and performance monitoring. Background jobs are controlled to avoid peak-time contention, and heavy integrations are scheduled or throttled. If sustained growth requires higher capacity, the tenant can be moved to a larger plan or dedicated resources. Performance baselines are measured and reviewed, and corrective actions (indexing, archiving, tuning) are applied under change control.

Analytics

• Service usage metrics: Yes
• Metrics types: Aarav provides service reporting aligned to the support tier, typically including: user activity, job/scheduler health, integration queue status, background worker performance, database/storage consumption, and error rates. Operational dashboards track response times for key transactions (for example, login, search, posting), and alerting is configured for threshold breaches and failed jobs. Monthly service reports can include incident counts, change releases, and capacity trends. For customers needing deeper observability, logs/metrics can be forwarded to a customer SIEM/monitoring platform under an agreed design, ensuring auditability and operational transparency.
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: Yes
• FOCUS resource tagging: Yes

Resellers

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

Staff security

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

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations:
  • United Kingdom
  • European Economic Area (EEA)
• User control over data storage and processing locations: Yes
• Datacentre security standards: Supplier-defined controls
• Penetration testing frequency: At least once a year
• Penetration testing approach: NCSC approved service provider
• Protecting data at rest:
  • Physical access control, complying with CSA CCM v4.0
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • Encryption of all physical media
• Data sanitisation process: Yes
• Equipment disposal approach: A third-party destruction service
• Data sanitisation type:
  • Deleted data can’t be directly accessed / Cryptographic Erasure
  • Data Erasure
  • Explicit overwriting of storage before reallocation / Secure Erase

Data importing and exporting

• Data export approach: Users export data from Odoo screens (list views/reports) and via integration APIs, depending on the module and use case. Operationally, Aarav supports scheduled exports for agreed datasets (for example, accounting extracts, inventory snapshots, order feeds) to customer endpoints using secure transfer and controlled credentials. For full exit, Aarav provides a consolidated export pack aligned to the customer’s data dictionary and validates completeness with sampling. Exports can be delivered to a customer-controlled storage location (SFTP/object storage) with checksum verification. If required, Aarav also supports incremental exports during transition.
• Data export formats:
  • CSV
  • Other
• Other data export formats: Excel/XLSX
• Data import formats:
  • CSV
  • Other
• Other data import formats: XLSX

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)
  • IPsec or TLS VPN gateway

Availability and resilience

• Guaranteed availability: Aarav’s Odoo SaaS uses tenant isolation and capacity controls so one customer’s workload cannot starve another. Each tenant is provisioned with defined resource reservations and scaling rules, and noisy-neighbour risks are mitigated through workload separation, quotas, and performance monitoring. Background jobs are controlled to avoid peak-time contention, and heavy integrations are scheduled or throttled. If sustained growth requires higher capacity, the tenant can be moved to a larger plan or dedicated resources. Performance baselines are measured and reviewed, and corrective actions (indexing, archiving, tuning) are applied under change control.
• Approach to resilience: Aarav designs the service for resilience using redundancy across critical layers: application services, database, storage, and network. Backups are automated, tested, and protected with access controls; recovery procedures are rehearsed to meet documented RPO/RTO targets agreed per tier. Production deployments use rolling updates to reduce downtime and separate non-production environments to reduce change risk. Capacity management and autoscaling policies are used to absorb predictable spikes (for example, month-end posting) while protecting steady-state performance. Datacentre/region resilience depends on the contracted hosting model: shared HA deployment, or optional multi-zone/multi-region architecture for higher assurance. The detailed datacentre topology, failover design, and recovery runbooks can be shared with buyers on request under NDA, including evidence of backup frequency, retention, and restoration testing aligned to “asset protection and resilience” expectations.
• Outage reporting: Aarav reports outages through: (1) service desk notifications (email) to nominated contacts, (2) ticket updates at defined intervals during active incidents, and (3) a post-incident report for severity-one events that includes timeline, impact, root cause, and corrective actions. Where available, a customer-facing status page can be provided to show current service state and incident updates, and webhooks/API-based notifications can be enabled for customers who want automated incident intake into their ITSM tooling. For planned maintenance, advance notices are issued with a window, expected impact, and rollback approach. Escalation paths (including an emergency channel for critical production impact) are defined in the support schedule.

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)
  • Username or password
• Access restrictions in management interfaces and support channels: Management access is restricted through least-privilege RBAC, segregation of duties, and controlled admin roles. Administrative interfaces enforce MFA, strong password policy, and conditional access controls. Support channels verify requester identity before acting on account changes, exports, or permission updates, using approved contacts and ticket-based authorisation. Sensitive actions (for example, role elevation, data extract initiation, integration credential changes) require explicit approval and are logged. Customer admins are limited to business configuration and user management within their tenant, while platform operations remain with Aarav. Access reviews are performed periodically, and accounts are disabled promptly on offboarding.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password

Audit information for users

• Access to user activity audit information: Users receive audit information on a regular basis
• How long user audit data is stored for: At least 12 months
• Access to supplier activity audit information: Users receive audit information on a regular basis
• How long supplier audit data is stored for: At least 12 months
• How long system logs are stored for: At least 12 months

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: Our Security Policy requires protecting all company assets from harm. Key processes include a Clear Desk Policy, regular data backups, secure material disposal, using strong passwords, locking computers, Multi-Factor Authentication (MFA) for email, and caution with suspicious emails/links. The Security Policy is binding on all staff. For reporting, immediately notify the Help Desk, Security, or Admin if a virus is suspected, or a device is lost or stolen. Compliance is ensured through the binding policy and individual employee responsibility.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Supplier-defined controls
• Configuration and change management approach: Aarav tracks Odoo service components through version-controlled configuration management covering modules, custom fields, workflows, automated actions, access rights, record rules, and integrations. Changes are documented in a change register and assessed for security impact by reviewing access right modifications, record rule changes, integration credential updates, data exposure risks, and workflow alterations that could bypass controls. Aarav uses staged deployment (development → staging → production) with documented change requests, impact analysis, security review, user acceptance testing, and rollback plans. High-risk changes (privilege elevation, bulk data operations, security rule modifications) receive additional scrutiny and customer approval before production release.
• Vulnerability management type: Supplier-defined controls
• Vulnerability management approach: Potential threats from; Aarav maintains a vulnerability management lifecycle covering detection, triage, remediation, and verification. Threat intelligence sources include vendor advisories, CVE feeds, dependency scanning, and security researcher reports; Odoo also operates a public vulnerability disclosure channel via HackerOne. Patches are prioritised by severity and exploitability, with emergency changes accelerated under a defined change process and standard patches released in scheduled windows. Fixes are validated in staging, deployed using controlled releases, and confirmed through rescans and functional checks. Customer-impacting vulnerabilities trigger customer advisories and compensating controls where patching requires downtime.​
• Protective monitoring type: Supplier-defined controls
• Protective monitoring approach: Aarav uses centralized logging and alerting to identify compromise indicators including unusual authentication patterns (failed logins, off-hours access), privilege escalations, suspicious data exports, abnormal database queries, unauthorized module installations, and integrity anomalies. When potential compromise is detected, Aarav triggers incident triage, immediate containment (session termination, credential rotation, IP blocking), forensic log preservation, and root-cause investigation. Response times follow contracted incident severity targets: critical security events (active breach, data exfiltration) receive 24x7 immediate response under enhanced support tiers, while lower-severity events follow standard incident windows. All security events are logged, ticketed, and reported to customers with remediation actions.
• Incident management type: Supplier-defined controls
• Incident management approach: Aarav tracks Odoo service components through version-controlled configuration management covering modules, custom fields, workflows, automated actions, access rights, record rules, and integrations. Changes are documented in a change register and assessed for security impact by reviewing access right modifications, record rule changes, integration credential updates, data exposure risks, and workflow alterations that could bypass controls. Aarav uses staged deployment (development → staging → production) with documented change requests, impact analysis, security review, user acceptance testing, and rollback plans. High-risk changes (privilege elevation, bulk data operations, security rule modifications) receive additional scrutiny and customer approval before production release.
• Post-quantum cryptography secure: No

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: No

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

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

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: AMERICO QUALITY STANDARDS REGISTECH PVT. LTD
• ISO/IEC 27001 accreditation date: Tuesday 14 October 2025
• What the ISO/IEC 27001 doesn’t cover: Parts covered are: Global product engineering, digital transformation & enablement services, mobility solutions, revenue & customer management, IaaS, managed services, emerging technologies, IT consulting and home-grown product range to telecommunications, banking, finance, government, power and utilities among various other B2B segments.
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: AMERICO QUALITY STANDARDS REGISTECH PVT. LTD
• ISO 9001 accreditation date: Tuesday 14 October 2025
• What the ISO 9001 doesn’t cover: Parts covered are: Global product engineering, digital transformation & enablement services, mobility solutions, revenue & customer management, IaaS, managed services, emerging technologies, IT consulting and home-grown product range to telecommunications, banking, finance, government, power and utilities among various other B2B segments.
• 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: 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
    • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
    • Plans to engage the contract workforce in deciding the most important workplace issues to address
    • Monitoring of employee engagement rates (by protected characteristic) and, where necessary, the development of actions to ensure all voices are heard across the diversity of the workforce
    • 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
    • Offer a pay and leave entitlement to all eligible staff who become kinship carers, ideally equivalent to statutory adoption pay and leave
    • 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
    • Entitlement to sick pay for the contract workforce, with provision in place for any staff who do not meet the earnings threshold for statutory sick pay, payment of sick pay from day one of absence and payment of staff on the contract workforce who are off sick a replacement income of 100% of their usual earnings for as long as possible
    • Understanding of in-work progression issues affecting the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
    • Measures to support in-work progression to help people in the contract workforce, to move into higher paid work by developing new skills relevant to the contract
    • Support for the contract workforce by providing career advice, and providing opportunities for staff working on the contract with in-work progression career development into known skills shortages or high growth areas
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Volunteering opportunities for staff
    • Understanding of the modern slavery risks and issues affecting the market, industry, sector or country (of origin or of source) relevant to the contract, and the workforce in the supplier’s own organisation and those of its key subcontractors

  • 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

  • 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

  • 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
    • 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
    • Inclusive and accessible recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
    • Introducing transparency to pay and reward processes
    • Working conditions which promote an inclusive working environment and promote retention and progression
    • Understanding of the issues affecting inequality in employment, skills and pay in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors. Measures to tackle inequality in employment, skills and pay in the contract workforce
    • Inclusive and accessible development practices, including guidance for line managers on recruiting, managing and developing people with a disability or health condition

  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 7: Creating a pipeline of opportunities: For the contract workforce, reducing barriers to entry for under-represented groups.

    • Understanding of the issues affecting the development of new skills by target cohort
    • Understanding of the underlying factors affecting improvements to reduce barriers to entry and training schemes for the target cohort(s) related to the contract workforce
    • Understanding of issues relating to entering the contract workforce

  • Mission: Build an NHS fit for the future: That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.

    Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.

    • Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
    • Understanding barriers to access to health and social care services or employment opportunities e.g. digital inclusion
    • Inclusive and accessible recruitment practices, development practices and retention policies that support-focused activities including those provided in the Guide for line managers on recruiting, managing and developing which support people with a disability or health condition

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