RISKBASE LIMITED

Riskbase Fire & Building Safety Platform

RiskBase is a cloud-based fire and building safety platform that enables organisations to manage inspections, surveys and risk assessments in one system. It supports compliance, remedial actions, reporting and resident engagement, providing a secure, auditable golden thread of safety data across web and mobile devices.

Features

• Cloudbased fire and building safety platform accessed via web/mobile.
• FRAs, Door Checks, FRAEWs, Resident Engagement on site via App.
• Offline data capture with automatic synchronisation when connectivity returns.
• Real-time dashboards displaying compliance status, risks and actions
• Automated task and action management linked to assessment findings.
• Central asset register supporting golden thread safety data management.
• Automated branded PDF report generation from captured assessment data.
• Role-based access controls with configurable user permissions.
• REST API and webhooks enabling third-party system integrations.
• UK/EEA-hosted infrastructure with encryption, backups and built-in redundancy.

Benefits

• Capture safety and compliance data consistently across property portfolios.
• Complete assessments efficiently on site using mobile devices.
• Manage assessments, actions and assets within a single platform.
• Track remedial actions clearly from identification to closure.
• Gain visibility of compliance performance through real-time dashboards.
• Produce compliant reports quickly without manual data re-entry.
• Maintain an auditable golden thread of building safety information.
• Support collaboration between internal teams and external consultants.
• Adapt workflows and templates to organisational and regulatory requirements.
• Improve efficiency and consistency managing fire and building safety duties.

• 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 glenn.brawn@riskbase.uk. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

900494930715399

Contact

Glenn Brawn
07968342274
glenn.brawn@riskbase.uk

About your service

• Service categories:

  Applications

  Content workflow and management

  • Capture
• Multi cloud support: No

Service scope

• Software add-on or extension: Yes, but can also be used as a standalone service
• What software services is the service an extension to: RiskBase can integrate with third-party software systems using its REST API, webhooks and standard integration endpoints.
• Cloud deployment model: Public cloud
• Service constraints: Planned maintenance and updates may result in short periods of reduced availability, typically scheduled outside standard working hours.; ; The service requires a currently supported web browser or supported iOS or Android device.; ; Offline working is supported, but data synchronisation requires an internet connection.; ; Out-of-hours support is limited, with full support provided during UK business hours.; ; Onsite support and in-person training are available at additional cost and by arrangement.; ; Custom development is limited to ensure platform stability and roadmap consistency.
• System requirements:
  • Currently supported web browser including Chrome, Edge, Firefox or Safari.
  • Supported iOS device running a current, supported operating system.
  • Supported Android device running a current, supported operating system.
  • Internet connection required for access, synchronisation and reporting functions.
  • Email access required for user authentication and account notifications.
  • PDF reader required to view generated reports and exported documents.
  • Spreadsheet software required to view CSV and Excel exports.
  • Camera-enabled device required for capturing photographic assessment evidence.
  • API access requires secure token management and standard HTTPS connectivity.
  • No additional software licences required beyond standard device and browser.

User support

• Email or online ticketing support: Yes
• Support response times: Weekdays (Monday–Friday, 9-5):; Email and ticketing queries receive an initial response typically within 10 minutes during support hours.; ; Evenings and weekends:; Response times may extend to up to 45 minutes. Support ticketing is not monitored overnight.
• 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: The RiskBase documentation does not specify any formal user testing of web chat services with assistive technology users.
• Onsite support: No
• Support levels: RiskBase provides a single, comprehensive support service designed to support customers throughout the lifecycle of using the platform. Rather than offering multiple paid tiers, RiskBase combines responsive technical support with proactive customer success management to ensure consistent service quality for all clients.; ; Support is available through email,online ticketing,phone &web-chat during UK business-hours. All support requests are logged and managed through the ticketing system, allowing users to track progress, manage priority and maintain visibility of issues. Critical issues are responded to rapidly, with lower-priority requests managed through planned resolutions and product releases where appropriate. ; ; Support is delivered directly by RiskBase staff, ensuring continuity, platform knowledge and accountability. The service is designed to be both reactive, addressing technical issues as they arise, and proactive, supporting effective use of the platform.; ; Standard support is included within the service cost. There are no additional charges for email, ticketing, phone or web chat support. Optional services such as onsite support or in-person training are available at additional cost by agreement.; ; Each customer is assigned a Technical Account Manager. This role provides a single point of contact, leads onboarding, supports configuration and training, and delivers ongoing service reviews, ensuring customers gain value from RiskBase.
• Support available to third parties: Yes
• AI chatbot: No

