uTrack Software Solutions

Origin

Origin is a cloud-based real-time operational software platform that consolidates and aggregates data sources from systems used by bus operators. It offers historical and real-time analysis on punctuality, driver performance, timetable and duty optimisation data but also incident management and analytics and business statistics of entire operations.

Features

• Real-time information and Live map tracking, map view
• Vehicle Punctuality, efficiency and demand data visualisation and analytics
• Driver performance data visualisation and analytics
• Timetable and Duty optimisation
• Passenger Punctuality data visualisation and analytics
• Incident Management
• 3rd party data (ticketing, scheduling, GPS etc) aggregation and analytics
• Live ETA prediction
• Operator and route benchmarking

Benefits

• Comprehensive operator performance and network overview
• All data aggregated into single platform
• Hardware and software agnostic, avoid supplier lock-in
• Existing integrations with all common system suppliers
• Track all bus departures and see common delays
• Inform your passengers about delays in real-time
• Identify the root cause of any operational issues
• Make data-driven decisions
• Simple reporting and data export in all common formats

• Education pricing available
• Free trial available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at argo.verk@ridango.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

973698629508005

Contact

Argo Verk
07957330857
argo.verk@ridango.com

About your service

• Service categories:

  Application Development and Deployment

  Analytics and business intelligence

  • Location and geospatial data management and analytics
• Multi cloud support: No

Service scope

• Software add-on or extension: No
• Cloud deployment model: Public cloud
• Service constraints: The Origin platform has been designed to run on a 24/7/365 principle with an uptime of at least 99%. Customers are notified well in advance of all scheduled updates and system maintenance activities, which are planned to take place during periods when bus operations are least affected. As Origin is a cloud-based platform, remote support is sufficient and typically provided during standard business hours. Any incidents or service interruptions are logged, monitored and addressed outside normal business hours to minimise operational impact and maintain service availability.
• System requirements:
  • Data from existing 3rd party systems
  • Ticketing data
  • Scheduling data
  • AVL (Automatic Vehicle Location) data

User support

• Email or online ticketing support: Yes
• Support response times: Standard response time for customer questions is within one (1) Business Day, defined as Monday to Friday, 9 am to 5 pm. Resolution times vary depending on the priority and complexity of the issue and are managed in line with agreed Service Level Agreements. Support is available through email and phone channels. Where issues are deemed critical, response and resolution activities may be provided outside standard business hours. Urgent issues are prioritised to minimise operational impact and restore service as quickly as possible.
• 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: No
• Support levels: N/A
• Support available to third parties: No

Onboarding and offboarding

• Getting started: Buyers can tailor the service primarily through configuration rather than code changes, providing flexibility while maintaining platform stability and upgradeability. Authorised users are able to configure operational parameters including operators, depots, vehicles, routes, services, stops, calendars, and integration settings.; ; Users may define business rules, thresholds, alerts, reporting views, and data filters, and can enable or disable specific features according to their assigned role. All configuration is role-based and permission-controlled, ensuring that only approved users can make changes within their defined organisational scope.; ; Where applicable, branding options are available, including customer-specific naming conventions and visual identifiers within user-facing interfaces and reports.; ; Customisation does not extend to core platform logic, security controls, or shared system components. Structural changes, bespoke workflows, or non-standard integrations require supplier involvement and are delivered through a controlled change management process.; ; Configuration-based customisation does not impact support or upgrade processes. All customers operate on a common, fully supported platform version, with updates applied consistently and regularly across the service.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
  • Other
