In complex research equipment procurement, one of the most useful documents is often also one of the simplest:

a deviation list.

Yet many buyers do not request one.

Instead, they receive a quotation, technical proposal, product brochure, datasheet, and several emails—and assume that anything not explicitly questioned by the supplier is included and compliant.

That assumption can become expensive.

For a VSM, MOKE system, Hall effect measurement platform, cryogenic system, electromagnet, Helmholtz coil, or other customized research instrument, a proposal may satisfy 90% of the requirement while differing from the specification in several important details.

Those differences are not necessarily problems.

The real problem is discovering them after the purchase order.

A deviation list in research equipment procurement provides a structured way for the supplier to state:

• What fully complies
• What differs
• What is offered as an alternative
• What is optional
• What is excluded
• What still requires clarification

Used correctly, it turns technical ambiguity into something that procurement, engineering, distributors, and suppliers can review together.

1. What Is a Deviation List?

A deviation list is a project-specific document identifying where the offered equipment differs from the buyer’s stated requirement.

A simple format may include:

• Requirement number
• Buyer requirement
• Supplier offer
• Compliance status
• Description of deviation
• Technical impact
• Proposed alternative
• Buyer disposition

For example:

Item	Buyer Requirement	Offered Configuration	Status
Magnetic field	≥1 T at 40 mm gap	0.85 T at 40 mm gap	Deviation
Uniformity	±1% over 20 mm DSV	±0.8% over 20 mm DSV	Comply
Temperature	80–500 K	80–500 K	Comply
Python API	Required	Not included in standard software	Deviation
CSV export	Required	Included	Comply

The document does not need to be complicated.

Its purpose is to make differences visible.

2. Why “No Comment” Should Not Automatically Mean “Comply”

This is one of the most dangerous assumptions in technical procurement.

Suppose a tender specification contains 80 requirements.

The supplier’s proposal discusses only 25 of them.

What does that mean for the remaining 55?

Possibilities include:

• Fully compliant
• Not reviewed
• Not applicable
• Standard but undocumented
• Available only as an option
• Technically impossible
• Supplier interpreted the requirement differently

A buyer should not have to guess.

For formal projects, each important requirement should receive an explicit status.

ISO/IEC/IEEE 29148 describes requirements engineering as the process connecting acquirer and supplier needs and emphasizes requirements that are specific, precise, documented, analyzed, verified, and managed throughout a system life cycle. That principle is directly relevant to complex instrument procurement: requirements become useful only when both sides understand what they mean and how they will be addressed.

3. A Deviation List Is Different from a Compliance Matrix

The terms are sometimes used interchangeably, but they serve slightly different purposes.

Compliance Matrix

Usually lists all relevant requirements and the supplier’s response to each.

Typical statuses:

• Comply
• Partial compliance
• Deviation
• Not applicable
• Optional
• Clarification required

Deviation List

Usually focuses only on requirements where the supplier does not fully match the requested specification.

A practical procurement workflow can use both:

Compliance Matrix → identifies everything

Deviation List → isolates the exceptions

For a relatively simple purchase, the compliance matrix alone may be sufficient.

For a large system or tender, maintaining a separate deviation register can make review easier.

4. When Should You Ask for a Deviation List?

A deviation list becomes particularly valuable when at least one of the following applies.

The Specification Is Long

If the requirement contains:

• 30
• 50
• 100
• or more technical clauses

it becomes difficult to manage compliance through email discussion alone.

The Equipment Is Customized

Examples include:

• Custom electromagnet
• Three-axis Helmholtz coil
• Cryogenic MOKE
• Low-temperature Hall system
• Integrated VSM platform
• Magnet + optical system

Customized systems naturally create engineering trade-offs.

Multiple Suppliers Are Being Compared

A deviation list helps normalize proposals that otherwise use completely different formats.

The Procurement Is Formal

Examples include:

• University tender
• Government procurement
• Corporate purchasing
• Distributor-led bidding
• EPC-style technical evaluation

Acceptance Depends on Specific Specifications

If one missing parameter could cause rejection, deviation control becomes especially important.

