CONDATIS GROUP LIMITED

Decentralised Identity & Credential Orchestration Platform

Condatis Cenda is a secure SaaS platform for decentralised identity, portable credentials, and digital wallet integration. Built on Microsoft Entra, it enables identity verification, workflow orchestration, and interoperability across public sector systems, enhancing security, user control, and operational efficiency.

Features

• Decentralised identity using verifiable credentials and DIDs.
• Portable credentials reused across ecosystems and digital wallets.
• API‑based credential issuance and verification with silent operation.
• User journey orchestration for complex identity verification workflows.
• Management portal with role‑based access from Entra ID.
• Interoperability with legacy systems and multiple trust frameworks.
• Infrastructure‑as‑Code deployment using modular Terraform components.
• Digital wallet integration supporting UK, EU, and global standards.
• Cryptographic security aligned to zero trust architecture principles.
• Containerised, cloud‑agnostic environments enabling multi‑cloud deployment.

Benefits

• Reduce onboarding time with fast, automated digital identity verification.
• Empower users to control and share their credentials securely.
• Streamline processes by reusing verified credentials across multiple services.
• Minimise administrative effort through automated identity workflows and orchestration.
• Enhance security using decentralised credentials and zero‑trust principles.
• Improve interoperability by connecting legacy systems with modern identity platforms.
• Accelerate deployments with modular, repeatable cloud‑agnostic infrastructure.
• Support regulatory compliance through built‑in security and governance controls.
• Enable cross‑organisation collaboration with portable, trusted digital credentials.
• Future‑proof identity strategy with support for emerging wallet standards.

• Education pricing available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

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

Framework

G-Cloud 15

Service ID

382518393444266

Contact

Chris Tate
0800 538 5533
sales@condatis.com

About the service

• Service categories:

  Application Development and Deployment

  Application platforms

  • Model driven application platforms
• Multi cloud support: Yes

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: Cenda extends Microsoft Entra, Azure Active Directory, and Entra Verified ID by enabling advanced orchestration for human and non‑human identities, including services, devices, and applications. It integrates with HR systems, legacy directories, and third‑party digital wallets to enhance credential workflows across multi‑cloud environments.
• Cloud deployment model: Hybrid cloud
• Service constraints: Cenda requires network connectivity to supported cloud environments and relies on Microsoft Entra components for certain identity functions. Planned maintenance windows may cause brief, scheduled service interruptions, communicated in advance. Client‑hosted deployments must meet minimum infrastructure, security, and network requirements. Some advanced features, such as digital wallet integrations or non‑human identity orchestration, may depend on third‑party services or trust frameworks. Legacy system integration may require custom connectors or additional professional services.
• System requirements:
  • Microsoft Entra tenant for identity integration and role management.
  • Azure subscription for optional client‑hosted deployments and services.
  • Modern browser supporting WCAG‑compliant management portal features.
  • Network connectivity to required cloud environments and APIs.
  • Secure VPN or private network links for legacy system integration.
  • OIDC or SAML support for enterprise authentication connections.
  • Container‑compatible infrastructure for client‑hosted deployments.
  • Terraform execution environment for Infrastructure‑as‑Code deployments.
  • Mobile wallet app for credential storage and verification workflows.
  • TLS‑enabled endpoints for all service‑to‑service communications.

User support

• Email or online ticketing support: Yes
• Support response times: We respond to critical issues within 30 minutes, high‑priority issues within 1 hour, and standard enquiries within 4 business hours. Support is provided during UK business hours, Monday to Friday. Weekend response times may be slower and follow‑up may occur on the next business day. All incidents are managed according to predefined SLAs with escalation paths.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.2 AA
• Phone support: No
• Web chat support: No
• Onsite support: Yes, at extra cost
• Support levels: Support levels; Standard (included): UK business‑hours email/portal support. SLAs: critical response 30 minutes; high 1 hour; standard 4 business hours. Incident management with defined escalation paths and monthly reporting.; ; Enhanced (add‑on): Optional 24/7 coverage for critical environments, proactive monitoring, performance optimisation, and hypercare during cutover.; ; Professional Services (add‑on): Discovery workshops, integration and deployment assistance, custom connectors, and knowledge transfer. Onsite support available.; ; Costs; Standard support is included within the service subscription.; Enhanced and Professional Services are chargeable add‑ons; pricing is provided in the G‑Cloud Pricing Document and Statement of Work in GBP.; ; Named support roles; For Enhanced and above, customers receive a Technical Account Manager/Cloud Support Engineer as a named contact for service reviews, roadmap guidance, and escalations.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: We support users through a structured onboarding process designed to ensure a smooth and secure adoption of the service. Onboarding typically begins with discovery sessions to understand organisational requirements, identity workflows, and integration needs. We provide clear implementation guidance, including environment setup, configuration steps, and recommended deployment patterns.; ; Users receive access to comprehensive online documentation, covering administration, credential templates, workflow configuration, API usage, and integration patterns. We also offer remote training sessions for administrators and technical teams, focused on using the management portal, setting up identity flows, and operating credential services.; Where required, we provide onsite or remote workshops to support integration with legacy systems, design custom workflows, or prepare for client‑hosted deployment. During cutover, we deliver hypercare support to ensure stable operation and fast issue resolution.; ; This structured onboarding approach helps organisations quickly configure, integrate, and operationalise the service with confidence.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
  • Other
