Engineering Change Orders (ECO)

Overview

ECOs fix functional or timing issues late in the flow without restarting the entire design. They are common in modern tapeouts.

Metal-only ECOs are faster and cheaper because they change only interconnect layers.

Typical ECO Triggers

Functional bugs discovered after signoff.

Timing violations caused by routing or late constraints.

Power or signal integrity issues that need targeted fixes.

Best Practices

Sprinkle spare cells throughout the layout.

Keep ECO changes localized to reduce risk.

Re-run critical signoff checks after ECO insertion.

Engineering Change Orders (ECO): It is often necessary to fix functional bugs or timing violations late in the design cycle after the layout is complete. To avoid the massive cost and delay of redoing the entire physical design, an ECO process is used. Designers pre-populate the layout with spare cells (unused logic gates). An ECO can then be implemented by changing only the metal interconnect layers to wire these spare cells into the circuit to implement the required fix. This "metal-only" ECO is much faster and cheaper than a full mask set change.

Engineering Change Orders (ECO) in the Physical Design Flow

Engineering Change Orders (ECO) is not an isolated step in backend implementation. ECO work is where many projects recover schedule risk, because late timing or functional changes must be implemented with minimal disturbance to an already optimized layout. In a practical ASIC flow, engineers revisit this topic at least twice: once to prevent problems early, and again after optimization when the design context changes because of timing fixes, buffering, or routing decisions.

When using this page for learning or interview preparation, separate the topic into inputs, tool actions, and outputs. Inputs define what data must be clean before you start. Tool actions describe what the engine is optimizing. Outputs show whether the run is actually improving design quality. The most useful reviews combine those three views instead of memorizing a short definition.

Practical Checklist

Use this quick checklist while studying or debugging engineering change orders (eco). It helps turn theory into repeatable engineering practice and also improves project documentation quality.

Classify whether the ECO is functional, setup, hold, power, or DRC driven
Prefer minimal changes that protect routing stability and signoff convergence
Verify impacted modes and corners instead of checking only the original failing path
Document inserted cells or net re-routes for easier review and rollback
Run focused verification after each ECO batch before the final full signoff

Track the result of each change with measurable data instead of intuition alone. Track the number of fixes, affected paths, area impact, and correlation between pre-ECO and post-ECO signoff reports. Keeping a small log of assumptions, changes, and outcomes will make this topic easier to revise later and easier to explain in interviews or design reviews.

Engineering Change Orders