Onboarding and offboarding

• Getting started: RiskBase supports users in starting to use the service through a structured onboarding and customer success approach, designed to ensure organisations are set up quickly and confidently.; ; Each new customer is assigned a Customer Success Manager, who acts as the primary point of contact. Onboarding begins with an initial kick-off meeting to understand the organisation’s objectives, workflows and compliance requirements. This informs how the platform is configured, including templates, user groups and permissions.; ; RiskBase provides online onboarding and training sessions, including a full platform and mobile app demonstration. Follow-up training sessions are available, focusing on administration, template building and day-to-day use. Training can be repeated on an ad-hoc basis, for example when new users join the organisation.; ; New users receive a welcome email containing links to detailed user guides and supporting documentation. These materials explain how to use the platform, complete assessments, manage actions and generate reports.; ; Onsite training and support can be provided where required, including in-person training sessions or CPD days, and is available at additional cost by arrangement.; ; Throughout onboarding and beyond, the Customer Success team provides ongoing guidance, responsive support and regular check-ins to ensure users are comfortable using the service and gaining value from it.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: Users can extract their data in two ways. First, organisations can manually export data directly from the service interface during the contract term. This includes exporting individual datasets such as assessments, inspections, actions, assets and related records as CSV files, along with associated photos and documents.; ; Second, on request at the end of the contract, RiskBase can provide a complete data export. This is supplied as a ZIP file containing itemised CSV files, images and supporting documents. This approach ensures data can be reused, archived or migrated into another system without reliance on proprietary formats.; ; RiskBase supports customers during the offboarding process, including clarifying timelines, export scope and any specific data requirements. Data extraction is provided at no additional cost, reflecting RiskBase’s flexible, customer-focused commercial model.; ; All data handling during extraction follows GDPR requirements, ensuring confidentiality and security. After the agreed extraction period, and in line with contractual terms, RiskBase may securely delete customer data held within the platform.; ; This process ensures buyers retain full control of their data and can exit the service without technical or commercial barriers.
• End-of-contract process: Where a contract reaches its natural end, or a customer chooses to cease using the service, RiskBase works with the customer to agree timelines and confirm data requirements. Users retain full ownership of their data. During the contract term, and following contract end on request, customers can export their data from the platform. RiskBase can also provide a complete data extract in a structured ZIP file containing CSV data, images and associated documents, enabling reuse or migration to another system.; ; Support during offboarding, including data extraction and clarification of outputs, is included within the standard contract price. There are no exit fees or additional charges for providing customer data, reflecting RiskBase’s flexible and transparent commercial approach.; ; Following the agreed extraction period, RiskBase may securely delete customer data in line with contractual terms and GDPR requirements.; ; The contract price includes access to the RiskBase platform, standard support services, customer success management, onboarding support, documentation and ongoing updates to the service.; ; Additional costs may apply for optional services such as onsite support, in-person training or bespoke professional services requested outside standard service delivery.
• Documentation accessibility standard: EN 301 549

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
  • Opera
