Project & Programme Delivery
We run decontamination and sterile services programmes end to end, from business case through validation to go-live. That is the core of what we do, and the discipline it demands travels: the same governance, the same gates and the same evidence apply to a business change, a relocation or a system rollout in any sector. Where a programme needs IT, we have our own consultants to draw on rather than another supplier to coordinate, so the equipment, the rooms and the systems get planned together.
Three Kinds of Programme
Decontamination is where we are strongest, and it is the hardest version of this work: fixed dates, a regulator, a Notified Body and a service that cannot stop. What travels is the discipline rather than the setting. The same governance, gates and evidence run a business change, a relocation or a system rollout in any sector, to the same standard.
SSD & CSSD builds
Programme management for new and refurbished sterile services departments: equipment, rooms, IT, validation and handover to an audit-ready state.
Track & trace implementations
Selecting, configuring and migrating instrument tracking systems, including item and set data moved between systems without losing history.
Super centres & service change
Consolidation, capacity planning and transition, so service continues while the operation moves underneath it.
Where these projects come unstuck
Decontamination projects rarely fail on the engineering. They fail in the gaps between the people doing it. These are the five we see most, and what we do about each one.
The equipment, the room and the network are designed separately
Three suppliers design three things to three briefs. The gaps between them are invisible on paper and obvious on the day the machines arrive and nothing will talk to anything.
We design them as one job. The equipment schedule, the room layout and the network come out of the same conversation, because decontamination equipment, the data it produces and the building it sits in are a single problem.
Configuration happens on site, against a fixed date
Kit arrives in boxes and gets built in a corridor in the week before an audit. Anything that does not work is discovered in the worst possible week, with no time left to do anything about it.
We build and test on our bench before anything reaches the building. Installation day becomes patching and checking rather than configuration, which is what makes a fixed audit date survivable.
Evidence gets assembled after the fact
The work was done properly, but nobody captured the proof while it was happening. Validation then turns into an archaeology exercise, reconstructing months of decisions from memory and email.
Evidence is produced as the work happens, in the form qualification and a Notified Body audit actually ask for. Segmentation and failover are tested and recorded, not assumed.
Decisions have a sign-off but not a signatory
Everyone agrees a stage is complete. Months later, when something has to change, nobody can say who decided what, and the project relitigates a question it already answered.
We name who signs off each stage before the stage starts, and write down the decision with it. It takes minutes at the time and removes an entire category of argument later.
Tracking data loses its history on migration
Item and set records move to the new system, but the history behind them does not. The first time anyone needs to look backwards, usually under pressure, is when that gets discovered.
We treat the history as part of the migration, not as something to reconcile afterwards, and we prove it moved before the old system is switched off.
A sequence we run every time
The same five stages, whether it's a single washer replacement or a new-build department. Each one has an agreed exit before the next begins.
- 1
Define
We agree the brief, the business case, the scope and what success looks like, in writing, before anything is designed. That includes who signs off each stage, so there is no ambiguity later about who decided what.
- 2
Design
Equipment, room layout, systems and the network are designed together rather than in sequence. Decontamination equipment, the data it produces and the building it sits in are one problem, and designing them separately is where most projects come unstuck.
- 3
Build
Installation is managed on site, and the IT is built and tested on our bench before it ever reaches the building. That means installation day is patching and checking rather than configuration, which is what keeps a fixed audit date achievable.
- 4
Validate
Machines, systems and data are verified against the requirements, with the evidence qualification and a Notified Body audit will actually ask for. Segmentation and failover are tested, not assumed.
- 5
Go live & support
Audit, a full as-built handover pack and an honest list of open items. Then we stay on as the support partner, because the best measure of a project is how it runs a year later.
What you are left holding
A project is finished when the department can run and prove itself without us in the room. That means the paperwork matters as much as the kit, and it is the part most often left thin.
- An as-built pack: layouts, equipment schedule and network design as they actually ended up, not as first drawn.
- The evidence pack: verification records against the requirements, in the form an audit asks for.
- Credentials, licences and administrative access, documented and formally handed over.
- An honest list of open items, each with an owner and a date, rather than a clean report and a surprise.
- A named person who stays on, so the first question after go-live goes to someone who was there.
Two we can talk about
Clients stay unnamed unless they have told us otherwise.
A secure, resilient network in five weeks
A regulated production facility needed a complete, segregated network built, tested and live before validation started.
- 5 weeks approval to live
- 10 segregated networks
- 0 ports open from the internet
A new-build SSD, from empty building to audit
A new building with the audit date already fixed, the permanent line not yet installed and the corporate network months away.
- Bench-built before site
- Separate networks per system
- Stayed on as support partner
What people ask before they call
Do you only take on whole departments, or smaller projects too?
Both. The same five stages run whether it is a single washer-disinfector replacement or a new-build department; the difference is how long each stage takes, not whether it happens. If a job is small enough that our process would cost more than it saves, we will tell you that rather than sell it to you.
Can you pick up a project that has already started?
Yes, and it is a common way to work with us. We start with an honest review of where the project actually is, as opposed to where the plan says it is, and give you a written view of the gap and what we would do next. Taking over mid-flight is a different job from starting clean, and we scope it as one.
Do you work outside the NHS and outside healthcare?
Yes. Our background is sterile services, where the standards are about as demanding as they get, and the same engineering applies anywhere a site has machines, data and people that have to be kept apart. We work with independent providers, manufacturing sites and laboratories as well as NHS trusts.
Who owns the design and the evidence at the end?
You do. The as-built pack, the evidence pack and the administrative credentials are yours, handed over in full, whether or not you keep us on afterwards. We do not hold a department hostage to its own documentation.
Do you stay involved after go-live?
Usually, because the best measure of a project is how it runs a year later, and because the team that built something is the team that can fix it quickest. It is not a condition of the project, though. If you would rather take it in-house at handover, the pack is written so that you can.
Planning a department, or a move?
Tell us where the project is up to, whether that's business case, design, or already on site, and we'll tell you honestly what we'd do next.