5. Tenders Are One of the Clearest Use Cases

Formal tenders often require suppliers to answer requirements line by line rather than simply referring buyers to brochures.

A current scientific-equipment tender published by the Central University of Karnataka provides a concrete example: its technical compliance sheet requires bidders to complete each column and explicitly identify deviations from the specification; it also states that simply referring the buyer to a catalogue or brochure is not sufficient.

This illustrates why deviation lists matter.

The buyer is not asking:

“Does your product generally look similar?”

The buyer is asking:

“Where does the offered configuration differ from what we specified?”

Check source: Central University of Karnataka technical tender document

6. But Do Not Assume Every Tender Allows Deviations

This distinction is critical.

Some tenders allow:

• Equivalent solutions
• Better specifications
• Minor deviations
• Alternative technical approaches

Others may state that certain requirements are:

• Mandatory
• Pass/fail
• Non-negotiable
• Required for responsiveness

In those cases, declaring a deviation may reveal that the offer is technically unacceptable.

That is not a reason to hide the deviation.

It is a reason to identify the issue before bid submission.

Tender rules vary by project and jurisdiction, so the actual bid document always takes priority.

7. Not Every Difference Is a Negative Deviation

Suppose the buyer requests:

Field uniformity: ±1%

and the supplier offers:

±0.5%

Technically, this exceeds the requirement.

That normally belongs under:

• Comply
• Better than required
• Exceeds requirement

rather than being treated as a problematic deviation.

Similarly:

Buyer:

Minimum field: 1 T

Supplier:

1.2 T at the specified working gap

This is usually compliance, assuming no related disadvantage changes the requested system architecture.

A deviation list should focus attention on meaningful differences, not punish suppliers for better performance.

8. An “Improvement” Can Still Create a System-Level Deviation

Higher numbers are not always better.

Consider an electromagnet.

The buyer requests:

• 0.8 T
• 50 mm pole gap
• Large optical access

Supplier proposes:

• 1.2 T
• 20 mm pole gap

The field specification looks better.

But the proposed system may be unusable because the customer’s cryostat cannot fit.

Therefore:

Performance must be evaluated against the complete requirement, not isolated numbers.

This is especially important for magnet systems where field, pole gap, cooling, dimensions, and access are coupled.

9. A Deviation Should State the Offered Value

A weak deviation statement says:

“Cannot fully comply.”

A useful deviation says:

Requirement: ≥1 T at 40 mm gap
Offered: 0.86 T at 40 mm gap
Alternative: 1 T can be achieved at approximately 30 mm gap
Impact: Customer’s current cryostat requires 38 mm minimum clearance

Now engineering can make a decision.

The purpose is not simply to mark a red box.

It is to expose the actual trade-off.

10. “Partial Compliance” Should Always Be Explained

Partial compliance is one of the vaguest statuses in procurement.

Suppose the buyer requests:

Automatic M–H, M–T, scripted sequences, and Python API.

Supplier writes:

Partially compliant.

That is nearly useless.

A better response is:

• Automatic M–H: Comply
• Automatic M–T: Comply
• Sequence testing: Comply
• Python API: Not included
• External scripting: Optional/custom development

Now the buyer understands the boundary.

Whenever “partial compliance” appears, it should trigger a detailed explanation.

11. Deviation and Clarification Are Not the Same Thing

This distinction prevents unnecessary conflict.

Deviation

The supplier understands the requirement but offers something different.

Example:

Required: 4 K minimum
Offered: 10 K minimum

Clarification

The requirement is not sufficiently defined to determine compliance.

Example:

Required: “High magnetic-field uniformity”

The supplier cannot confirm compliance because no:

• Percentage
• Spatial region
• DSV
• Plane
• Volume

has been defined.

That is not yet a deviation.

It is a clarification request.

12. Clarifications Should Be Closed Before They Become Deviations

Consider:

Buyer:

“Large uniform magnetic-field region required.”

Supplier assumes:

±2% over 50 mm DSV.

Buyer actually expected:

±0.5% over 100 mm DSV.

The supplier may believe the system complies.

The buyer may believe it does not.

The real failure occurred earlier:

the requirement was not measurable.

This is why clarification and deviation management should work together.

13. Alternatives Should Be Listed Separately

Sometimes the requested configuration is technically possible but inefficient.

For example:

Buyer requests:

• 1 T
• 80 mm gap
• Large optical access
• Compact desktop magnet

The supplier may determine that achieving all four requirements simultaneously creates:

• Very high power
• Large cooling demand
• Heavy magnet
• Significantly higher cost

A useful technical response might propose:

Requested Configuration

Possible, but large and expensive.

Alternative A

0.7 T at 80 mm gap.

Alternative B

1 T at 50 mm gap.

Alternative C

Different magnet geometry with improved optical access.

These should be clearly identified as alternatives—not silently substituted.

14. Options Are Not Deviations Either

Suppose a VSM quotation states:

• Room-temperature VSM included
• Low-temperature option available
• High-temperature option available

If the customer requires low temperature, but it is only listed as an optional extra, that becomes a scope issue.

However, if the customer never requested low temperature, it is simply an option.

Therefore, useful compliance categories may include:

• Comply
• Exceeds
• Deviation
• Optional
• Not offered
• Not applicable
• Clarification required

This is more informative than a simple Yes / No table.

15. Commercial Deviations Should Usually Be Separated from Technical Deviations

A supplier may technically comply but request different commercial conditions.

Examples include:

• Payment terms
• Warranty duration
• Delivery schedule
• Incoterms
• Liquidated damages
• Bond requirements

These are commercial deviations.

Technical deviations may include:

• Field strength
• Temperature
• Sample dimensions
• Software capabilities
• Interface limitations

Separating them makes evaluation much cleaner.

Engineering should not have to search through payment clauses to find a magnetic-field exception.

16. Documentation Deviations Can Also Matter

Some projects specify mandatory deliverables such as:

• User manual
• Calibration certificate
• Factory test report
• Installation drawing
• CE documentation
• Training certificate
• Country-of-origin documentation

If the supplier cannot provide one of these documents, that can be a deviation even if the equipment itself performs correctly.

This is particularly relevant for:

• Government tenders
• University procurement
• Distributor projects
• Institutional acceptance processes

Do not treat documentation obligations as administrative details if they affect acceptance.

17. Interface Deviations Are Often More Dangerous Than Performance Deviations

A system may meet every headline performance number but still fail integration.

Consider a Hall system.

Buyer expects:

• Existing Lakeshore temperature controller
• Existing vacuum pump
• Existing sample holder

Supplier’s proposed system uses different:

• Sensor interfaces
• Vacuum flange
• Mechanical mounting

The Hall measurement specifications may all comply.

But the existing equipment cannot connect.

This is an interface deviation.

These differences deserve the same attention as core performance specifications.

18. Sample Compatibility Should Be Included

Research systems exist to measure real samples.

Therefore, sample compatibility belongs in the compliance review.

For VSM:

• Maximum dimensions
• Powder / film / bulk compatibility
• Sample moment range
• Holder type

For MOKE:

• Surface condition
• Sample size
• Field orientation
• Optical access

For Hall systems:

• Sample dimensions
• Hall bar / Van der Pauw
• Contact configuration
• Resistance range

A supplier should not simply state:

“Sample holder included.”

The offered holder should be compared with the actual sample requirement.

19. Magnetic-Field Deviations Need Operating Conditions

Consider this requirement:

Maximum field ≥1 T

Supplier:

Comply: 1 T

That may still be incomplete.

For electromagnets, ask:

• At what pole gap?
• Continuous or short duration?
• With what cooling?
• At what current?

For Helmholtz coils:

• At what working volume?
• Continuous duty?
• Single axis or simultaneous three-axis operation?

A deviation list is useful only when values are compared under equivalent conditions.

20. Uniformity Deviations Need Geometry

Buyer:

Uniformity ≤1%

Supplier:

0.8%

Still incomplete.

Over what region?

Possible definitions include:

• 10 mm DSV
• 50 mm cube
• 100 × 100 mm plane
• Entire sample volume

For magnet systems, uniformity without a spatial definition is not a complete requirement.