• Application to install: Yes
• Compatible operating systems:
  • Android
  • IOS
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: RiskBase provides the same core functionality across mobile and desktop, with differences reflecting how the service is used in practice. The mobile applications are optimised for on-site working, enabling users to carry out assessments, inspections and surveys in the field. This includes offline data capture, photographic evidence collection and later synchronisation when connectivity is restored.; ; The desktop, browser-based service is typically used for administration, configuration and oversight activities. This includes template building,user and permission management, reporting, dashboard analysis and integration management. Both interfaces access the same underlying data,ensuring consistency and a single source of truth across web and mobile use.
• Service interface: Yes
• User support accessibility: EN 301 549
• Description of service interface: RiskBase provides a clear, intuitive service interface available through a web browser and mobile applications. The interface is designed around practical workflows, allowing users to create, complete and review assessments, inspections and surveys efficiently. Dashboards present compliance status, risks and actions using configurable filters and visual summaries. Forms and templates guide consistent data capture, while reporting tools allow users to generate outputs directly from captured data. The interface supports role-based access, ensuring users only see functions and information relevant to their responsibilities.
• Accessibility standards: EN 301 549
• Accessibility testing: The RiskBase documentation does not describe formal or structured user testing of the service interface with assistive technology users. Instead, accessibility is addressed through adherence to recognised accessibility standards and good practice in interface design.; ; The service interface is developed to meet EN 301 549, which aligns with public sector accessibility requirements and covers usability, compatibility and accessibility across web and digital services. This includes considerations for screen readers, keyboard navigation, colour contrast, readable layouts and consistent interaction patterns.; ; RiskBase takes a standards-led approach to accessibility, ensuring that interface components, web-based interactions and support services are designed to be accessible to a broad range of users. Where accessibility issues are identified through customer feedback or internal review, these are addressed through the platform’s change and release management process.; ; Accessibility improvements are considered as part of ongoing product development and continuous improvement, ensuring the interface remains usable and inclusive as the platform evolves.
• API: Yes
• What users can and can't do using the API: RiskBase provides an API that allows users to consume and update data stored within the platform. The API is typically used to integrate RiskBase with other systems and to support automated data exchange rather than full platform configuration.; ; Using the API, users can:; ; Retrieve assessment, inspection, asset and action data held within RiskBase.; ; Update existing records where appropriate, supporting synchronisation with third-party systems.; ; Manage users and user groups through SCIM 2.0 provisioning.; ; Enable SAML single sign-on for authentication and identity management.; ; Use webhooks to receive notifications when data changes occur within the platform.; ; Initial service setup, such as creating templates, configuring workflows, permissions and organisational settings, is primarily completed through the RiskBase user interface with support from the Customer Success team, rather than solely through the API.; ; The API provides a standard set of endpoints for self-serve integrations. New or custom endpoints can be requested, but availability is subject to technical review to ensure platform stability and security. The API is not intended for unrestricted customisation of core application behaviour.
• API documentation: Yes
• API documentation formats:
  • Open API (also known as Swagger)
  • HTML
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Service customisation; ; RiskBase allows users to customise the service to reflect organisational structures, workflows and compliance requirements without altering the core platform.; ; What can be customised; Users can configure organisation-wide settings including user groups, teams and role-based permissions. Assessment, inspection and survey templates can be customised, including question sets, fields, categories and scoring. Users can also tailor notifications, timescales, dashboards and reporting views. Asset registers and action management workflows can be configured to align with internal processes.; ; How users can customise; Customisation is completed directly through the RiskBase service interface. Administrators can create, edit and manage templates, configure permissions and adjust workflows using built-in configuration tools. The Customer Success team provides onboarding support, guidance and training to help organisations configure the platform effectively.; ; Who can customise; Customisation is typically carried out by authorised administrators within the buyer’s organisation. Permissions are role-based, ensuring only approved users can make structural or configuration changes. RiskBase support staff may assist with setup, configuration and best-practice guidance, but control remains with the buyer.; ; This approach ensures flexibility while maintaining platform stability and data consistency.

Scaling

• Independence of resources: The service is hosted on resilient cloud-infrastructure with built-in failover and redundancy. Capacity is actively monitored,&sufficient headroom is maintained across compute, storage and bandwidth to manage peak usage and growth. This approach reduces the risk of contention between customers and helps maintain consistent performance.; ; System performance, availability &error rates are continuously monitored. Automated alerts enable rapid identification and response to abnormal load or degradation. Infrastructure scaling &resource management are used to maintain responsiveness as demand changes.; ; Planned maintenance is scheduled to minimise disruption,typically outside working-hours,with advance communication where required. These measures ensure stable performance and reliable access for all users.

Analytics

• Service usage metrics: Yes
• Metrics types: RiskBase provides service usage and operational metrics through built-in dashboards and reporting tools. Metrics include visibility of assessments completed, inspections undertaken, actions raised and closed, asset coverage, compliance status and user activity. Dashboards can be filtered to present relevant numeric and graphical views, supporting oversight and performance monitoring. These metrics help organisations track progress, identify risk areas and manage workloads effectively.
• Reporting types:
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: No
• FOCUS resource tagging: No

Resellers

• Supplier type: Not a reseller

Staff security

• Staff security clearance: Other security clearance
• Government security clearance: None

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

Data importing and exporting

• Data export approach: Users can export their data directly from the RiskBase service during the contract term and at contract end. Data can be manually exported through the service interface as structured CSV files, alongside associated photos and documents.; ; On request, RiskBase can also provide a complete data export supplied as a ZIP file containing itemised CSV datasets, images and supporting files. This ensures data can be reused, archived or migrated to another system without proprietary constraints.; ; All exports follow GDPR requirements and are provided in open, commonly used formats.
• Data export formats:
  • CSV
  • Other
• Other data export formats:
  • JPEG
  • PDF
• Data import formats:
  • CSV
  • Other
• Other data import formats:
  • JPEG
  • PDF

Data-in-transit protection

• Data protection between buyer and supplier networks: TLS (version 1.2 or above)
• Data protection within supplier network: TLS (version 1.2 or above)

Availability and resilience