• Other documentation formats: Online Knowledge Base and Guides
• End-of-contract data extraction: At contract end, buyers are able to extract all customer-owned data created, processed, or stored within the service. This includes operational and reference data such as vehicles, routes, services, stops, configuration settings, user accounts, and audit logs, as well as historical operational data including AVL location data, journey records, and performance and service metrics.; ; Data extraction is carried out using documented export processes and secure transfer methods. Data can be provided in standard, open formats such as CSV, JSON, or other commonly used formats, allowing the data to be reused in alternative systems without reliance on proprietary technologies.; ; Extraction may be requested during the contract term or as part of the offboarding process, subject to agreed notice periods. Support is available to assist with planning, scoping, scheduling, and validating data exports.; ; Once data extraction is completed and confirmed, access to the service is securely removed. Customer data is securely deleted or retained where required, meeting legal, regulatory, or contractual obligations.; ; There are no restrictions on data ownership or the buyer’s ability to reuse their data. Any limitations apply only to reasonable operational considerations, including data volumes, retention policies, and statutory requirements, ensuring a controlled exit process with no vendor lock-in.
• End-of-contract process: The contract concludes in accordance with the agreed terms and notice period. Throughout the notice period, the service continues to operate normally, allowing buyers sufficient time to plan transition activities, complete data extraction, and offboard users in a controlled and orderly manner.; ; Support is available at contract end to assist with exit planning, data scoping, scheduling and executing data exports, and confirming successful completion. User access remains available during the notice period and is securely removed at contract termination using role-based access controls.; ; All customer data remains the property of the buyer at all times. Buyers may extract their data prior to contract end using documented export processes and secure transfer methods. Data is provided in standard, open formats such as CSV and JSON, enabling reuse in alternative systems without reliance on proprietary tools or technologies.; ; Once data extraction has been completed and confirmed by the buyer, customer data is securely deleted or retained only where required by law or contractual obligation, in accordance with GDPR and applicable data protection requirements.; ; There are no exit penalties, technical barriers, or vendor lock-in. Standard end-of-contract and offboarding activities are documented and included, providing buyers with a clear, predictable, and compliant exit process.
• Documentation accessibility standard: WCAG 2.2 AA

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: Yes
• Differences between the mobile and desktop service: The platform is designed for desktop use but remains functional on mobile devices. It is delivered through a browser-based interface and does not require an application. The user interface is optimised for desktop and tablet use, and functionality on smaller mobile screens may be limited. Tablet or larger display recommended.
• Service interface: Yes
• User support accessibility: None or don’t know
• Description of service interface: The Origin platform is accessible through all commonly used web browsers and does not require local installation. After logging in, users are presented with map and list views displaying all configured routes, vehicles and services. The interface is designed to be intuitive, with clear menu structures and easily selectable on-screen controls. Users can view real-time operational status as well as historical data across routes, trips and vehicles, supporting detailed analysis and organisation-wide operational insight. The landing page also provides access to a concise, user-friendly manual supporting effective use of the interface.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: No testing has been done with users of assistive technology.
• API: Yes
• What users can and can't do using the API: The Origin platform provides a production-grade REST API that uses JSON over HTTPS and exposes clearly versioned endpoints. The API is designed for use by transport authorities, operators and approved third-party integrators, supporting secure system integration, automation and data exchange.; ; Authorised users retrieve a wide range of operational and reference data, including information on vehicles, services, routes, stops, operators and depots. The API also allows access to real-time and historical datasets such as automatic vehicle location (AVL) positions, journey progress, event and incident logs, and performance or compliance metrics. Where explicitly enabled and contractually agreed, users may submit or update selected operational data, including vehicle assignments, configuration records and approved integration feeds, to support live operations, reporting and interoperability with external systems such as AVL, RTPI, ticketing platforms, GTFS-RT and SIRI.; ; Users cannot access data beyond their assigned organisation, contract or role permissions. The API doesn't allow cross-tenant access, modification of core system logic, or execution of administrative or security-sensitive actions unless explicitly authorised.; ; API access is secured using authentication tokens or keys and enforced over HTTPS. Role-based permissions, logging and monitoring apply to all API activity. Rate limits, payload restrictions and approval processes govern write access and high-volume integrations.
• API documentation: Yes
• API documentation formats:
  • Open API (also known as Swagger)
  • HTML
• API sandbox or test environment: Yes
• Customisation available: No

Scaling

