CAREBUILDER UK LIMITED

CareBuilder SaaS

CareBuilder is a cloud-hosted Technology Enabled Care platform that strengthens workforce capacity and improves outcomes. It enables remote care, daily living prompts, sensor-driven alerts and two-way video. Dashboards support triage, escalation and response coordination, with action logging for assurance. Organisations reduce avoidable visits, target support and evidence value to commissioners.

Features

• Real time alerts and escalations (triage and match)
• ADL planning, task prompting and monitoring
• Interoperability and API's
• AI Sound (acoustic monitoring)
• Dashboards, reporting & analytics
• Sensors and Devices (IoT)
• Care worker app
• Family portal
• Auto video
• Security and compliance

Benefits

• Greater independence (clients and care givers)
• Supports personalised, consistent care (promotes choice)
• Supports early & timely interventions (Pro-active care)
• Enhanced communication with families and friends (reduces isolation)
• Improved wellbeing and dignity (improved outcomes)
• Reduces the need for in person care (Virtual Care)
• Reduces administration (so more time for care)
• Promotes stronger compliance and evidence
• Helps support and involve the whole care circle (Pillars-of-5)
• Reduces care costs

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

Framework

G-Cloud 15

Service ID

507401211689532

Contact

Colin Foskett
02035197717
info@carebuilder.com

About your service

• Service categories:

  Applications

  Production and operations

  Service industry and public sector operations

  • Healthcare
  • Adult Social Care
• Multi cloud support: No

Service scope

• Software add-on or extension: No
• Cloud deployment model: Public cloud
• Service constraints: Our apps run on Android devices only
• System requirements:
  • Android 14 or above
  • Minimum download speed is 10 Mbps
  • The minimum upload speed is 2 Mbps

User support

• Email or online ticketing support: Yes
• Support response times: Standard support is Monday to Friday - 9am to 5pm GMT; ; Critical - CareBuilder will immediately assess issue &; update Business Owner / Problem Owner within 60 mins and every 60 mins; ; Serious - CareBuilder will immediately assess issue &; update Business Owner / Problem Owner within 60 mins and every 3 hrs; ; For Critical or serious issues we provide a 24/7 telephone helpline
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.2 AA
• Phone support: Yes
• Phone support availability: 24 hours, 7 days a week
• Web chat support: No
• Onsite support: Yes, at extra cost
• Support levels: We provide tiered support to meet different operational needs, from business-hours assistance to 24/7 mission-critical cover. Our service desk operates an ITIL-aligned incident, request, problem, and change process. Customers can raise tickets via web portal, email, or phone. We offer defined SLAs, clear escalation paths, and regular service reporting.; ; We provide the following Support; ; Standard - provide support via ticket based system Mon to Fri 09.00 to 17:00 (excluding public holidays). Included in subscription.; Enhanced - as above but with 24/7 telephone support for Critical and Serious issues. Price is 10% of annual subscription.; Premium - non-standard support. Price is £110 per hour.; A technical account manager is provided for all customers.
• Support available to third parties: No

Onboarding and offboarding