The deviation list should preserve these conditions.

21. Temperature Deviations Need Both Minimum and Maximum Limits

For cryogenic systems, “low temperature” is not enough.

The matrix should compare:

• Minimum temperature
• Maximum temperature
• Stability
• Cooling method
• Sample environment

Example:

Required: 80–500 K
Offered: 80–400 K
Status: Deviation
Alternative: 500 K option requires different heater/sample-stage assembly

That is actionable information.

22. MOKE Projects Often Need a Geometry Deviation List

For MOKE, a supplier may meet:

• Laser wavelength
• Kerr measurement
• Field range

but differ in:

• Longitudinal vs polar geometry
• Incident angle
• Sample rotation
• Pole gap
• Cryostat compatibility
• Optical access

These can fundamentally change the experiment.

A statement such as:

“MOKE supported”

is not enough.

The compliance review should separate optical and magnetic geometries.

23. VSM Automation Is Another Common Source of Hidden Deviations

Buyer requests:

“Fully automatic VSM.”

Supplier says:

“Fully automated.”

Both sides may still mean different things.

The deviation/compliance matrix should separate:

• Automatic field sweep
• Automatic M–H
• Automatic M–T
• Sequence measurement
• Temperature control
• Data export
• Scripting
• API
• External instrument integration

Otherwise, the missing capability may only become obvious after installation.

24. Hall Systems Need Method-Level Compliance

A Hall system may advertise:

• Carrier concentration
• Mobility
• Resistivity

But buyers may also require:

• +B/−B field reversal
• +I/−I current reversal
• Automatic contact switching
• Van der Pauw
• Hall bar
• Temperature sweeps
• Raw data export

These should appear as individual compliance lines where they matter.

One generic line stating:

“Hall measurement: comply”

is too broad for an advanced project.

25. Cryogenic Systems Need Utility Deviations

Suppose a system technically reaches 4 K.

But it requires:

• 400 V three-phase power
• Dedicated cooling water
• Specific compressor ventilation

and the customer’s laboratory does not have them.

Technically, the cryogenic specification may comply.

Operationally, the project does not.

Therefore, important site conditions should be included in the deviation review.

26. When Should the Supplier Prepare the Deviation List?

Ideally, before the final technical offer.

A useful sequence is:

Customer specification → Supplier review → Clarifications → Compliance matrix → Deviation list → Technical alignment → Final quotation → PO

This is much safer than:

Customer specification → Price → PO → Engineering review → Surprise

The earlier a deviation is discovered, the cheaper it is to solve.

27. When Should a Distributor Ask the Manufacturer for One?

For distributors and intermediaries, this is especially important.

The distributor may receive a 50-page tender specification but understand only part of the technical detail.

Sending the tender to a factory and receiving:

“We can do it.”

is not enough.

A better request is:

Please review every technical clause and provide a compliance/deviation table against the customer specification.

This transfers technical interpretation back to the engineering source where it belongs.

The distributor can then manage the commercial communication without accidentally guaranteeing an unverified requirement.

28. Do Not Rewrite the Manufacturer’s Deviation Into “Comply”

This deserves explicit warning.

Suppose the factory says:

“1 T is achievable only at a 20 mm gap; at the customer’s required 40 mm gap, maximum field is approximately 0.75 T.”

The distributor should not simplify this to:

“Field: 1 T — comply.”

That may help win the tender temporarily.

But it creates a technical obligation that the delivered system cannot satisfy.

The correct strategy is to determine whether:

• 0.75 T is acceptable
• Gap can be reduced
• Magnet can be redesigned
• Requirement is mandatory
• Bid should be abandoned

before submission.

29. A Good Deviation List Protects the Supplier Too

Deviation lists are often seen as buyer-protection documents.

They protect suppliers as well.

Without one, the buyer may later say:

“We assumed this function was included.”

The supplier may respond:

“We never offered it.”

Both statements may be true.

A deviation register creates a record that:

• Requirement was reviewed
• Difference was disclosed
• Alternative was proposed
• Buyer accepted or rejected it

That reduces future disputes.