• Independence of resources: Each customer is deployed to its own virtual server environment, providing strong isolation of compute, storage, and data. This ensures one buyer’s activity cannot impact another’s performance or availability. The service is professionally operated with defined service levels for availability and performance, supported by continuous monitoring and alerting. Capacity is actively managed, and environments can be scaled to handle peak demand or sudden increases in usage. Rate limiting and workload controls protect system stability. In the event of unexpected demand spikes, additional resources are provisioned in line with SLA commitments to maintain a consistent and reliable service for all customers.

Analytics

• Service usage metrics: Yes
• Metrics types: The service provides a range of operational and usage metrics to support visibility and oversight. Metrics include user activity, system usage, data volumes, integration health, service availability, and performance indicators such as processing latency and data freshness. Where applicable, operational metrics such as vehicle activity, journey volumes, and event counts are also available. Metrics are updated in near real time or on a scheduled basis, depending on the metric type, and are accessible to authorised users only. Metrics can be viewed online and exported for analysis and reporting.
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: Yes
• FOCUS resource tagging: No

Resellers

• Supplier type: Not a reseller

Staff security

• Staff security clearance: Other security clearance
• 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
  • European Economic Area (EEA)
• 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: ‘IT Health Check’ performed by a CHECK service provider
• Protecting data at rest:
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Other
• Other data at rest protection approach: Data at rest within the Origin platform is protected using encryption, access controls, and secure cloud infrastructure.; ; Stored customer data is encrypted-at-rest using AWS-managed encryption services and industry-standard cryptographic algorithms. Encryption keys are managed using AWS Key Management Service, supporting controlled access, key rotation, and audit logging.; ; Physical access to storage infrastructure is restricted by AWS through secure datacentre environments.; ; Data access is limited using role-based access control and least-privilege principles.; ; Additional controls:; • Encrypted backups stored in protected environments.; • Segmented customer environments.; • Logging and monitoring data access.; ; Protections operate within Ridango’s ISO:27001-certified information security management framework.
• Data sanitisation process: Yes
• Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001
• Data sanitisation type:
  • Deleted data can’t be directly accessed / Cryptographic Erasure
  • Data Erasure
  • Explicit overwriting of storage before reallocation / Secure Erase

Data importing and exporting

• Data export approach: Users can request a data export at any time by raising a ticket through the service support desk. This ensures appropriate validation, security checks, and controlled delivery.; ; Buyers can export all customer-owned data, including operational, configuration, user, and historical data such as journey and performance records. Data is provided in standard, non-proprietary formats including CSV and JSON, enabling straightforward reuse in alternative systems. Exports can be requested during the contract term or as part of offboarding. Support is provided throughout the process to agree scope, timelines, and confirm successful delivery, ensuring buyer control with no technical barriers or vendor lock-in.
• Data export formats:
  • CSV
  • Other
• Other data export formats: JSON
• Data import formats:
  • CSV
  • Other