• Getting started: Onsite onboarding and training (where needed): practical set-up support, role-based training for responders, managers and administrators, and a Think-Build-Run-Manage (first live use-case) session to ensure the service works in real conditions.; Online training: live remote sessions for new starters and refreshers, plus short, focused modules for key tasks (e.g., triage, escalation, reporting, device set-up).; User documentation: clear step-by-step guides, quick-start checklists, and standard operating procedures covering daily use, troubleshooting, and safeguarding/escalation pathways.; Implementation playbook: a repeatable plan covering readiness checks, configuration, testing, go-live, and early-life support.; Ongoing support: a helpdesk/service desk, release notes, and periodic service reviews to embed good practice and drive adoption.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: How data is extracted; ; Standard export pack provided on request, covering the agreed in-scope datasets (e.g., user profiles, configurations, audit logs, events/alerts, activity records, reports, and associated metadata).; ; Formats: typically CSV/XLSX for tabular data and JSON for structured records; PDF copies of key reports can be included if required.; ; Delivery: via a secure transfer method (encrypted download link, SFTP, or customer-managed secure storage). Encryption and access controls are applied throughout.; ; Validation: we provide an export manifest (what’s included, date range, field definitions) so customers can reconcile completeness.; ; Assisted extraction: for larger customers, we offer technical support to map fields, confirm joins, and ensure import into the next system is straightforward.; ; After extraction; ; Retention and deletion follow the contract and our retention schedule.; ; We provide written confirmation of deletion/anonymisation once the agreed period has elapsed (subject to any legal or regulatory retention requirements).
• End-of-contract process: At the end of the contract we run a controlled off-boarding process to ensure continuity, secure data handling, and orderly service closure. We confirm termination/non-renewal, agree the end date and off-boarding plan, and identify any operational dependencies (e.g., monitoring, alerting, responder workflows). ; ; We then provide a standard customer data export pack (typically CSV/XLSX for tabular data and/or JSON for structured records, delivered via an agreed secure method (encrypted link or SFTP), with an export manifest so customers can reconcile completeness. Access is restricted on the agreed date and services are wound down in a managed way to avoid unintended gaps. ; ; Where applicable, we agree return/transfer/decommissioning of any equipment and record outcomes. Data is retained only as required by the contract and applicable law, then securely deleted/anonymised, with written confirmation provided.; ; Included in the contract price: standard off-boarding management, one standard export pack, secure transfer, account closure, and deletion confirmation.; ; Additional costs (if needed): custom or repeated exports, accelerated timelines, extensive migration support, onsite support, hardware collection/refurbishment/disposal, and extended data retention beyond standard terms.
• Documentation accessibility standard: WCAG 2.2 AA

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Chrome
• Application to install: Yes
• Compatible operating systems:
  • Android
  • Linux or Unix
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: CareBuilder provides a mobile app optimised for frontline care staff and people receiving care, and a desktop web console optimised for managers, coordinators, family and analysts. Both connect to the same platform and data, but each is optimised to the role.
• Service interface: Yes
• User support accessibility: WCAG 2.2 AA
• Description of service interface: Clients and family access CareBuilder through a secure mobile app and web portal. They can view live care plans, daily notes, medications, and upcoming visits, with simple timelines and plain-English summaries. Real-time notifications highlight missed tasks, changes, and incidents. Two-way messaging enables questions, photo sharing, and acknowledgements. Consent, preferences, and goals are clearly visible and editable with permissions. Family members get role-based access to exactly what’s relevant, including wellbeing dashboards. Accessibility is built-in: large text, high contrast, screen-reader support, and multiple languages. Privacy is central: encrypted data, audit trails, and configurable sharing.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: We design and test the CareBuilder web console and mobile apps with disabled users and assistive technologies as part of an ongoing accessibility programme aligned to WCAG 2.2 AA and EN 301 549.
• API: Yes
• What users can and can't do using the API: Our REST API provides secure, role-based access to manage and integrate key operational data, including users, devices, services, service orders, roles, qualifications, and locations.; ; It enables authorised third-party systems to import, update, and synchronise records directly, as well as to trigger and receive real-time service alarms via an integrated real-time signalling server or through webhooks.; ; Users set up the service by registering an account and obtaining an authentication token (Bearer token), which governs both access control and rate-limiting policies. Once authenticated, clients can create, edit, delete, or query data entities through standard HTTPS endpoints.; ; They may also subscribe to webhooks to receive event notifications (for example, when an alarm or service order status changes) or connect through the signalling server to receive live updates.; ; Configuration is flexible: domain-based isolation allows each organisation or site to manage its own data, roles, and rate-limit policies securely.; API usage and authorisation are centrally controlled for full auditability.; ; Limitations: each account operates under defined access and rate-limit policies, and administrative rights are required for structural or configuration changes.
• API documentation: Yes
• API documentation formats: Open API (also known as Swagger)
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: We offer multiple ways in which the platform can be customised depending on the subscription type.

Scaling

• Independence of resources: We we ensure one customer’s peak demand doesn’t affect others through tenant isolation, per-tenant capacity limits, and automated scaling. Workloads and data are logically separated with scoped permissions and segregated storage. We enforce quotas and throttling (e.g., rate limits, connection caps, queue limits) to prevent disproportionate consumption. Services scale horizontally with load balancing to maintain performance. Time-critical workflows (alerts and communications) are prioritised over non-urgent reporting. Continuous monitoring and capacity planning trigger early remediation before users are impacted.

Analytics

• Service usage metrics: Yes
• Metrics types: We provide service usage metrics to help customers monitor adoption, performance, and outcomes. Typical metrics include number of active users/devices, alert volumes and types, response times (acknowledge, triage, resolution), escalation rates, false alarm rates, and service availability/uptime. We also report engagement measures such as completed check-ins, completed prompts, two-way contacts, and trends over time by site/cohort. Operational metrics can include caseload distribution, peak demand periods, and workload by responder/team. Where relevant, we support outcome and assurance reporting (e.g., overnight activity summaries, wellbeing indicators) and provide exports in CSV/XLSX plus dashboards and optional (at additional cost) API exports.
• Reporting types:
  • API access
  • Real-time dashboards
  • Reports on request
• 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: 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: Managed by a third party
• Penetration testing frequency: At least once a year
• Penetration testing approach: ‘IT Health Check’ performed by a CREST-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: 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 importing and exporting

• Data export approach: Users export their data either through self-service reporting (where enabled) or via a secure export request. Authorised users can download reports and datasets (e.g., alerts/events, activity records, user lists, and configuration summaries) in CSV/XLSX for local analysis. For full or more complex requirements, we provide a structured export pack in CSV/XLSX and/or JSON, including an export manifest/data dictionary covering scope, date ranges, and field definitions. Exports are delivered through an agreed secure method (encrypted time-limited download link, SFTP, or customer-managed secure storage), with role-based permissions, access controls, and audit logging to ensure appropriate governance.
• Data export formats:
  • CSV
  • Other
• Other data export formats:
  • JSON
  • PDF (depending on type)
• Data import formats: CSV

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: Our availability SLA for the core service (platform access and critical functions) is 99.9% uptime per calendar month, excluding pre-agreed maintenance windows and events outside our reasonable control (e.g., widespread internet failures or force majeure).
• Approach to resilience: Our service is designed for resilience through multi-site architecture, automated failover, and tested recovery processes, aligned to the UK Government/NCSC principle on asset protection and resilience.; ; Service resilience (application and data):; Three mirrored AWS sites (geographically separated). If one site suffers an outage or degradation, we can fail over service delivery to another site to maintain continuity.; Each site is built using redundant components (e.g., multiple availability zones), avoiding single points of failure.; Operational resilience: continuous monitoring and alerting, automated recovery where possible, clear incident response, and post-incident review.; ; Datacentre setup (cloud hosting):; Our “datacentre” resilience is provided through AWS’ regional and availability-zone design, supplemented by our cross-site mirroring and failover runbooks.; Specific site/region details can be provided on request.
• Outage reporting: Our outage reporting is designed to give customers fast visibility, clear impact information, and reliable updates through multiple channels.; ; How we report outages; Status dashboard: we provide a service status page showing current service health.; ; Email alerts: customers can subscribe nominated contacts to incident notifications (new incident, impact updates, mitigation in progress, resolution, and post-incident summary). ; ; API / integration option: where required, we can provide an API endpoint or webhook-style integration to feed incident state into a buyer’s tooling (e.g., ServiceNow, Jira, Teams) for automated updates and internal comms.; ; What customers receive; ; Initial notice with start time, affected components, and known impact; ; Regular updates with progress, mitigations, and workarounds (if available); ; Resolution notice and (for material incidents) a post-incident report including root cause and corrective actions

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: We restrict access to management interfaces and support channels using least-privilege, strong authentication, and audited administration. Admin access is limited to authorised personnel with role-based permissions and segregation of duties. We enforce MFA and, where possible, SSO with conditional access. Privileged actions are performed through controlled admin accounts, with time-limited access for higher-risk tasks and “break-glass” procedures for emergencies. Network controls (IP allowlists/VPN where required) reduce exposure of management interfaces. Support channel access is restricted to named customer contacts and verified requestors; sensitive changes require secondary verification and approval. All admin and support actions are logged and reviewed.
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)