• Guaranteed availability: RiskBase is designed to deliver a high level of service availability, supported by resilient cloud infrastructure with built-in failover and redundancy. The service is hosted on infrastructure engineered for reliability,with continuous monitoring of uptime,performance and errors.; ; RiskBase targets availability exceeding 99.0%, ensuring continuity of service for day-to-day operational use. The platform is supported by proactive monitoring and automated alerts, enabling rapid response to incidents that could affect availability. Planned maintenance and updates are managed through a controlled change process and are typically scheduled outside standard working hours to minimise disruption. Where planned maintenance may affect availability, customers are informed in advance.; ; RiskBase offers service level agreements (SLAs) that are agreed at the point of contracting. These SLAs define availability expectations, response times &support arrangements and may vary depending on the customer’s requirements and scale of use. This allows flexibility while maintaining clear and transparent service commitments.; ; The RiskBase documentation does not define a standard financial refund or service credit model linked specifically to availability breaches. Any remedies or commercial adjustments related to service performance are addressed contractually,in line with agreed SLAs and contract terms.; ; This approach ensures availability is actively managed, monitored and communicated, while remaining aligned with customer needs.
• Approach to resilience: RiskBase is designed to be resilient by default, with service availability and data protection built into both the application architecture and the underlying hosting environment.; ; The service is hosted on resilient cloud infrastructure with built-in failover and redundancy. This infrastructure is designed to tolerate component failure without loss of service,supporting continuity of access. Capacity is monitored continuously,with sufficient headroom maintained across compute, storage&network resources to manage fluctuations in demand.; ; RiskBase operates regular data backup processes, using both on-site and off-site backups to reduce the risk of data loss. Incremental and differential backups are used to optimise recovery while maintaining data integrity. Disaster recovery and business continuity plans are in place, with defined procedures for restoring systems and data following incidents. These plans are tested and reviewed to ensure effectiveness.; ; Datacentres used to host the service comply with recognised security and resilience standards, including CSACCM and SSAE-16/ISAE3402–aligned controls. Facilities include physical security, environmental controls and resilient power and connectivity.; ; The platform is actively monitored for uptime, errors and performance. Automated alerts enable rapid response to incidents, while planned maintenance is managed through controlled change processes, typically outside working hours.; ; Further technical detail on resilience and datacentre architecture is available on request.
• Outage reporting: RiskBase reports service outages through direct communication channels rather than public-facing dashboards.; ; Where an outage or service degradation occurs, RiskBase provides email notifications to affected customers, outlining the issue, expected impact and estimated resolution times. During incidents, updates are provided as appropriate until service is restored.; ; The service does not provide a public status dashboard or a dedicated outage reporting API. Outage communication is managed through the customer support and customer success teams to ensure information is clear, timely and relevant to each customer.; ; In addition to email alerts, users can raise and track incidents through the support ticketing system, where outage-related issues are logged, monitored and resolved. Post-incident reviews are carried out internally to identify root causes and inform preventative actions.; ; This approach ensures customers receive targeted, accurate information without relying on generic public reporting channels.

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
  • Other
• Other user authentication: MFA and single sign-on (SSO) are available, including SAML-based identity federation, allowing organisations to integrate RiskBase with existing identity providers. User and group management can also be supported through SCIM 2.0 provisioning.
• Access restrictions in management interfaces and support channels: Access to the service interface is limited to authorised users, with permissions assigned based on defined roles. Administrative functions, such as user management, configuration and template changes, are restricted to approved administrators only. This ensures users can access only the features and data relevant to their responsibilities.; ; Support channels are similarly controlled. Only known users can raise support requests through email, ticketing, phone or web chat. Support tickets are linked to user accounts, providing traceability and preventing unauthorised access. Access to support systems is restricted to authorised RiskBase staff, with activities logged and monitored to maintain security and accountability.
• 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
  • Other
• Description of management access authentication: Management and administrative users authenticate using the same secure mechanisms as standard users, with additional controls applied through role-based permissions. This includes passwordless authentication using emailed one-time codes, optional MFA, and SAML-based single sign-on for organisations integrating with their own identity providers. Access to management functions is restricted to authorised roles only.

Audit information for users

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

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards:
  • CSA CSM version 4.0
  • ISO/IEC 27001
