HomePhysical DesignDay 14 — Sign-off & Tape-out

Sign-off & Tape-out

The final milestone: complete sign-off checklist, GDSII foundry package, PDK version locking, tape-out review meetings, common pitfalls, and what happens after the data hits the foundry.

By EcrioniX Engineering Team · Published June 14, 2026 · ~4,500 words · 14 min read

1. What is Tape-out?

Tape-out is the moment when the complete chip layout data is delivered to the foundry for manufacturing. The name originated from the era when final design data was literally written to magnetic tape. Today it's a digital delivery of a GDSII file — but the stakes are exactly the same.

The Highest-Stakes Deadline in Engineering

A tape-out is irreversible. Once the foundry begins exposing masks ($1M+) and running wafers ($500K/lot), errors are enormously expensive to fix. A missed DRC violation or timing bug that made it to silicon requires a full respin — costing millions and adding 6 months. Every item on the sign-off checklist exists because someone, somewhere, once shipped a chip with that bug.

2. Sign-off Verification Pipeline

Complete Sign-off Verification Flow
Physical Verification
DRC — Zero foundry design rule violations
LVS — Layout matches final netlist
ERC — No floating nodes, no bus fights
Antenna — All violations resolved
DFM — Fill inserted, redundant vias added
Electrical Sign-off
STA — All MCMM corners, post-PEX timing
Power — IR drop, EM, power budget met
Signal Integrity — Crosstalk, noise margin
Formal — Layout netlist ≡ RTL (equivalence)
CDC — All clock domain crossings verified

3. The Tape-out Package

The tape-out deliverable is not just a GDSII file. The foundry requires a complete package to begin manufacturing:

DeliverableFormatPurpose
Layout databaseGDSII / OASISPhysical geometry for all mask layers
Netlist (sign-off)Verilog / SPICEElectrical connectivity reference for LVS
Sign-off STA reportPDF / HTMLProves all timing constraints met
DRC clean reportCalibre reportZero violations, foundry-certified tool
LVS clean reportCalibre nmLVSLayout matches netlist
Layer map fileASCII mapMaps design layers to foundry GDS layers
Fill GDS mergeGDSIICombines design + standard cell GDS + fill
Test structure GDSGDSIIProcess monitor structures in scribe lane
PDK version recordText fileExact PDK version used for sign-off
Design rule waiver listText + justificationAny DRC waived violations with written justification

4. PDK Version Locking

The PDK (Process Design Kit) version must be locked before sign-off begins and must not change. Foundries periodically update PDKs with corrected models, new DRC rules, or revised standard cells. Using a different PDK version than what was used during implementation can:

PDK Version Tracking (production practice): Design start: Lock to PDK v1.5.2 Document in design_spec.txt: FOUNDRY: TSMC PROCESS: N5 PDK_VERSION: v1.5.2 PDK_LOCK_DATE: 2026-03-15 SIGN_OFF_TOOLS: DRC: Calibre 2023.1.7 + TSMC_N5_DRC_v1.5.2.svrf LVS: Calibre nmLVS 2023.1.7 + TSMC_N5_LVS_v1.5.2.svrf STA: PrimeTime 2023.12 + TSMC N5 TLU+ files v1.5.2 PEX: StarRC 2023.12 + tech_file v1.5.2 Never upgrade PDK after sign-off freeze without: 1. Full re-run of DRC + LVS on complete chip 2. Spot-check of timing on 3 representative corners 3. Written sign-off from PD lead + DV lead + Program manager

5. Tape-out Review Meeting

The tape-out review (TOR) meeting is the final gate before data delivery. All disciplines sign off in the same meeting — one person objecting can stop a tape-out.

TOR Meeting Agenda (Typical 4-hour meeting)
0:00–0:30
Physical Verification Summary — DRC/LVS sign-off status, waiver list reviewed
0:30–1:00
Timing Sign-off — Worst slack per corner, clock summary, critical path review
1:00–1:30
Power/IR/EM — Static/dynamic IR drop, EM violations, power budget
1:30–2:00
DV Status — Simulation coverage, formal verification, CDC status
2:00–2:30
Known Issues / Waivers — Every open item reviewed with risk assessment
2:30–3:30
Q&A / Escalations — Any team member can raise blocking concerns
3:30–4:00
Go/No-Go Decision — All stakeholders sign tape-out approval form

6. Common Tape-out Pitfalls

PitfallRoot CausePrevention
DRC violation in PDK cellWrong cell GDS version mergedLock PDK version; verify cell GDS matches tech.lef
LVS shorts after fillMetal fill incorrectly touching signal netFill exclusion zones; LVS re-run after fill insertion
Timing fails post-PEXRC parasitics higher than estimatedAlways sign-off with PEX-extracted parasitics, not estimates
Missing test structuresProcess monitor cells not added to scribe laneFoundry checklist includes test structure requirement
Wrong PDK corner usedFast corner used for setup; should be slowDocument MCMM corner set; tooling enforces correct corners
GDSII layer map errorDesign layer 25 mapped to wrong foundry layerDouble-check layer map against foundry spec; run test layout

7. After Tape-out — The Manufacturing Timeline

From Tape-out to First Silicon (TSMC N5, typical)
Week 0
Tape-out data delivered to TSMC
Week 1–2
Foundry data prep, mask tape-out (OPC, mask write)
Week 3–4
Mask fabrication (e-beam write, inspect, qualify)
Week 5–14
Wafer processing (~80 mask steps: oxide, implant, metal, polish)
Week 15–16
Wafer electrical test (probe, speed sort, yield measurement)
Week 17–20
Die packaging, final test, first silicon delivery to design team

Final Tape-out Checklist (Master List)

Next — Day 15: Post-silicon validation — first silicon bring-up, ATE testing, scan chains, speed binning, yield analysis, and silicon debug strategies.

← Previous
Day 13: EDA Tools
Next →
Day 15: Post-Silicon Validation