• Other documentation formats:
  • Word
  • Excel
• End-of-contract data extraction: At the end of the contract, users can extract all relevant data through the service’s standard export capabilities. Administrators can export configuration data, credential templates, workflow definitions, audit logs, and related metadata using the management portal or API. For client‑hosted deployments, all data remains within the customer’s cloud environment, allowing full direct access and extraction without Condatis involvement.; ; Where required, Condatis provides additional support to assist with data export, including preparing structured export files and ensuring secure transfer. All exported data is provided in open or commonly used formats, such as JSON, CSV, and PDF, depending on the data type.; ; Buyers may also request professional services to support migration to another platform or identity system. Once extraction is complete, data within Condatis‑managed environments is securely erased following approved data‑sanitisation procedures.
• End-of-contract process: At the end of the contract, buyers can export all relevant data using the platform’s standard export tools or APIs, including configuration data, credential templates, workflow definitions, audit logs, and metadata. For client‑hosted deployments, all data remains within the buyer’s environment, so no additional extraction steps are required.; ; Once data extraction is complete, Condatis securely deletes any remaining data held within Condatis‑managed environments using approved data‑sanitisation processes. A record of data deletion can be provided on request.; ; Included in the contract price:; Access to the service for the duration of the agreement; Standard data export via portal or API; Secure deletion of data at contract end; ; Additional cost items:; Professional services for complex extraction, transformation, or migration; Custom export formats beyond standard outputs; Onsite or enhanced support during offboarding
• Documentation accessibility standard: WCAG 2.2 AA

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
• Application to install: No
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: Mobile is optimised for credential holding and presentation via digital wallets; end‑users can receive, store, and share verifiable credentials on devices. Administrative tasks are performed in the browser‑based management portal, best experienced on desktop for complex configuration and reporting. The portal is responsive on mobile, but advanced orchestration, template design, and integrations are recommended on desktop. Push notifications and camera access streamline mobile verification journeys. No desktop installation is required; mobile wallet apps may be used for issuance and verification.
• Service interface: Yes
• User support accessibility: WCAG 2.2 AA
• Description of service interface: Cenda provides a browser‑based management portal that allows administrators to configure organisations, manage credential templates, create clients, and control role‑based access using Microsoft Entra ID. The interface supports workflow orchestration, silent issuance settings, and integration management across legacy and cloud systems. It is WCAG‑aligned and designed for clear navigation, enabling secure configuration, monitoring, and ongoing administration of decentralised identity services.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: Cenda’s management portal is designed using inclusive design principles and developed to meet WCAG 2.2 AA accessibility standards. Accessibility considerations include screen‑reader compatibility, clear navigation, semantic markup, keyboard‑only operation, and adaptable layouts. Regular accessibility audits are conducted with clients to review usability for people with disabilities, and improvements are implemented as part of continual service enhancement. The platform supports users of assistive technologies such as screen readers, voice‑recognition software, and alternative input devices. Feedback channels allow administrators and end‑users to report accessibility issues, informing ongoing refinement of the interface and documentation.
• API: Yes
• What users can and can't do using the API: Cenda provides a comprehensive REST API that enables organisations to automate credential issuance, verification, and identity‑workflow orchestration. Users can set up the service via API by configuring organisations, clients, credential templates, and silent‑issuance rules, enabling full machine‑to‑machine onboarding without needing the management portal.; ; Through the API, users can issue and verify decentralised credentials, interact with digital wallets, manage non‑human identities, and integrate legacy or third‑party systems using standards such as OpenID Connect. The API also allows updates to workflows, templates, and configuration items, supporting continuous integration and automated deployment pipelines.; ; Some capabilities - for example, advanced orchestration design, trust‑framework mapping, and certain governance settings - are best managed through the portal rather than exclusively via API. Client‑hosted deployments may require additional setup, connector development, or infrastructure preparation not fully automated through the API.; ; The API does not provide direct control of underlying cloud infrastructure; Infrastructure‑as‑Code deployment uses Terraform rather than API calls. Digital wallet interactions may also depend on external providers’ APIs or standards compliance.
• API documentation: Yes
• API documentation formats: Open API (also known as Swagger)
• API sandbox or test environment: No
• Customisation available: Yes
• Description of customisation: Buyers can customise Cenda across multiple areas. They can configure organisations, credential templates, workflows, and clients through the management portal, tailoring identity journeys and verification steps to their operational needs. Role‑based access controls can be customised using Microsoft Entra ID to match internal governance requirements.; ; Cenda’s REST API allows automated setup of credential issuance, verification rules, non‑human identity onboarding, and silent‑issuance processes. Buyers can also develop custom connectors to integrate with legacy systems, HR platforms, and third‑party digital wallets.; ; For client‑hosted deployments, organisations can customise Terraform‑based Infrastructure‑as‑Code modules to meet their cloud, security, and network standards.; ; Customisation can be carried out by administrators via the portal, technical teams or developers via the API or IaC components, or Condatis consultants through professional services such as workflow design, integration, and hypercare.