• Information security policies and processes: RiskBase follows a structured set of information security policies and processes aligned to its ISO/IEC27001–certified Information Security Management System(ISMS).These policies govern how information security is managed across the organisation and how customer data is protected throughout the service lifecycle.; ; Information security governance is overseen by a named, board-level responsible person, providing accountability and senior oversight. Day-to-day responsibility for implementing and maintaining security controls sits with designated operational leads, supported by documented policies, procedures and controls.; ; Core policies&processes include information security management, access control, data protection, incident management, vulnerability management, change management and supplier management. Security risks are identified, assessed and treated through a formal risk management process, with controls selected and reviewed in line with ISO/IEC27001 requirements.; ; Compliance with policies is ensured through a combination of role-based access controls, staff awareness, documented procedures and regular review.Changes to systems and services follow a controlled change management process, including testing and approval before release. Security incidents are logged,investigated and managed through defined incident response processes,with escalation to senior management where required.; ; RiskBase also undertakes regular independent assurance, including penetration testing and ISO audits,to validate that policies are followed in practice and remain effective. Continuous improvement is embedded through management reviews &corrective actions.
• 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: Service components are tracked using version control and documented release management, with all changes recorded from development through testing to production.Changes move through defined environments, ensuring traceability and rollback capability if required.; ; All proposed changes are assessed for security, performance and service impact before approval. This includes reviewing potential risks, dependency impacts and alignment with information security controls. Access to make or approve changes is restricted to authorised personnel.; ; Emergency changes are managed through an expedited process but remain subject to the same governance, logging and post-implementation review.This approach ensures changes are controlled, auditable and aligned with operational security requirements.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: Potential threats are assessed through continuous system monitoring, automated vulnerability scanning and regular independent penetration testing. Identified vulnerabilities are evaluated for risk, impact and likelihood to prioritise remediation.; ; Security patches and updates are deployed promptly, either through scheduled maintenance or as soon as possible for critical issues. Emergency fixes are released using an expedited change process, while maintaining approval, logging and rollback controls.; ; Information about potential threats is gathered from vendor security bulletins, industry security advisories, automated scanning tools and external penetration testing providers. Staff are subscribed to relevant security feeds to ensure emerging risks are identified early.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: Potential compromises are identified through continuous monitoring of uptime,system performance,access activity&error logs,supported by automated alerts when activity deviates from normal thresholds.Automated vulnerability&malware scanning further supports early detection.; ; When a potential compromise is detected,the incident is logged immediately&assessed by authorised personnel.Defined incident management procedures are followed to contain the issue,investigate root cause&apply corrective actions.Senior management are notified where appropriate,&customers are informed if service or data may be affected.; ; RiskBase responds promptly to incidents, with investigation and mitigation initiated as soon as alerts are raised. Response priority is based on severity, with critical incidents addressed immediately to minimise impact and restore service.
• 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: Pre-defined processes are in place for common incident types, including service availability issues, security incidents and data-related events. Incidents are logged,categorised &prioritised based on severity &potential impact.; ; Users can report incidents through email, online ticketing, phone or web chat during support hours. Incidents may also be identified through automated monitoring &alerts.Once logged,incidents are tracked through to resolution using internal issue management systems.; ; Where required,RiskBase provides incident updates and reports to affected customers. This includes details of the issue, actions taken, resolution status and root cause and preventative measures. Significant incidents are escalated to senior management &reviewed to inform continuous improvement.
• 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: Yes
• Description of free trial: 'Sandbox' setup and system log-ins created for a specified number of administrators and users to test the application, platform and template workflows. Length of trial period TBC dependent on scale and requirement.

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: 10%
• Between £1,000,001 and £2,500,000: 15%
• Between £2,500,001 and £5,000,000: 20%
• Over £5,000,001: 25%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: IAF
• ISO/IEC 27001 accreditation date: Friday 2 May 2025
• What the ISO/IEC 27001 doesn’t cover: Customer data collection (sales information and leads). Building and maintaining software which holds; clients’ data.; Statement of Applicability Version
• ISO 28000:2022 certification: No
• ISO 9001 certification: No
• Quality management systems (QMS): No
• 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
    • 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
    • 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
    • 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 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
    • Plans to respond flexibly and adapt approaches to community engagement and initiatives

  • 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
    • 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
    • Creation of employment opportunities particularly for those who face barriers to employment, such as prison leavers, care leavers and/or who are located in deprived areas, and for people in industries with known skills shortages or in high growth sectors
    • Delivery of training schemes and programmes to address any identified skills gaps and under-representation in the workforce for the contract (e.g. prison leavers, care leavers, kinship carers, disabled people)
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach the target cohort
    • 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
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach the target cohort
    • 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
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach the target cohort

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

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

    • Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
    • 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 glenn.brawn@riskbase.uk. Tell them what format you need. It will help if you say what assistive technology you use.