How we work
Four steps, and the order does not change. We don’t install before the scope is agreed, and we don’t hand over without training and handover documents.
Scoping call
We start by listening to your work and the questions you face in audits. The output of this call is not a quote but the scope in writing: which processes go into the system and which stay outside.
Output of this step
- The scope in writing: which processes go in and which stay outside
- The list of standard clauses to be covered
- If data migration is needed, what can be migrated
Installation and adaptation
Depending on your preference, the installation runs on your own servers or on servers we host. Either way, the installation belongs to your organisation alone: a separate database, permission scheme and backup plan. Everything specific to your organisation — methods, formulas, document types, approval flows — is set up through configuration, not hard-coded.
Output of this step
- An installation of your own — on your own servers or hosted by us
- Separate database and permission scheme
- Configured document types, approval flows and organisation-specific rules
- Backup plan
Training and handover
Handover is done with role-based training and handover documents: separately for everyday users, the quality manager and the IT department. For the product with validation infrastructure in place (Labdata LIMS), installation, operational and end-to-end validation (IQ · OQ · PQ) records are also produced and delivered.
Output of this step
- Role-based training: users, quality manager, IT department
- Handover documents
- IQ · OQ · PQ records and standard clause – screen mapping for Labdata LIMS
Maintenance and support
After handover, version upgrades continue and changes to standards are reflected in the system. What an upgrade changes is written in the release notes.
Output of this step
- Version upgrades and release notes
- Reflecting changes to standards in the system
What happens after handover
Handover is not the moment the work ends; it is the moment the system changes owner. From then on, everyday configuration — a new method, a new document type, a new approval step — can be done by the organisation’s own quality manager. What they cannot do is touch the code; and since we leave no rule embedded in code, there is no need to.
What a version upgrade changes is written in the release notes. For Labdata LIMS, validation records are produced again after an upgrade; “nothing broke” does not count as evidence on its own.
The first step is a conversation
Tell us what you are working on and which questions you face in audits. Our first reply will not be a price list but how the scope should be set up.
We reply the same day.