• Other data import formats:
  • TXC (XML)
  • VDV
  • Excel Template
  • JSON
  • GTFS (txt files)

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • 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: The service is delivered with a guaranteed availability of 99.95% per calendar month, excluding planned maintenance. Availability is measured on a monthly basis and applies to the core service components as defined in the service description.; ; Planned maintenance windows are scheduled outside of peak operational hours wherever possible and are communicated to customers in advance. Emergency maintenance may be carried out where required to protect service security or stability.; Availability and performance are continuously monitored using automated monitoring and alerting systems. The service is professionally operated with defined incident management and support processes in place. In the event of service disruption, incidents are prioritised, investigated, and resolved in line with agreed support procedures.; ; Exclusions to availability calculations include planned maintenance, customer-caused issues, force majeure events, and failures of third-party networks or services outside the supplier’s reasonable control. This approach provides a clear, realistic, and transparently managed availability commitment.
• Approach to resilience: The service is hosted on professionally managed cloud infrastructure, with each customer deployed to a dedicated virtual server environment to ensure isolation and resilience. The platform is designed to minimise single points of failure through layered architecture, including separate application, data, and integration components, protected by network controls and monitoring.; ; Data is protected through regular automated backups, secure storage, and defined retention policies. Backups are tested periodically to ensure data can be restored when required. Service availability and performance are continuously monitored using automated health checks, logging, and alerting, allowing issues to be detected and addressed promptly.; ; If a fault occurs, incidents are managed through defined operational procedures, including triage, investigation, and remediation. Where required, services can be restarted, scaled, or restored in line with support and availability commitments. Customers are kept informed of significant incidents in accordance with support processes.; ; Resilience is reviewed regularly as part of operational management and security governance. This includes testing backup restoration, reviewing incident trends, and assessing the impact of platform changes. This planned, monitored approach ensures failures are anticipated, recovery is controlled, and the service remains reliable and professionally operated.
• Outage reporting: Service availability is continuously monitored using automated health checks, logging, and alerting across all core service components. Potential outages or service degradation are detected automatically and escalated to on-call support staff for immediate investigation.; ; When an outage affecting users is confirmed, customers are notified promptly, typically within 15 minutes, using agreed communication channels such as email or in-service notifications. Initial communications include a description of the issue, affected services or users, current status, and any available workarounds.; ; For incidents that extend beyond initial resolution efforts, regular progress updates are provided at defined intervals until service is restored. These updates communicate changes in impact, actions being taken, and estimated restoration times where available.; ; Once the service is fully restored, customers are informed and normal operations are confirmed. For significant incidents, a post-incident summary is available on request. This includes an overview of the incident, root cause, resolution actions, and any preventative measures implemented.; ; Outage reporting is governed by documented incident management procedures, ensuring timely communication, transparency, and a consistent, professional approach that supports customer confidence.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
• Access restrictions in management interfaces and support channels: Access to Origin management interfaces is controlled using role-based access control, least-privilege principles, and privileged access management. Administrative access is limited to authorised personnel and managed through formal joiner-mover-leaver processes. Origin supports SSO and MFA via SAML, integrating with enterprise identity providers such as Google Workspace, Microsoft Entra ID (Azure AD), and Okta, allowing customers to enforce their own authentication and conditional access policies. Administrative activity is logged and auditable, with access rights reviewed periodically. Support channels are restricted to approved uTrack staff and verified customer contacts. Access to customer data is limited, logged, and monitored.
• 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)
  • 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: Between 6 months and 12 months