Audit information for users

• Access to user activity audit information: Users have access to real-time audit information
• How long user audit data is stored for: User-defined
• Access to supplier activity audit information: Users have access to real-time audit information
• How long supplier audit data is stored for: User-defined
• How long system logs are stored for: User-defined

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards: ISO/IEC 27001
• Information security policies and processes: We follow a structured information security management approach with documented policies, clear accountability, and routine assurance to ensure controls are implemented and evidenced.; ; Our policies cover (as a minimum): access control and MFA, acceptable use, data classification and handling, encryption and key management, secure configuration and patching, vulnerability management, incident response and breach reporting, supplier risk, secure development (SDLC), change management, logging and monitoring, backup and recovery, and retention/deletion.; ; Reporting structure: overall accountability sits with senior management through our infosec team, with an assigned security lead responsible for day-to-day governance. Security risks, incidents, and compliance status are reviewed regularly by leadership, with escalation for high-severity issues and formal sign-off for material risk decisions.; ; How we ensure policies are followed: we use role-based access, least-privilege permissions, segregation of environments, and preventative controls (e.g., enforced encryption, logging, and secure baseline configurations). We run staff onboarding and refresher training, maintain an audit trail of admin activity, and perform scheduled risk assessments, internal checks, vulnerability scanning, and penetration testing. Findings are tracked to remediation with owners and deadlines. Where we use AWS services, we apply cloud security best practice and continuous monitoring to detect and respond to threats.
• 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: Our configuration and change management follows our SDLC gates. All work is raised and tracked in ClickUp as user stories/defects, reviewed for duplicates and prioritised, then scheduled into feature or maintenance sprints. Code and configuration are version-controlled in GitLab, giving full traceability from ticket to commit to release. Security impact is assessed during sprint planning and through mandated testing (including security-focused test cases), plus updates to the risk register and third-party component register where relevant. Before release we complete a Release Readiness Review (RRR) with release and rollback plans; emergency fixes remain tested and reviewed.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: We run a risk-based vulnerability management process. At least weekly we review new CVEs and supplier security advisories relevant to our stack and subscribe to notification services for emerging issues. We assess threats by severity, exploitability, exposure (internet-facing vs internal) and data sensitivity. Patches are deployed as soon as practicable, typically via automated patching for routine updates and controlled maintenance releases for scheduled vendor cycles (e.g., Microsoft). Where a patch is not available, we apply safe mitigations (configuration changes, compensating controls, IP blocking/rules) informed by log monitoring for anomalous activity. Actions are recorded, tracked to closure, and verified.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: We operate protective monitoring through continuous log and event review across our services and infrastructure. Potential compromises are identified by detecting anomalies and indicators of compromise, such as unusual login patterns, privilege changes, unexpected traffic spikes, repeated authentication failures, suspicious API usage, or integrity/availability alerts. Alerts are triaged by severity/verified using supporting logs and system context. Where compromise is suspected, we initiate incident response: contain (block IPs, disable accounts/keys, isolate components), eradicate (remove artefacts, patch/configure), and recover (restore services, validate integrity). We respond to high-severity alerts immediately, with initial triage within hours, and provide timely communications and post-incident reporting.
• 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: We operate a structured incident management process with defined severity levels, roles, and escalation. We maintain pre-defined playbooks for common events (service outage, security alert, failed deployment, performance degradation, third-party disruption) including containment, rollback, and communications steps. Users can report incidents via our support email/helpdesk and (where agreed) a dedicated phone or on-call escalation route for high-severity issues. We acknowledge incidents, provide regular updates until resolution, and coordinate actions with affected customers. For material incidents, we provide an incident report covering timeline, impact, root cause, corrective actions, and any prevention measures, shared by email and available for download on request.
• Post-quantum cryptography secure: No

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: 5%
• Between £500,001 and £1,000,000: 9%
• Between £1,000,001 and £2,500,000: 14%
• Between £2,500,001 and £5,000,000: 18%
• Over £5,000,001: 20%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: Amtivo Group Limited T/A British Assessment Bureau Ltd.
• ISO/IEC 27001 accreditation date: Monday 1 September 2025
• What the ISO/IEC 27001 doesn’t cover: N/A assessment covers the full business
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: Amtivo Group Limited T/A British Assessment Bureau Ltd.
• ISO 9001 accreditation date: Monday 1 September 2025
• What the ISO 9001 doesn’t cover: N/A assessment covers the full business
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Please provide your Cyber Essentials Certificate Number: 0a6443d6-ccb2-46e9-8c50-ecd203f1a543
• Cyber essentials plus: No
• Cyber Essentials Alternative: In relation to the services you do not have a current and valid Cyber Essentials Plus 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 Plus certificate by one of the government approved accreditation bodies within 12 months of the date of award.
• 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
    • 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
    • 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

  • 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
    • Plans for engaging a diverse range of businesses in engagement activities prior to appointing subcontractors (including activities prior to award of the main contract and during the contract term)
    • Activities that demonstrate a collaborative way to work with a diverse range of businesses as part of the supply chain
    • Advertising of supply chain opportunities openly and to ensure they are accessible to a diverse range of businesses, including advertising all subcontracting opportunities on Contracts Finder
    • 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
    • Methods for engaging with different parts of the community (including the education system and charities representing the community) and how communities come together to inform decisions, strategy and projects to leave a positive legacy for future generations
    • Measures to involve local stakeholders and/or users in design (e.g. in the design of services, systems, products or buildings)
    • Plans for positive actions with community groups.
    • Measures to engage users and communities and build relationships to increase community integration build trust and influence how the contract is delivered
    • Collaborating with anchor institutions and community groups to make facilities available for education, training or community events

  • 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

  • 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
    • Offering a range of quality opportunities with routes of progression if appropriate, e.g. T Level industry placements, students supported into higher level apprenticeships.
    • 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: 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 info@carebuilder.com. Tell them what format you need. It will help if you say what assistive technology you use.