30. The Buyer Should Formally Dispose of Each Important Deviation

Once deviations are identified, do not leave them unresolved.

Possible buyer decisions include:

Accepted

The offered difference is acceptable.

Rejected

Supplier must modify the proposal.

Accepted with Condition

Acceptable if another requirement is changed.

Clarification Required

More technical information needed.

Alternative Selected

Buyer chooses a proposed alternative.

The final status should be documented.

31. Accepted Deviations Should Flow Into the Final Technical Baseline

Suppose a buyer originally requested:

1 T at 40 mm gap

but formally accepts:

0.8 T at 40 mm gap

The final PO package should not continue showing the original 1 T requirement without explanation.

The accepted deviation should be incorporated into:

• Final specification
• Technical proposal
• PO attachment
• Acceptance criteria

Otherwise, the same disagreement can return during FAT.

32. The Deviation List Should Match the Latest Specification Revision

Tender and engineering specifications change.

For example:

• Rev. A: 0.5 T required
• Rev. B: 0.8 T
• Rev. C: 1 T

A supplier responding to Rev. A while the buyer evaluates Rev. C creates obvious risk.

The deviation list should therefore include:

• Project name
• Requirement document number
• Requirement revision
• Supplier proposal revision
• Date

Version control is not bureaucracy.

It prevents teams from comparing different projects without realizing it.

33. Deviations Should Have Evidence References

A useful deviation matrix may include a supporting-document column.

For example:

Requirement	Offered Value	Status	Evidence
Field ≥0.8 T	0.85 T	Comply	Field map TR-012
CSV export	Yes	Comply	Software manual §6.3
4 K operation	10 K minimum	Deviation	Proposal Rev. 3 §4.2

This allows reviewers to verify important claims quickly.

34. Avoid Filling Every Row with “Comply” Without Evidence

A compliance sheet containing 80 rows of:

Comply / Comply / Comply / Comply

looks reassuring.

But if no offered values or document references are included, it may provide little technical information.

For critical requirements, a better response includes:

• Offered value
• Unit
• Test condition
• Evidence

Compliance should be demonstrable.

35. Focus Most Attention on High-Risk Deviations

Not every deviation deserves the same review effort.

A useful classification is:

Critical

Could make the experiment impossible.

Examples:

• Insufficient field
• Wrong field direction
• Temperature range unavailable
• Sample does not fit

Major

Experiment still possible, but important capability changes.

Examples:

• Reduced automation
• Larger footprint
• Slower measurement
• Different cooling infrastructure

Minor

Little impact on experimental objective.

Examples:

• Cosmetic enclosure differences
• Different connector location where installation remains practical

The exact labels can vary.

The principle is to prioritize consequences.

36. Do Not Confuse “Different” with “Worse”

Research equipment is often customized.

A supplier may propose a different engineering solution that meets the same scientific objective.

For example:

Buyer specifies:

• Particular commercial temperature controller model

Supplier proposes:

• Different controller with equivalent range, stability, sensor support, and interface

Whether this is acceptable depends on why the original model was specified.

If the customer needs compatibility with existing software, the deviation may matter.

If the requirement was simply copied from another specification, the alternative may be completely acceptable.

Deviation review creates the right discussion.

37. Sometimes a Deviation Reveals a Bad Requirement

Buyers are not always correct.

A specification may contain:

• Contradictory requirements
• Physically incompatible parameters
• Unnecessary brand-specific details
• Requirements copied from another instrument
• Unrealistic combinations of field, gap, and size

A good supplier should not blindly write “Comply.”

It should identify the conflict.

For example:

Required: 2 T, 100 mm pole gap, passive air cooling, compact benchtop size.

The engineering constraints may be mutually incompatible.

The deviation discussion can therefore improve the final system.

38. What Should Be in a Research Equipment Deviation List?

A practical format can include:

Identification

• Project
• Tender / RFQ number
• Customer specification revision
• Supplier proposal revision

Requirement

• Clause number
• Exact requirement
• Mandatory / preferred if known

Supplier Response

• Offered specification
• Compliance status

Deviation

• Exact difference
• Reason
• Technical impact