• Access to supplier activity audit information: Users contact the support team to get audit information
• How long supplier audit data is stored for: Between 6 months and 12 months
• How long system logs are stored for: Between 6 months and 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: UTrack operates a structured information security management framework to protect the confidentiality, integrity, and availability of customer and operational data processed within the Origin platform.; ; We maintain a comprehensive set of documented information security policies covering access control, data protection, secure development, incident management, vulnerability management, supplier assurance, and acceptable use. Policies are reviewed and updated regularly to ensure alignment with security risks, regulations, and operational changes.; ; System access and customer data are controlled using role-based access control and least-privilege principles, supported by formal joiner, mover, and leaver processes. Data is protected through encryption (in transit and at rest) with monitoring and logging controls to support detection, investigation, and response to security events.; ; Security is embedded through secure coding standards, peer review, controlled change management, and timely remediation of identified vulnerabilities. This includes patch management, dependency assessment, and periodic security testing.; ; Security incidents are managed through detection, escalation, investigation, and remediation, with lessons learned creating improvement.; ; Supplier security is assessed as part of third party risk management activities, and business continuity and disaster recovery planning incorporates information security and data protection requirements.; ; Information security controls and processes are aligned with recognised industry best practice, including the principles of ISO/IEC 27001.
• 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: Configuration and change management is operated in line with our Information Security Management System (ISMS), aligned to ISO/IEC 27001.; ; Customer-level configuration changes can be made by authorised users using role-based permissions, without impacting shared platform components.; ; Changes affecting core services or controls are managed by the supplier through change control; risk assessment, approval, and testing in non-production environments. Changes are reviewed for security, stability, and operational impact before release.; ; Service updates are deployed using planned release, with backward compatibility maintained where possible. Users are informed in advance of changes through release notes or service notifications. Rollback procedures are in place.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: Vulnerability management operates as a defined, repeatable process within the organisation’s ISO/IEC 27001 aligned Information Security Management System. Vulnerabilities are identified through automated scanning, internal testing, external penetration testing, and supplier or third-party advisories. Issues are assessed, prioritised, and tracked on a risk-based basis, with high-risk and critical vulnerabilities addressed as a priority. Remediation actions are planned, implemented, verified, and tested in non-production environments. Clear ownership is assigned to security and engineering roles. Serious vulnerabilities are mitigated immediately, customers are informed where appropriate, and remediation is tracked to resolution.
• Protective monitoring type: Supplier-defined controls
• Protective monitoring approach: Protective monitoring is delivered through the organisation’s ISO/IEC 27001 aligned Information Security Management System. Continuous monitoring is applied across infrastructure, applications, and networks, including security logging, system health checks, and automated alerts. Monitored events include authentication activity, access control changes, privileged actions, configuration changes, anomalous usage, and API activity. Logs are centrally collected and analysed. Alerts are triaged by designated security and operational staff, with defined escalation and incident response procedures. Monitoring controls and alert thresholds are reviewed regularly to support early detection and ongoing service security.
• Incident management type: Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
• Incident management approach: Ridango operates documented incident management procedures aligned with its ISO/IEC 27001-certified ISMS. The service is hosted on professionally managed cloud infrastructure with dedicated, isolated customer environments and layered architecture to support resilience. Service availability and security events are continuously monitored using automated health checks, logging, and alerting. Incidents are triaged, investigated, and remediated through defined operational processes, including restart, scaling, or restoration from tested backups where required. Customers report issues via controlled support channels and are notified promptly of significant incidents, typically within 15 minutes, with progress updates until resolution. Post-incident summaries are available on request.
• 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: Yes
• Free trial available: Yes
• Description of free trial: 30-minute demo trial of the Origin service, available via booking request form on the utrack website.
• Link to free trial: https://www.utrack.com/request-demo/

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

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

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: No
• ISO 28000:2022 certification: No
• ISO 9001 certification: No
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: No
• Cyber Essentials Alternative: In relation to the services you do not have a current and valid Cyber Essentials certificate which has been awarded by one of the government approved Cyber Essentials accreditation bodies but you are working towards gaining it, and will be in a position to confirm that you have been awarded a current and valid Cyber Essentials certificate by one of the government approved accreditation bodies within 12 months of the date of award.
• 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
    • 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
    • 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
    • Plans for an appropriate income replacement policy for staff who are required to spend time away from work to care for a sick dependent or close relative
    • 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
    • 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
    • How the supplier will work with NGOs, trade unions or other businesses to address modern slavery risk
    • 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
    • Activities to support relevant sector related skills growth and sustainability in the contract workforce. Illustrative examples: careers talks, curriculum support, literacy support, safety talks and volunteering

  • 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
    • Activities to identify opportunities to open up sub-contracts under the prime contract to a diverse range of businesses, including new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Activities that demonstrate a collaborative way to work with a diverse range of businesses as part of the supply chain
    • Ensuring accessibility to contracting and subcontracting opportunities for disabled business owners and employees
    • 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
    • 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)
    • 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
    • Support for community-led initiatives relevant to the contract. Illustrative examples: improving transport links; reducing loneliness; helping with English language proficiency; and facilitating social mixing among people with different backgrounds

  • 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
    • Collection of the views and expertise of disabled people and their representative organisations on successfully supporting disabled employees or applicants
    • 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
    • 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
    • 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
    • Other measures to offer development opportunities for the target cohort(s) in the contract workforce
    • Understanding of issues relating to entering the contract workforce
    • Creation of outreach activities to create a pipeline of employees for the future contract delivery
    • Content of the outreach activity is designed to suit 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
    • Understanding barriers to access to health and social care services or employment opportunities e.g. digital inclusion
    • Inclusive and accessible recruitment practices, development practices and retention policies that support-focused activities including those provided in the Guide for line managers on recruiting, managing and developing which support people with a disability or health condition
    • Actions to invest in the physical and mental health and wellbeing of the contract workforce

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at argo.verk@ridango.com. Tell them what format you need. It will help if you say what assistive technology you use.