Scaling

• Independence of resources: We guarantee resource independence by using isolated, tenant‑specific environments and scalable cloud infrastructure. Each customer’s workloads operate within separate logical boundaries, preventing demand from other users affecting performance. Capacity automatically scales to meet demand, and monitoring ensures proactive management of load, throughput, and service health. For client‑hosted deployments, performance is fully controlled within the buyer’s own cloud environment.

Analytics

• Service usage metrics: Yes
• Metrics types: We provide metrics covering service availability, uptime, incident response and resolution times, API usage volumes, credential issuance and verification activity, workflow performance, and system health indicators. Monthly reports include SLA compliance, support ticket trends, and improvement actions. Buyers can also access audit logs and operational insights to support governance, compliance, and performance monitoring.
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: Yes
• FOCUS resource tagging: No

Supplier type

• Supplier type: Not a reseller

Staff security

• Staff security clearance: Conforms to BS7858:2019
• Government security clearance: Security Clearance (SC)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations:
  • United Kingdom
  • 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 CREST-approved service provider
• Protecting data at rest:
  • Physical access control, complying with CSA CCM v4.0
  • Encryption of all physical media
  • Other
• Other data at rest protection approach: Data at rest is protected using strong encryption, secure key‑management controls, and tightly restricted role‑based access. Storage systems are isolated within dedicated environments, with network segmentation preventing unauthorised lateral movement. Access to underlying infrastructure is strictly controlled and logged, with multi‑factor authentication enforced for administrative operations. Continuous monitoring, vulnerability scanning, and regular security reviews ensure proactive detection of risks. Backup data is encrypted and handled according to secure retention and deletion policies.
• 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

Data importing and exporting

• Data export approach: Users can export their data through the management portal or via the API. Administrators can download configuration data, credential templates, workflow definitions, and audit logs directly in standard export formats. API endpoints allow automated extraction for larger or recurring exports. For client‑hosted deployments, all data remains fully accessible within the buyer’s own environment, enabling direct export without Condatis involvement. Professional services are available for more complex or large‑scale data extraction needs.
• Data export formats:
  • CSV
  • Other
• Other data export formats:
  • JSON
  • PDF
• Data import formats:
  • CSV
  • Other
• Other data import formats: JSON

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection between networks: Data in transit is protected using strong encryption, including TLS 1.2+ for all browser, API, and service‑to‑service communication. Mutual TLS or VPN tunnels can be used where secure private connectivity is required for integrations with legacy systems or client‑hosted components. Network traffic is monitored for anomalies, and strict authentication and authorisation controls are enforced for all API access. No unencrypted channels are permitted.
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • Other
• Other protection within supplier network: Data within the network is protected through strong encryption at rest, strict role‑based access controls, network segmentation, and continuous monitoring. All internal service communication uses TLS 1.2+, and sensitive workloads run in isolated environments. Access to management systems is restricted, logged, and audited. Infrastructure follows secure‑by‑design practices, with regular vulnerability scanning, patching, and compliance reviews to ensure ongoing protection of customer data.

Availability and resilience

