Release cadence
| What | How often |
|---|---|
| Major release | One a year |
| Updates | Weekly |
| Critical updates | Not later than one working day |
Standard maintenance — bug fixing, system upgrades, software updates and secure updates, covering the application, the database and the operating system — is included in every support tier, including the free Basic tier. On-going updates carry no additional charge.
Standard releases and updates do not require planned downtime: you do not need to book a maintenance window, and users are not asked to stop work while we release.
How a release reaches you
Each customer has three environments: Test, Training and Production. Test and Training mirror the configuration of your production instance — the same forms, workflows, rules and structures — with their own access, single sign-on registration and notification routing, so changes can be trialled and staff trained without touching live data. Production data is not copied into them.
A release goes to your Test environment first, so it can be seen against your own configuration, and then to Production. Configuration moves between environments as configuration objects rather than being rebuilt by hand, and each promotion is recorded in the full audit trail — when, who, what and how it changed.
How we tell you about a release
We notify customers of releases by email and on the support portal. Release communication also runs through your named manager, who is your single point of contact.
Release notes are produced for every release and sent to customers by email.
Where a change needs you to alter your own configuration, we tell you before the release rather than with it.
Legislative and regulatory change
We track changes to health and safety legislation and to regulator guidance that bear on the system — for example a change to RIDDOR reporting requirements, or a change in HSE guidance. Monitoring regulatory change is a documented responsibility, assigned to a named role rather than left informal.
Statutory and regulatory change is delivered through the same release process as any other change, and is notified with it. The notification says what has changed and why: the legislative or regulatory source, what has changed in the system as a result, and what — if anything — you need to do at your end.
How customers feed into the roadmap
Every customer has a named manager as a single point of contact, at no separate charge. Requests for change, and the priority you attach to them, reach us through that manager, through the support portal and by email.
Service reporting and review with your named manager form part of your support subscription, and are one of the routes by which customer priorities reach the roadmap. Third parties acting for you — for example a managed service provider — may raise and escalate items on your behalf on the same channels.
The support portal also carries an ideas and feature-request board that customers can see and vote on.
AI capabilities
AI is not an active component of the service as supplied. The core service operates on deterministic, rule-based processing; no AI or machine-learning model takes part in recording, workflow, assessment, scoring or reporting.
AI capability is optional, separately enabled and separately priced. It is not part of the standard release stream: no major release or weekly update switches it on. It is enabled only where a customer chooses it, either as an integration with a commercially available tool the customer selects and supplies credentials for, or as a separate Bondap capability enabled on the published additional-module basis.
Customer data is never used to train, fine-tune or evaluate AI or machine-learning models, and is not sent to any third-party AI service.
Questions about releases or the roadmap: gc@bondap.com
© BONDAP LTD. This document is the property of Bondap and is published for information only. It may not be copied, reproduced, adapted, distributed or used for any purpose without our prior written consent.