A structured tender workflow covering need definition, specifications, bidder evidence, evaluation, award and contract mobilisation. The purpose is to help teams make a clearer, better documented decision without turning a commercial checklist into a clinical recommendation.
Quick answer
Tenders fail when specifications are copied from catalogues, evaluation rules are vague or post award implementation is ignored. A stronger approach produces a fair, auditable tender that protects clinical requirements while enabling comparable competition.
This is the pillar guide for the topic cluster. Use the linked specialist guides to build operating checklists for individual tasks. The main search topic for this guide is medical device tender preparation. Related language includes medical equipment tender, hospital tender specification, medical device bid evaluation, but the article uses those terms only where they help the reader rather than repeating them mechanically.
Why this matters
A medical device tender should convert a clinical and operational need into clear, testable requirements. The evaluation model must be written before bids are reviewed, and mandatory failures should not be hidden inside a high total score.
For hospital procurement committees, project teams, finance, quality and clinical stakeholders, the practical risk is not limited to price. A wrong reference, incomplete pack, uncertain shelf life, late shipment or unsupported alternative can create rework, unused inventory and avoidable delays. A useful buying process therefore connects the technical request, commercial offer and receiving standard.
The best time to resolve ambiguity is before the purchase order. Once goods are dispatched, every unclear field becomes harder and more expensive to correct. The controls below are designed to move important questions to the beginning of the process.
Key checks
| Check | What to do | Why it matters |
|---|---|---|
| Need statement | Describe the service need, scope, volumes and outcomes before naming products. | A clear need supports better specifications and evaluation. |
| Specification design | Use performance and compatibility requirements where appropriate, while retaining exact references when genuinely necessary. | Specifications should be precise without creating accidental ambiguity. |
| Bidder evidence | List legal, quality, product, logistics and service documents with submission rules. | Bidders need one visible compliance standard. |
| Evaluation model | Separate mandatory requirements from weighted criteria and price. | A high score should not rescue a mandatory failure. |
| Mobilisation | Include stock transition, training, data setup, delivery and performance reporting. | Award is the start of implementation, not the end. |
These checks should be adapted to product risk and organisational policy. A routine low risk item and a sterile implantable or procedure critical device should not automatically receive the same depth of review.
A practical workflow
- Step 1: Form a cross functional tender team and governance plan. Record the owner, evidence and completion date so the action can be checked later.
- Step 2: Analyse demand, current performance and market options. Record the owner, evidence and completion date so the action can be checked later.
- Step 3: Draft and challenge the specification. Record the owner, evidence and completion date so the action can be checked later.
- Step 4: Publish clear response schedules and evidence requirements. Record the owner, evidence and completion date so the action can be checked later.
- Step 5: Evaluate consistently and document clarifications. Record the owner, evidence and completion date so the action can be checked later.
- Step 6: Mobilise the contract and monitor agreed indicators. Record the owner, evidence and completion date so the action can be checked later.
A workflow is only useful when exceptions are visible. If a field is unknown, mark it as unknown and assign an owner. Do not fill the gap with an assumption merely to complete the form. The decision record should show what was confirmed, what remained conditional and which stakeholder accepted the residual risk.
Documentation and verification
Vendor evidence should match the approved scope. Legal documents, quality controls, product capability, logistics, service and commercial integrity all matter, but the depth of review should remain proportionate to product and supply risk.
The tender and vendor file should allow another reviewer to follow the decision without relying on memory. Clarifications, scoring, conflicts, approvals, mobilisation actions and performance reviews should be documented consistently.
For every important document, record the document title, issuing organisation, product or company scope, version or validity date, source and date reviewed. This simple index helps prevent a valid document from being attached to the wrong product or reused after it becomes outdated.
Minimum decision record
- The original request and clinician or technical approval where required
- The exact quoted product identity, pack and quantity
- Supplier assumptions, deviations and proposed alternatives
- Quality, regulatory and traceability evidence proportionate to risk
- Price basis, landed cost assumptions, lead time and shelf life
- Approval names, dates and any conditions
- Receiving checks and final disposition of discrepancies
Questions to ask before approval
- Can the supplier demonstrate the need statement described in the RFQ, and can the answer be connected to the exact quoted product?
- Can the supplier demonstrate the specification design described in the RFQ, and can the answer be connected to the exact quoted product?
- Can the supplier demonstrate the bidder evidence described in the RFQ, and can the answer be connected to the exact quoted product?
- Can the supplier demonstrate the evaluation model described in the RFQ, and can the answer be connected to the exact quoted product?
- Can the supplier demonstrate the mobilisation described in the RFQ, and can the answer be connected to the exact quoted product?
Ask suppliers to answer against each RFQ line rather than in a general email. A line level response makes it easier to compare offers, detect partial matches and transfer the approved information into the purchase order.
Common mistakes
- Copying one manufacturer’s marketing language into a broad tender. Correct it by returning to the approved requirement, recording the missing evidence and resolving the gap before the order or release decision.
- Changing evaluation criteria after bids are opened. Correct it by returning to the approved requirement, recording the missing evidence and resolving the gap before the order or release decision.
- Combining mandatory and desirable requirements. Correct it by returning to the approved requirement, recording the missing evidence and resolving the gap before the order or release decision.
- Failing to plan depletion of existing stock. Correct it by returning to the approved requirement, recording the missing evidence and resolving the gap before the order or release decision.
Most procurement errors are not caused by one dramatic failure. They develop through several small gaps, such as an abbreviated name, an unrecorded assumption and a receiving check that compares quantity but not reference. Closing those gaps consistently is more effective than adding a large document request after a problem occurs.
Practical example
A tender for cath lab consumables initially specifies broad family names. The team converts them into controlled line items, compatibility fields and mandatory documentation, then publishes the scoring model before bids are received.
The lesson is not that every enquiry must become slow. A structured template is usually faster because it reduces repeated emails and makes approval requirements visible from the start.
Final checklist
- Need statement has been reviewed: Describe the service need, scope, volumes and outcomes before naming products.
- Specification design has been reviewed: Use performance and compatibility requirements where appropriate, while retaining exact references when genuinely necessary.
- Bidder evidence has been reviewed: List legal, quality, product, logistics and service documents with submission rules.
- Evaluation model has been reviewed: Separate mandatory requirements from weighted criteria and price.
- Mobilisation has been reviewed: Include stock transition, training, data setup, delivery and performance reporting.
Before closing the file, confirm that the purchase order reflects the approved quotation rather than an earlier draft. At receiving, compare the physical label and condition with the same approved record. This completes the link between request, order and delivered product.
Frequently asked questions
Should a tender name a brand?
This depends on the need, compatibility, policy and applicable procurement rules. Specifications should be justified, accurate and reviewed for competition implications.
What is a mandatory criterion?
It is a requirement a bid must meet to remain eligible. It should be objective, relevant and clearly stated.
How should samples be evaluated?
Use a predefined, ethical and documented protocol with qualified reviewers, consistent criteria and appropriate clinical governance.
Related AJA guides
Browse the medical device product catalogue, review the brand sourcing profiles or read about AJA International’s quality and compliance approach.
Send the manufacturer, catalogue number, configuration, quantity, destination and required delivery date. AJA International can review the enquiry and identify any missing information before quoting.
Official resources and further reading
- WHO health product procurement resources
- European Commission medical devices sector
- FDA medical device information
Editorial review: Prepared for publication in 2026. Regulatory, registration and product information can change, so readers should confirm current requirements and manufacturer documentation before acting.