• Guaranteed availability: We guarantee a monthly service availability of 99.9% for the Condatis‑managed SaaS platform, excluding scheduled maintenance windows. Availability is monitored continuously, and any service degradation or outage is logged and reviewed as part of our operational processes. Scheduled maintenance is communicated to customers in advance to minimise disruption.; ; If availability falls below the guaranteed level, customers are eligible for service credits, calculated as a percentage of the monthly service fee and applied to a future billing period. Service credits are the sole remedy for failure to meet availability targets.; ; For client‑hosted deployments, availability is determined by the customer’s own cloud environment and infrastructure configuration. Condatis provides guidance and support to help customers achieve equivalent availability levels through recommended deployment patterns.; ; Our SLAs cover uptime, incident response, and resolution times, ensuring reliable and predictable service performance throughout the contract term.
• Approach to resilience: Cenda is engineered for resilience through a layered architecture and fault‑tolerant cloud design. The Condatis‑managed SaaS deploys across multiple availability zones, with stateless services behind load balancers and autoscaling to absorb spikes. Stateful components use highly available managed services with replication and automated failover. Configuration is codified with Terraform (Infrastructure‑as‑Code) to ensure consistent, repeatable recoveries and rapid environment rebuilds.; ; Continuous monitoring and alerting cover health, latency, error rates, and capacity. Backups are encrypted and performed on a scheduled cadence; restoration procedures are tested regularly. Network paths are segmented, and zero‑trust controls reduce blast radius. Release pipelines employ staged rollouts and automated rollback to minimise change risk.; ; Disaster recovery options—including cross‑region deployment, defined RPO/RTO targets, and emergency runbooks—are available on request. For client‑hosted deployments, Condatis provides reference architectures and guidance to achieve equivalent resilience using the buyer’s cloud regions, availability zones, backup policies, and scaling settings.; ; A detailed datacentre and platform resilience overview, including component‑level dependencies, failover sequencing, and recovery playbooks, is available to buyers under NDA on request.
• Outage reporting: Outages are reported through multiple channels to ensure timely communication. Customers receive email alerts for any service disruption, planned maintenance, or degradation. A service status page is available to provide real‑time visibility of incidents, maintenance windows, and current system health. For clients requiring deeper integration, API‑based status information can be made available to support automated monitoring or alerting within their own environments. Regular post‑incident reports are shared as part of the service review process, detailing root causes, remediation actions, and improvements to prevent recurrence.

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
  • Other
• Other user authentication: Users authenticate through Microsoft Entra ID, which provides secure access using multi‑factor authentication and modern identity federation. Administrators sign in through the browser‑based portal using their organisational Entra accounts, with MFA enforced according to the buyer’s policies. API clients and non‑human identities authenticate using certificates, signed tokens, or service principals. All authentication requests occur over encrypted channels, and access is granted based on defined roles and permissions. No unauthenticated access to management functions or APIs is permitted.
• Access restrictions in management interfaces and support channels: Access to the management portal is restricted through Microsoft Entra ID authentication and role‑based access controls, ensuring only authorised administrators can configure or manage the service. Permissions are assigned using least‑privilege principles, and privileged actions require MFA. API access is restricted using service principals, certificates, or signed tokens. Support channels such as the ticketing portal only allow access to verified customer contacts, and all interactions are logged. Sensitive information is never disclosed without prior authorisation, and identity verification is required before making changes or discussing account‑specific details.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
  • Other
• Description of management access authentication: Management access is authenticated through Microsoft Entra ID using multi‑factor authentication and federated identity. Administrators sign in with their organisational Entra accounts, with MFA required for all privileged actions. Access is further restricted through role‑based permissions, ensuring only authorised users can perform management functions. API‑based management actions use certificates, signed tokens, or service principals for strong authentication. All authentication requests occur over encrypted channels, and no unauthenticated or anonymous access to management interfaces is permitted.

Audit information for users

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

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards:
  • CSA CSM version 4.0
  • ISO/IEC 27001
  • Other