Resolution

• Proposed alternative
• Buyer disposition
• Final agreed requirement

For complex projects, adding an evidence-reference column is also useful.

39. A Practical Status System

One simple status system is:

• C — Comply
• E — Exceeds
• D — Deviation
• O — Optional
• N/A — Not Applicable
• CR — Clarification Required

The exact abbreviations are less important than using them consistently.

Avoid ambiguous states such as:

• “Basically”
• “Normally”
• “Should be possible”
• “Approximately comply”

Those expressions belong in engineering discussion, not final compliance status.

40. Questions Buyers Should Ask About Every Deviation

For each important deviation, ask:

What exactly is different?

Require the offered value.

Why is it different?

Technical limitation, standard design, or cost optimization?

Does it affect the experiment?

Not every specification difference does.

Is there an alternative?

Could configuration be changed?

Does the alternative affect price?

A deviation may be solvable at additional cost.

Does it affect delivery time?

Custom redesign may extend lead time.

How will the final requirement be tested?

Acceptance criteria should reflect the agreed result.

These questions turn the deviation list into an engineering tool rather than a paperwork exercise.

41. A Simple Decision Rule: Ask for a Deviation List When Assumptions Become Expensive

Not every USD 500 accessory purchase needs a formal deviation register.

But the need increases rapidly when:

• Equipment is expensive
• Configuration is customized
• Specification is long
• Integration is complex
• Multiple parties are involved
• Tender compliance matters
• Acceptance testing is formal
• Modifying the system later would be expensive

A useful principle is:

The more expensive an assumption would be after PO, the more explicitly it should be resolved before PO.

42. How Cryomagtech Can Approach Technical Deviations

For customized magnetic and materials-characterization projects, Cryomagtech can organize technical discussions around individual requirements rather than relying only on generic product descriptions.

This approach can be used for:

• Electromagnet systems
• Helmholtz coil systems
• VSM
• MOKE
• Hall effect measurement systems
• Cryogenic measurement systems
• Integrated magnet + temperature + optical platforms

A technical review may identify:

• Fully compliant parameters
• Configuration-dependent specifications
• Required clarification
• Technical deviations
• Optional functions
• Alternative configurations

👉 Product link placeholder: Cryomagtech Magnet & Field Systems and Magnetic Measurement Solutions

For formal tenders or customized systems, supplying the complete technical specification before final quotation allows the configuration to be reviewed clause by clause rather than relying on assumptions.

43. Key Takeaways

A deviation list in research equipment procurement is not merely a tender formality.

It is a practical tool for making technical differences visible before they become contractual disputes.

Ask for one when:

• The system is customized
• The technical specification is long
• The project involves a formal tender
• Multiple suppliers are being compared
• Existing equipment must be integrated
• Acceptance depends on specific parameters
• A distributor is translating customer requirements to a manufacturer

A useful deviation process should distinguish:

• Compliance
• Better-than-required performance
• Deviations
• Clarifications
• Options
• Exclusions
• Alternatives

And every important deviation should eventually be:

Accepted, rejected, modified, or incorporated into the final specification.

The most important principle is simple:

A declared deviation can be evaluated.

An undisclosed deviation becomes a surprise.

In research equipment procurement, surprises discovered before the PO are engineering discussions.

Surprises discovered after delivery are disputes.

References

1. ISO/IEC/IEEE 29148:2018 — Requirements Engineering

ISO/IEC/IEEE 29148 provides a formal framework for defining, analyzing, communicating, documenting, verifying, and managing requirements between acquirers and suppliers. The current 2018 edition was reviewed and confirmed by ISO in 2024, making it a useful reference for the principle that important system requirements should be clear and manageable rather than left to assumption.

Check source: ISO/IEC/IEEE 29148:2018 — Requirements Engineering

2. Central University of Karnataka — Scientific Equipment Tender Compliance Requirements

A current university scientific-equipment tender provides a practical procurement example: bidders are required to complete the technical compliance sheet, identify deviations, and provide supporting document references rather than merely directing the buyer to generic brochures or catalogues.

Check source: Central University of Karnataka — Technical Tender Document