Home/Insights/Process
Process Published 2026-06-16 · Updated 2026-10-16 · 4 min read

How to Specify Custom Optics — The Requirements That Actually Matter

Prepare optical requirements for a design discussion: field, wavelength, image quality, interfaces and acceptance criteria.

Illustrative workflow linking requirements, optical design and engineering review
Requirements connect to an optical model, an engineering review and a documented next step. Explanatory architecture, not to scale or a project prescription.
On this page

An optical requirements document should connect the intended task to measurable performance. Missing constraints and unnecessarily tight targets can both make development harder. This guide is a starting checklist for product engineers commissioning optical work.

Start from the scene, not the lens

The strongest optical specifications describe the task: what must be detected, resolved, measured or illuminated, at what distance, under what light. From a well-posed task, a designer can derive focal length, aperture and format honestly. From a pre-guessed lens spec ("50 mm, f/2.8, C-mount"), a designer can only inherit your assumptions — including the wrong ones.

Give the scene: object size and distance range, required feature size, motion, illumination level and spectrum, and the environment (temperature, vibration, washdown, altitude). Every one of those maps to glass.

The ten numbers a designer actually needs

  1. Wavelength band — not "visible," but a band with weights: e.g. 450–650 nm, peak sensitivity 550 nm. Every glass choice hangs on this.
  2. Field of view / object size — with the tolerance on it. State which variation the application can accept; flexibility can change the available design options.
  3. Resolution at the object — the feature you must resolve, in millimeters, and the contrast at which you must resolve it. This converts to an MTF requirement, which is what a designer can actually optimize.
  4. Sensor — model or at least format, pixel pitch and cover-glass details. Optics and sensor are one system; specifying them separately is how Nyquist mismatches are born.
  5. Aperture / light budget — either a radiometric requirement (SNR at scene illuminance) or an f-number with the reasoning attached.
  6. Working distance and envelope — including the volume the lens may occupy and every keep-out. Check track length alongside image quality early in the design.
  7. Depth of field — the object depth that must stay usable, and what "usable" means for your task.
  8. Distortion tolerance — with a statement of whether software correction is acceptable. Allowing correction may simplify the optical design, depending on sampling and image-quality requirements.
  9. Environment — operating and storage temperature, shock and vibration, sealing. Athermalization is a design-in decision, not a retrofit.
  10. Volume and target cost — 5 prototypes and 50k/year units yield different designs, different glass, different tolerancing philosophies. Say which product you are building.

What to leave open — on purpose

A specification's power comes as much from its silences. Unless they are genuinely constrained, leave open: the number of elements, glass types, aspheric usage, and the internal architecture. Locking these early converts your requirements document into a worse version of the designer's job and removes the degrees of freedom that make hard specs achievable.

Flag, rather than fix, anything you suspect matters: "boresight stability probably matters — we don't know how much yet" is a professional and useful sentence.

The traps that cause requirement churn

  • Adjectives instead of numbers. "Sharp," "compact" and "robust" cannot be optimized. Convert each to a measurable with a test method, or delete it.
  • Copy-pasted heroics. Requirements inherited from another program ("λ/10 surfaces," "0.1% distortion") multiply cost silently. Every tight number should be traceable to a task need.
  • The missing tolerance on the requirement. Every value needs a tolerance or a min/max direction. "EFL = 35 mm" is incomplete; "EFL = 35 mm ± 2%, shorter preferred" is actionable.
  • Interface amnesia. Mounting geometry, flange distance, filter placement, cover glass, connector keep-outs — interface surprises at CDR are self-inflicted.
  • Specifying the prototype, meaning the product. If the real goal is a manufacturable volume product, say so on page one; the design path diverges immediately.

What a good response looks like

When a specification like this reaches a competent optics partner, the response should not be a quote — it should be a requirements review: a table restating each requirement, its derived optical consequence, the two or three that dominate cost or risk, and any conflicts made explicit with options. Ask which assumptions the proposal relies on and how unresolved requirements will be handled.

A scoped requirements review can be a useful first engagement. Its duration and outputs depend on the information available and the questions to resolve.


Working on a similar optical question? Discuss your project with us. We can agree the scope, inputs and next steps together.