• Other security governance standards: Cyber Essentials Plus, ISO 9001, Secure Development Lifecycle practices, NIST‑aligned data sanitisation controls, and industry‑standard penetration‑testing methodologies.
• Information security policies and processes: We operate a comprehensive Information Security Management System aligned to ISO/IEC 27001, supported by documented policies covering access control, data protection, secure development, vulnerability management, incident response, and business continuity. Policies apply to all staff and contractors and are reviewed annually or when significant changes occur. Mandatory training, regular security awareness updates, and defined disciplinary procedures ensure compliance.; ; A formal reporting structure is in place: security responsibilities are assigned to dedicated roles, with escalations routed through the Security Lead and ultimately to an executive‑level owner accountable for governance. All policy exceptions or security events must be logged, assessed, and approved through defined processes.; ; Secure development practices are followed throughout the software lifecycle, including code reviews, dependency checks, threat modelling, and regular penetration testing. Access to systems is restricted using role‑based controls and multi‑factor authentication. Logs are monitored for anomalies, and changes follow controlled configuration‑management procedures.; ; Internal audits, external assessments, and continuous monitoring ensure policies remain effective and consistently applied across the organisation.
• 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: We follow a controlled configuration and change‑management process aligned to our ISMS and secure development lifecycle. All service components are tracked throughout their lifetime using version control, asset registers, and documented configuration baselines. Changes follow a formal assessment process that evaluates security, operational impact, and dependency risks before approval. High‑risk changes require additional review and testing before release. Deployments use automated pipelines to ensure consistency, traceability, and rollback capability. All changes are logged, monitored, and periodically reviewed to ensure compliance, with audit trails maintained for governance and security assurance.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: We operate a risk‑based vulnerability management process within our ISO 27001 ISMS. Potential threats are assessed via continuous infrastructure scanning, code‑dependency/SBOM analysis, container image scanning, and configuration baseline checks. We prioritise remediation using CVSS scores, exploitability, asset criticality, and exposure. Patches for critical issues are deployed within 24–72 hours; high within 7 days; medium within 30 days; low within planned cycles. Threat intelligence is sourced from vendor advisories, CVE/NVD feeds, OWASP, cloud provider security bulletins, and trusted CERT/NCSC alerts. All actions are tracked to closure with verification scans and audit trails.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: We use continuous logging and monitoring across infrastructure, applications, and access events to identify unusual activity or indicators of compromise. Automated alerts flag anomalies such as failed authentication attempts, privilege escalation, configuration changes, or suspicious API usage. When a potential compromise is detected, it is triaged immediately, with critical incidents investigated and contained within 30 minutes. Our incident‑response process includes isolation, root‑cause analysis, remediation, and follow‑up reporting. Logs are retained for forensic analysis, and monitoring rules are updated to prevent recurrence.
• 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 follow a defined incident‑management process covering detection, triage, escalation, containment, remediation, and post‑incident review. Pre‑defined runbooks exist for common events such as service outages, performance degradation, unauthorised access attempts, and integration failures. Users can report incidents through the support portal or by email. All incidents are logged and tracked through to resolution, with critical issues acknowledged within 30 minutes. Incident reports, including root cause, impact, and corrective actions, are provided to customers after closure and shared again during scheduled service reviews. Continuous improvements are implemented based on lessons learned.
• 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: Yes
• 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: 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%

Standards and certifications

• ISO/IEC 27001 certification: Yes
• ISO/IEC 27001 accredited by: Centre for Assessment
• ISO/IEC 27001 accreditation date: Wednesday 24 April 2024
• What the ISO/IEC 27001 doesn’t cover: Out of scope for the Condatis ISO 27001:2022 certificate:; - Any office locations other than Edinburgh; - Business activities not related to digital identity and access management; - Customer‑owned or customer‑hosted environments; - Third‑party systems or services not included in Condatis’ ISMS; - Products/platforms not developed or supported by Condatis; - Any controls or activities excluded in Statement of Applicability v2
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• ISO 9001 certification accredited by: Centre for Assessment
• ISO 9001 accreditation date: Wednesday 24 April 2024
• What the ISO 9001 doesn’t cover: The following activities and areas are not covered by Condatis’ ISO 9001:2015 certification:; - Activities outside the provision of digital identity & access management solutions; - Non‑IAM consultancy, products, or service lines; - Sales, marketing, finance, HR, legal, and executive corporate functions; - Any office locations other than the Edinburgh HQ; - Customer‑hosted or customer‑managed environments; - Third‑party systems not included in Condatis’ Quality Management System; - Any activities excluded within Condatis’ internal Quality Manual/QMS scope
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Cyber Essentials Certificate Number: Bfa164bc-3281-4172-8320-4754934cded4
• Cyber essentials plus: Yes
• Cyber Essentials Plus Certificate Number: Fc2b79db-abcd-4e57-9095-972b3119da7b
• Other security certifications: No

Social value

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

  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

  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
  • 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
  • Plans to respond flexibly and adapt approaches to community engagement and initiatives
  • 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
  • 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
  • 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)
  • Understanding of the issues affecting the representation of disabled people in the workforce in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
  • Inclusive and accessible recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
  • Offering a range of quality opportunities with routes of progression if appropriate, e.g. T Level industry placements, students supported into higher level apprenticeships.
  • Working conditions which promote an inclusive working environment and promote retention and progression
  • 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

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