Scoped engineering support

Diagnostic cartridge design

Connect the assay workflow to the disposable device. Define sample and reagent handling, reader interfaces, and the evidence a cartridge prototype needs to produce.

Scope, responsibilities, timing, and fees are agreed before paid work begins.

The engineering question

A work product tied to your next decision.

Moving a manual assay into a cartridge changes more than its geometry. User steps, volumes, timing, material compatibility, controls, and the reader interface become connected design decisions. An architecture brief can make these dependencies visible before detailed CAD or supplier handoff.

Example work products

  • A sample-to-readout workflow and functional cartridge architecture.
  • A map of sample, reagent, waste, optical, and mechanical interfaces relevant to the proposed device.
  • A requirements and risk-question register connecting design assumptions to evidence gaps.
  • A prototype roadmap with bench checks and proposed review criteria.

These are examples, not a bundled commitment. The agreed scope defines the actual outputs and review criteria.

Useful starting inputs

  • A non-confidential assay protocol and intended research or development use.
  • Sample type, reagent needs, incubation steps, and available bench evidence.
  • Known reader, optical, mechanical, or manufacturing constraints.
  • The current development stage and decision that the cartridge design must support.

Share non-confidential information in the initial enquiry. A finished specification is not required.

Decisions to make explicit

Questions the work can help resolve.

Disposable workflow

What does the user do, what does the device do, and where could an invalid sample or failed step go unnoticed?

Assay and reader interfaces

Which fluidic volumes, optical regions, mechanical alignments, and timing requirements must be defined together?

Verification planning

Which proposed checks can establish transfer, containment, sequence, or readout behavior at the prototype stage?

Development work you can inspect

Explore the technical context.

CLAIR illustrates an in-development centrifugal platform and its open evidence questions. It is not a validated cartridge, a commercial diagnostic, or a customer case study.

Review the CLAIR development workflow ↗

Before we begin

Common project questions.

Does cartridge design include assay validation or regulatory approval?

No. Assay validation, clinical evaluation, regulatory strategy, and approvals are separate workstreams. The agreed scope must state the intended use and evidence boundaries.

Can a manual assay be the starting point?

Yes. A manual workflow and its bench observations can be used to identify cartridge functions, interfaces, and experiments. Transfer into a device does not establish equivalent performance.

Will the first deliverable be a production-ready cartridge?

Not by default. Early work may be an architecture or prototype brief. Detailed design, manufacturing responsibility, verification, and release criteria require their own agreed scope.

Start a conversation

Describe the question. Define the next step.

Send a short technical brief with the current stage, constraints, and result you need. We will review your enquiry and follow up by email.

Discuss diagnostic cartridge design